Retail integration

Walmart EDI integration and automation

A practical guide for suppliers connecting to Walmart, organized by program (stores and DCs, Walmart.com drop-ship, direct store delivery and Marketplace), covering documents, connection options and ERP integration.

At a glance

Walmart integration, in three pictures

The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific Walmart program or a customer relationship.

Illustration of a retail storefront with an awning and a shopping bag, representing the retail industry that Walmart operates in.
Industry. Retail: where Walmart operates.
Workflow diagram: your ERP and warehouse systems exchange documents with Walmart through ECOM. You send 855, 856, 846, 810; you receive 850, 860, 820, 852; 997 acknowledgments go both ways. Your systems ERP · warehouse · finance ECOM integration map · validate · connect · monitor Walmart 855 856 846 810 855 856 846 810 850 860 820 852 850 860 820 852 997 both ways
Workflow. Documents in each direction. Orange: you send. Blue: you receive. Typical, not confirmed.
Comparison diagram: without integration, documents are re-keyed, files are emailed and rejections are found late; with ECOM, documents are mapped to your ERP, validated and monitored, and exceptions are visible early. Without integration Orders re-keyed by hand Files emailed or uploaded Rejections found late With ECOM Documents mapped to your ERP Every file validated and monitored Exceptions visible early
Outcome. From manual handling to a monitored flow. No figures: results depend on your setup.

Talk to an EDI/API Expert about Walmart

Tell us which documents you exchange with Walmart, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with Walmart.

  • Review of Walmart's requirements with you, once you have them
  • EDI and API integration with your ERP and warehouse systems
  • Monitoring and managed service after go-live, if you want it

Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.

Takes about 30 seconds. Phone and note are optional.

Your request is about

Trading partner
Walmart

When should we talk?

Times are in your time zone. We use this to schedule the conversation.

We use your details only to respond to your request. See our privacy notice. Prefer to talk? Call Sales at 972-836-7750.

Integration and onboarding

How Walmart integration fits your systems

Your systemsERP, WMS and accounting
ECOMMapping, validation, connectivity and monitoringSFTP · AS2 · EDI service provider or VAN
WalmartIts program, documents and requirements
  1. ConfirmConfirm your Walmart program, role and the documents it requires.
  2. MapMap each document to your ERP fields and business rules.
  3. ConnectConfigure the connection and security the program needs.
  4. TestTest against the applicable specifications and acknowledgments.
  5. Go liveGo live with monitoring, alerts and exception handling.
Typical implementation path. Exact requirements are confirmed against the applicable specifications during onboarding.

Overview

Understanding Walmart integration

Who this is for: Suppliers and brands selling to Walmart stores, clubs or Walmart.com, including drop-ship vendors and the 3PLs and EDI teams that support them.

Walmart is one of the largest retail trading partners in the world, and it relies on electronic data interchange to manage the flow of orders, shipments and invoices with its suppliers. For most suppliers, the relationship runs on a small set of core X12 documents: purchase orders from Walmart, ship notices that describe what is on the truck before it arrives, and invoices that request payment. Functional acknowledgments confirm that each document was received.

What makes Walmart integration demanding is not the number of documents but the precision expected in each one. Ship notice contents must match the cartons, pallets and labels that physically arrive, and identifiers must line up with the original purchase order. Suppliers that sell through more than one Walmart program, such as store replenishment and drop-ship fulfillment for Walmart.com, often maintain different document flows for each program.

Walmart publishes its drop-ship vendor (DSV) EDI specifications openly on its developer site, while store and distribution center guides are in Retail Link behind the supplier login, and Marketplace sellers connect mainly through Walmart's Marketplace APIs. Because requirements differ by program and change over time, suppliers should treat Walmart's current specifications for each program as the authoritative reference and build integrations that are easy to update.

Program summary

What Walmart asks of suppliers

A summary in ECOM's own words. Requirements vary by program and change over time, so confirm the details with Walmart during setup.

Standard
X12 4010
Order types
Drop-ship to consumer · Direct to store
Business units
Walmart.com drop ship

