Acumatica sales order to accepted load: how freight gets tendered to an approved carrier
Key Takeaways
Updated November 3, 2026
An Acumatica sales order becomes a load accepted by an approved carrier in four moves: the order’s freight details leave Acumatica, approved carriers quote the same shipment, the company’s rules select one, and that carrier accepts the tender in writing with a pickup window. Acumatica holds the order; the freight work between the order and the accepted load is execution. Wilson, by Cartage, is an AI logistics coordinator that does that work and works with Acumatica among other ERP environments, with the exact connection depending on the customer’s data flow and scope.
- An imported order is not a booked load. A load is accepted only when an approved carrier confirms it in writing, with a rate confirmation and a pickup window.
- The order needs freight details carriers can price: pallets, weight, dimensions, freight class for LTL, pickup and delivery addresses, dates, and services such as a liftgate or appointment.
- Orders can leave Acumatica as a scheduled file, an email, or through an API connection. Many companies start with a daily file and add a deeper connection later.
- Wilson requests quotes from the company’s approved carriers, negotiates against rate targets within approval limits, tenders, and follows up until the carrier accepts or declines.
- What goes back to Acumatica, such as carrier, PRO number, or ship date, depends on scope. No integration project is required to start.
- Test the workflow with your own Acumatica orders, including one with missing freight details and one tender the carrier does not answer.
How does an Acumatica sales order become a load accepted by an approved carrier?
An Acumatica sales order becomes an accepted load when its freight details reach approved carriers, a carrier is selected under the company’s rules, and that carrier accepts the tender in writing. An AI logistics coordinator does the steps in between. The table shows each step, who owns it, and what proves it finished.
| Step | What happens | Owner | Proof it finished |
|---|---|---|---|
| 1. Order ready to ship | The sales order is released and the freight is planned to ship | Order owner in Acumatica | Order status and requested ship date |
| 2. Freight details out | Pallets, weight, dimensions, class, addresses, dates, and services leave Acumatica | Agreed export or connection | A complete shipment request |
| 3. Quotes | Approved carriers price the same shipment | Wilson | Comparable quotes with expiry |
| 4. Selection | Contract carrier first, or best quote within the rate target and limits | Wilson, under the company’s rules | A selected carrier, or an approval request |
| 5. Tender | The load is offered to the selected carrier | Wilson | A sent tender |
| 6. Acceptance | The carrier accepts in writing and confirms a pickup window | Carrier, followed up by Wilson | Written acceptance, rate confirmation, confirmed window |
Hypothetical example: a manufacturer of industrial pumps runs Acumatica for orders, inventory, and accounting. Its two coordinators copy order details from Acumatica into quote emails, wait for carrier replies, and type the chosen carrier and PRO number back into the order. About a fifth of their day goes to loads where the carrier has not answered. The company wants the time between “order released” and “carrier accepted” to stop depending on someone’s inbox.
Why Acumatica alone does not tender the load
Acumatica is an ERP: it manages sales orders, shipments, inventory, and financials. Acumatica documents a contract-based REST API that lets external systems create and update shipments for sales orders, including tracking numbers and freight cost. That makes Acumatica a good source and destination for freight data. The freight coordination itself, such as asking carriers, following up, comparing, negotiating, and getting acceptance, happens with outside carriers and is usually done by people or by execution software.
Where Wilson fits
Wilson replaces the TMS for freight execution and connects to the company’s ERP. It 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 company running Acumatica does not need to implement a TMS first.
Who owns each handoff
Three teams touch the load before a carrier accepts it. Sales or customer service owns the order and its delivery promise. The warehouse owns readiness: whether the freight is picked, packed, and palletized for the ship date. Logistics owns the freight: which carrier, at what rate, and when. When those handoffs are informal, the order sits in Acumatica marked ready while the warehouse is still building pallets, or logistics books a truck for freight that is not there. Writing down who confirms what, and where, is the first step of any Acumatica-to-carrier workflow.
What changes with an AI logistics coordinator
The order owner and the warehouse keep their jobs. What changes is the logistics part: instead of a coordinator copying details into emails and chasing replies, Wilson reads the order, asks the right questions, contacts the carriers, and records each step. The coordinator approves what is outside the rules and handles the loads that need judgment.
Common ways the handoff breaks
- The order is released, but nobody tells logistics until the afternoon.
- The quote request leaves out the liftgate or appointment in the order notes.
- A carrier quotes, but nobody tenders before the quote expires.
- The tender is sent and nobody checks that the carrier accepted.
- The carrier and PRO number never make it back to the order, so customer service cannot answer.
Each break is small, and each one turns into a missed pickup, a surprise charge, or a customer call. The workflow above closes them in order.
What the Acumatica order must contain before a carrier can quote
Before a carrier can quote, the Acumatica order must contain the freight facts that change the price and the service. An AI logistics coordinator should check those facts as soon as the order arrives and ask the right person for anything missing, before carriers are contacted.
| Field | Why carriers need it | Common gap in ERP orders |
|---|---|---|
| Pickup location and hours | Where and when the truck comes | Plant address correct, dock hours missing |
| Delivery address and type | Commercial, residential, job site, or distribution center | Ship-to address without the receiving type |
| Pallet count and dimensions | Space on the truck and LTL density | Item quantity only, no pallet count |
| Weight | Price and equipment | Item weights not summed per shipment |
| Freight class (LTL) | LTL price depends on class | Class missing or guessed |
| Ship date and delivery date | Which carriers can make it | Requested date not tied to freight readiness |
| Services | Liftgate, appointment, inside delivery, notification | In order notes, not in fields |
| References | PO number, sales order number, customer reference | Several references with no rule for the BOL |
Where the freight details live
In many Acumatica setups, part of this information sits on the sales order, part on the shipment, and part in notes or with the warehouse. The pallet count may only exist after the warehouse builds the pallets. The first decision is which record starts freight work: the released sales order, the shipment, or a warehouse confirmation that freight is ready.
What Wilson does with missing details
Wilson checks the order for the details carriers need. If the class, pallet count, or a delivery requirement is missing, it asks the order owner or the warehouse before requesting quotes, rather than letting carriers guess. A quote based on guessed details often turns into a reclass, a reweigh, or an accessorial on the invoice.
Hypothetical example: a missing liftgate
The pump manufacturer’s order for three pallets to a contractor’s job site has “call before delivery, no dock” in the order notes. Wilson reads the note, flags that a liftgate and delivery notification are needed, and includes both in the quote request. All carriers price the same service, and the invoice later matches the rate confirmation.
Shipments with several orders, or orders with several shipments
One truck may carry several Acumatica orders to the same customer, and one large order may ship in parts over several days. Carriers price the physical shipment, not the order. The workflow should decide how order lines become shipments: by customer, ship date, and destination for consolidation, and by release for partial shipments. Acumatica documents that a shipment can cover several sales orders or one sales order at a time, which mirrors the choice the freight workflow has to make.
Freight readiness
A released order is not always ready freight. Production may finish the goods the day before shipping, or the warehouse may need time to build pallets. The quote request can go out on the planned ship date, but the pickup window should be confirmed against the warehouse’s readiness, not only the order date. That prevents a truck from arriving for freight that is not ready and the detention that follows.
For a closer look at the same question with another ERP, see how to tender to approved carriers from a Sage order feed.
How the order gets out of Acumatica: file, email, or API
An Acumatica order can reach freight execution as a scheduled file, an email, or through an API. An AI logistics coordinator should start from the method the company can maintain today and move to a deeper connection when volume justifies it.
| Method | How it works | Good for | What to agree |
|---|---|---|---|
| Scheduled file | A report or export of released orders sent on a schedule | Starting on a few lanes without IT work | Which orders, which fields, how often |
| Orders or shipment requests sent to Wilson’s address | Low volume or exceptions | A consistent format and who sends it | |
| Spreadsheet | A shared sheet of orders to ship | Teams already working from a list | Who updates it and when |
| API | A connection that reads orders as they are released | Higher volume and faster handoffs | Access, field mapping, and error handling |
Start with what you can maintain
Wilson works from the connection or data flow the company already has: an ERP feed, a scheduled file drop, a spreadsheet, email, or an API. No integration project is required to start. Many companies begin with a daily or twice-daily export of released orders for the first lanes. The method matters less than the content: a complete file once a day beats an incomplete feed every minute.
Changes after the order leaves Acumatica
Orders change: a quantity drops, a date moves, an address is corrected. The agreed method should say how changes reach freight execution, for example in the next file with a changed flag, or by email to Wilson. When a change affects a booked load, Wilson sends it to the carrier and, for BOL changes, saves each version and sends changes to address, class, carrier, or price to the load owner.
Hypothetical example: from file to quotes
The pump manufacturer exports released orders for its Midwest LTL lanes from Acumatica at 7:00 a.m. and 1:00 p.m. Wilson reads each file, groups lines by shipment, checks the freight fields, and sends quote requests to the approved carriers on each lane within minutes. Orders released after 1:00 p.m. go out the next morning, which matches the plant’s pickup cut-off.
Choosing which orders to send
Not every Acumatica order needs freight coordination. Customer pickups, parcel orders handled at the dock, and internal transfers may follow other routines. The export or connection should include only the orders the company wants Wilson to coordinate, filtered by ship method, warehouse, or lane. Starting with a clear filter keeps the first lanes clean and makes the before-and-after comparison easy.
Parcel orders
Wilson also schedules FedEx and UPS pickups through the customer’s carrier accounts via API or email. Companies that ship parcel from the same Acumatica orders can include those orders too, so parcel, LTL, and truckload follow one routine and one record.
Security and access
An export only shares the fields the company chooses. An API connection needs credentials, a user with the right permissions, and a plan for when credentials change. In both cases, agree who at the company owns the connection and who is notified if a file does not arrive or an API call fails. A missing file should be noticed the same morning, not discovered when a customer asks about an order.
Whichever method the company starts with, the content of the handoff is the same: the shipment, its freight details, its dates, its services, and its references. Getting those right in the first file is what makes the first lanes work, and the same fields carry over when the company later moves to an API.
From quote request to written carrier acceptance
Quote request to written acceptance is where most coordination time goes. An AI logistics coordinator should send the request, follow up on silence, select within the rules, tender, and keep following up until an approved carrier accepts in writing with a pickup window.
Contract carriers first
If the lane has a contract carrier, Wilson tenders to it first at the contract rate. If that carrier declines or does not answer in time, Wilson requests quotes from other approved carriers on the lane. Wilson books only carriers the company has approved. Cartage can introduce additional carrier capacity, but the company must approve each carrier before Wilson uses it.
Quotes and negotiation
Wilson compares quotes like for like: same pickup, delivery, pallets, class, and services. It negotiates against the company’s rate targets under configured rules and approval limits; rates outside those limits go to the logistics team with the options and context.
Follow-up until acceptance
| Situation | What Wilson does |
|---|---|
| Carrier has not replied to the quote request | Follows up by email, then by phone where configured |
| Carrier has not answered the tender | Follows up at the configured interval |
| Carrier declines | Tenders to the next approved carrier when the rules allow |
| Carrier accepts without a pickup window | Asks for the window and confirms it with the dock |
| No approved carrier accepts in time | Escalates to the load owner with each attempt and answer |
Wilson works with carriers through email, API, EDI where the carrier supports it, and phone calls where configured, and contacts drivers directly by phone or text when the carrier shares driver contact information.
What counts as accepted
A load is accepted when the carrier confirms it in writing, the rate confirmation shows the agreed terms, and the pickup window is confirmed. A sent tender, a quote, or a verbal “should be fine” is not acceptance. For more on that difference, see how AI automates carrier quotes, tenders, and booking confirmations.
Hypothetical example: one order to acceptance
At 7:05 a.m., Wilson reads the pump manufacturer’s file and finds an order for four pallets, 2,600 pounds, class 85, to a distributor in Ohio, ready to ship tomorrow. The lane has no contract carrier, so Wilson asks three approved LTL carriers for quotes. Two reply by 8:00 a.m.; the third gets a follow-up and replies at 9:10. The best quote is $30 over target; Wilson counters at the target and the carrier accepts. Wilson tenders, receives written acceptance at 9:45, sends the rate confirmation, and confirms a pickup window of 1:00 to 3:00 p.m. with the carrier and the dock. The load owner did not touch it.
Escalations that save time
When no approved carrier accepts in time, the load owner gets one message with the order, the carriers asked, their answers, and the time left before the ship date. The decision might be to pay more, move the date, or approve a new carrier. Wilson carries out the decision and records it.
Exceptions after acceptance
Acceptance is not the end. If the carrier misses the pickup or cancels, Wilson contacts the carrier, notifies the internal team, notifies the customer when configured, and initiates rebooking from the approved carrier list, automatically within the rules or after approval. It reconfirms each pickup the day before and records arrival separately from pickup, marking a load picked up only when the signed BOL or the departure is confirmed.
What goes back to Acumatica after booking
After booking, some facts usually need to reach Acumatica: the carrier, the PRO or tracking number, the ship date, and sometimes the freight cost. An AI logistics coordinator can return them, but what goes back and how depends on the scope agreed with the company.
| Data | Why Acumatica users want it | How it can return |
|---|---|---|
| Carrier and PRO number | Customer service can answer “who has it?” | Return file, email, or API, depending on scope |
| Actual ship date | Order and invoicing status | Return file or API |
| Freight cost | Margin and customer billing | Return file or API, after audit |
| Delivery and POD | Close the order and support invoicing | Return file or API; POD as a document |
Write-back depends on scope
Write-back to the ERP depends on scope. Some companies want only a daily return file their team imports; others want an API update when each load is booked. Acumatica documents API operations for shipments, such as setting tracking numbers and freight cost, which makes an API return possible where the company chooses it. Agree in discovery which fields return, through which method, and what happens if a return fails, for example a notice to the order owner and a retry.
Records stay in Wilson too
Wilson keeps each load’s full record: quotes, counters, tenders, acceptance, documents, status, and invoice decisions, with change history, searchable and exportable. Acumatica does not need to hold every carrier message. It needs the facts its users rely on.
Invoices and payment
Before paying from the Wilson Wallet, Wilson audits each carrier invoice against the POD and the rate confirmation; customers can require a signed POD before payment releases. If any line does not match what was booked, the whole invoice waits for a person. Payments above approval limits or outside the rules also wait.
Customer updates
Customer service often answers “where is my order?” from Acumatica. If carrier and status details return there, they can answer faster. Wilson also updates customers directly when configured: the shipper by email at each step, the consignee by email or SMS, and the customer with the signed BOL after pickup. The company decides which updates go where, so customers do not receive the same news twice.
What finance needs
Finance usually wants the final freight cost on the order or in the books, the carrier invoice tied to the load, and proof of delivery. Wilson audits each invoice before payment and keeps the invoice, rate confirmation, and POD on the load, so the freight cost that returns to Acumatica or to the books is the audited amount, not the quote.
What an Acumatica-to-carrier demo should prove
An Acumatica-to-carrier demo should run your own Acumatica orders from export to written carrier acceptance, including the hard cases. An AI logistics coordinator that only shows clean sample orders has not proven the workflow you would buy.
Bring these orders
- Five released Acumatica orders from last week on your main lanes.
- One order with a delivery requirement only in the notes.
- One order with a missing pallet count or class.
- One order that changed after release.
- The carriers that moved them, including one that answers only by email or phone.
What the demo should show
| Check | Pass |
|---|---|
| Order intake | Orders read from your actual export, with missing details flagged |
| Quotes | Requests to your approved carriers, with follow-up on silence |
| Selection | Contract carrier first, then best quote within target and limits |
| Acceptance | Written acceptance, rate confirmation, and a confirmed pickup window |
| Changes | The changed order reaches the carrier and the record |
| Return | The agreed fields ready to go back to Acumatica |
Questions to ask
- Which Acumatica export or connection would you use for our first lanes?
- What happens when an order arrives without a class or pallet count?
- How do you handle a carrier that does not answer the tender?
- Which fields can go back to Acumatica, and how?
- What stays with our team?
Starting
Most teams start Wilson on a few lanes and expand from there; timing depends on scope. Wilson gets an email address on the company’s domain and is onboarded like a new team member, with approved carriers, rate targets, approval limits, and customer requirements. Wilson has no subscription or platform fee; pricing is a percentage of the freight it coordinates, with pricing scaling down as volume grows, and Enterprise pricing is custom. For how the same workflow looks with other ERPs, see which ERPs Wilson integrates with and Oracle ERP orders are ready: which freight software sends the tender?
Measure the first lanes
- Time from order release to written carrier acceptance.
- Share of orders with complete freight details on arrival.
- Pickups confirmed and reconfirmed.
- Missed pickups and rebookings.
- Coordinator hours spent re-entering orders and chasing carriers.
Compare the same lanes before and after, and report freight dollars, service, and hours separately.
Warning signs
- A demo that only uses sample orders.
- “Integration required” before any of your orders can run.
- No answer to who follows up when a carrier is silent.
- A sent tender shown as a booked load.
- No plan for what returns to Acumatica.
FAQs
How does an Acumatica sales order become a load accepted by an approved carrier?
The order’s freight details leave Acumatica by file, email, or API; approved carriers quote; the company’s rules select one; and the carrier accepts in writing with a pickup window. Wilson, by Cartage, is an AI logistics coordinator that runs those steps.
Does Wilson work with Acumatica?
Yes. The AI logistics coordinator works with Acumatica among other ERP environments, with the exact connection depending on the customer’s data flow and scope. Many companies start with a scheduled order export.
Do we need a TMS to tender from Acumatica?
No. The AI logistics coordinator replaces the TMS for freight execution and connects to the ERP, so a company running Acumatica does not need to implement a TMS first.
Can booking details go back to Acumatica?
Yes, depending on scope. The AI logistics coordinator can return fields such as carrier, PRO number, ship date, and freight cost by return file or API, as agreed during discovery.