The ERP Order Changed. Can Freight Software Keep Up?
Key Takeaways
- An ERP order change becomes freight work when a quote, booking or pickup still depends on the old order.
- Quantity, date, address and cancellation changes each hit freight differently; the shipment's stage decides the rework.
- Wilson, by Cartage, matches the revised order to the shipment and goes back to approved carriers under the company's rules.
- Changes that move cost, carrier, service level or a confirmed pickup go to a person; routine updates inside the rules continue.
- A purchase acceptance test changes four real orders at four stages and checks detection, carrier action, approval, history and write-back.
What should freight software do when an ERP order changes?
It should notice the new version of the order, work out which freight commitment the change breaks (the quote, the booking or the pickup), and either fix that commitment with the carrier or hand the decision to a person. Copying the new fields into a record is not enough.
Orders are rarely final when logistics first sees them. A customer adds two pallets, sales pushes the ship date to Friday, or a purchase order is canceled after the carrier is booked. Each edit is correct in the ERP. The problem is what it leaves behind: a quote priced on the old weight, a truck still dispatched for Thursday, a bill of lading with the old consignee.
Software that only stores the latest order fields can show the correct date and still send the truck on the wrong day. The buyer's question is narrower: when the order moves, does the freight work move with it, and can the team see what changed, what was done and who agreed?
This is the opposite direction from a shipment update flowing back into the ERP, which is covered in The shipment changed. Did the ERP record change with it?. Here the order moves first and freight has to follow.
How a changed order moves through the freight workflow
A changed order should pass through the same eight steps, whatever field changed.
Detect. The revised order or cancellation arrives through the normal order flow. Its reference matches an existing shipment, so it is treated as a new version, not a new order.
Compare. Old and new versions are lined up field by field, and both are kept.
Locate the stage. Not quoted, quoted, booked or picked up: the same change means different work at each stage.
Decide the freight action. Requote, ask the booked carrier to confirm, rebook, cancel, or treat it as an exception.
Contact the carrier. The booked carrier or approved carriers are contacted.
Approve where required. Changes beyond the company's limits go to a person.
Record and notify. The change, carrier response and approval go into the shipment history; the team and configured contacts are told.
Write back where in scope. The revised carrier, pickup date or cancellation returns to the ERP by the agreed method, if the company wants it.
Steps 1 and 2 are where many tools stop. The freight work sits in steps 3 through 7.
What each type of change does to the quote or booking
Quantity, date, address and cancellation changes create different freight work, and the later they arrive the fewer options remain.
Quantity
More units means a different weight and sometimes a different class or equipment. Before booking, quotes are reissued with the new details. After booking, the booked carrier confirms the new rate and space, or approved carriers are requoted if the load outgrew the mode. How pallet counts move rates and class is covered in The pallet count changed. Your freight quote might have too.
Date
A later ship date is the most common change and the easiest to miss. After booking, the carrier must accept the new pickup day or release the truck. An earlier date is harder: the booked carrier may not have a truck, which can mean rebooking with another approved carrier.
Address
A new ship-to changes the lane, the rate, the transit time and sometimes the carrier. A pickup location change can strand a driver at the wrong dock, as described in The pickup address changed after booking. Who closes the loop?. Either way the bill of lading and delivery appointment have to follow.
Cancellation
Before booking, the open quote requests are closed so carriers stop holding capacity. After booking, the carrier has to receive the cancellation and confirm it, and any charge the carrier applies under its terms goes to a person. A partial cancellation is really a quantity change. After pickup, a cancellation is no longer a freight edit; it is an exception that needs a decision about return or reroute.
Which order changes should wait for a person?
A person should decide when the change alters money, the carrier, the service level or a commitment the carrier has already confirmed. Everything else can continue inside the configured rules.
- Continue inside the rules: closing quote requests for an order canceled before booking; reissuing quotes with new details before any carrier is selected; asking the booked carrier to confirm a later pickup date when the rate does not change.
- Ask for approval: a new rate above the approval limit; switching to a different carrier after booking; moving from LTL to a volume or full truckload quote; any cancellation where the carrier says a charge applies.
- Always escalate: any change after pickup; an earlier ship date the booked carrier cannot cover and no approved carrier accepts; conflicting signals, such as the ERP showing a cancellation while the customer's email asks to ship.
Two timing rules help: a freight cutoff (for example, changes after noon the day before pickup go to a named person), and a rule for bursts of edits, so three revisions within an hour produce one carrier contact with the final values, not three.
Ask to see the approval request itself. It should show the old and new order, what the carrier said and the options left, so the approver does not have to open the ERP.
A purchase acceptance test: four orders, four changes
Pick four real orders from recent weeks and change each one at a different stage. Decide the pass condition before the test starts.
| Order | Stage when changed | Change made | Pass condition |
|---|---|---|---|
| A | Quotes requested, no carrier selected | Quantity up by two pallets | Quotes are reissued with the new weight; responses to the old request are not used for booking |
| B | Booked, pickup tomorrow | Ship date moved two days later | Booked carrier is asked to confirm the new date; if it can't, approved carriers are contacted; the team is told before the truck is dispatched |
| C | Booked, pickup confirmed | Ship-to changed to a different state | New lane is requoted or confirmed; the rate change goes to approval if it crosses the limit; documents show the new consignee |
| D | Booked, pickup in two days | Order canceled in the ERP | Carrier receives and confirms the cancellation; any carrier charge is routed to a person; the shipment closes as canceled |
For each order, check six things:
- Detection: the change came from the normal order flow, not a forwarded email.
- Impact: the system named what the change invalidated.
- Carrier action: the right carrier was contacted and answered.
- Approval: requested only where the rules required it, with old and new values side by side.
- History: both order versions, carrier messages and the decision are recorded.
- Write-back: where in scope, the ERP received the revised status or cancellation.
An order passes only if all six boxes are checked. If three of four pass, the failed one points to a specific gap worth discussing.
How Wilson, by Cartage, carries an order change through freight execution
Wilson replaces the TMS for freight execution and connects to the company's ERP, so a changed order arrives where the shipment is already being run.
Wilson works with SAP, NetSuite, Microsoft Dynamics 365, Oracle, Infor, Epicor, Sage, Acumatica, and other ERP environments, with the exact connection depending on the customer’s data flow and scope. A revised order reaches Wilson through the same ERP feed, scheduled file drop, spreadsheet, email or API that sent the original, and Wilson matches it to the existing shipment.
Wilson then requotes or confirms with carriers the company has approved, negotiates against the company's rate targets under configured rules and approval limits, rebooks within those rules or with approval, and sends cancellations to the booked carrier. If no approved carrier accepts the revised load, Wilson escalates. The team is updated in Slack or Microsoft Teams, and configured customer contacts by email or SMS.
Wilson starts with assisted execution. The company sets the approval boundaries, and the scope of execution can expand step by step as the team gains confidence in the workflow. Messages, confirmations and changes are recorded in each shipment's change history. Write-back is optional and scoped: an updated file, a shared table, or an API connection where available.
Bring two versions of one order that changed after booking last month, the original and the revision, and we'll walk through how Wilson would have handled the change.
Sources
- Cartage, Wilson product FAQ and product scope, October 2026: https://cartage.ai