Two people ask about the same shipment and get two answers. How do you keep one record?

Carrier email and shared freight inboxes guideNov 15, 202618 min read

Two people ask about the same shipment and get two answers. How do you keep one record?

Imagine a hypothetical manufacturer of commercial kitchen equipment. A restaurant group is waiting on three walk-in cooler panels for a store opening. At 10:15 on Thursday, the group's project manager calls the sales rep, who opens the ERP and sees "Shipped, Tuesday." The rep says the panels are on the way. At 10:40, the same project manager emails customer service, whose coordinator searches the shared inbox and finds a carrier email from Tuesday afternoon: the truck never showed, pickup moved to Wednesday. The coordinator replies that the panels left a day late and should arrive Monday.

At 11:05 the project manager forwards both answers to the logistics manager with one line: "Which is it?" The logistics manager checks the carrier's website by PRO number, which shows the freight picked up Wednesday and now sits at a terminal with an appointment needed for delivery. A spreadsheet the team keeps for big customers says "delivery Friday," typed in on Monday before any of this happened.

Nobody lied. Each person read a real record. The ERP said "Shipped" because someone marked the order shipped when the bill of lading was printed. The inbox had the carrier's change. The website had the latest scan. The spreadsheet had a plan that was never updated. The customer heard three answers in one morning and trusted none of them.

The way to keep one answer is to keep one shipment record that every update lands on, with the time and source of each change, and to make every other place read from it rather than keep its own version. That means deciding which system owns which facts, routing every carrier message and status to the shipment record, and sending status back to the ERP from there. It doesn't require a new team or a large software project. It does require deciding, for each kind of fact, where it lives.

Why this matters beyond one awkward call

Conflicting answers cost more than embarrassment. The sales rep who promised Friday may have told the restaurant to schedule installers. The customer service coordinator may have told finance the order is in transit, so the invoice went out. If the delivery needs an appointment nobody booked, the freight sits at the terminal and storage charges start. Each wrong answer triggers a decision somewhere else.

There's also the cost of the hunt. When three people each spend fifteen minutes checking a different system, that's most of an hour on one question, and the next customer who calls starts the same hunt again.

Who runs into this

This happens most at manufacturers and distributors that run freight in-house with an in-house logistics function and a separate sales and customer service team. Orders live in the ERP. Carrier conversations happen by email and phone. Tracking lives on each carrier's website. And because none of those is easy to search by customer, someone builds a spreadsheet.

Let's review where your shipment answers live 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 →

Why do the inbox, the ERP, the carrier portal and the spreadsheet disagree?

They disagree because each one is updated by different people, at different moments, for different reasons, and none of them is told when the others change. Understanding what each place is good at, and when it goes stale, is the first step to deciding what the shipment record should own.

What each place knows

Place What it gets right When it goes stale Who usually updates it
ERP sales order The order, items, customer, ship-to, promised date, invoice After the order is marked shipped; carrier changes rarely reach it Customer service or warehouse, often once
Shared inbox Carrier messages: confirmations, delays, reschedules, PODs Immediately for anyone who didn't read that thread Carriers and coordinators, message by message
Carrier website or portal Scans and events once the freight is in the carrier's network Before pickup, and on carriers that scan rarely The carrier
Team spreadsheet The plan and notes the team cares about As soon as nobody has time to type the update Whoever built it
Someone's memory The phone call that changed everything When that person is out One person

The specific ways answers split

Status words mean different things. "Shipped" in the ERP often means the warehouse finished the order. To the customer, it means a truck has left. If the pickup is missed, the ERP still says shipped. For more on that gap, see why an ERP order can say shipped before the carrier has picked it up.

Carrier messages land in one inbox but matter to many people. A reschedule email to the logistics coordinator doesn't reach the sales rep. Even within a shared inbox, a reply in one thread can be missed by someone reading another. See why a load can still look open after a carrier replied in the shared inbox.

Different sources report different times. A carrier's estimate, the customer's promised date and the last scan on the website can all be different, and each is "the ETA" to someone. For choosing between them, see what to do when the carrier status conflicts with the promised delivery date.