Labels and pallets

  • Direct-to-store shipments use a UCC-128 label printed at 4 by 6 inches, with one label per pack.

Testing

  • Testing covers the 855, 856 and 846 flows along with the label.

Requirements at a glance

What Walmart publishes for suppliers

Walmart publishes its drop-ship vendor (DSV) EDI specifications for Walmart.com openly on its developer site, in X12 version 4010. Specifications for store and distribution center suppliers are in Retail Link under EDI B2B, behind the supplier login, and Walmart's public food traceability page describes the ship notice food suppliers must send. We checked both sources on October 30, 2026.

Walmart developer site

Public EDI specifications, samples and file conventions for Walmart.com drop-ship vendors.

Public Official site

Retail Link and Supplier One

Supplier systems for EDI B2B guides, item setup and ship notice dashboards; the public supplier requirements page links to Walmart's standards.

Official site

Business units and channels

Walmart business units suppliers trade with

Large companies often handle each business unit or channel as a separate EDI relationship, with its own documents, guides and setup. Confirm with Walmart which of these applies to you before mapping.

Stores and distribution centers

Warehouse (DC) orders

Wholesale orders shipped in bulk pallets to Walmart distribution centers, with strict 856 pallet structure, GS1-128 (UCC-128) labels and DC appointment windows.

Documents: 850,856,810

From ECOM's trading-partner records; confirm your program with Walmart

Drop-ship

Drop-ship vendors (DSV)

Single-parcel orders the supplier ships to Walmart.com customers. Each customer order has its own document trail, and frequent 846 inventory updates keep Walmart.com in stock.

Documents: 850,860,855,856,846,997

Confirmed on a public Walmart page

Stores and distribution centers

Direct store delivery (DSD)

Local or perishable goods delivered straight to Walmart stores, bypassing the distribution centers, with store-level documents and receiving.

From ECOM's trading-partner records; confirm your program with Walmart

Marketplace

Marketplace sellers

Third-party sellers listing on Walmart.com as the merchant of record, connected mainly through Walmart Marketplace APIs rather than EDI documents.

From ECOM's trading-partner records; confirm your program with Walmart

Workflows

Typical Walmart business workflows

The steps summarize the documents below. Where a step is not in Walmart's published documents, it reflects common practice.

Stores and DCs (from Retail Link guides)

  1. 1Receive 850 purchase order
  2. 2Plan to the DC appointment
  3. 3Ship with GS1-128 labels
  4. 4Send 856 ship notice
  5. 5Send 810 invoice

Walmart.com drop-ship (DSV)

  1. 1Receive 850 customer order
  2. 2Send 855 with IA then AR
  3. 3Process any 860 change
  4. 4Ship to the consumer
  5. 5Send 856 ship notice
  6. 6Send 846 inventory

Marketplace sellers

  1. 1List items through Marketplace APIs
  2. 2Receive orders by API
  3. 3Ship and confirm by API
  4. 4Reconcile settlements

Documents and APIs

Walmart documents by program

Every document this guide names, with the program it applies to and its status. Required, optional and conditional come from Walmart's published documents cited below; documents marked general guidance are common in this industry but not confirmed for Walmart.

