Channel
Arcbest via Mercury GateArcBest via MercuryGate
Plan a reliable EDI exchange for Arcbest via Mercury Gate / ArcBest via MercuryGate. Explore 4 document references, map them to your business records and test the complete workflow before launch.
- Documents
- 4 transactions
- Standards
- X12
- Implementation
- Mapping and launch plan
Implementation guide
Arcbest via Mercury Gate / ArcBest via MercuryGate: EDI implementation plan
Build a reliable EDI workflow for Arcbest via Mercury Gate / ArcBest via MercuryGate. Use 4 document types to plan record mapping, prevent duplicate processing and reconcile results in your business systems.
The document list is based on the linked partner reference. Confirm the required messages, versions and directions for your account.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| X12 990 Response To A Load TenderListed for ArcBest via MercuryGate | load-tender response original load reference, carrier and response |
|
| X12 210 Motor Carrier Freight Details And InvoiceListed for ArcBest via MercuryGate | freight invoice carrier invoice, shipment reference and charge line |
|
| X12 204 Motor Carrier Load TenderListed for ArcBest via MercuryGate | load tender load reference, pickup and delivery stop identifiers |
|
| X12 214 Transportation Carrier Shipment Status MessageListed for ArcBest via MercuryGate | shipment status event shipment reference, event code, event time and location |
|
Implementation steps
-
Choose the trading account and channel
Confirm the supplier or customer account, sender and receiver IDs, test environment and current guide for ArcBest via MercuryGate. Compare other Arcbest via Mercury Gate channels before reusing a mapping.
-
Map records and assign owners
Start with load-tender response, freight invoice, load tender. For each document, assign the source system, destination record, stable identifiers and person responsible for exceptions. Agree whether a change updates an existing record or creates a new event.
-
Test a complete exchange
Run a successful exchange and the failure cases in the mapping table. Track delivery, document validation and processing in your business system separately. Agree on the Arcbest via Mercury Gate production handoff and save the results of each approved test.
-
Check results after launch
Match records between systems using original load reference, carrier and response. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.
Go-live checklist
- The required X12 documents, versions and sample files are agreed.
- Sender and receiver IDs, test connections and production connections are agreed with the channel owner.
- Delivery receipts, document validation and business responses have monitoring and a named owner.
- Tests cover duplicates, partial processing and reconciliation with realistic business records.
Document catalog
EDI documents listed for Arcbest via Mercury Gate / ArcBest via MercuryGate
4 EDI transactions listed in this catalog.
Document flow on this channel
Document relationships on ArcBest via MercuryGate
This channel lists all 4 document types in the Arcbest via Mercury Gate directory. Example relationships are shown below; confirm the required sequence in the channel guide.
Network onboarding
Plan the MercuryGate connection
The directory associates MercuryGate with 26 partner entries across 35 channels. Confirm transport, network enrollment, commercial terms and testing with the channel owner before implementation.
Most frequently listed documents on MercuryGate
- 204 35 ch
- 214 35 ch
- 990 35 ch
- 210 24 ch
Other partner entries associated with MercuryGate
ArcBest via MercuryGate questions
Which EDI documents are listed for Arcbest via Mercury Gate / ArcBest via MercuryGate?
X12 990 Response To A Load Tender; X12 210 Motor Carrier Freight Details And Invoice; X12 204 Motor Carrier Load Tender; X12 214 Transportation Carrier Shipment Status Message. Confirm which documents, directions and versions apply to your account.
How should I choose the Arcbest via Mercury Gate EDI channel?
ArcBest via MercuryGate lists 4 distinct document types. Match the channel to your business unit, account and delivery arrangement; compare the other channel links before choosing a connection. Confirm access and enrollment with the channel owner.
Which identifiers should the Arcbest via Mercury Gate mapping preserve?
For X12 990 Response To A Load Tender, plan around original load reference, carrier and response. For X12 210 Motor Carrier Freight Details And Invoice, use carrier invoice, shipment reference and charge line. Use the partner guide to locate these values and check their allowed formats.
Does a successful EDI receipt mean Arcbest via Mercury Gate accepted the business document?
Track delivery, document validation and business processing separately. An AS2 message disposition notification (MDN) confirms transport receipt; an X12 997 or 999 reports technical validation. Use the agreed business response or reconciliation report to confirm that the order, shipment or invoice was processed.
What should be tested before launching Arcbest via Mercury Gate / ArcBest via MercuryGate EDI?
Associate acceptance with the correct version of the load tender. Test a declined tender and ensure it returns to dispatch for reassignment. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.
Connect Arcbest via Mercury Gate EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
