Skip to content

Channel

Mercury GateFerguson Enterprises via MercuryGate

Plan a reliable EDI exchange for Mercury Gate / Ferguson Enterprises via MercuryGate. Explore 4 document references, map them to your business records and test the complete workflow before launch.

Book an EDI demo ← All Mercury Gate channels
Documents
4 transactions
Standards
X12
Implementation
Mapping and launch plan

Implementation guide

Mercury Gate / Ferguson Enterprises via MercuryGate: EDI implementation plan

Build a reliable EDI workflow for Mercury Gate / Ferguson Enterprises 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.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
X12 210 Motor Carrier Freight Details And InvoiceListed for Ferguson Enterprises via MercuryGate freight invoice

carrier invoice, shipment reference and charge line
  • Separate line-haul, fuel and accessorial charges before comparing the invoice with the agreed rate.
  • Test a second invoice for the same shipment and distinguish a revision from a duplicate.
X12 990 Response To A Load TenderListed for Ferguson Enterprises via MercuryGate load-tender response

original load reference, carrier and response
  • Associate acceptance with the correct version of the load tender.
  • Test a declined tender and ensure it returns to dispatch for reassignment.
X12 204 Motor Carrier Load TenderListed for Ferguson Enterprises via MercuryGate load tender

load reference, pickup and delivery stop identifiers
  • Send an amended pickup appointment and retain the previous tender decision.
  • Test a multi-stop load whose stop sequence differs from address sorting.
X12 214 Transportation Carrier Shipment Status MessageListed for Ferguson Enterprises via MercuryGate shipment status event

shipment reference, event code, event time and location
  • Deliver an older status after a newer one and retain event history without moving the current status backward.
  • Send one milestone twice and avoid duplicate customer notifications.

Implementation steps

  1. Choose the trading account and channel

    Confirm the supplier or customer account, sender and receiver IDs, test environment and current guide for Ferguson Enterprises via MercuryGate. Compare other Mercury Gate channels before reusing a mapping.

  2. Map records and assign owners

    Start with freight invoice, load-tender response, 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.

  3. 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 Mercury Gate production handoff and save the results of each approved test.

  4. Check results after launch

    Match records between systems using carrier invoice, shipment reference and charge line. 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 Mercury Gate / Ferguson Enterprises via MercuryGate

4 EDI transactions listed in this catalog.

Document flow on this channel

Document relationships on Ferguson Enterprises via MercuryGate

This channel lists all 4 document types in the 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

Ferguson Enterprises via MercuryGate questions

Which EDI documents are listed for Mercury Gate / Ferguson Enterprises via MercuryGate?

X12 210 Motor Carrier Freight Details And Invoice; X12 990 Response To A Load Tender; 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 Mercury Gate EDI channel?

Ferguson Enterprises 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 Mercury Gate mapping preserve?

For X12 210 Motor Carrier Freight Details And Invoice, plan around carrier invoice, shipment reference and charge line. For X12 990 Response To A Load Tender, use original load reference, carrier and response. Use the partner guide to locate these values and check their allowed formats.

Does a successful EDI receipt mean 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 Mercury Gate / Ferguson Enterprises via MercuryGate EDI?

Separate line-haul, fuel and accessorial charges before comparing the invoice with the agreed rate. Test a second invoice for the same shipment and distinguish a revision from a duplicate. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.

Related references

Other Mercury Gate channels

Compare the document lists for other Mercury Gate channels.

Veritiv Operating Company via Mercury Gate 4 docs HD Supply via Mercury Gate 4 docs Amstan Logistics via Mercury Gate 4 docs Geodis Logistics via Mercury Gate 4 docs Mercury Gate (Generic)(Templates) 4 docs Atrium via Mercury Gate 3 docs THE CONTAINER STORE - OTR 3 docs Graphic Packaging Spot via Mercury Gate 4 docs Moen via Mercury Gate 4 docs Sartori Cheese (via MercuryGate) 4 docs Molnlycke Health Care via Mercury Gate 3 docs

Showing 11 of 11 references

Browse the full directory

Connect 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.

Book an EDI demo Explore the EDI platform