Odoo EDI for Walmart, Target and Home Depot suppliers

A Walmart, Target, or Home Depot compliance letter is a document deadline. The exchange it describes is an inbound 850, an outbound 855, an outbound 856, an outbound 810, and a 997 both ways. Odoo's EDI screen covers e-invoices such as Factur-X and Peppol, which will not produce that 856. The retail path Odoo documents is an SPS Commerce integration, priced by quote and installed as a project. For Business Central, Rand Group's EDI 365 page lists USD 2,000 setup and USD 69.99 per customer trading partner each month, as of October 2026.

The binding spec is the guide inside the portal that sent the letter: Retail Link, Partners Online, or the Home Depot supplier center. Public blogs are checklists. They are useful for knowing what to ask, and they are a poor substitute for the PDF attached to your vendor number.

What those four documents do in a warehouse

Think of the flow as one order moving through your building, with a receipt at each handoff.

The retailer sends an 850. Your team confirms it with an 855, ships against it with an 856, and bills it with an 810. Each of those messages gets a 997 so both sides know the file was structurally accepted. Content can still be wrong after a clean 997. Walmart's public drop-ship notes use a separate transaction, the 824 Application Advice, to report acceptance, rejection, or acceptance with changes of the content itself.

Vendor checklists, not a Walmart fee card, converge on that same core for Walmart: 850, 855, 856, 810, and 997, plus a connection through AS2 and Retail Link or the Global Enterprise Mailbox. The same write-ups add conditional documents: 860 for a buyer change, 846 inventory advice, 852 product activity, 753 and 754 for routing, and 940 and 945 when the program is drop ship. That matrix is published by Endless Commerce as a supplier checklist. Match it to the implementation guide on your supplier number before you pay to map a document you will never send.

Odoo's February 2024 SPS announcement lists a narrower supported set: 850 in and out, 855, 856, 810, 846, 945, and ASN shipping labels. Extra document types are case by case. If your letter names an 860 or an 852, put that on the quote. Do not assume the module you read about already includes it.

Home Depot does not publish a public fee card. Implementation write-ups aimed at suppliers describe a required set of 850, 855, 856, and 810, and some also name the 997. They also describe GS1-128 labels whose SSCC-18 must match the ASN, testing before live purchase orders, and the ASN sitting in Home Depot's system before the freight arrives. Dollar ranges on those pages are the publishers' estimates. Use the description of the document set as a question list for Supplier Hub, then price only what Hub assigns to you.

Why Odoo's EDI menu will not clear a retailer test

Odoo 18 documentation uses EDI for e-invoicing. The formats it names are Factur-X (CII), Peppol BIS Billing 3.0, and country invoice layouts. Peppol registration is free in Community, and Odoo can act as a Peppol access point and SMP for customer invoices, credit notes, vendor bills, and refunds. That is a real capability for companies that must send a European-style e-invoice. It does not build an ANSI X12 856, a GS1-128 label, or a carton hierarchy a DC will scan.

TrueCommerce's Odoo page states the same gap from the provider side: Odoo does not include a full EDI solution out of the box, and community modules typically need custom development per trading partner. Those modules, on that page's account, do not include compliance management or partner-map updates when the retailer changes a segment. Treat that as a vendor's description of the product it sells against, and still take the warning: a forum module that once parsed an 850 for a single partner will not track a year's worth of retailer map changes by itself.

The supported retail route Odoo describes is SPS Commerce. On that post there is no quick-setup guide. An official partner still buys a Partner Pack for the initial implementation help, and Odoo recommends its professional services team install and maintain the integration using success-pack hours. Hours rise as you add trading partners and document types. Pricing is a regional quote. There is no list price on the post.

SPS, in Odoo's announcement, is described as having 1,000,000+ trading connections, 12,000+ drop-ship connections, 1,000+ pre-qualified 3PLs, and connections to 3,500+ buying organizations, with Amazon, Target, and Walgreens named. Walmart and Home Depot are not named there. Confirm those two on the quote you sign, in writing, against the vendor numbers in your letter.

