Walmart Moves EDI Monitoring From Retail Link to Luminate

Walmart is pulling supplier-facing EDI transaction monitoring out of Retail Link and putting it into Luminate during 2026, while leaving core EDI setup where it's always been. According to SignalEDI's 2026 Walmart compliance guide, some EDI monitoring and transaction status tools are migrating from RetailLink to Luminate as of 2026, and new suppliers should set up both portals. If you're an EDI manager who has spent years pulling 856 status and chargeback data out of Retail Link, that's a workflow you need to start rebuilding now, not after the reports you rely on go quiet.

This is not the same event as Walmart's 2024 shakeup, and it's worth being precise about the difference. Back then, Walmart retired the Decision Support System app inside Retail Link and moved sales analytics to what's now called Scintilla. As 8th & Walton explains, that misconception gained traction around March 2024, when Walmart sunset the DSS features inside Retail Link and migrated analytics to Scintilla. That was a sales-and-inventory-reporting migration. What's happening in 2026 is narrower and more relevant to your job: it's EDI transaction status and monitoring specifically, not general analytics.

What's actually moving, and what isn't

Retail Link stays the system of record for the plumbing. Trading partner registration, AS2 certificate setup, and compliance testing all still run through it. Per SignalEDI, Retail Link is used for EDI setup and testing, chargeback dispute management, invoice status, inventory reports, and compliance scorecards, and all EDI configuration including trading partner agreements, AS2 setup, and test certification happens there. And after establishing AS2 connectivity, your EDI connection must be registered in the RetailLink Supplier Portal under the EDI setup section before testing can begin. None of that changes.

What's shifting is the layer where you'd normally check whether a specific 856 got rejected or an 810 kicked back a mismatch. Luminate wasn't built for that. It started as an analytics product, and Walmart has already shown it's willing to route AS2-adjacent data through Luminate's reporting tools rather than Retail Link's native screens. In the 2024 DSS transition, Walmart confirmed that access to EDI (AS2) feeds in DSS would be removed, with the data instead available in Walmart Luminate's Channel Performance Report Builder. That precedent is exactly what's playing out again with transaction status monitoring in 2026.

What hasn't changed

The document set and the protocol are untouched. Suppliers still send and receive the same four core transactions the same way. Per BOLD VAN's 2026 compliance checklist, Walmart's essentials remain four core documents (850 PO, 855 PO Acknowledgment due within 24 hours, 856 ASN sent before the shipment arrives, and 810 Invoice), with AS2 as the mandatory communication protocol and digital certificates tested before go-live. Certification testing runs through Retail Link, and chargebacks are automated regardless of which portal you happen to be staring at when the penalty hits. This is a visibility migration, not a standards change.

What EDI teams need to do, and by when

Luminate Basic costs nothing to activate. Walmart made Luminate Basic available to suppliers free of charge in December 2023, so there's no procurement delay standing between your team and getting a login. There's no excuse for waiting until reports vanish to find out where they went.

Why this adds real overhead, not just a login to bookmark

Walmart already runs suppliers on a tight compliance clock. Its EDI standards document gets revised annually, and updated versions are typically published annually, with suppliers expected to implement changes within 90 days of publication. Layer a portal migration on top of that 90-day cycle and you've got two moving targets instead of one, for teams that are often already managing Amazon Vendor Central, Target's supplier portal, and a half-dozen other retailer-specific tools at the same time. Walmart uses the ANSI X12 standard suppliers are used to, so the underlying data hasn't gotten harder to produce. It's just harder to find once it's produced.

The case for not relying on any single retailer's portal

This is where a two-portal Walmart reality becomes a bigger argument than just Walmart. Teams that already centralize transaction and shipment status across a neutral integration layer, rather than logging into each retailer's own dashboard, are less exposed every time a retailer reorganizes its internal tooling. That's the pitch behind managed EDI providers like SPS Commerce, TrueCommerce, and Cleo, and it's also increasingly true of carrier and transport-visibility platforms such as Cargoson that pull order and shipment status into one place instead of forcing you back into a retailer's native portal every time something changes.

Next steps

• Confirm your Luminate access today. Don't wait for a Retail Link report to disappear before you go looking for its replacement.
• Document which EDI reports currently live in Retail Link and where their Luminate equivalent will sit.
• Assign clear ownership between your EDI analyst team and category managers for each portal, since Luminate wasn't historically an EDI team's tool.
• Keep your AS2 setup, certification, and chargeback workflows exactly where they are. Nothing about the protocol or document set has changed.