DocumentNameDirectionProgramStatusPurpose
850 Purchase Order You receive from Walmart Stores and DCs, Drop-ship (DSV) Named; level not stated Walmart orders merchandise for stores and distribution centers, or passes on a Walmart.com customer order to a drop-ship vendor.
860 Purchase Order Change You receive from Walmart Drop-ship (DSV) Named; level not stated Walmart.com sends order changes to drop-ship vendors; the 850 is not used for changes.
855 Purchase Order Acknowledgment You send to Walmart Drop-ship (DSV) RequiredIA on every line, then AR Drop-ship vendors acknowledge each line with IA, then release it for shipment with AR.
856 Advance Ship Notice You send to Walmart Drop-ship (DSV); food suppliers (stores, DCs, Sam’s Club) ConditionalRequired for food shipments, with FSMA 204 key data elements; drop-ship level not stated Describes the shipment before arrival: pallet and carton structure for DC orders, the customer shipment for drop-ship, and FSMA 204 traceability data for food.
846 Inventory Inquiry/Advice You send to Walmart Drop-ship (DSV) Named; level not stated Drop-ship vendors report how much of each item they can ship, so Walmart.com availability matches stock.
810 Invoice You send to Walmart Stores and DCs General guidance Requests payment for goods shipped to stores and DCs. The drop-ship EDI file list has no 810, so confirm how drop-ship orders are invoiced.
820 Payment Order/Remittance Advice You receive from Walmart Not stated General guidance Explains payments and deductions applied to invoices.
852 Product Activity Data You receive from Walmart Not stated General guidance Shares sales and inventory data where provided.
997 Functional Acknowledgment Both directions Drop-ship vendors (DSV) Named; level not stated Confirms each document was received and is syntactically valid.
How documents flow between a supplier and WalmartSequence diagram of documents between a supplier and Walmart: 850 Purchase Order from Walmart, 860 Purchase Order Change from Walmart, 855 Purchase Order Acknowledgment to Walmart, 856 Advance Ship Notice to Walmart, 846 Inventory Inquiry/Advice to Walmart, 810 Invoice to Walmart, 820 Payment Order/Remittance Advice from Walmart, 852 Product Activity Data from Walmart and 997 Functional Acknowledgment to Walmart.How documents flow between a supplier and WalmartThe documents on this page in a typical order. Your Walmart program and guides decide which applySupplierWalmart850 Purchase Order860 Purchase Order Change855 Purchase Order Acknowledgment856 Advance Ship Notice846 Inventory Inquiry/Advice810 Invoice820 Payment Order/Remittance Advice852 Product Activity Data997 Functional AcknowledgmentEach side acknowledges what it receivesDocuments as listed on this page, checked 2026-10-30. Walmart's current guides are the authoritative reference.
How documents flow between a supplier and WalmartSequence diagram of documents between a supplier and Walmart: 850 Purchase Order from Walmart, 860 Purchase Order Change from Walmart, 855 Purchase Order Acknowledgment to Walmart, 856 Advance Ship Notice to Walmart, 846 Inventory Inquiry/Advice to Walmart, 810 Invoice to Walmart, 820 Payment Order/Remittance Advice from Walmart, 852 Product Activity Data from Walmart and 997 Functional Acknowledgment to Walmart.How documents flow between asupplier and WalmartThe documents on this page in a typical order.Your Walmart program and guides decide whichapplySupplierWalmart850 Purchase Order860 Purchase OrderChange855 Purchase OrderAcknowledgment856 Advance Ship Notice846 InventoryInquiry/Advice810 Invoice820 PaymentOrder/Remittance Advice852 Product Activity Data997 FunctionalAcknowledgmentEach side acknowledges whatit receivesDocuments as listed on this page, checked2026-10-30. Walmart's current guides are theauthoritative reference.

Read from top to bottom. Solid arrows are documents Walmart names in its own public documentation; dashed arrows are common practice that this page could not confirm for Walmart, or acknowledgments. The order is typical, not a Walmart rule: programs such as vendor direct to consumer use their own documents and timing.

Expand diagram Download SVG

Document by document

What each Walmart document needs

For each document: what it does for you as the supplier, what Walmart's own documents say about it (with the source and its date), and general EDI practice that helps, labelled as such. Your Walmart mapping guide for your version is the final word on fields and codes.

850

Purchase Order

You receive · Walmart.com drop-ship

Each Walmart.com customer order reaches a drop-ship vendor as an 850, with the ship-to customer, the items and the carrier details.

What Walmart states

General EDI practice

  • Return a 997 for each 850 and create the order in your ERP before you acknowledge it with the 855.

How the 850 works in X12

855

Purchase Order Acknowledgment

You send · Walmart.com drop-ship

