We're moving to a new ERP. What happens to our freight process during go-live?

AI logistics agent vs. traditional TMS guideNov 17, 202619 min read

Short answer

Make your own freight plan for the go-live, because the ERP plan rarely covers open loads. List every open load and decide which system closes it. Check the order fields freight needs, like addresses, dock hours and weights. Test a few real orders before cutover. Keep a manual path for orders in the first weeks. Wilson, by Cartage, an AI logistics agent, can take those orders by email or file while the new connection settles.

Book 15 minutes with the team →

What happens to freight when a company moves to a new ERP?

It is the Thursday before go-live weekend. The ERP team has frozen new orders in the old system at noon. The logistics coordinator has 41 open loads. Nine picked up yesterday and are in transit. Twelve are booked for Monday and Tuesday pickups. Eight are delivered but have no POD yet. Seven carrier invoices sit in the inbox. Five orders arrived this morning and are not in either system. Nobody on the project plan owns any of this.

During an ERP go-live, freight keeps moving only if logistics plans its own cutover: list every open load, decide which system closes each one out, check the fields freight depends on, test a few real loads and run a clear manual path until the new connection is proven. The trucks do not stop for the project. Carriers still pick up on Monday. Customers still expect deliveries. Invoices still arrive.

Most ERP projects plan around finance, inventory, purchasing and sales. Freight shows up as a field or two on the sales order: a ship-via code, a freight terms value, maybe a carrier name. The work that happens after the order is released lives in email, phone calls, carrier websites and spreadsheets. That work is easy to forget on a project plan, and it is the first thing customers notice when it breaks.

Why freight is at risk during go-live

Freight sits at the edge of the ERP. It starts from an order the ERP creates and ends with an invoice the ERP has to pay. In between, it depends on people and systems outside the ERP: carriers, customers, warehouses and docks. A go-live changes the start and the end at the same time. Order numbers change. Customer and address records are moved. Payment terms and vendor records for carriers are loaded again. If any of those links break, a load can be picked up with nobody able to match it to an order, or an invoice can arrive with nobody able to pay it.

There is also a timing problem. Most go-lives happen over a weekend or at month end. Freight does not have a quiet weekend. Loads that ship Friday are in transit Saturday and deliver Monday. Their PODs and invoices arrive in the new system's first week, but they were booked from the old one.

What logistics should own

Logistics should own three things in the project:

  • The open load list. Every load that is booked, in transit, delivered without a POD or delivered without a paid invoice on the freeze date.
  • The freight fields. Every piece of order data that a quote request, a booking, a BOL or an invoice check depends on.
  • The fallback path. How orders reach the people who book freight if the new connection is late or wrong in the first weeks.

None of this is hard. It just has to be written down before the freeze, not discovered on Monday morning.

Let's review your ERP go-live plan and the freight fields it touches. 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.15 minutes with the team behind Wilson. No prep needed.

Book 15 minutes →

How do you plan freight around the ERP go-live?

Plan freight in five stages: before the freeze, freeze day, cutover weekend, the first week and the first month. Each stage has a short list of jobs and one person who owns them.

Stage 1: Four to six weeks before the freeze

This is when logistics gets its fields and examples into the project. Do these things:

  • Write the list of freight fields the new ERP must carry (see the table in the next section).
  • Give the ERP team five to ten real orders that cover your hardest cases.
  • Ask how the new ERP will send orders out and take updates back: a connection, a scheduled file or a manual export.
  • Ask whether order numbers will change and how the old number will be kept for reference.
  • Tell carriers who receive orders or tenders from your system that something may change, and give them a contact.
  • Agree what happens to carrier vendor records and payment terms in the new ERP.

Stage 2: The week before the freeze

Now build the open load list. For each load, record:

  • The old order number and, if known, the new one.
  • The carrier, PRO or load number and pickup date.
  • The status: booked, in transit, delivered, POD received, invoiced, paid.
  • The system that will close it out: old or new.
  • The owner on the logistics team.

Try to book every load that will ship in the freeze window before the freeze starts. A booking made before the freeze has all its data in one place. A booking made during the freeze often has data in two.

Stage 3: Freeze day and cutover weekend

During the freeze, new orders may not be entered in either system. Decide how they will be captured. Common choices:

  • The sales or customer service team keeps a list of orders that arrive during the freeze.
  • Customers' emails are kept in one shared folder.
  • Urgent orders that must ship are booked by hand, with the booking details kept on a separate sheet for entry later.

