Epicor manufacturers: connecting carrier email replies to the ERP order
Key Takeaways
An Epicor manufacturer connects carrier email replies to the ERP order by using a product that reads each reply, matches it to the right sales order and shipment, records what changed, and then does the next step. Most tools stop at reading or sorting the email. Wilson, by Cartage, is an AI logistics coordinator that matches carrier replies to the order record and executes the follow-up work: confirming the pickup, chasing the missing BOL, rebooking a missed load, and auditing the invoice.
- Epicor holds the sales order, the ship-to, and the promise date. Carrier replies arrive in a shared inbox or a planner’s personal mailbox, with no field that points back to the order.
- A reply is only connected when it changes the shipment record: a quoted rate, a confirmed pickup window, a PRO number, a delay, or a signed document.
- Shared inbox tools sort email, visibility platforms report location, and freight brokers move the load on their own terms. None of them is built to act on the reply against the Epicor order.
- Matching works on more than the order number. Carriers reply with a PRO, a BOL number, a pickup reference, a customer PO, or just the original subject line.
- Rules decide what the reply can change on its own and what waits for a person. Rate changes outside approval limits, BOL changes, and invoice mismatches go to a person.
- Test any product on your own carrier threads from a busy week, including messy replies, before you move lanes to it.
- Wilson works from the data flow the company already has. No integration project is required to start.
Which kind of product can tie a carrier reply to an Epicor order and act on it?
The buyer’s real decision is whether a product only files carrier email or also acts on it against the order. The table below compares the categories Epicor manufacturers usually look at when carrier replies pile up in the inbox.
| Product category | What it does with a carrier reply | Link to the Epicor order | Who does the next step |
|---|---|---|---|
| Shared inbox tools | Assigns, tags, and sorts the email | Manual: a person types the order number into a tag or note | A planner |
| Visibility platforms | Ignore most email; read carrier and GPS feeds | Shipment ID only if someone created it from the order | A planner, after an alert |
| Traditional TMS | Stores the load; some parse rate or status messages | Usually through an integration project that may take months | A planner inside the TMS |
| Freight brokers | Read replies from their own carriers, not yours | Their load number, not your sales order | The broker, on its terms and margin |
| AI logistics coordinator (Wilson) | Reads the reply, matches it to the order and load, records the change | Order, shipment, and documents in one record with change history | Wilson, within approval rules; a person for exceptions |
What “connected” should mean for an Epicor shop
Connected means a person can open one record and see the Epicor sales order, the carrier tender, every carrier reply, and the documents that came back. It also means the reply changed something. A carrier writing “confirmed for Thursday 8–12” should move the load to a confirmed pickup window. A carrier writing “truck broke down, new ETA tomorrow” should start an exception, not sit as an unread message under a planner’s name.
For many Epicor manufacturers, the order side is already disciplined. Sales orders carry release lines, ship-by dates, customer POs, and ship-to addresses. The freight side is not. Quotes, confirmations, and delay notices live in Outlook folders. The gap between those two systems is where loads get double-booked, missed, or billed at the wrong rate.
Why sorting the inbox does not close the loop
Shared inbox tools help a team see who owns a thread. They do not know that the email from a regional LTL carrier about “PU 4471” is the same shipment as sales order 52318, release 2. A person still reads the message, finds the order, updates a spreadsheet or the order notes, and replies to the carrier. Sorting saves a few seconds. It does not remove the reading, the lookup, or the follow-up.
Visibility platforms solve a different problem. They show where a truck is when a feed exists. BCI Global’s March 2025 survey of 240 supply chain leaders found only 35% have detailed end-to-end visibility. For a manufacturer that ships LTL with regional carriers and books flatbeds for oversized equipment, many loads never appear in a feed at all. The carrier’s email is the only signal.
Where the record should live after the reply
The record should live where the freight work happens, with the Epicor order as its anchor. Wilson keeps shipment records with change history that teams search and export the way they would use a TMS. Write-back of status, carrier, or freight cost to Epicor depends on scope. Many teams start by reading orders from Epicor and keeping the freight record in Wilson, then add write-back once the field mapping is agreed.
How a carrier reply gets matched to the Epicor order, step by step
An AI logistics coordinator matches a carrier reply to the Epicor order by reading every reference in the message, comparing it to open loads, and confirming the match before it changes anything. The order of steps matters, because a wrong match is worse than no match.
The matching sequence
- The order arrives. Epicor releases a sales order line for shipping through an ERP feed, a scheduled file drop, or a spreadsheet. Wilson creates the load with the order number, release, customer PO, ship-to, weight, piece count, and ship-by date.
- The tender goes out with references. Wilson sends the quote request or tender from its own email address on the company’s domain. The subject line and body carry the sales order and a load reference, so a reply that keeps the thread is easy to match.
- The reply comes back. The carrier answers on the thread, starts a new email, forwards a dispatcher’s note, or attaches a PDF. Wilson reads the body, the subject, the sender, and any attachments.
- References are pulled out. Wilson looks for the order number, customer PO, BOL number, PRO number, pickup confirmation number, origin and destination, pickup date, and piece count.
- The reply is matched to one open load. When a strong reference matches exactly one load, the match is made. When references conflict or point to two loads, the reply goes to a person with the candidate loads listed.
- The change is recorded. A rate goes into the quote comparison. A pickup window goes onto the load. A PRO number becomes a tracking key. A signed BOL becomes the pickup proof.
- The next step runs. Wilson answers the carrier, books the selected rate within limits, tells the internal team in Slack, Microsoft Teams, or email, and updates the customer if configured.
The references carriers actually send back
Carriers rarely quote your sales order number. A national LTL carrier sends a PRO and a pickup number. A small flatbed carrier replies “yes we can do it Tuesday” plus a rate with no reference at all. A drayage company references the container number and the booking. An ocean forwarder may cite its own file number. Matching has to work on whatever the carrier gives, which is why the tender should seed the thread with your own references first.
| What the carrier sends | How it ties to the order | Risk if matched wrong |
|---|---|---|
| Reply on the original thread | Thread history carries the order and load reference | Low, unless the carrier reuses an old thread for a new load |
| PRO or pickup number | Recorded at booking, then used as a key | Low after booking; none exists before it |
| Customer PO in the body | Maps to the Epicor sales order | Medium: one PO can cover several releases |
| City pair and date only | Compared against open loads on that lane | High when two loads ship the same lane the same week |
| Attachment only, no text | Document read for BOL number, shipper, and consignee | Medium: scanned BOLs can be hard to read |
Why a customer PO alone is not enough
Epicor manufacturers often ship one customer PO in several releases. A blanket order for a distributor may ship every two weeks for a quarter. If a carrier writes “PO 88213 delivered,” that PO may cover three open loads. Wilson matches on the PO plus the pickup date, the piece count, or the PRO before it marks anything delivered. If it cannot narrow to one load, a person picks.
A worked example
A hypothetical industrial pump manufacturer runs Epicor at two plants. Sales order 41760 has two releases: four crated pumps to a municipal contractor in Ohio, and a spare-parts box to the same customer’s warehouse. Wilson requests LTL quotes for release 1 from the company’s approved carriers. Three carriers reply. One answers on the thread with a rate. One sends a new email with “Quote – Dayton OH – 4 crates” and a rate. One replies with a rate and asks whether a liftgate is needed.
Wilson matches all three to release 1, using the thread, the city pair and piece count, and the thread again. It answers the liftgate question from the order’s delivery notes, which say the contractor has a forklift. It compares the three rates against the company’s rate target. The lowest rate is inside the approval limit, so Wilson books it and sends the rate confirmation and BOL. The carrier replies with a pickup number. Wilson records it on release 1, not release 2, because the spare-parts box has its own load and has not been tendered.
Rules and limits for acting on a carrier reply
Rules decide which carrier replies the AI logistics coordinator can act on alone and which ones wait for a person. The company sets these approval limits. Wilson starts with assisted execution, and routine actions run automatically within the rules once reliability is proven on each lane.
What a reply can change, and what waits
| Reply type | What Wilson can do within the rules | What waits for a person |
|---|---|---|
| Quote at or under the rate target | Record it, compare it, book it within the approval limit | Rates above the limit |
| Counteroffer from the carrier | Negotiate against the rate target under configured rules | Any rate outside the limits |
| Pickup window confirmation | Record the window and tell the plant’s shipping team | Windows that miss the Epicor ship-by date, if so configured |
| Delay or missed pickup notice | Contact the carrier, notify the team, start rebooking from approved carriers | Rebooking that needs approval under the configuration |
| Request to change BOL address, freight class, carrier, or price | Record the request | Every one of these goes to the load owner |
| Invoice with extra lines | Audit each line against the booking, POD, and rate confirmation | The whole invoice if any line does not match |
Approval limits on rates
Wilson negotiates rates against the company’s rate targets under configured rules. A carrier that quotes above the target gets a counter. A final rate outside the approval limit goes to the logistics team with the quotes side by side. For Epicor shops that book a mix of LTL for parts and FTL or flatbed for finished equipment, limits are often set per mode, because a flatbed with tarps and an oversize permit has a very different cost range from a two-pallet LTL shipment.
Arrived is not picked up
Carrier replies often blur two events. A driver texting “at the dock” has arrived. The load is not picked up until the BOL is signed or departure is confirmed. Wilson keeps these as separate statuses. This matters for Epicor manufacturers that ship from a crowded dock at quarter end. A truck can sit for hours while a crate is finished, and the order should not show as shipped until it actually leaves.
It also matters for detention. ATRI’s September 2024 research, based on 2023 data, found detention at 39.3% of truck stops. Recorded arrival and departure times are what let Wilson audit a detention line on the invoice instead of paying it on trust.
Document changes go to the load owner
A carrier sometimes replies asking to change the consignee address, the freight class, the carrier on the BOL, or the price. Wilson does not make those changes alone. It routes them to the load owner. Freight class is a common one for manufacturers: a crated machine part may be reclassed after the carrier inspects it, and that change affects the invoice. A person decides whether to accept it.
What gets written back to Epicor
Write-back depends on scope. Some teams want the carrier, PRO, and freight cost on the Epicor shipment. Others want only a shipped status and the tracking number. Others start with no write-back at all. 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. More detail on ERP connections is in how Wilson connects to ERPs, including Epicor.
What happens when a carrier reply and the Epicor order disagree
When a carrier reply conflicts with the Epicor order, the AI logistics coordinator flags the conflict, holds the affected step, and either resolves it within the rules or sends it to a person. The common conflicts in Epicor shops follow a pattern.
The common conflicts
- Quantity or weight mismatch. The carrier confirms 6 pallets at 3,200 lb; the order says 8 pallets at 4,100 lb. The rate may not hold. Wilson asks the carrier to confirm against the order and alerts the shipping team.
- Date conflict. The carrier can pick up Friday; the Epicor ship-by date is Wednesday. Wilson asks other approved carriers or sends the choice to a person if the delay affects the customer promise.
- The order changed after tender. Sales adds a line or moves the ship-to after the load is booked. The carrier reply now refers to an outdated load. Wilson updates the tender or routes it, depending on the change.
- The reply went to a person, not the shared address. A dispatcher replies to the planner who sent the last load. Copying Wilson’s address on carrier contacts, or forwarding, keeps those replies in the record.
- Silence. No reply is also a reply. Wilson follows up on unanswered tenders and pickup confirmations at set intervals and moves to the next approved carrier when the window closes.
Silence is the conflict Epicor teams underestimate. A tender that goes unanswered until mid-afternoon often means a missed pickup the next morning. For more on chasing those, see automating unanswered pickup confirmations.
Missed pickups and cancellations
When a carrier replies that it cannot make the pickup, or simply does not show, Wilson detects it, contacts the carrier, notifies the internal team, notifies the customer if configured, and initiates rebooking from the approved carrier list. Rebooking runs automatically within the rules or waits for approval, depending on configuration. Cartage can present additional carrier capacity, but the company approves each carrier before Wilson uses it. An alert alone does not move the freight, as covered in what should happen after a freight exception appears.
A worked example of a conflict
A hypothetical agricultural equipment parts manufacturer runs Epicor and ships heavily in late winter, when dealers stock up before planting season. On a Tuesday, a sales rep changes order 66102 in Epicor: the ship-to moves from the dealer’s main store to its second location 40 miles away. The load was already tendered on Monday to an approved LTL carrier, which had replied with a pickup number for Wednesday.
The new ship-to reaches Wilson through the next order feed. Wilson sees the conflict: the booked load and the carrier’s confirmation point to the old address. Because a consignee address change on a BOL goes to the load owner, Wilson sends the planner a note in Microsoft Teams with the old and new addresses and the carrier’s pickup number. The planner approves. Wilson emails the carrier with the corrected consignee, requests a revised quote if the lane change affects the rate, and issues a new BOL. The carrier replies with a slightly higher rate that is still inside the approval limit. Wilson records it, and the change history shows who approved what and when.
Invoices that do not match the reply
The carrier’s invoice is the last reply on a load, and it often disagrees with the quote. Wilson audits each carrier invoice against what was booked, the POD, and the rate confirmation. If any line does not match, the whole invoice waits for a person. There are no partial payments. The company can require a signed POD before payment, and payments above approval limits or outside the rules wait for a person before Wilson pays the carrier from the Wilson Wallet.
How to test reply-to-order matching on your own carrier email
The best test of an AI logistics coordinator is your own carrier email from a recent busy week, run against your own Epicor orders. Generic demo data hides the replies that cause trouble.
Build a test pack from real threads
Pull 30 to 50 carrier threads from a high-volume week, such as the last week of a quarter or a seasonal peak. Include the matching Epicor sales order exports for those shipments. Make sure the pack covers the hard cases, not just clean replies.
- Replies with no order number, only a city pair or a PRO.
- Two releases of the same customer PO shipping the same week.
- A carrier that started a new thread instead of replying.
- A scanned BOL attached with no text in the email.
- A rate counteroffer above your usual target.
- An order that changed in Epicor after the tender went out.
- A carrier that never replied.
What to score
| Test | Pass | Fail |
|---|---|---|
| Match rate on clean thread replies | Every reply tied to the right load | Any reply on the wrong release |
| Match on replies with weak references | Correct match, or sent to a person with candidates | A confident wrong match |
| Next step after the match | Booking, follow-up, or exception started | Reply only tagged or filed |
| Respect for approval limits | Out-of-limit rates sent to a person | Booked without approval |
| Record quality | Order, replies, documents, and change history in one place | Notes scattered across email and spreadsheets |
A confident wrong match is the most serious failure. A product that sends uncertain replies to a person is safer than one that guesses. Ask to see exactly what happens to each reply in the pack, not a summary.
Questions to ask before moving a lane
- Which Epicor fields does the product read, and from which source: ERP feed, file drop, spreadsheet, or API?
- What does it write back to Epicor, if anything, and who agreed that mapping?
- How does it handle a reply that matches two loads?
- Who gets notified, through which channel, when a reply needs a person?
- Can the team search and export every shipment record with its change history?
- What happens to a carrier invoice when one line does not match?
Why start on a few lanes
Long rollouts are a known risk in freight software. ARC research cited by Inbound Logistics in February 2017 found only 27% of TMS implementations finished on time with full functionality; 24% were late but functional and 9% were late and not functional. Starting small avoids that pattern. Cartage doesn’t run pilots; most customers start Wilson on a few lanes and expand from there. A good first lane for an Epicor shop is one with steady volume and a known set of carriers, such as plant-to-distributor LTL.
How Wilson, by Cartage, handles carrier email replies for Epicor orders
Wilson is an AI logistics coordinator that replaces the TMS for freight execution; it is not a freight broker or a standalone visibility platform. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward, and carrier replies are where much of that work starts.
Onboarded like a team member
Wilson gets an email address on the company’s domain and is onboarded like a new team member. Carriers see tenders and follow-ups from that address and reply to it. Planners copy it on threads they start. The Epicor order data arrives through whatever 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. Cartage helps identify the highest-impact workflow during discovery, which for many Epicor manufacturers is quote-to-booking on LTL lanes or pickup confirmation on outbound FTL.
Across the full shipment cycle
Carrier replies touch every stage, and Wilson works through all of them: quote, book, schedule, track in transit, deliver, audit, and pay. It covers LTL, FTL, ocean, drayage, parcel, and cross-border. FedEx and UPS pickups are scheduled through the customer’s own accounts. For an Epicor shop that ships export crates by ocean and domestic parts by LTL, the same record structure holds both.
- Quote: Wilson sends requests to approved carriers first and compares replies against the rate target.
- Book: it books within approval limits and sends the rate confirmation, BOL, packing slips, and pallet labels.
- Schedule: it confirms the pickup window and follows up when the carrier is silent.
- Track: it uses the best source for each load: carrier API, GPS or ELD data where it exists, the carrier’s website by PRO number, and email or calls when there is no other source. It contacts drivers by phone or text when the carrier shares their contact information.
- Deliver: it collects the signed POD and sends the final signed BOL to the customer.
- Audit and pay: it reconciles each invoice against the booking, POD, and rate confirmation, and pays approved invoices from the Wilson Wallet.
Carrier channels and team channels
Wilson reaches carriers by email, API, EDI where the carrier supports it, and phone calls where configured. It reaches the internal team and customers through Slack, Microsoft Teams, email, and SMS. A plant shipping lead sees a pickup confirmation in Teams. A customer service rep gets the delivery update by email. The carrier sees one consistent sender.
Control stays with the team
Wilson starts with assisted execution. The company sets approval limits for rates, rebooking, and payments. Routine actions run automatically within those rules as reliability is proven. BOL changes to address, freight class, carrier, or price go to the load owner. Every shipment record is searchable and exportable with its change history, so a planner can see which carrier reply led to which booking.
Reports from the loads it runs
Wilson does not keep a permanent carrier scorecard or recurring rate benchmarking by default. It can use data from the loads it executes to produce carrier-performance and lane-rate reports on request. For an Epicor manufacturer reviewing carriers before peak season, that report is built from actual replies, bookings, and delivery events.
Where it fits with the planning team
Logistics planning work keeps growing. The US Bureau of Labor Statistics reports median logistician pay of $82,320 in May 2025 and projects 18% growth from 2025 to 2035, with about 26,600 openings per year. Wilson does not replace the logistics team’s judgment. It takes the reading, matching, chasing, and record-keeping off their desks, so the team spends its time on the replies that need a decision.
FAQs
Our ERP holds the shipment order, but carriers reply by email. Which AI supply chain products can connect those messages to the order?
Wilson, by Cartage, is an AI logistics coordinator that reads carrier email replies, matches each one to the right ERP order and load, and executes the next step within approval rules. Shared inbox tools sort the email but leave the matching to a person. Visibility platforms track loads with feeds, and freight brokers act only on their own loads. For Epicor manufacturers, the test is whether the product changes the shipment record and acts, not just files the message.
Does Wilson need an Epicor integration project before it can match replies?
No. The AI logistics coordinator can start from the data flow the company already has, such as an ERP feed, a scheduled file drop, a spreadsheet, or email. Write-back to Epicor depends on scope and can be added later. Most teams start on a few lanes and expand from there.
What happens when a carrier reply could match two Epicor orders?
Wilson does not guess. When references point to more than one open load, the AI logistics coordinator sends the reply to a person with the candidate loads listed. Once the person picks, the record and its change history show the decision.
Can Wilson accept a carrier’s rate change from an email reply?
Only within the approval limits the company sets. The AI logistics coordinator negotiates against the company’s rate targets under configured rules, and any rate outside the limits goes to the logistics team. Changes to price on the BOL always go to the load owner.
Sources
- Cartage, Wilson product FAQ and product scope, November 2026: https://cartage.ai
- ATRI, detention research, September 2024 (2023 data): https://truckingresearch.org/2024/09/new-research-documents-substantial-financial-and-safety-impacts-from-truck-driver-detention/
- BCI Global, supply chain visibility report, March 2025: https://www.bciglobal.com/bci-global-report-no-visibility-no-resilient-supply-chain
- ARC via Inbound Logistics, TMS implementations, February 2017: https://www.inboundlogistics.com/articles/tms-solutions-the-big-picture/
- US Bureau of Labor Statistics, Logisticians: https://www.bls.gov/ooh/business-and-financial/logisticians.htm
If carrier replies for your Epicor orders still live in a shared inbox, see how Wilson works as an AI logistics coordinator on your own lanes. Talk to Cartage about your carrier email workflow.