The 855 tells Walmart.com, line by line, whether you accept, cancel or reject each item, and when it is released for shipment.

What Walmart states

General EDI practice

  • Send the 855 as soon as stock is confirmed, and use the rejection codes rather than leaving lines unanswered.

How the 855 works in X12

856

Advance Ship Notice

You send · Walmart.com drop-ship; stores, DCs and Sam's Club food suppliers

The 856 tells Walmart what you shipped and how. For drop-ship it confirms the customer shipment; for food it carries the traceability data.

What Walmart states

General EDI practice

  • Generate the 856 from your shipping system so carrier, package and item details match what left the dock.

How the 856 works in X12

846

Inventory Inquiry/Advice

You send · Walmart.com drop-ship

The 846 tells Walmart.com how much of each item you can ship, so online availability matches your stock.

What Walmart states

General EDI practice

  • Send available-to-promise quantities on a fixed schedule so customers cannot order stock you do not have.

How the 846 works in X12

997

Functional Acknowledgment

Both directions

A 997 confirms a file arrived and passed syntax checks, and Walmart.com sends one for each file you send.

What Walmart states

General EDI practice

  • Watch for rejected groups and re-send the whole group after fixing the error.

How the 997 works in X12

Deductions

What Walmart charges for EDI problems

Walmart's public pages do not list chargeback amounts for EDI problems. The food traceability page states the consequence of missing traceability data, without an amount.

ProblemCharge stated by WalmartSource
Insufficient food traceability data, such as a missing ASN with FSMA 204 key data elementsFreight may be held or rejected, and penalties levied; no amount statedSource: Walmart food traceability requirements (update of Oct 2, 2025), Oct 2, 2025

General practice for handling deductions

  • Monitor the ship notice dashboards in Retail Link weekly so traceability gaps are fixed before penalties.

Onboarding

Getting set up with Walmart, step by step

Steps with a source come from Walmart's own onboarding material; the others are general practice that keeps the project on track.

  1. Confirm your Walmart programs

    Store and DC, Walmart.com drop-ship and Sam's Club each have their own documents and guides.

    General EDI practice, not a stated requirement
  2. Get the specifications

    Drop-ship specifications are public on Walmart's developer site; store and DC guides are in Retail Link under EDI B2B.

    Source: Walmart developer site, EDI interface for drop-ship vendors, as checked, Oct 30, 2026
  3. Choose how to connect

    Drop-ship vendors can use SFTP with Walmart's file naming convention, or AS2 or a solution provider without it.

    Source: Walmart developer site, EDI interface for drop-ship vendors, as checked, Oct 30, 2026
  4. Set up items in Supplier One

    Food suppliers declare, item by item, whether each item is subject to FSMA 204 in Supplier One.

    Source: Walmart food traceability requirements (update of Oct 2, 2025), Oct 2, 2025
  5. Test and go live

    Test each document against Walmart's specifications and watch the 997s and dashboards from the first live file.

    General EDI practice, not a stated requirement
Getting set up with WalmartFlow diagram of 5 onboarding steps with Walmart: Confirm your Walmart programs, Get the specifications, Choose how to connect, Set up items in Supplier One and Test and go live.Getting set up with WalmartThe onboarding steps on this page, in order1ConfirmprogramsGeneral practiceStep 12GetspecificationsWalmart sourceStep 23ChooseconnectionWalmart sourceStep 34Set up itemsWalmart sourceStep 45Test and goliveGeneral practiceStep 5Onboarding steps as listed on this page, checked 2026-10-30. Walmart's current onboarding instructions are the authoritative reference.
Getting set up with WalmartFlow diagram of 5 onboarding steps with Walmart: Confirm your Walmart programs, Get the specifications, Choose how to connect, Set up items in Supplier One and Test and go live.Getting set up with WalmartThe onboarding steps on this page, in order1Confirm programsGeneral practiceStep 12Get specificationsWalmart sourceStep 23Choose connectionWalmart sourceStep 34Set up itemsWalmart sourceStep 45Test and go liveGeneral practiceStep 5Onboarding steps as listed on this page, checked2026-10-30. Walmart's current onboardinginstructions are the authoritative reference.