Copies drift. Every time someone copies a fact into a spreadsheet or an email to a colleague, a second version exists. When the original changes, the copy doesn't.

Phone calls leave no trace. A dispatcher calls the coordinator to say the driver will be late, and the coordinator updates nobody because the next call is already ringing. That call is now the most current fact about the load, and it exists only in one person's head. When that person is at lunch, the rest of the team is working from an older answer without knowing it.

Partial shipments look like one shipment. When one order ships in two loads, the ERP may show one order and one status, while the carrier sees two PRO numbers moving on different days. A customer asking about "the order" can be told about either load.

The pattern underneath

The problem isn't that any of these tools is bad. It's that nobody decided which one owns the answer to "where is this shipment, and when will it arrive?" Without that decision, each person picks the place they know best, and the customer hears whichever version the person they reached happened to open.

What should one shipment record contain?

A shipment record should hold everything needed to answer any question about the load without opening another system: what was ordered, what was booked, what has happened, what documents exist, who to contact and what changed along the way. A status field alone isn't enough, because the next question is always "since when, and says who?"

The core fields

Part of the record What it holds Why it matters
Order link ERP order number, customer, ship-to, promised date, items Ties the freight to the sale; one shipment may cover part of an order
Booking Carrier, mode, pickup window, delivery window, agreed rate, accessorials The commitment the carrier made
Carrier acceptance The written acceptance and rate confirmation Proves the booking, and what price was agreed
Current status One status from an agreed list, with time and source The answer people actually need
Event history Every status change, message and call note, with time and source Shows how the current status came about
Documents BOL, pallet labels, rate confirmation, POD, invoice Needed for claims, billing and audit
Contacts Carrier dispatcher, driver if known, consignee receiving, customer contact Who to call next
Rules for the delivery Appointment needed, receiving hours, liftgate, special notes Prevents the next missed delivery
Change history Who or what changed which field, when, and the old value Lets anyone see why two people heard different things

One status list everyone uses

Agree on a short list of statuses that mean the same thing to sales, customer service, logistics and finance. For example:

  • Booked: a carrier has accepted in writing.
  • Pickup scheduled: a pickup date and window are confirmed.
  • Picked up: the carrier confirmed the freight is on its truck.
  • In transit: moving, with the latest event and its source.
  • Delivery scheduled: an appointment or delivery date is confirmed with the consignee.
  • Delivered: the carrier or consignee confirmed delivery.
  • POD received: the signed proof of delivery is on file.
  • Exception: something went wrong, with what, when and who is handling it.

"Shipped" isn't on that list on purpose. It means too many different things.

Time and source on every update

The most useful habit is recording, for every status change, when it happened and where the information came from: "Picked up, Wednesday 2:10 pm, carrier email from dispatcher" or "In transit, Thursday 8:05 am, carrier website scan." When two people disagree, the record shows which update is newer and how reliable its source is.

What the kitchen equipment example looks like as one record

Time Event Source
Mon 3:20 pm Booked with carrier, pickup Tue 1 to 4 pm Carrier written acceptance
Tue 9:00 am Order marked shipped in ERP Warehouse (not a carrier event)
Tue 4:45 pm Pickup missed, moved to Wed Carrier email
Wed 2:10 pm Picked up Carrier dispatcher email
Thu 8:05 am At destination terminal, appointment needed Carrier website by PRO
Thu 8:30 am Exception: delivery appointment not booked Logistics

With that record, the sales rep, the coordinator and the logistics manager would all have given the same answer at 10:15: picked up Wednesday, at the terminal, delivery depends on an appointment that still needs booking.

Who should update the record, and when?

Each kind of fact should have one owner, and every update should land on the shipment record at the moment it's received, not when someone has time. If several people can type a status, they'll type different ones. If nobody is responsible for a fact, it won't be updated.

Ownership by fact