Keep the weekend simple. Track the loads in transit. Answer carrier and customer questions. Do not try to re-enter open loads into the new ERP while it is still being checked.

Stage 4: The first week after go-live

The first week is when freight problems show up. Watch these things every day:

  • Did every new order reach the people who book freight?
  • Do ship-to addresses, dock hours and contact names match the old records?
  • Do BOLs and pallet labels show the right order numbers and references?
  • Are carrier invoices matching to the right loads and orders?
  • Are updates going back to the ERP, and are they going to the right order?

Hold a short daily check with the ERP team. Bring the specific orders that went wrong, not general complaints.

Stage 5: The first month

By the end of the first month, the open load list from the freeze should be closed. Every load should have a POD. Every carrier invoice should be matched and paid or held for a reason. Then you can retire the manual path and rely on the new connection.

Which freight fields and steps does the new ERP need to get right?

The new ERP needs to carry every field that a quote, a booking, a BOL and an invoice check depend on. If one is missing or moved, the order still looks fine in the ERP, but the freight work fails later.

The order fields freight depends on

Start with the order. Freight needs more than the customer name and the line items.

Field Why freight needs it What breaks if it is wrong
Ship-from location Picks the dock, hours and pickup contact Carrier goes to the wrong plant
Ship-to address Destination for quotes, BOL and delivery Wrong rate, wrong delivery, possible re-delivery charge
Ship-to dock hours and appointment rule Sets delivery window and appointment needs Missed appointment, refused delivery
Requested ship and delivery dates Sets pickup and delivery targets Late order or rushed premium freight
Weight, pallet count and dimensions Needed for LTL quotes and the BOL Reweigh and reclass charges
Freight class or commodity Needed for LTL rating Wrong quote, reclass charge
Freight terms (prepaid, collect, third party) Decides who books and who pays Load booked and paid by the wrong party
Customer PO and reference numbers Needed on BOL and for the customer's receiving Delivery refused or delayed
Special services Liftgate, inside delivery, temperature, appointment Extra charges or a failed delivery
Carrier or ship-via code Shows required or preferred carrier Wrong carrier booked

Check each field in the new ERP with a real order. A field that exists is not enough. It must hold the same values, in the same format, as before.

Addresses are the most common failure

During data moves, customer addresses are often cleaned, merged or split. A customer with three distribution centers may become one record with three ship-to codes. A dock note that lived in a comment field may not come across at all. Ask for a list of ship-to addresses before and after, and compare them for your top customers. If the receiving hours or appointment notes are lost, put them back before the first order ships.

Freight terms decide who does the work

Freight terms are easy to miss. If prepaid and collect shipments are coded differently in the new ERP, the team may book loads the customer was supposed to book, or skip loads it was supposed to book. Check that every freight terms value maps to the right action. If your team uses third-party billing for some customers, test one of those orders too.

Order numbers and references

Carriers, customers and invoices all use order and reference numbers. When the ERP changes the numbering, three things can go wrong:

  • A carrier invoice arrives with the old number and nobody can match it.
  • A customer's receiving team looks for a PO on the BOL and finds a new internal number instead.
  • An update from tracking goes back to the wrong order, or to no order at all.

Keep a cross-reference of old and new numbers for every open load and every order in the first month. Put the customer's PO on every BOL, whatever the internal number is.

How updates return to the ERP

Before go-live, decide which freight updates the new ERP needs: shipped date, carrier, PRO, delivered date, POD, freight cost. Some companies want all of them. Some only want the shipped date and freight cost. Write down what goes back, where it goes and who checks it in the first week. The guide on shipment updates back into the ERP covers the choices in more detail.

How carrier invoices find their way to payment

Carrier invoices are paid through accounts payable, which usually means the new ERP. Check that every approved carrier exists as a vendor in the new system, with the right remit-to details. A carrier that is missing from the vendor list can hold up payment for weeks, and carriers notice. Treat any change in remit-to or bank details during the move with care: confirm it with the carrier through a known contact before anyone pays.

What goes wrong with freight during an ERP go-live?

Most freight problems during a go-live come from gaps between the two systems, not from the new ERP itself. The fixes are simple when someone owns them.

Mistake 1: Nobody owns open loads

Loads booked from the old system and delivered after go-live belong to neither project. The POD arrives. The invoice arrives. Nobody knows where to file them. Fix: the open load list, with one owner per load and a closing date.

Mistake 2: Testing only clean orders