Read left to right, or top to bottom on a phone. 3 of the 5 steps come from Walmart's own published material and are marked "Walmart source"; the rest are general practice. Week numbers are given only where Walmart states them.

Expand diagram Download SVG

Verification

What we checked, and where

Each statement below shows its source and the date we checked it. Statements we could not confirm from an official Walmart source are labelled as such.

TopicStatementEvidenceChecked
StandardsWalmart.com drop-ship EDI specifications use X12 version 4010, with ~ as segment terminator, * as element separator and > as sub-element separator.Confirmed on a public Walmart pageOct 30, 2026
DocumentsDrop-ship vendors receive 850, 860 and 997 files from Walmart.com and send 855, 856, 846 and 997 files.Confirmed on a public Walmart pageOct 30, 2026
ConnectivityDrop-ship vendors can connect by SFTP, using Walmart's file naming convention, or through AS2 or solution providers, where the convention is not required.Confirmed on a public Walmart pageOct 30, 2026
DocumentsIn the drop-ship 855, line acceptance (IA) is mandatory, and release for shipment (AR) is a second status that must come after IA.Confirmed on a public Walmart pageOct 30, 2026
Shipping and labelsSince August 1, 2025, food suppliers to Walmart and Sam's Club must send an ASN with FSMA 204 key data elements, an SSCC-18 pallet label linked to the ASN and GS1-128 case labels.Confirmed on a public Walmart pageOct 30, 2026
DocumentsWalmart publishes perishable and goods-for-resale 856 guides in Retail Link under EDI B2B.Named in a public Walmart document title; contents not reviewedOct 30, 2026

Available only after supplier login

Walmart keeps these behind its supplier portal. This guide does not reproduce them; use your own Walmart access or ask your Walmart contact.

  • Retail Link EDI B2B guides for store and DC suppliers, including the goods-for-resale and perishable 856
  • Supplier One item setup, including the FSMA 204 traceability attribute
  • The ship notice and food traceability dashboards in Retail Link

Not confirmed

We could not confirm these from an official public source, so we do not state them as Walmart requirements.

  • The full document set and versions for store and DC suppliers, which are in Retail Link
  • How drop-ship vendors invoice, since the drop-ship EDI file list has no 810
  • Chargeback amounts for store, DC or drop-ship EDI problems
  • Testing steps and timelines for each program

Checklist

Walmart EDI readiness checklist

  1. Confirm which Walmart programs you supply: Walmart.com drop-ship, stores and DCs, or Sam's Club.
  2. For drop-ship, download the 850, 855, 856, 860, 846 and 997 specifications from Walmart's developer site.
  3. Choose SFTP, AS2 or a solution provider, and follow the file naming convention if you use SFTP.
  4. Use Walmart's delimiters: ~ for segments, * for elements and > for sub-elements.
  5. Send the 855 with IA before AR on every drop-ship line.
  6. Process 860 changes; Walmart does not use the 850 for changes.
  7. For food, include the FSMA 204 key data elements in the 856 and link the SSCC-18 pallet label to it.
  8. For store and DC programs, get the EDI B2B guides from Retail Link.

Connectivity and contacts

How Walmart connects with suppliers

What Walmart's public documents say about networks and setup, and the department contacts it publishes for suppliers. Connection credentials and trading-partner IDs are exchanged with Walmart during setup and are never shown on this page.

What Walmart states about connecting

Avoid these

Common mistakes with Walmart EDI

Sending AR before IA

In the drop-ship 855, release for shipment (AR) must follow the mandatory line acceptance (IA), even in the same file.

Source: Walmart developer site, 855 Purchase Order Acknowledgement (drop-ship), as checked, Oct 30, 2026

Waiting for a new 850 after a change

Walmart.com sends order changes as an 860; the 850 is not used for changes.

Source: Walmart developer site, 850 Purchase Order (drop-ship), as checked, Oct 30, 2026