Fact Owner Where it's changed Where others read it
Order, items, customer terms ERP ERP ERP, linked from the shipment record
Carrier, rate, pickup window Logistics or whoever books Shipment record Shipment record; status sent to ERP
Carrier events (pickup, transit, delivery) Carrier, captured by logistics Shipment record Shipment record; status sent to ERP
Delivery appointment Logistics, confirmed with consignee Shipment record Shipment record
Promise to the customer Sales or customer service, using the record Customer message, logged on the record Shipment record
POD and invoice Logistics and finance Shipment record, then ERP Both

Direction of flow

The order starts in the ERP and flows to the shipment record. Freight status starts in the shipment record and flows back to the ERP. When those directions are mixed, for example when someone marks an order "Delivered" in the ERP from memory, the two systems drift apart. For which statuses are worth sending back, see which delivery status goes back to the ERP.

Rules that stop the drift

  • Carrier messages go to the record. Every carrier email, text or call note about a load is attached to that load, not left in a personal inbox.
  • No status from memory. Statuses change on evidence: a carrier message, a scan, a signed document.
  • Side spreadsheets are views, not records. If a team wants a list of open loads for a big customer, it should be pulled from the shipment records, not typed in separately.
  • Customers hear what the record says. Anyone answering a customer reads the current status and its source before replying, and logs what was promised.
  • Changes are kept, never overwritten. Correcting a status adds a new entry; the old one stays in the history.

What the change history is for

The change history isn't paperwork for its own sake. When a customer says "your rep told me Friday," the history shows what the record said at that moment and who changed it after. When a carrier invoice includes a redelivery charge, the history shows whether the first attempt was missed because of a missing appointment. It turns "who said what" arguments into a quick look.

How do you get from four places to one record?

Start with a few lanes or one large customer, agree on the status list, route every carrier message for those loads to the shipment record, stop the side spreadsheet for them and test by asking three people the same question. A big-bang switch is rarely needed and usually stalls.

Step 1: Map where answers live today

For one week, each time someone answers a shipment question, note where they looked. Most teams find the same four or five places. That list is the starting point and shows which copies to retire first.

Step 2: Agree on statuses and their meaning

Use the short list above or adapt it, and get sales, customer service, logistics and finance to agree on what each status means. Write down which evidence moves a load from one status to the next.

Step 3: Choose where the shipment record lives

The shipment record can live in a TMS, in freight execution software or in an AI logistics agent that keeps the record as it works. The ERP usually isn't a good home for the full freight record, because it was built around orders and invoices, not carrier events and documents. What matters is that one place holds the whole load and that the ERP stays connected to it.

Step 4: Route carrier communication to the record

This is where most efforts fail. If carrier emails still land only in personal inboxes, the record will always be behind. Use a shared freight address, or software that reads carrier messages and attaches them to the right load.

Step 5: Send status back to the ERP

Decide which statuses the ERP needs, typically picked up, delivered and POD received, and send them from the shipment record. Then customer service and sales can keep working in the ERP and still see the freight answer.

Step 6: Retire the copies

For the lanes in scope, stop updating the side spreadsheet. If people need a list, build it from the records. Copies that nobody updates are worse than no copy.

Step 7: Test with three people

Pick five open loads. Ask a sales rep, a customer service coordinator and the logistics manager to answer "where is it and when will it arrive?" for each. If all three give the same answer, with the same source, the record is working. If not, the gap shows which step needs work. For a related problem in tools that duplicate data entry, see how to avoid entering the same shipment twice in two systems.

Common objections

"Our carriers don't have APIs." Many don't. The record can still be kept from carrier emails, website lookups by PRO number and phone calls, as long as each one is logged on the load.

"Sales won't use another system." They don't have to, if status flows back to the ERP they already use.

"We don't have time to set this up." The test above takes a week of noticing, not a project plan. The setup work depends on how the team chooses to keep the record.

How does Wilson, by Cartage, keep one record per shipment?

Wilson, by Cartage, is an AI logistics agent that works as a company's free logistics department and keeps the shipment record as it does the work, so the answer to "where is my load?" lives in one place and flows back to the ERP. What big shippers build over years, Wilson does from day one. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward. The department has four parts, and the record runs through all of them.

The data