Test orders created by the project team are usually clean. Real orders have two ship-to addresses, missing weights and special notes. Fix: test with real orders from the last month, including the hard ones.

Mistake 3: Losing dock hours and appointment notes

Address records move, but notes in free-text fields often do not. The first delivery to a customer DC that only takes appointments in the morning arrives in the afternoon and is refused. Fix: compare ship-to records for your main customers before and after.

Mistake 4: Re-keying open loads into the new ERP during cutover

Re-entering loads during the weekend creates duplicates and typing mistakes. Fix: close open loads where they started, unless the project has a clear plan to move them.

Mistake 5: Assuming the connection works because orders appear

An order can appear in the freight process with a wrong weight, a missing reference or the wrong freight terms. Fix: check the first 20 to 30 orders field by field. The guide on what to do when an ERP order is missing freight data shows how to handle the ones that fail.

Mistake 6: No manual path

When the connection fails on day two, orders stop reaching the team, and nobody notices until a customer calls. Fix: agree a fallback path before go-live, such as a daily export file or an email from customer service, and check every morning that orders arrived.

Mistake 7: Changing too many things at once

Some companies change carriers, routing rules and freight software in the same month as the ERP. When something breaks, nobody knows which change caused it. Fix: keep freight rules and carriers the same through go-live where you can, and change one thing at a time after.

A quick decision table

Situation during go-live What to do
Load booked in the old system, delivers after go-live Close it out where it was booked; keep the old order number on the POD and invoice
New order arrives during the freeze Capture it on the freeze list; book by hand if it must ship
Order in the new ERP missing weight or pallet count Hold it and ask for the missing detail before quoting
Ship-to address in the new ERP differs from the old record Check with the customer before booking
Carrier invoice shows an order number nobody recognizes Use the cross-reference list; do not pay until matched
Carrier is not set up as a vendor in the new ERP Ask accounts payable to add it before the invoice is due
Carrier sends new bank details during the move Confirm through a known contact before any payment
Updates from tracking go to the wrong order Stop the write-back for that field and fix the mapping

What checklist should logistics bring to the ERP project?

Logistics should bring one checklist to the ERP project and get each item signed off before go-live. It covers data, connections, people and the first month.

Item Question to answer Owner
Field list Does the new ERP carry every field in the freight field table? Logistics and ERP lead
Real test orders Have five to ten real orders, including hard ones, passed end to end? Logistics
Ship-to records Do addresses, dock hours and appointment notes match for top customers? Customer service
Freight terms Does each freight terms value map to the right action? Logistics
Order numbers Is there a cross-reference of old and new numbers? ERP lead
Order flow How do orders reach the people who book freight: connection, file or email? ERP lead
Update flow Which updates go back to the ERP, and where? Logistics and ERP lead
Carrier vendors Is every approved carrier set up for payment in the new ERP? Accounts payable
Bank details Are remit-to and bank details confirmed for each carrier? Accounts payable
Open load list Does every open load have an owner and a closing system? Logistics
Freeze plan How are new orders captured and urgent ones shipped during the freeze? Logistics and sales
Fallback path What happens if the connection fails in week one? Logistics
Carrier notice Have carriers been told about changes to order numbers or contacts? Logistics
Daily check Who checks orders, BOLs, invoices and updates each day in week one? Logistics manager
Exit date When is the manual path retired? Logistics manager

How to run the test loads

Pick a few real orders from the last month: one simple truckload, one LTL with a liftgate, one collect shipment, one multi-line order that ships in two parts, one order to a customer with strict receiving hours. Run each from order to quote, booking, BOL, tracking, POD and invoice match, using the new ERP's data. Write down every field that was wrong, missing or in the wrong place. Fix and run again. A clean pass on real orders is worth more than a hundred clean test orders.

What IT will ask

The IT team will want to know what connects to what, which data moves and who has access. The IT checklist for connecting freight software to an ERP lists the usual questions. Answer them early, because a connection that is approved late is often switched on late.

How does Wilson, by Cartage, keep freight moving while a company changes ERPs?

Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays freight for manufacturers and distributors, and it keeps the freight work and its records outside the ERP change, so loads keep moving while the new system settles. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.

Wilson works as a free logistics department, in four parts.

The labor