SPS's own Odoo product page (the Europe URL) says its team manages 9,000 retailer changes a year and that, with 50,000 trading partners already mapped, most connections can be ready in a matter of hours. Read that as a claim about map reuse when the partner map already exists. It is not a certification timeline, and it does not include your label printer, your pack hierarchy, or the test mailbox inside Retail Link.

A July 2026 thread on r/Odoo includes a comment that the SPS integration works and that "you need odoo.sh or on-premise in order for it to work". Another comment on that thread says the hard part is exception handling when an ASN fails or a partner changes a spec. If SPS is the route you want, ask the installer to show the connector running on the host you will pay for, before you schedule retailer testing.

A marketplace app is a different mandate

Search results for Odoo EDI mix two products. A Retail Link, Partners Online, or Home Depot supplier mandate wants X12 documents, labels, and a test cycle. A marketplace connector moves seller-center orders.

The Webkul Walmart connector on the Odoo Apps store imports Walmart Marketplace products and orders and exports listings and inventory. The listing does not describe an 850, an 856, an 810, AS2, or a GS1-128. Installing it will not satisfy a supplier compliance letter. If your buying team also sells on the Walmart.com marketplace, that connector can still be a separate project. Keep it off the EDI quote so the two scopes do not get billed as one.

The same split applies at Target. Target+ seller tools are not Partners Online vendor compliance. Ask which portal issued the deadline, and scope only that portal in phase one.

Walmart rules you can read without a Retail Link login

Walmart's public supplier developer docs publish X12 4010 implementation notes for drop-ship vendor documents. The set you can open without a login includes the 855 Purchase Order Acknowledgement, the 860 Purchase Order Change Request, and the 824. Sample interchanges on those pages use version 004010. The full 856 guide for EDI-B2B lives in Retail Link, which is what the food-traceability page tells suppliers.

On Walmart.com drop-ship 855s, line acceptance code IA is mandatory and must come before a later AR status. AR means accepted and released for shipment. Walmart's guide says AR is what stops the customer cancelling the line on the website. A map that jumps straight to a ship notice, or that sends AR before IA, is not following that drop-ship note. Have the test 855 reviewed line by line against those codes before anyone calls the connection certified.

For food and beverage, Walmart's enablement page says that as of 1 August 2025 suppliers must send an ASN containing FSMA 204 key data elements, label pallets with an SSCC-18 linked to that ASN, and label cases with GS1-128. If the letter is for a food or beverage item, the ASN key data elements and the pallet SSCC-18 are part of that mandate. Pull the 856 guide from Retail Link under EDI-B2B and give that file to whoever builds the map. A generic grocery ASN from another retailer will miss elements that page now requires.

One supplier working a DSDC integration wrote that "Walmart does ask for 1 ASN per Purchase Order". Ask your Retail Link contact whether your department wants one 856 per 850 before you design a consolidated shipment message.

Vendor checklists name AS2 alongside Retail Link or the Global Enterprise Mailbox. Your letter and the EDI questionnaire name the protocol for your vendor number. Have the provider show a successful test on that protocol, and ask whether a VAN mailbox is accepted for that same number.

Chargebacks: pull the fee card, then fix the ASN

Walmart, Target, and Home Depot do not leave a current public price list of EDI fines on the open web. Secondary write-ups disagree with each other, and they disagree with older articles that still rank. Use them to see which defects exist. Take the dollar schedule from the portal.

SupplierWiki, summarizing Walmart SQEP, places traditional EDI 856 defects in Phase 1 PO Accuracy and lists separate rows: No ASN Label (DSDC), ASN Not Downloaded (DSDC and Pharmacy), No ASN Received, ASN Error, and Late ASN (sent after the PO arrives at the DC). It states those ASN-related Phase 1 fines as a flat USD 25 per PO, and it is not Walmart's published schedule. An SPS Commerce community article from 21 June 2023, written when the author was at SupplierWiki, gives an older Phase 1 formula: ASN Not Downloaded at USD 200 per PO for DSDC and Dept 38 and USD 25 per PO for non-DSDC, with other Phase 1 defects at USD 200 per defect plus USD 1 per impacted case. Those two accounts do not match. Do not budget from either number. Download the current SQEP schedule from Retail Link and price your risk off that file.