Wrong file names over SFTP

SFTP files must follow Walmart's naming pattern with your DSV ID, GMT date and time and a random number.

Source: Walmart developer site, EDI interface for drop-ship vendors, as checked, Oct 30, 2026

Food ASNs without traceability data

Food shipments need the FSMA 204 key data elements in the ASN and an SSCC-18 pallet label linked to it.

Source: Walmart food traceability requirements (update of Oct 2, 2025), Oct 2, 2025

Connectivity

Your options for connecting to Walmart

  • SFTP

    Walmart.com drop-ship vendors can connect by SFTP, following Walmart's file naming convention with the DSV ID, GMT date and time and a random number.

    From Walmart's published documents

  • AS2

    A direct, encrypted connection between your EDI platform and Walmart; for drop-ship, Walmart's file naming convention is not required over AS2.

    From Walmart's published documents

  • EDI service provider or VAN

    Walmart's developer site lists solution providers as a drop-ship connection option; the provider maintains the connection on your behalf.

    From Walmart's published documents

  • WebEDI through a provider

    Smaller suppliers can handle Walmart documents in a browser through a WebEDI service, with the provider holding the connection to Walmart.

    General guidance

Challenges

Common integration challenges

  • Ship notice accuracy

    The 856 must reflect exactly what was shipped, including carton and pallet structure, or receiving and payment can be disrupted.

  • Program differences

    Stores and DCs, Walmart.com drop-ship, DSD and Marketplace each use different documents, connections and rules, so maps, tests and processes must be kept separate per program.

  • Label and data alignment

    Carton and pallet labels need to carry the same identifiers as the ship notice, which requires tight integration with warehouse data.

  • Keeping up with changes

    Requirements evolve, so integrations need to be easy to update and re-test without disrupting production.

Automation options for Walmart suppliers

Four ways to automate. One foundation.

Walmart's requirements on this page cover the 850, 860, 855, 856, 846 and 997. ECOM helps you automate them, meet Walmart's labeling and ship notice requirements, and see what needs action. Walmart sets its program's rules; ECOM confirms which options fit yours.

PRISM Supply Chain Automation Foundation

One platform beneath every option. Use one, or combine them for different partners and documents.

Compliance and actionable visibility

Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.

Discuss Your Trading Partner Requirements

Connect Walmart documents to your ERP

ECOM can integrate Walmart documents with your ERP through APIs, IDocs, database interfaces or flat files, so purchase orders post as sales orders and ship notices and invoices are generated from ERP and warehouse data.

Solution

Drop-Ship Automation

Automate the Walmart.com drop-ship flow: 850 and 860 in, 855 IA and AR, 856 and 846 out.

Zero Trust for supplier data exchange

Zero Trust EDI and MFT for your Walmart connection

Supplier exchanges with Walmart carry orders, ship notices, invoices and item data. A Zero Trust design assumes no connection, file or user is safe by default.

ECOM has implemented Zero Trust EDI and Zero Trust MFT in retail.

For supplier exchanges this means each supplier and vendor connection has its own scope, orders, ship notices and invoices are verified on arrival, late or altered files are noticed early, and the transfer log helps answer deduction and security-review questions.

  • Authentication

    Every connection proves who it is: partner-specific accounts with SSH keys or certificates over SFTP, FTPS, HTTPS or AS2, never a shared login.

    Business outcome: A lost or reused credential affects one partner, not all of them.

  • Least privilege

    Each partner and user reaches only its own folders, file types and actions. Internal user permissions are managed centrally and reviewed with you.

    Business outcome: A mistake or compromise in one account stays limited to what that account could reach.

  • Isolation

    Partners are kept apart by account and file area. Where your design calls for it, a proxy or DMZ keeps outside connections away from internal systems. The design follows your architecture.

    Business outcome: Outside connections do not land directly on your internal systems.

  • Encryption

    Encrypted protocols in transit and PGP for files at rest. Encryption protects the data. It is one control, and not Zero Trust on its own.

    Business outcome: Less exposure if a file is intercepted or a file store is reached.

  • Certificate and key management

    Partner keys and certificates are managed centrally. Renewal and rotation are planned with you, so an expiring certificate does not stop a flow.

    Business outcome: Fewer outages caused by an expired certificate or key.

  • Monitoring and access controls

    Real-time transfer status and alerts for late, missing or failed files, so unexpected access or a broken flow is seen quickly.

    Business outcome: Late, missing or failed files are noticed early, before they hold up late shipments or deductions.

  • Audit trail

    Every transfer is logged with sender, receiver, time and outcome, which supports your own review and audit work.

    Business outcome: You can answer who sent what and when, for your own audits and partner reviews.