The labor is the daily freight work. Wilson requests quotes from the company's approved carriers, compares them on total cost, negotiates toward the company's rate targets within approval limits, books with written acceptance and a rate confirmation and schedules the pickup. It tracks each load with the best source available, handles missed pickups and delays, generates BOLs, packing slips and pallet labels and requests and files PODs. During go-live, this work does not wait for the new ERP. Loads booked before the freeze are tracked, closed out and invoiced the same way as any other load.

Orders reach Wilson by email, an ERP connection or CSV/XLSX files. That matters during a go-live. If the new connection is not ready, or fails in the first week, orders can still reach Wilson through a file or an email while the connection is fixed. If an order arrives with a missing weight, an impossible date or another gap, Wilson does not book it. It holds the order as pending, asks for the missing detail and tells the team. It never invents the missing value.

The data

The data is the record. Wilson keeps every order, load, quote, rate, document and contact on record as it works. Every message, confirmation and change is kept in the shipment's change history. Open loads from the old system keep their history, their carrier messages and their documents, so the team can answer a carrier or a customer without opening the old ERP. 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 of shipment updates to the ERP depends on scope, so the team decides which updates go back to the new ERP and when.

The network

The network is the carriers. The shipper's volume counts with every other Wilson customer's for better rates on its lanes. The network includes carriers and brokers, and the company still approves who hauls its freight. A company can also keep its own carriers. Wilson books only carriers the company has approved, so an ERP change does not change who moves the freight.

The payments

The payments close each load. Wilson audits each carrier invoice against the rate confirmation and the POD before money moves, then pays carriers from the Wilson Wallet. Invoices over the rate or outside the rules wait for a person. A change in a carrier's remit-to or bank details is flagged to the team as a possible fraud signal, and Wilson does not act on it alone. That check matters during an ERP move, when vendor records are being loaded again.

Control during the change

Control starts with assisted execution. The company sets approval limits, and routine actions can run automatically within those rules as the workflow is proven. The company also controls scope: it can start with a subset of shipments, a few customers or a few lanes, and exclude loads by rule. Some companies start with Wilson before the ERP go-live, so the freight process is settled before the new system arrives. Others start after, once the new ERP is stable. Either way, timing depends on scope: most teams start on a few lanes and expand from there.

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.

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.15 minutes with the team behind Wilson. No prep needed.

Book 15 minutes →

FAQs

Can Wilson keep freight moving while we change ERPs?

Wilson, by Cartage, an AI logistics agent, keeps quoting, booking, tracking and closing out loads while the ERP changes, because the freight work and its records are kept on Wilson's side. Orders can reach Wilson by email, an ERP connection or CSV/XLSX files, so a file or an email can carry orders while the new connection settles. Write-back to the new ERP depends on scope.

When should logistics join the ERP project?

As early as possible, and at least four to six weeks before the freeze. That gives time to send the freight field list and real test orders. Joining after the data is moved means finding problems with live loads.

What happens to loads booked in the old ERP?

Close them out where they started, unless the project has a clear plan to move them. Keep the old order number on the POD and invoice. Track every one on an open load list with an owner.

Which freight fields break most often in an ERP move?

Ship-to addresses, dock hours and appointment notes, freight terms, weights and pallet counts, and customer reference numbers. They often exist in the new ERP but hold different values or formats. Check them with real orders.

Should we change carriers at the same time as the ERP?

It is better not to. When several things change at once, nobody can tell which change caused a problem. Keep carriers and freight rules the same through go-live where you can.

Does Wilson need the new ERP connection before it can start?

No. Orders can reach Wilson by email or CSV/XLSX files, as well as through an ERP connection. The exact connection depends on the customer's data flow and scope.

What does Wilson do with an order that comes through with missing data?

Wilson does not book it. It holds the order as pending, asks for the missing detail and tells the team. It never invents the missing value.

How do carrier invoices get paid during the change?

Make sure every approved carrier is set up as a vendor in the new ERP before invoices are due. With Wilson, each invoice is audited against the rate confirmation and the POD, and carriers are paid from the Wilson Wallet. Invoices outside the rules wait for a person.

What if a carrier sends new bank details during the move?

Treat it as a warning sign. Confirm the change through a known contact before any payment. Wilson flags a change in remit-to or bank details to the team and does not act on it alone.

How long should the manual path run after go-live?

Until the new connection has passed a few weeks of daily checks and the open load list is closed. For many projects that is about a month. Retire it on a set date, not when people forget about it.

Sources

Let's review your ERP go-live plan and the freight fields it touches. You don't need to prepare anything: Cartage maps the workflow with you on the call.

Add Cartage as a preferred source on Google