Alison Crawford
Your enterprise systems know exactly what went wrong. They just can't do anything about it.
Every supply chain runs on a stack built to record the business and plan the business. ERP, WMS, TMS, and OMS preserve what happened. Planning systems determine what should happen under expected conditions. Together they give you a record of the past and a plan for the future.
What they were never built to do is execute when reality changes.
When an OTIF penalty lands, the system of record logs it. When a supplier moves a ship date, the system captures it. But interpreting the event, coordinating the response, updating systems, and carrying the decision through to done still falls to people working outside those systems, in an inbox, a portal, a PDF, a spreadsheet, a chat thread.
That space between what the business knows, what it plans, and what it actually executes has a name: the execution gap.
What is the execution gap?
Roughly 40 to 60 percent of supply chain execution happens outside the system of record: the carrier email, the chargeback notice buried in a retailer portal, the supplier changing a commitment, the exception that never fits a structured field.
Systems of record were built for structured transactions. Planning systems were built to optimize expected outcomes. Neither can interpret an unstructured signal or coordinate work as conditions change. They can't act on information they can't understand.
Take something as ordinary as a supplier scorecard. Most teams assume the ERP should produce one. But the signals that actually determine supplier performance, including missed SLAs, delayed confirmations, repeated promise-date changes, and the conversations around every disruption, live outside the ERP. The data exists; it just never becomes operational knowledge inside the systems responsible for running the business.
This is where revenue quietly disappears. Not through one catastrophic failure, but through thousands of execution tasks handled late, handled manually, or missed altogether. Across an enterprise, that leak runs to about 2 percent of revenue, roughly $20 million a year for a billion-dollar company, bleeding out through missed dispute windows and chargebacks, through the expediting and overstocking that manual work invites, and through skilled people spending their days on data entry. The strategy, the forecast, the inventory plan can all be right. The failure happens in execution, because recording and planning are not the same as making it happen.
What layer is missing from enterprise software?
For four decades, enterprise software has done two jobs: record the business and plan the business. Systems of record capture transactions and preserve operational truth. Planning systems model demand and recommend how to respond under expected conditions.
Between them they answer two questions, what happened? and what should happen?, and leave a third unanswered: how does the work actually get done?
Deciding, coordinating, communicating, and executing have never had a system of their own. That work stays scattered across inboxes, portals, spreadsheets, and the heads of experienced operators.
A system of action is the missing layer, the category Emerix was built for: the system of action for supply chain execution. It works alongside your existing systems to understand operational signals, evaluate them in context, apply your business rules, and execute governed work across the systems you already run. It doesn't replace the ERP, WMS, TMS, or planning systems; those remain the trusted systems for recording and planning. It connects them to execution.
Systems of record preserve what happened. Planning systems determine what should happen. Systems of action execute what happens next.
What a system of action looks like in practice
A supplier emails to move a delivery date.
Today, someone reads the email and updates the ERP. To the system of record, the task is done: the new date is captured. To the business, execution has only begun. Days later a planner finds inventory at risk, customer commitments already affected, transportation plans that need to change, alternate supply to source, a delay to communicate. One email becomes a chain reaction, because the information moved but the work didn't.
In a system of action, that same email starts an autonomous execution workflow. The delay is recognized on arrival, its downstream impact is evaluated, and a response is determined from your business rules and priorities. A planner reviews the recommendation. The ERP is updated, the supplier gets a reply, affected orders are evaluated, downstream workflows begin. The operator spends less time moving information between systems and more time applying judgment where it matters.
Why this matters now
The supplier email is one of thousands of moments like it every day: delayed shipments, chargeback notices, PO confirmations, order changes, quality issues, transportation disruptions. Each one needs someone to gather the information, interpret it, decide, and execute across multiple systems.
For decades, organizations accepted this as unavoidable: software kept the records, people did the work. That assumption is changing. The next generation of enterprise software won't be defined by better dashboards or better predictions. It will be defined by software that participates in execution while staying governed by the business, its rules, and its people.
Systems of record and planning systems remain foundational. They should. But foundations don't execute work.
That is the shift from systems of record to systems of action, the shift Emerix was built to make.
Alison Crawford is Director of Product Marketing at Emerix, where she builds the story, category, and go-to-market motion for an AI-native platform reimagining supply chain execution. With two decades in supply chain software, she's known for building marketing teams and programs that help sophisticated products win in competitive markets. Before Emerix, she held product marketing leadership roles at companies including RELEX Solutions, Aera Technology, o9, and Kinaxis.