The data is the heart of this article's problem. Wilson keeps every order, load, quote, rate, document and contact on record as it works, connected to the company's ERP. No TMS needed: Wilson replaces the TMS for freight execution and connects to the company's ERP. Every message, confirmation and change is kept in the shipment's change history, and records are searchable and exportable with that history.

Wilson also keeps memories and rules that apply to a shipment, learned from its own work or added by the team, and the team can edit them. Hypothetical examples: "This customer's restaurant sites need a call two hours before delivery," or "The regional distribution center in Columbus only receives from 7 to 11 am." Those notes sit with the load instead of in one coordinator's head.

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. Which statuses are written back to the ERP depends on scope.

The labor

The labor is why the record stays current. Wilson does the work from the first quote to the final POD, including the carrier follow-ups that usually feed the inbox: confirming pickups, asking for updates, chasing PODs. It 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, and email or phone calls when nothing else is current. Each update lands on the load with its time and source. The team doesn't chase carriers.

People reach Wilson by email, Microsoft Teams, Slack, WhatsApp, text or phone. A sales rep can ask "where is the cooler order?" in the channel they already use and get the answer from the same record the logistics manager sees. Wilson reaches carriers by email, API, EDI where supported and phone calls where configured.

The network

The network brings better freight rates on every lane, because the shipper's volume counts with every other Wilson customer's. It includes carriers and brokers, and the company still approves who hauls its freight. Loads moved by network carriers and by the company's own carriers sit in the same kind of record.

The payments

The payments use the record. Wilson audits every freight invoice against the load before money moves, then pays carriers from the Wilson Wallet. If an invoice is over the rate, Wilson flags it and asks the carrier why before paying. Invoices over the rate or outside the rules wait for a person. Because the booking, the events and the POD are on the same record, a redelivery or storage charge can be checked against what actually happened.

How control works

Teams start with assisted execution, where more steps wait for a person's approval. The company owns its carriers, rules, approval limits and contacts, and widens what runs automatically as the workflow is proven. Timing depends on scope: most teams start on a few lanes and expand from there. Wilson covers LTL, FTL, ocean, drayage, parcel and cross-border freight.

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.

FAQs

Where does Wilson keep the answer to "where is my load?"

Wilson, by Cartage, an AI logistics agent, keeps it on the load's record, together with the order, booking, carrier acceptance, documents, contacts and every change with its time and source. The record is connected to the company's ERP, and the team can ask Wilson by email, Teams, Slack, WhatsApp, text or phone.

Why does the ERP say shipped when the carrier hasn't picked up?

Often because the order was marked shipped when the warehouse finished it or the BOL was printed. That's an order event, not a carrier event. Freight status should come from the carrier's confirmation and flow back to the ERP.

Should the ERP be the main shipment record?

The ERP should own the order, customer and invoice. The full freight record, with carrier events, messages and documents, usually lives better in freight software that sends key statuses back to the ERP.

What is the minimum a shipment record should include?

The order link, the booking and carrier acceptance, one current status with time and source, the event history, the documents, contacts and delivery rules, and a change history.

How do we stop people keeping their own spreadsheets?

Give them a list built from the shipment records, and make sure the answer they need is easier to find there. Then stop updating the side copies for the lanes in scope.

What if our carriers don't send electronic updates?

Log every carrier email, website lookup and call on the load with its time and source. Wilson tracks with the best source available, including email and phone calls when nothing else is current.

Can our sales team see shipment status without learning new software?

Yes, if status flows back to the ERP they use, or if they can ask in a channel they already use. With Wilson, ERP write-back depends on scope.

Can we export shipment records if we change tools?

The company owns its records. With Wilson, records are searchable and exportable with their change history.

Do we need a TMS to keep one record?

Not with Wilson. It keeps every order, load, quote, rate, document and contact on record and replaces the TMS for freight execution while connecting to the ERP.

How long does it take to move to one record?

It depends on scope. Most teams start with a few lanes or one large customer and expand from there.

Sources

Let's review where your shipment answers live today. You don't need to prepare anything: Cartage maps the workflow with you on the call.

Add Cartage as a preferred source on Google