AventX—Built on 40 Years. Designed for What’s Next.

Every generation of AventX has reflected what enterprise document delivery required at the time. The platform has grown continuously, adding delivery channels, expanding ERP depth, and responding to the evolving needs of Oracle EBS and eAM (and other ERP systems) environments across industries.

Continuous innovation requires the right foundation underneath it. Over time, we decided to modernize AventX. Not because the existing platform failed to serve customers, but because a modern foundation allows us to deliver new value faster, more reliably, and to a broader set of customers than before.

Development cycles should have been faster. Upgrades complex enough that teams delayed them. Enhancement requests that deserved a quicker answer than the architecture allowed. Multi-component installs that required specialist knowledge to manage. These were not failures of intent; they were the natural consequence of building on a foundation that had reached the limits of what it could support.

The decision was a natural progression, an investment in the platform’s ability to serve customers better and move faster. It was made because forty years of customer knowledge, ERP expertise, and document delivery depth deserved a foundation capable of putting all of it to work…faster, more reliably, and for a broader set of customers than ever before.

The result is a single, unified application for print and document delivery. Not a collection of components. Not a stack that requires a specialist to install and maintain. One application, deployable on Linux, Windows, or Docker, with a guided install on every platform.

For teams that have managed legacy AventX environments and the operational complexity that came with them, that is a meaningful change in itself. Here is what else it delivers.

The multi-component model is gone, or going away, wherever possible. In some cases, it cannot be avoided. The new AventX is designed to be a single service for managing your output (print and delivery). Upgrades preserve your configuration. The operational burden that used to be part of the installation and maintenance process has been treated as a design problem rather than an acceptable cost of running enterprise software. An IT administrator who has never worked with AventX before can install, configure, and own it without a specialist in the room.

Every document that enters AventX now has a job ID. Every step—received, queued, processing, delivered, failed—is visible in a browser-based interface without touching a log file or accessing the server directly.

Print jobs, email delivery, fax. All of it tracked, auditable, and accessible from any machine.

For a finance or procurement team, the answer to “did that purchase order go out?” is no longer a thirty-minute investigation. For an Oracle eAM maintenance team, print failures surface to IT before a technician discovers them at the start of a shift, wrench time is protected before the first job of the day begins.

Printer health is monitored automatically on a configurable schedule. When a printer fails repeatedly, AventX disables it before jobs pile up. When it recovers, AventX re-enables it. The help desk call that starts with “my document never printed” becomes something IT can get ahead of rather than respond to.

The proprietary database is replaced with modern, open components. Development cycles are faster. When a customer calls with an enhancement request today, the conversation about cost and timeline has a different character than it used to. The work that was previously constrained by architectural debt is, in many cases, simply faster to deliver now.

The new AventX platform is still maturing and has meaningful work ahead, but the ceiling is gone. That changes what is possible, and how quickly it can reach customers.

The new AventX is ERP-agnostic by design. Oracle EBS and eAM are the core; that is where forty years of STR Software’s depth lives and where the platform is most mature today. But the architecture is built to ingest documents from any direction: REST API, directory scan, SMTP listener. The underlying queue does not care which ERP sits behind it, the connector is what bridges the two.

For customers already running AventX with connectors for Oracle Cloud, SAP, JDE, SunGard, or custom ERP environments, this new foundation serves you the same way it serves EBS environments. The visibility, the simplified install, the modern delivery pipeline. Very little of it is EBS-exclusive.

For teams on those platforms who have assumed STR Software was an Oracle EBS-only solution, it is worth a second look.

Oracle Cloud, SAP S4/HANA, JDE, and SunGard are on the roadmap with intent. If document delivery is a friction point in your environment, the conversation is worth having.

If you are running AventX today, the question forming as you read this is a fair one: What does this mean for my environment, and what am I being asked to do?

The answer is straightforward. Your current environment continues to work. The path forward is a conversation. STR Software works with you to understand your environment and your specific requirements, advances the platform to meet them if needed, and supports your transition when it is ready on your terms.

The goal of that conversation is to ensure that the next time you call with a request, we can deliver on it faster than ever before.

STR Software turns 40.

Four decades of solving the document delivery problems that slow ERP teams down, through every generation of enterprise technology, every shift in how organizations operate, every change in what getting a document from point A to point B actually requires.

The new AventX foundation is the most direct expression of that history. Not a departure from it. Everything learned over forty years of customer conversations, ERP integrations, and document delivery challenges is now running on a platform built to put it all to work. More quickly. More visibly. And for more ERP environments than ever before.

If you want to see what is new and talk through what it means for your environment, we would like to have that conversation.

Schedule a call »