Skip to content

LXP (Armada) via Mercury Gate EDI
across every channel.

Stacksync wires the full LXP (Armada) via Mercury Gate trading-partner footprint, LXP (Armada) via Mercury Gate, into your ERP, WMS, or warehouse from one workspace.

Book a LXP (Armada) via Mercury Gate EDI demo Explore the LXP (Armada) via Mercury Gate catalog
Document types
4
X12 + EDIFACT
Channels
1
LXP (Armada) via Mercury Gate
Go-live median
5d
Across 240+ LXP (Armada) via Mercury Gate suppliers

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo

Document catalog

EDI documents we support for LXP (Armada) via Mercury Gate

4 transactions across 1 channel.

Document flow

How EDI documents flow with LXP (Armada) via Mercury Gate

Where each document sits in its trading cycle, based on the 4 document types LXP (Armada) via Mercury Gate trades across 1 channel.

Network context

LXP (Armada) via Mercury Gate trades through MercuryGate

EDI traffic with LXP (Armada) via Mercury Gate is routed over this network. Stacksync maintains certified connections to each, so one integration covers every partner reachable on them.

MercuryGate

35 channels · 26 trading partners on Stacksync

MercuryGate is a multimodal transportation management system used by shippers, brokers, and 3PLs; after Korber Supply Chain Software acquired it in August 2024 and rebranded in 2025, it is marketed as Infios Transportation Management. It is a TMS endpoint rather than a VAN: carriers integrate with the instance a shipper or 3PL operates. These channels carry tendering and settlement documents: load tenders out to the carrier, with tender responses, shipment statuses, and freight invoices (204, 990, 214, 210) returned.

LXP (Armada) via Mercury Gate channel on this network: LXP (Armada) via Mercury Gate

Most-traded documents
  • 204 35 ch
  • 214 35 ch
  • 990 35 ch
  • 210 24 ch
Also reachable via MercuryGate

How it works

Three steps to live LXP (Armada) via Mercury Gate EDI.

Stacksync handles the complexity of LXP (Armada) via Mercury Gate EDI so your team doesn't have to. Connect your ERP, WMS, or database through a simple API, we translate, validate, and deliver every transaction automatically.

  1. 01

    Connect your systems

    Plug Stacksync into your ERP, WMS, or database with a no-code connector. We handle authentication, schema discovery, and field mapping.

  2. 02

    Map to LXP (Armada) via Mercury Gate guidelines

    We ship pre-built mappings for every LXP (Armada) via Mercury Gate document type. Override any field, add custom validation, or extend with custom code.

  3. 03

    Send & receive in real time

    Stacksync translates, validates, and delivers every transaction over AS2, SFTP, or API. Watch every document flow live in the dashboard.

Why Stacksync

Built for EDI suppliers, not enterprise legacy.

From pre-built LXP (Armada) via Mercury Gate mappings to real-time compliance checks, Stacksync removes the friction from EDI, so you can focus on growing your business.

  • Pre-built mappings

    Stacksync ships native mappings for every LXP (Armada) via Mercury Gate document type. No more 6-week field-mapping projects.

  • Real-time monitoring

    Every transaction shows up in the dashboard the second it lands, with retry, revert, and replay built in.

  • No vendor lock-in

    Your data lives in your ERP/WMS/database. Stacksync is the translation layer, not the system of record.

  • Days, not months

    Most LXP (Armada) via Mercury Gate suppliers go live in under a week. We migrate from SPS Commerce, TrueCommerce, Cleo and IBM Sterling.

LEGACY EDI MIGRATION FUND

Still with a legacy EDI vendor? We cover the buyout.

Stacksync buys back your current contract with SPS Commerce, Cleo, TrueCommerce, or OpenText. No migration cost, no overlap billing.

Check your eligibility for the EDI migration fund
Migrate from SPS Commerce
Migrate from Cleo
Migrate from TrueCommerce
Migrate from OpenText
SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Trading partners

5,000+ trading partners.
And every channel covered.

We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.

E2open, LLC John Deere Costco Ryder The Home Depot Kleinschmidt Mercury Gate Walmart Dillard's Department Stores, Inc. Nordstrom JCPenney CVS Amazon Target Saks Fifth Avenue & Saks OFF 5th NEXCOM (Navy Exchange Service Command) Sprouts Farmers Market Ulta Beauty Macy's Master Electronics Aldi
Browse the full directory

FAQ

LXP (Armada) via Mercury Gate EDI questions

How long does it take to set up LXP (Armada) via Mercury Gate EDI with Stacksync?

Most suppliers are fully connected and processing live LXP (Armada) via Mercury Gate EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

What is LXP (Armada) via Mercury Gate EDI?

LXP (Armada) via Mercury Gate accepts EDI for 4 document types across 1 channel. Trading partners use EDI to exchange purchase orders, invoices, shipping notices, and acknowledgements with LXP (Armada) via Mercury Gate programmatically, Stacksync handles the entire EDI exchange, validation, and translation into your ERP, WMS, or database.

Which EDI standards does LXP (Armada) via Mercury Gate use?

LXP (Armada) via Mercury Gate uses X12. Stacksync supports both X12 (the dominant North American standard) and EDIFACT (the dominant European and global shipping standard) for every connected trading partner. Channel-specific implementation guidelines from LXP (Armada) via Mercury Gate are pre-built into the Stacksync connector and validated on every outbound transaction.

Which transaction codes does LXP (Armada) via Mercury Gate support?

LXP (Armada) via Mercury Gate supports 4 transaction codes in total. The most common include: 210, 214, 990, 204. Each code is mapped to its business-record equivalent (purchase order, ASN, invoice, etc.) inside Stacksync, so EDI exchanges land directly in your ERP or warehouse without manual translation.

How long does LXP (Armada) via Mercury Gate EDI integration take with Stacksync?

Most LXP (Armada) via Mercury Gate EDI integrations go live in 3 to 10 business days. The Stacksync team handles partner enrolment, channel certification, transaction-set mapping per LXP (Armada) via Mercury Gate's implementation guide, and end-to-end testing. Complex multi-channel deployments or custom transaction sets take 2 to 4 weeks. Cutover is zero-downtime and parallel-run validated.

Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own