Target's public site does not publish the vendor compliance fee schedule. Partners Online is login-gated. A Vendormint write-up dated 21 April 2025 says ASN availability moved on 4 May 2025 from 3 percent of COGS (minimum USD 150) to USD 0.75 per carton (minimum USD 100), with no minimum when the 856 is not in A status. Another public description still uses a percent-of-COGS ASN fine. Until you export the policy from Partners Online, both figures are someone else's reading.

What you can prepare, without the dollar card, is the dispute file. SupplierWiki's Target guide says an ASN-missing defect (never sent, sent after arrival, or unreadable) is disputed with the 856, the 997 of that ASN, an 824 if one exists, and the BOL or POD. Other defect rows on that guide use the 850, the 860, and the 810. If those files live only inside a provider portal that your team cannot export, you will lose disputes you were otherwise right about. Keep a copy of the outbound 856 and the inbound 997 where your shipper can reach them.

The failure mode suppliers describe is often a unit conversion. On a Retail Link thread, one vendor wrote: "I wracked up over $50,000 in ASN fines before I figured out what was wrong (unit of measure conversion was wrong)". A case pack of 12 mapped as eaches, or a pound mapped as a kilogram, will make the 856 disagree with the label and with the 850. The DC then records a shortage or an overage that your invoice does not match. Another comment on that thread says "it takes you 6 weeks to accomplish the simplest thing with them", and that other partners finish the same kind of change by email in about 30 minutes. Build the unit-of-measure cross-reference before the first test 856, because a fix after go-live waits on that ticket queue.

Labels have to come from the shipment that builds the 856. The SSCC-18 on the GS1-128 is the barcode the DC scans. If a separate label PC prints a different serial than the one in the message, the ASN can be on time and still fail as unreadable or mismatched. Food suppliers have this in writing from Walmart as of 1 August 2025: the pallet SSCC-18 has to be the one linked to the ASN. Run one test order through pick, pack, print, and transmit, then scan the label and compare the serial to the 856 segment before you call the test a pass.

What Business Central EDI costs when a price is public

You may be choosing the ERP while the compliance clock runs. A Business Central implementation can sit in front of the same retailers. The license decision for a distributor is covered in our guide to ERP for wholesale distributors. EDI is a separate line from the user licenses, and only one of the common apps publishes a US price.

EDI 365, as of October 2026, prices Business Central retail EDI like this:

• Initial setup (Amount: USD 2,000 once · What it covers: Remote training, Business Central setup, label printer configuration, document-flow monitoring)
• Customer trading partner (Amount: USD 69.99 per ISA per calendar month · What it covers: First 500 inbound 850, 875, or ORDERS; USD 0.05 per extra inbound PO; other documents unlimited; billed at zero volume)
• Vendor trading partner (Amount: USD 74.99 per month · What it covers: First 500 inbound 810 or INVOIC; USD 0.05 per extra inbound invoice)
• 3PL trading partner (Amount: USD 135 per month · What it covers: That partner's monthly connection)
• Standard onboarding (Amount: USD 500 per trading partner · What it covers: 850, 855, 856, 810, 820, 997, a basic SSCC-18 label, standard testing)
• Certification, if required (Amount: USD 950 · What it covers: Listed apart from the USD 500 onboarding)

A trading partner on that page is a unique EDI ID pair (the ISA). A large retailer often uses more than one ID, so the banner name on a slide can be several rows on the invoice. The monthly fee is charged even when you send nothing.

An older EDI 365 sheet on ERP Software Blog, dated 11 May 2023, used different monthly tiers and listed a VAN add-on at USD 55 per partner per month, with direct AS2 or SFTP at no extra communication charge. Do not add those 2023 figures to the table above. Price communication off the current Rand Group page and the provider's quote.

Two other Business Central apps cover the US and Canada and do not publish a price on AppSource. SPS Commerce's Fulfillment app supports Essentials and Premium and describes one connection to SPS, not a separate connection per retailer. TrueCommerce's North America app supports the United States, Canada, and Mexico, on Essentials and Premium, and says trading-partner maps, GS1-128 labels, and ASN compliance are handled in the ERP. The listing also says new suppliers can be onboarded in days. That is marketing copy on the listing, not a clock you can hold them to. Our roundup of Business Central apps from AppSource is the place to compare what else sits next to those two listings. Neither listing is a fee schedule.

SPS Commerce's 2025 10-K, filed around 25 March 2026, says Fulfillment revenue is a recurring subscription, contracts generally cancel on 30 to 90 days' notice, and one-time revenue includes a set-up fee specific to each trading-partner connection. The filing leaves the dollar amount of that fee off the page. Ask for it per ISA, as its own line for each connection.

TrueCommerce's only stable package prices we can cite are on its UK page: Starter from GBP 75 per month for one retailer, Essentials from GBP 379 per month for up to five trading partners, and Advanced from GBP 749 per month for 6 to 19 partners with managed services. The page says plans vary by region. Those pounds are not a US budget. Use them only as proof that a public menu exists somewhere, then insist on a US quote in dollars.

Why one retailer becomes a stack of trading partners

EDI 365's definition matches how suppliers talk. On a cost thread, one practitioner wrote: "Walmart for us is like equal to 4 trading partners. ... Home Depot times 6." Divisions, DSDC versus warehouse, and drop ship often carry different ISA IDs. Each ID is a map, a test, and a monthly line.

Assume, for a budget conversation only, that your letter names three banners and that the IDs break the way that comment describes: 4 Walmart IDs, 6 Home Depot IDs, and 1 Target ID, all of them customer partners who send you 850s. Assume each ID stays at or under 500 inbound POs a month, so the USD 0.05 overage never applies. Assume you buy standard onboarding and that nobody requires the separate certification line. Using the October 2026 EDI 365 rates:

The one-time setup is USD 2,000 for the app, not per retailer. Onboarding is 11 times USD 500, which is USD 5,500. The monthly partner fees are 11 times USD 69.99, which is USD 769.89, including months with no orders. Twelve months of partner fees are USD 9,238.68. First-year cash on those assumptions is USD 2,000 plus USD 5,500 plus USD 9,238.68, which is USD 16,738.68.

If all 11 IDs also require certification at USD 950, add USD 10,450. First-year cash becomes USD 27,188.68. If a single ID runs 200 POs past the 500 included, that month adds 200 times USD 0.05, which is USD 10, on top of the USD 69.99. The expensive surprise is the count of ISAs, not the per-PO overage.

The figures above are EDI 365 list prices as of October 2026. SPS, TrueCommerce, and an Odoo project are quoted on their own forms. Odoo's SPS post says the integration is a regional quote, with hours that rise as partners and document types rise. A three-banner letter can still be a dozen onboardings. Ask every bidder to list each ISA, each document, the label, the test cycle, and the monthly minimum as its own line. One blended implementation number hides the fourth Walmart division until testing week.

SPS's filing structure matters here. A set-up fee per trading-partner connection, plus a subscription you can cancel on 30 to 90 days' notice, means a banner you later drop still has a notice period. Get that notice in the order form before the first division goes live.

What the project includes before the first live PO

Map install is the short piece when the provider already holds that retailer's base map. Everything the retailer grades sits around it: pack quantities, ship-confirm timing, label print, and a person who reads rejects.

Odoo says there is no quick-setup document for the SPS module and that hours scale with partners and document types. SPS's Odoo page says most connections can be ready in a matter of hours when the map already exists. TrueCommerce's Business Central listing says new suppliers can be onboarded in days. A Home Depot implementation page describes testing before live purchase orders, and an ASN that must be in Home Depot's system before the truck arrives. A Retail Link user describes six weeks for a ticket. Those clocks measure different work. Ask the provider to date four milestones separately: map load, a passed test in the mailbox, label approval, and the first live PO.

Phase one, for a supplier who just received the letter, is usually one banner, one ship program, and the documents that banner will test. Later divisions wait until the first ISA posts a clean 856 that matches a scanned label. Splitting the work that way keeps a drop-ship 855, with Walmart's IA-then-AR sequence, from being designed in the same sprint as a DC ASN you have not read yet.

Someone on your payroll owns the mailbox daily. A 997 that rejects, or an 824 that accepts with changes, is a same-day job. The Odoo thread's point on exception handling is the operating model: when the ASN fails, who fixes the pack, who resends, and who tells the planner the PO is still open. A provider's support desk can transmit the file. Your warehouse lead decides whether a short pick reduces the 856 or the order waits for the missing units.

For the ERP around that flow, an Odoo implementation phased around finance, inventory, and then the retailer documents keeps the EDI map from becoming a custom side system. Warehouse steps that have to agree with the 856, including pick, pack, and the SSCC, belong with supply chain implementation so the label printer is configured against the same shipment the message uses. If Business Central wins the ERP decision, the same phase rule applies: user licenses first, then one certified ISA, then the next division.

Before you sign, ask each bidder for five artifacts: the document list taken from your portal guide, the ISA count, a sample 856 built from a real pack in your warehouse, the label that barcode-scans to that 856, and the name of the person who will read rejects during the first 30 days. If a bidder calls any of the five included, have them show it on your item, your case pack, and your retailer.

How Flectic can help

Flectic implements Odoo for companies of 20 to 100 people in the US and Canada, and discovery sets the scope and price of each phase before any retailer document goes live. Flectic sends a written proposal with a fixed price for each phase before work starts. Review the Odoo implementation approach, then Book a free discovery call with Flectic to scope the retailer documents your first phase must cover.

Sources

• Electronic invoicing (EDI), Odoo 18 documentation, Odoo, October 2026
• Odoo and SPS Commerce: Direct Integration for EDI, Odoo, February 2024
• Odoo EDI Integration, SPS Commerce, SPS Commerce, October 2026
• Odoo Integration, TrueCommerce, TrueCommerce, October 2026
• 855 Purchase Order Acknowledgement, Walmart, October 2026
• 824 Application Advice, Walmart, October 2026
• 860 Purchase Order Change Request, Walmart, October 2026
• Food traceability requirements, Walmart, October 2026
• Walmart EDI requirements checklist, Endless Commerce, October 2026
• ASNs and PO accuracy in SQEP, SupplierWiki, September 2025
• Calculating SQEP fines by defect, SPS Commerce, June 2023
• Target supplier compliance policy write-up, Vendormint, April 2025
• Compliance fine defects and dispute documentation at Target, SupplierWiki, October 2026
• Home Depot EDI partner notes, SBSATECH, October 2026
• EDI 365 for Dynamics 365 Business Central, Rand Group, October 2026
• EDI 365 add-on product sheet (11 May 2023), ERP Software Blog, May 2023
• SPS Commerce EDI for Dynamics 365 Business Central, Microsoft AppSource, October 2026
• TrueCommerce EDI and eCommerce (NA) for Business Central, Microsoft AppSource, October 2026
• TrueCommerce UK request-pricing page, TrueCommerce, October 2026
• SPS Commerce 2025 annual report, SPS Commerce, March 2026
• Odoo Multichannel Walmart Connector, Odoo Apps / Webkul, October 2026
• Odoo EDI integration thread, Reddit r/Odoo, July 2026
• Walmart Retail Link secrets, Reddit r/edi, October 2026
• TrueCommerce and SPS costs, Reddit r/edi, October 2026
• Walmart DSDC 850, 856, and 810, Reddit r/edi, October 2026