What this means for your data

Supplier and vendor access

Each supplier, 3PL and vendor connection has its own account and limited scope, so one compromised credential cannot reach other partners' data.

Orders, ship notices and invoices

Documents are verified when they arrive and every transfer is logged, so a missing or altered file shows up quickly.

Portals and file drops

Replace shared logins and open folders with named accounts, reviewed on a schedule you set.

Zero Trust is an approach, not a product or a certification. ECOM covers the EDI and file-transfer side. Your identity, network and endpoint controls stay yours, and so does the assessment of your own compliance obligations. ECOM does not guarantee compliance or any security outcome. Walmart may set its own security requirements, which come first.

Next step

Get help with your Walmart program

Each request goes to an ECOM EDI specialist with Walmart's name attached, so the reply starts from your program.

  • Review Walmart's requirements

    Send us Walmart's guide or your program details; we explain the documents, rules and options for meeting them.

    Request a requirements review
  • Connect Walmart to your ERP

    Orders in, ship notices and invoices out, from the ERP and warehouse systems you already run.

    Discuss ERP integration
  • Testing and certification

    Build, test and certify each Walmart document, then go live with monitoring from the first file.

    Plan testing and certification
  • Shipping labels and ASNs

    Labels and ship notices that match Walmart's rules, to help avoid receiving problems and compliance deductions.

    Review shipping compliance

Walmart integration FAQs

Which EDI documents do Walmart.com drop-ship vendors use?

Walmart's developer site lists 850, 860 and 997 files from Walmart.com, and 855, 856, 846 and 997 files from the vendor, in X12 version 4010.

How do drop-ship vendors connect to Walmart.com?

By SFTP using Walmart's file naming convention, or through AS2 or a solution provider, where the naming convention is not required.

Where are Walmart's store and DC EDI guides?

In Retail Link under EDI B2B, behind the supplier login. Walmart's food traceability page names the goods-for-resale and perishable 856 guides there.

What does Walmart require from food suppliers?

An ASN with FSMA 204 key data elements for every food shipment, SSCC-18 pallet labels linked to the ASN and GS1-128 case labels, since August 1, 2025.

What is the IA and AR rule in the Walmart 855?

Each drop-ship line must first be acknowledged with IA. Release for shipment (AR) is a second status and must come after IA, even in the same file.

Do small suppliers need EDI software to work with Walmart?

Not necessarily. A WebEDI service lets smaller suppliers receive orders and send ship notices and invoices from a browser, with the provider handling the connection to Walmart.

Can ECOM integrate Walmart EDI with our ERP?

Yes. ECOM integrates Walmart documents with ERP and warehouse systems so orders, ship notices and invoices flow without re-keying, and monitors the flow in PRISM-SCV.

Is ECOM a Walmart-certified provider?

This page is an integration guide. It does not indicate a certification or partnership with Walmart. ECOM builds Walmart integrations to Walmart's published requirements.

Sources and accuracy

This guide summarizes publicly available information as of November 2026. Walmart sets its own requirements and can change them at any time; your Walmart implementation guide, supplier portal or account contact is the authoritative source for your program.

Walmart documents cited on this page

Learn the general practice

Request Walmart integration assistance

Tell us about your Walmart program, documents and ERP. We will outline the connection, mapping and testing plan.