ERP, WMS, TMS, carrier and EDI integration
Interfaces between the systems you already run and the partners you already trade with, each one listed, owned, monitored and written up so your team can run it.
Start your integration inventory
Most logistics data problems turn out to be integration problems: an order keyed twice, a ship notice that never reached receiving, an inventory feed that runs nightly when the warehouse changes every hour. We build the interfaces between your ERP, WMS, TMS, carriers and trading partners, and we document and monitor them so your own team can run them after we leave.
What we connect
- ERP: items, customers, suppliers, purchase orders, sales orders, receipts, invoices and inventory valuation.
- WMS: receipts, stock by location, picks, shipments and adjustments.
- TMS: load tenders, carrier assignments, freight costs and invoices.
- Carrier APIs: rates, labels and tracking events.
- Trading partners: X12 EDI through your VAN or a direct connection.
The method follows what each system supports and how fresh the data must be: an API where both sides offer one, X12 EDI where the partner requires it, and files over SFTP where nothing else is available. There is no connector catalog here. We build the interface to each system and partner on your list, and we write down why each method was chosen.
X12 transaction sets we work with
The names below are the official X12 names. The use column is our short description of how each set usually appears in logistics.
| Set | X12 name | Typical use |
|---|---|---|
| 850 | Purchase Order | A buyer orders from a supplier |
| 855 | Purchase Order Acknowledgment | The supplier confirms or changes the order |
| 856 | Ship Notice/Manifest | The ship notice (ASN) listing cartons and pallets |
| 810 | Invoice | The commercial invoice |
| 846 | Inventory Inquiry/Advice | Stock levels shared between partners |
| 940 | Warehouse Shipping Order | An owner tells a 3PL warehouse what to ship |
| 943 | Warehouse Stock Transfer Shipment Advice | An owner tells a 3PL what inbound stock is coming |
| 944 | Warehouse Stock Transfer Receipt Advice | The 3PL confirms what it received |
| 945 | Warehouse Shipping Advice | The 3PL confirms what shipped |
| 947 | Warehouse Inventory Adjustment Advice | The 3PL reports adjustments |
| 204 | Motor Carrier Load Tender | A shipper offers a load to a carrier |
| 990 | Response to a Load Tender | The carrier accepts or declines |
| 214 | Transportation Carrier Shipment Status Message | Pickup, in-transit and delivery status |
| 210 | Motor Carrier Freight Details and Invoice | The carrier’s freight invoice |
| 997 | Functional Acknowledgment | Confirms a transmission was received |
The standard is only half the work. Each partner publishes its own implementation guide with the version, segments and codes it expects, and that guide, not the standard, is what your 856 has to pass. Partner testing is scheduled in the project plan because partners run their own onboarding queues.
Master data ownership
Every interface depends on master data, and every master data object needs exactly one owner. We agree the system of record for each and the direction it flows:
- Items, units of measure and conversions: usually the ERP.
- Locations and bins: usually the WMS.
- Carriers and service levels: usually the TMS.
- Customers, ship-to addresses and partner IDs: usually the ERP, with EDI partner IDs held in the translator.
Other systems receive copies and do not edit them. Mismatched units of measure, such as a case of 12 in one system and a case of 24 in another, are a common source of quantity errors, so conversions are tested before any transactions flow.
Error handling and replays
Every message is logged with its raw content, a status (received, translated, posted or failed) and a reference back to the business document, such as the PO or shipment number. Failures are sorted by kind:
- Data errors go to a queue owned by the business, with a plain-language message: “Item EX-20118 is not set up at warehouse 2”, not a stack trace.
- Temporary failures, such as a system being offline, retry on a schedule before anyone is alerted.
- Duplicates are recognized by a key, such as partner plus document number, and are not posted twice.
Once the cause is fixed, the original message can be replayed from the log. Nobody re-keys an order, and the history shows what was replayed and by whom.
Monitoring
A monitor watches each interface for the signs that something is wrong before a customer calls:
- Message counts per interface compared with a normal day.
- Failed messages by reason and by age.
- Expected messages that never arrived, such as no 945 within a set time after a 940.
- Overdue 997 acknowledgments by partner.
Alerts go to a named owner, and the integration runbook from our documentation service tells that owner what to check and how to replay.
An integration inventory
Every engagement starts with a list of interfaces. You can begin one with the integration inventory worksheet.
Example (fictional). Part of an integration inventory for a distributor with its own warehouse and an outside 3PL.
| Interface | From and to | Trigger | Method | Peak-day volume | Owner |
|---|---|---|---|---|---|
| Purchase orders | ERP to WMS | PO released | API | 180 | Purchasing |
| Ship notices (856) | Suppliers to WMS | Supplier ships | X12 via VAN | 140 | Receiving lead |
| Receipts | WMS to ERP | Receipt closed | API | 160 | Inventory control |
| Shipping orders (940) | ERP to 3PL | Order released | X12 via VAN | 900 | Customer service |
| Shipping advice (945) | 3PL to ERP | Shipment confirmed | X12 via VAN | 900 | Customer service |
| Shipment status (214) | Carriers to tracking layer | Carrier event | X12 and carrier API | 3,500 | Transportation |
| Inventory advice (846) | WMS to a key customer | Daily at 5:00 a.m. | X12 via VAN | 1 | Sales operations |
| Freight invoices (210) | Carriers to TMS | Invoice issued | X12 via VAN | 220 | Accounts payable |
What you receive
- The integration inventory and a field-level data map for each interface.
- Interfaces built and tested with each system and partner.
- Error queues, a replay tool and a monitoring view with alerts.
- An integration runbook for your IT team.
- Source code and configuration, delivered at handover. Ownership and licensing terms are set out in each statement of work.
Scope your project.
Tell us what you need to track, which systems you run and when it has to work. We reply with questions or a time to talk.