How does a daily SAP batch file become scheduled pickups?
Key Takeaways
- A daily SAP batch file becomes scheduled pickups in four moves: intake, shipment creation, carrier booking and pickup confirmation with the carrier.
- The file has to carry enough data to book a truck: ship-from, ship-to, ready date, weight, piece or pallet count, dimensions and a reference number.
- Orders with missing or conflicting fields should be held and flagged, not guessed at, so one bad line doesn't hold up the rest of the file.
- Wilson, by Cartage, is an AI logistics agent that has scheduled 2,800+ shipments for a plastics and rubber manufacturer by processing its daily SAP batch files.
- Write-back to SAP is optional and usually set up after order intake is working.
From file drop to confirmed truck: what actually happens?
A daily SAP batch file becomes scheduled pickups when each order line is turned into a shipment, booked with an approved carrier and confirmed with that carrier for a specific pickup window. A pickup is scheduled only when the carrier has agreed to send a truck to a known address on a known date.
Most manufacturers already export a scheduled file from SAP: a CSV or Excel extract of the orders released to ship, dropped at the same time every day. The gap is what happens next. In many plants a coordinator opens the file, copies each order into a carrier email or portal, waits for replies and updates a spreadsheet.
That handoff is where freight execution (the work of quoting, booking, confirming and tracking each load) either runs as a routine or depends on one person's morning.
What does the batch file need to contain?
Each order line needs the data a carrier asks for before it will commit a truck. If a field is missing, someone will have to chase it later, usually by email, and usually after the pickup is already late.
| Field | Why the carrier needs it | What breaks if it’s missing |
|---|---|---|
| Order or delivery reference | Ties the load to the order, BOL and invoice | Replies and invoices can’t be matched |
| Ship-from and ship-to address | Defines the lane and the pickup stop | No quote, no pickup |
| Ready date (and dock hours, if known) | Sets the pickup window | Carrier proposes a date the plant can’t meet |
| Weight and piece or pallet count | Sizes the load and sets the mode | Wrong equipment or a reweigh charge |
| Dimensions | Needed for LTL density and freight class | Reclassification and a higher invoice |
| Product description or SKU | Drives NMFC class lookup | Class can’t be calculated |
| Special requirements | Liftgate, appointment, hazmat flags | Accessorials appear on the invoice |
Column names don’t matter; what matters is that the same fields arrive in the same places every day. For a broader checklist, see the order data to confirm before you request a quote.
For plastics and rubber shippers, weight and dimensions deserve extra attention. Resin bags, rolls and molded parts can ship as dense pallets or as bulky, light freight, and LTL class depends on density. Wilson calculates freight class from weight and dimensions using the customer’s SKU catalog, so the accuracy of those inputs stays with the customer.
How do order lines turn into shipments?
Every order line is checked, grouped where it ships together and turned into a shipment record with its own reference, mode and pickup requirements. That record is what gets quoted, booked and tracked.
Wilson covers this as the first of its six lifecycle stages, which it calls Create: it turns an order from the ERP, a spreadsheet or email into a shipment. Orders can reach Wilson four ways: an ERP feed, a spreadsheet, email or a scheduled file drop. A daily SAP export is the last of these. Wilson works with SAP among other ERPs, and it does not need a full ERP integration to start.
From there the shipment moves through Quote and Tender. Wilson requests quotes from the company's approved carriers, compares them and books the selected carrier under the company's rules and approval limits. Wilson tenders the company's own carriers first. Bookings above a cost threshold, or with a specific carrier, can be set to wait for a person.
When fields are missing or don't add up
General practice is simple: don't let one incomplete line stop the file. Process the complete orders, hold the incomplete ones and send a clear request to whoever owns the data, naming the order and the missing field.
Common gaps in a daily file include:
- a ready date in the past, or one that falls on a weekend the plant is closed;
- a weight with no pallet count, or a pallet count with no dimensions;
- a ship-to address that doesn't match the customer master;
- a duplicate order line from a re-run export.
With Wilson, anything it can't resolve within the company's rules is escalated to the team, and every message and change on the shipment is recorded in its change history. The coordinator gets a specific question about a specific order, not a whole file to re-check.
How are pickups scheduled and confirmed?
For LTL and FTL, Wilson schedules the pickup with the carrier, confirms the pickup window and reconfirms it before the truck is due. A booking without a confirmed window is not yet a scheduled pickup.
A plastics and rubber manufacturer shows how this works day to day. Its orders reach Wilson as daily SAP batch files. Wilson processes each file, routes the carrier emails that follow and assigns pickup times, and it has scheduled 2,800+ shipments this way. The file lands, and the output is a set of shipments with carriers and pickup times attached, rather than a spreadsheet waiting for someone to work it.
Confirmation and reconfirmation run through the carrier’s channel: email, phone or API, with EDI where the carrier supports it. Wilson coordinates pickup times with carriers; it does not manage dock slots inside the plant or warehouse today. If the plant has dock hours or a daily truck limit, those belong in the playbook Wilson works from, and the facility still owns its own dock calendar.
Once a pickup is booked and confirmed, notifications follow the company’s settings. The team can get booked, picked up, running late, delivered and POD filed updates in Slack or Microsoft Teams. Each company chooses who’s notified and how. For what a complete confirmation should hold, see what a pickup confirmation should include.
Should shipment updates flow back into SAP?
Write-back is optional, and most teams add it after intake is stable. First prove that the file reliably becomes booked, confirmed shipments. Then decide what SAP needs to know.
Wilson can write updates back in three ways, chosen per customer during onboarding:
- an updated CSV or Excel file sent by email for the ERP to import;
- a write to a shared table;
- an update through an API connection, where one is available.
Typical fields to return are carrier, pro or tracking number, pickup date, delivery date and POD status. Keep the list short at first. The same review should cover what systems Wilson can access, what shipment data it handles and which actions need approval. More on the options in sending shipment updates back to the ERP.
What to check before you automate the handoff
The deciding question is whether yesterday's file could be booked without anyone retyping it. Pull one recent daily export and check four things:
Does every line carry ship-from, ship-to, ready date, weight, count and dimensions?
Is there one stable reference that will follow the load to the BOL and the invoice?
Who answers when a line is incomplete, and how fast?
Which bookings should wait for approval, and above what cost?
If the answers are clear, the file is ready to drive pickups. Send us a recent SAP export with a few orders on it and see how those lines would become scheduled pickups.
Sources
- Cartage customer results, October 2026 (anonymized)
- Cartage, Wilson product FAQ, October 2026: https://cartage.ai