How do shipment updates get back into the ERP so sales and finance see them?
How do shipment updates get back into the ERP so sales and finance see them?
It is 11:20 a.m. on a Tuesday. A customer calls the sales rep: "Where is our order? Our receiving team says nothing came yesterday." The rep opens the ERP. The sales order shows "Shipped" with no tracking number, no carrier and no delivery date. The rep emails logistics. Logistics is on a call. Meanwhile, finance is holding an invoice for a different customer because nobody can find the POD, and the freight cost on last week's orders still shows the estimate from the quote, not what the carrier billed.
Shipment updates get back into the ERP when the company decides which updates matter, which ERP field each one goes to, who or what writes it and when. The usual set is status, carrier and tracking or PRO number, expected and actual delivery date, freight cost and the POD. They reach the ERP through a direct connection that writes back, scheduled files, or people keying them in. The method matters less than the rules: one owner per field, clear status meanings and a check that the ERP matches the shipment.
When those rules exist, the sales rep in the example sees "Picked up Monday, delivery expected Wednesday, PRO 553201" and can answer the customer in a minute. Finance sees the POD attached and the final freight cost, and releases the invoice.
Why this is hard in most companies
The ERP owns the order. Freight work happens somewhere else: in email, on carrier websites, in phone calls and sometimes in a separate freight system. The shipment moves through many states, and each one creates information the ERP does not get on its own. If nobody carries it back, the ERP stops at "Shipped" and every question goes to logistics.
The guide on which delivery status should go back to the ERP covers the detailed status design. This article starts from the other side: what sales and finance need to see, and how to get it there.
What sales needs
Sales answers customer questions. It needs:
- The current status in plain words: booked, picked up, delayed, delivered.
- The carrier and the tracking or PRO number.
- The expected delivery date, and the reason if it changed.
- Whether there is a problem the customer should hear about from sales first.
What finance needs
Finance closes invoices and books costs. It needs:
- The actual ship date, to invoice the customer and recognize revenue under the company's rules.
- The POD, when customers will not pay without one.
- The freight cost, first the booked cost and then the final audited cost.
- Any accessorial charges that should be billed to the customer.
Let's review what your ERP shows about a shipment today. You don't need to prepare anything: Cartage maps the workflow with you on the call.
See it on your own loads. Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays for freight with your approved carriers.
Book a demo →How do you set up shipment updates to the ERP, step by step?
List the questions, map each answer to an ERP field, choose how each field is written, set the timing and test with real loads. The work is more about agreement between logistics, sales, finance and IT than about technology.
Step 1: List the questions people ask
Spend a week collecting the questions sales and finance ask logistics. Typical ones:
- Has this order shipped?
- When will it arrive?
- Who is the carrier and what is the tracking number?
- Did it deliver, and do we have the POD?
- What did the freight cost?
- Can we bill the customer for this liftgate charge?
Each question points to a field the ERP should show.
Step 2: Map each answer to a field
For each question, find the ERP field that should hold the answer. Some ERPs have standard fields for carrier, tracking number and ship date on the shipment or delivery record. Others need custom fields. Write the map down, field by field, with the meaning of each value.
| Question | ERP field (example) | Value written | Written when |
|---|---|---|---|
| Has it shipped? | Shipment status | Picked up | Carrier confirms pickup |
| Who is the carrier? | Carrier | Carrier name | Booking confirmed |
| Tracking number? | Tracking or PRO number | Carrier's number | Booking or pickup, when issued |
| When will it arrive? | Expected delivery date | Date | Booking, and again if it changes |
| Did it deliver? | Delivery date | Date and time | Delivery confirmed |
| Do we have the POD? | Attachment or document link | POD file | POD received |
| What did freight cost (booked)? | Freight cost estimate | Rate confirmation total | Booking confirmed |
| What did freight cost (final)? | Freight cost actual | Audited invoice total | Invoice approved |
The field names above are generic. Every ERP and every company's setup is different.
Step 3: Decide who writes each field
Every field needs one writer. If logistics keys the tracking number by hand and a connection also writes it, the ERP may show two values or overwrite a correction. Pick one. Write down which system or role writes each field and whether anyone else may change it.
Step 4: Choose the method
Choose how each update reaches the ERP. The four common methods are covered in the next section. Many companies mix them: a connection for status and tracking, a file for freight cost and manual attachment of PODs for a while.
Step 5: Set the timing
Decide how fast each update needs to arrive. Sales may need pickup and delay updates within an hour or two. Finance may be fine with a daily update of freight cost. Timing drives the method: a daily file cannot answer a customer at 11:20 a.m. about a load that picked up at 9:00 a.m.
Step 6: Test with real loads
Run a sample of real shipments through the setup, including the hard ones: a split order, a delayed load, a canceled load, a carrier change and a corrected invoice. Check what the ERP shows at each step. The guide on testing whether an AI freight agent can write status back to the ERP gives IT a detailed test plan.
A worked example
Consider a hypothetical order for 12 pallets to a distributor. On Monday at 2:00 p.m., the load is booked; the ERP order gets the carrier name, an expected delivery of Thursday and a booked freight cost of $1,260 from the rate confirmation. On Tuesday at 9:15 a.m., the carrier confirms pickup; the ERP shows "Picked up," the PRO number and the actual ship date, and finance can invoice the customer. On Wednesday, the carrier reports a one-day delay; the expected delivery changes to Friday with the reason "weather on route," and the sales rep sees it before the customer calls. On Friday, the freight delivers; the delivery date and a link to the signed POD arrive. Two weeks later, the carrier invoice is audited and approved at $1,335, including a $75 liftgate charge that was on the rate confirmation; the final cost replaces the booked cost. Five updates covered everything sales and finance asked about this order.
What operational detail decides whether ERP updates work?
Status meanings, references, split orders, cost timing and corrections decide whether the ERP tells the truth. Most failures come from these details, not from the connection itself.
The four common methods
| Method | How it works | Speed | Accuracy | Effort |
|---|---|---|---|---|
| Direct connection with write-back | The freight side writes fields into the ERP through an API or similar link | Fast | High, if fields are mapped well | IT setup and upkeep |
| Scheduled files | A file of updates is imported into the ERP on a schedule | Hours to a day | Good, if references match | Some IT setup |
| Structured emails keyed in | Updates arrive by email in a set format; someone enters them | Depends on the person | Prone to typos | Daily staff time |
| Manual entry from many sources | Coordinators update the ERP from carrier emails and websites | Slow | Often incomplete | High staff time |
No method is right for every company. A company with a busy IT team may start with files and move to a direct connection later. What matters is that the method is chosen on purpose and the rules are written down.
Status meanings
"Shipped" can mean the order was picked, the truck was booked, the truck arrived or the freight left the dock. Sales and finance will read it differently. Define each status by the event that triggers it. "Picked up" should mean the carrier has the freight and a signed BOL exists, not that a truck is scheduled.
The same applies to "Delivered." A carrier's delivered status and a signed POD are not always the same thing. The guide on what to do when the carrier POD and the ERP delivery status disagree covers that gap.
References
Updates must land on the right order. That needs a shared reference: the sales order number, the delivery number or the shipment number. Put it on the BOL and the rate confirmation so carriers return it. If the reference is missing or wrong, updates land on the wrong order or nowhere.
Split and combined orders
One order can ship on two trucks. Two orders can ship on one truck. The ERP map must say how each case is handled: two tracking numbers on one order, or one tracking number on two orders. Freight cost must be split across orders by a rule, such as weight or pallet count, if finance wants cost per order.
Freight cost timing
The booked cost is known at booking. The final cost is known when the carrier invoice is audited, sometimes weeks later. If the ERP shows only one number, people will assume it is final. Show both, or label which one the field holds, and replace the booked cost with the final cost once the invoice is approved.
Changes and corrections
A delivery date changes. A carrier is replaced. An invoice is corrected. The ERP should show the latest correct value, and someone should be able to see what it was before. The guide on whether the ERP record changed when the shipment changed looks at this in detail.
Accessorials that should be billed to the customer
Some freight charges belong on the customer's invoice: a liftgate the customer asked for, an inside delivery or a redelivery the customer caused. If those charges never reach the ERP, finance cannot bill them, and the company quietly pays for its customers' requests. Flag billable accessorials when the carrier invoice is audited, and send them to the ERP with the order reference so finance can add them to the customer invoice under the company's terms.
Customer updates are a separate decision
Updating the ERP is not the same as telling the customer. Some companies send customers shipping and delay notices straight from the freight side, by email or text. Others want every customer message to come from sales. Decide this together with the ERP map, so the customer does not get two different messages about the same delay, one from logistics and one from sales.
Who can see what
Sales may not need freight cost for every order. Finance may not need every delay update. ERP roles and screens decide who sees what. Agree on that before turning updates on, so nobody is surprised.
What decision rules and mistakes matter most?
Keep the update set small, give each field one owner, label cost clearly and plan for corrections. These rules prevent most problems.
Decision rules
| Situation | Rule |
|---|---|
| A tracking event that does not change the plan | Keep it in the shipment record; do not send it to the ERP |
| Pickup confirmed | Send status, carrier, tracking number and actual ship date |
| Delivery date changes | Send the new expected date and a short reason |
| Delivery confirmed with POD | Send delivery date and attach or link the POD |
| Carrier invoice approved | Replace booked cost with final cost |
| Carrier replaced after booking | Update carrier and tracking number; keep the old values visible in history |
| Order split across trucks | Send each truck's tracking number to the order, with quantities |
Mistake 1: Sending everything
Every GPS ping in the ERP buries the updates that matter. Send events that change what sales or finance would do.
Mistake 2: Two writers for one field
A coordinator types a tracking number, then a connection overwrites it with a different one. Pick one writer per field.
Mistake 3: Calling the booked cost "actual"
Finance closes the month on estimated freight and is surprised when invoices arrive with accessorials. Label the two values, and replace the estimate when the audited invoice is approved.
Mistake 4: No reference on the paperwork
If the BOL and rate confirmation do not carry the order number, carriers cannot return it, and updates cannot be matched.
Mistake 5: Ignoring split orders
The ERP shows one tracking number on an order that went on two trucks. Sales tells the customer it all delivered. Half of it is still on the road.
Mistake 6: Turning everything on at once
Start with a few lanes or customers, check the ERP every day for two weeks and then expand. Errors in a small set are easy to fix. Errors across every order become a cleanup project.
Mistake 7: Forgetting canceled and replaced loads
A load is canceled and rebooked with another carrier, but the ERP keeps the first carrier's tracking number. Sales gives the customer a number that leads nowhere. Every cancellation and carrier change needs its own update rule, tested before go-live.
What should an ERP shipment-update checklist include?
A short checklist lets logistics, sales, finance and IT agree before any update flows. Review it whenever the ERP or the freight process changes.
| Item | Question to answer | Owner |
|---|---|---|
| Questions | Which questions do sales and finance ask most? | Logistics |
| Fields | Which ERP field holds each answer? | IT and logistics |
| Status meanings | What event triggers each status? | Logistics |
| Writer | Which system or role writes each field? | IT |
| Method | Connection, file, structured email or manual, for each field? | IT |
| Timing | How fast must each update arrive? | Sales and finance |
| Reference | Which order or shipment number do the BOL and rate confirmation carry? | Logistics |
| Split orders | How are two trucks on one order, or two orders on one truck, shown? | Logistics and IT |
| Freight cost | Are booked and final cost labeled and replaced on approval? | Finance |
| POD | Where is the POD attached or linked? | Finance and IT |
| Corrections | Can people see what changed and when? | IT |
| Access | Who can see freight cost and delay details? | Finance and IT |
| Test | Have real loads, including hard cases, been run through? | Logistics and IT |
| Rollout | Which lanes or customers start first? | Logistics |
How to roll it out
Start with status, carrier, tracking number and delivery date for one customer group. Add POD links next, because they free up invoices. Add freight cost once invoices are audited against rate confirmations. Each step should run cleanly for a couple of weeks before the next one starts.
What to do in the meantime
Until updates flow, give sales one place to look for shipment status and one person to ask. A shared view of loads, even outside the ERP, cuts the "where is my order" emails while the connection is built.
How does Wilson, by Cartage, get shipment updates back to the ERP?
Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays freight for manufacturers and distributors, and it connects to the company's ERP so shipment updates have a path back. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.
Wilson works as the company's logistics department, in four parts: the labor, the data, the network and the payments.
The labor
The labor is the work that creates the updates in the first place. Orders reach Wilson by email, an ERP connection or CSV and XLSX files. Wilson requests quotes from the company's approved carriers, books with written acceptance and a rate confirmation, schedules pickups and tracks each load with the best source available: carrier API or EDI, GPS or ELD data where the carrier shares it, the carrier's website by PRO number, or email and phone calls when nothing else is current. It requests and files PODs. When a load is delayed, Wilson contacts the carrier, tells the team and tells the customer if configured.
The data
The data is the record. Wilson keeps every order, load, quote, rate, document and contact on record as it works, connected to the company's ERP. Every message, confirmation and change is kept in the shipment's change history. Wilson replaces the TMS for freight execution and connects to the company's ERP.
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.
Write-back to the ERP depends on scope. Which fields Wilson writes, such as status, tracking number, delivery date, freight cost or a POD link, and how often, is agreed with the customer during setup, based on its ERP and data flow. Where write-back is not in scope, the shipment record still holds every update for the team.
The network
The network is the carrier side. A shipper's volume counts with every other Wilson customer's, which helps get better freight rates on every lane. The network includes carriers and brokers, and the company still approves who hauls its freight.
The payments
The payments produce the final freight cost finance needs. Wilson audits every carrier invoice against the rate confirmation and the POD before money moves, then pays carriers from the Wilson Wallet. An invoice outside the rules is held and flagged for a person. A corrected invoice that replaces the original counts only in its latest version, so the final cost reflects the corrected amount. Payments above the approval limits or outside the rules wait for a person.
Each customer's data is encrypted and lives inside that customer's organization. Customer data is not used to train Wilson.
Control starts with assisted execution. The company sets approval limits, and routine actions can run automatically within those rules as the workflow is proven. Teams reach Wilson by email, Slack, Microsoft Teams, WhatsApp, text or phone.
Pricing
Wilson is free on Wilson's network: the shipper pays the freight rate and nothing on top. When a shipper keeps its own carriers, the fee is 2% to 0.5% of what Wilson pays them, falling with volume. There are no seat fees, no setup cost and no contract. Timing depends on scope: most teams start on a few lanes and expand from there.
FAQs
Can Wilson write shipment updates back to our ERP?
Wilson, by Cartage, an AI logistics agent, connects to the company's ERP, and write-back depends on scope. Which fields it writes, such as status, tracking number, delivery date, freight cost or a POD link, is agreed during setup based on the ERP and the data flow. The full shipment record stays on file either way.
Which shipment updates should go into the ERP?
Status at a few key points, carrier, tracking or PRO number, expected and actual delivery date, freight cost and the POD. Keep tracking pings and carrier messages in the shipment record, not in the ERP.
Should the ERP show booked freight cost or final freight cost?
Both, clearly labeled, or one field that starts with the booked cost and is replaced by the audited final cost once the invoice is approved. Finance should always know which one it is looking at.
How do updates find the right order in the ERP?
Through a shared reference, usually the sales order, delivery or shipment number. Put it on the BOL and the rate confirmation so carriers return it and updates can be matched.
What if one order ships on two trucks?
The ERP should show both tracking numbers and the quantity on each. If finance wants freight cost per order, set a rule for splitting cost, such as by weight or pallet count.
Is a scheduled file good enough, or do we need a direct connection?
It depends on timing. A daily file is fine for freight cost. Sales usually needs pickup and delay updates faster. Many companies start with files and add a connection for the time-sensitive fields.
Which ERPs does Wilson work with?
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.
How do we stop two systems writing different values to the same field?
Name one writer for each field and do not let others change it without a reason recorded. If a coordinator and a connection both write tracking numbers, one of them should stop.
What should sales do until updates reach the ERP?
Give sales one place to see shipment status and one person to ask. That cuts the "where is my order" emails while the ERP updates are set up.
Does Wilson use our shipment data to train its models?
No. Customer data is not used to train Wilson. Each customer's data is encrypted and lives inside that customer's organization.
How should billable accessorials reach the ERP?
Flag them when the carrier invoice is audited and send them with the order reference, so finance can add them to the customer invoice under the company's terms. Otherwise the company pays for liftgates and redeliveries its customers asked for or caused.
Sources
- Cartage, Wilson product FAQ and product scope, October 2026: https://cartage.ai
Let's review what your ERP shows about a shipment today. You don't need to prepare anything: Cartage maps the workflow with you on the call.
