Walmart and NetSuite Integration for Beauty Brands: Automate Orders, Inventory, and Settlements

To integrate Walmart and NetSuite for a beauty brand, eZintegrations receives Walmart EDI 850 purchase orders via AS2, maps each UPC to the corresponding NetSuite item internal ID via a cross-reference table, creates a NetSuite sales order using SuiteTalk REST (POST /services/rest/record/v1/salesOrder), generates and transmits the EDI 855 acknowledgment with inventory-validated quantities, triggers the EDI 856 ASN within 15 minutes of carrier scan with pre-validation against the 855, creates the EDI 810 invoice from the NetSuite billing document, and posts Walmart settlement payments (including OTIF deductions and SQEP fines) to the correct NetSuite GL accounts automatically. The full cycle from Walmart PO receipt to NetSuite payment posting requires zero manual touchpoints for compliant shipments.

---

TL;DR

• Walmart uses EDI (ANSI X12 over AS2): 850 PO, 855 acknowledgment, 856 ASN, 810 invoice, 846 inventory. NetSuite uses SuiteTalk REST. Bridging these two systems is the full Walmart-NetSuite integration challenge.
• The five NetSuite record types involved: sales order (from Walmart 850), item fulfilment (triggers 856 ASN), invoice (triggers 810), inventory adjustment (from 846 update cycle), and journal entry (for Walmart settlement deductions).
• The settlement reconciliation problem is the most painful and least-automated part of Walmart-NetSuite for beauty brands: Walmart deducts OTIF fines, SQEP fines, and pricing adjustments directly from the EFT payment. NetSuite’s AR balance shows the open invoice. The deduction creates a discrepancy that finance teams resolve manually every quarter.
• eZintegrations automates the complete Walmart-NetSuite cycle: EDI document handling (AS2), NetSuite record creation (SuiteTalk REST), inventory sync (NetSuite → EDI 846), and settlement deduction posting (Walmart HighRadius deduction → NetSuite GL).
• UPC-to-NetSuite item ID mapping is the critical configuration element (equivalent to ASIN-to-Material mapping in the Amazon-SAP integration).
• Automation Hub templates for Walmart-NetSuite: 4-6 hours to configure.

---

Why Walmart-NetSuite Integration Is a Different Problem From Other Retail Integrations

Your NetSuite system handles every aspect of your beauty brand’s finances. Revenue, COGS, AR, AP, inventory valuation, project accounting. It is your source of financial truth.

Walmart is your largest retail customer. 18 purchase orders per quarter, each covering 8-15 beauty SKUs across multiple shades. Walmart represents 40% of your retail revenue.

But Walmart does not send emails. Walmart does not use a vendor portal you can download from. Walmart sends EDI 850 purchase orders to your AS2 endpoint. And your NetSuite does not have a native AS2 connection.

Every time a Walmart PO arrives, your EDI coordinator downloads it from your EDI provider’s portal, translates the PO into a spreadsheet, and manually enters a NetSuite sales order. It takes 25-45 minutes per PO. At 18 POs per quarter, that is 8-14 hours of sales order entry per quarter, not counting the inventory acknowledgment, the ASN generation, or the invoice.

Then the settlement arrives. Walmart pays 18 invoices across the quarter as a single EFT payment with a remittance advice that lists deductions: OTIF fines from two late shipments, a SQEP deduction for an ASN carton count mismatch, and a pricing adjustment from invoice 810 that did not match the 850. Your finance team spends 3-5 hours tracing each deduction back to the original NetSuite invoice and posting the deductions to the correct GL accounts.

This is the Walmart-NetSuite integration problem. It is not just order entry. It is the complete cycle: PO to order to fulfilment to invoice to payment to deduction reconciliation.

---

The Five NetSuite Records in a Walmart Order Cycle

Every Walmart purchase order creates and progresses through five distinct NetSuite records. Understanding this chain is the foundation for designing the integration.

Record 1: Sales Order Created from the Walmart EDI 850. Contains: Walmart as the customer (or a named subsidiary), line items (each UPC mapped to a NetSuite item), ordered quantities, agreed unit prices, required delivery date (from the MABD in the 850), and the Walmart PO number stored in the otherRefNum or externalId field for cross-reference.

Record 2: Item Fulfilment Created when the order is ready to ship (from the warehouse or 3PL). Contains: shipped quantities per line, carrier SCAC code, tracking number, and actual ship date. When the item fulfilment is saved in NetSuite, this event triggers the EDI 856 ASN generation and transmission to Walmart.

Record 3: Invoice Created from the item fulfilment (typically auto-generated by NetSuite billing run). Contains: billable quantities (matching the shipped quantities), agreed prices from the sales order, and the Walmart PO reference. When the invoice is created, it triggers the EDI 810 invoice transmission to Walmart.

Record 4: Inventory Adjustment Created after inventory-affecting events: when the Walmart PO commits stock, when the item fulfilment ships, or when a return arrives. The inventory adjustment keeps NetSuite’s available quantity accurate for the EDI 846 inventory update sent to Walmart.

Record 5: Journal Entry (Settlement Deductions) Created from the Walmart settlement remittance. For each deduction (OTIF fine, SQEP penalty, pricing adjustment, shortage claim), a NetSuite journal entry posts the deduction amount against the appropriate GL account and clears the corresponding AR balance.

---

The UPC-to-NetSuite Item Mapping

Just as ASIN-to-Material mapping is critical for Amazon-SAP integration, UPC-to-NetSuite-Item mapping is the most critical configuration for Walmart-NetSuite.

Walmart’s EDI 850 identifies products by UPC (Universal Product Code, the barcode on the product). NetSuite identifies products by internal item ID and optionally by UPC if configured. The mapping must be explicit for every item sold to Walmart.

The cross-reference structure:

Walmart EDI Field	NetSuite Field	Notes
UPC (from 850 PO1 segment)	NetSuite item upcCode or internalId	One-to-one mapping for most beauty items
Walmart Item Number	NetSuite custom field custitem_walmart_item_no	Walmart internal item identifier
Case pack quantity	NetSuite unitsType conversion	Defines units per case for carton-level ASN
Unit cost from 850	NetSuite rate on sales order line	Agreed wholesale price from PO
Display-ready case GTIN	NetSuite kit or bundle item	Used for seasonal bundles and retail-ready packaging

For beauty brands with shade variants: A foundation with 12 shades means 12 UPCs in the Walmart EDI. These may map to 12 separate NetSuite item records or to a single NetSuite matrix item (parent + child variants). The mapping table must specify the variant relationship.

Consequences of mapping errors: If a UPC maps to the wrong NetSuite item, the wrong item is committed from inventory, the wrong cost of goods is posted, and the 856 ASN will contain the wrong item data. Walmart’s receiving system will flag a discrepancy. SQEP chargeback.

Maintaining the mapping: When Walmart adds a new beauty item to the assortment (a new shade, a new size), the item must be set up in NetSuite and the UPC mapping updated before the first 850 arrives for that item. For beauty brands with frequent new product introductions (seasonal shades, limited editions), maintaining this mapping is an ongoing operational task.

---

Flow 1: Walmart 850 PO to NetSuite Sales Order

eZintegrations handles the complete Walmart-NetSuite cycle using all four platform levels. Level 1 (iPaaS Workflows) manages AS2 EDI reception, ANSI X12 parsing, SuiteTalk REST record creation, and all EDI document transmission. Level 2 (AI Workflows) validates the 856 carton totals against NetSuite fulfilment quantities and the 810 invoice prices against 850 agreed prices before transmission. Level 3 (AI Agents) detects invalid settlement deductions by comparing 856 timestamps against OTIF fine dates, monitors inventory threshold levels for 846 triggers, and routes exceptions to the ops team. Level 4 (Goldfinch AI) orchestrates the full Walmart order-to-cash cycle as a Workflow Node and provides the Goldfinch AI Chat UI for finance and ops teams: “What Walmart invoices have open deductions this quarter?”, “Show me all 856 ASNs not yet confirmed received at Walmart DCs”, or “Which Walmart SKUs are below safety stock for the next PO cycle?”

EDI 850 Receipt and Parsing

eZintegrations receives the Walmart EDI 850 at the AS2 endpoint. The document is parsed from ANSI X12 format:

Key 850 segments mapped to NetSuite:

BEG segment:
  BEG03 (PO Number) → NetSuite salesOrder.otherRefNum

DTM segment:
  DTM*010 (Required Delivery Date = MABD) → salesOrder.shipDate

N1 segments:
  N1*ST (Ship-To DC address) → salesOrder.shipAddress

PO1 segments (one per line item):
  PO1*{line}*{qty}*EA*{unit_price}**UP*{UPC}
  → mapped to salesOrder.item[n].item (via UPC lookup)
  → salesOrder.item[n].quantity
  → salesOrder.item[n].rate

The EDI 997 Functional Acknowledgment is auto-sent within seconds of 850 receipt.

NetSuite Sales Order Creation via SuiteTalk REST

POST /orders/v0/orders/114-7284912-1234567/shipment
Content-Type: application/json

{
  "carrierCode": "UPS",
  "trackingNumber": "1Z9W4872...",
  "shipDate": "2026-03-30T16:38:00Z",
  "orderItems": [
    {
      "orderItemId": "...",
      "quantity": 2
    }
  ]
}

Response: NetSuite sales order internal ID and transaction number (e.g., SO-2026-WM-4882).

EDI 855 Acknowledgment

Within 24 hours of 850 receipt, the EDI 855 is auto-generated with inventory-validated quantities. Before generating the 855, eZintegrations queries NetSuite inventory:

SELECT quantityAvailable FROM inventoryItem WHERE id = {item_id}

If available quantity is below the ordered quantity for any line item, the 855 acknowledges the available quantity (not the ordered quantity). This prevents the in-full OTIF violation from over-commitment.

---

Flow 2: NetSuite Inventory to Walmart EDI 846

The EDI 846 (Inventory Inquiry/Advice) sends Walmart your current available stock per UPC. This is critical for preventing Walmart from placing POs against stock you do not have.

eZintegrations queries NetSuite inventory using SuiteQL:

SELECT
  i.itemId,
  i.upcCode,
  ii.quantityAvailable,
  ii.locationId
FROM item i
JOIN inventoryItem ii ON i.id = ii.item
WHERE ii.locationId = {walmart_fulfillment_location}
  AND i.upcCode IS NOT NULL

The result feeds the EDI 846 generation:

BIA*00*{YYYYMMDD}*{HHMMSS}~
LIN**UP*{UPC}~
QTY*1*{quantityAvailable}~
DTM*011*{YYYYMMDD}~

Trigger conditions for 846:

• NetSuite sales order created from Walmart 850 (inventory committed): immediate 846 update
• NetSuite item fulfilment posted (inventory shipped): immediate 846 update
• NetSuite inventory adjustment (new stock received): immediate 846 update
• Scheduled: every 4 hours as a safety net

This 846 cycle is what prevents the weekend oversell scenario: Amazon sells units, NetSuite inventory decreases, and the next 846 to Walmart reflects the reduced quantity before Walmart places a new PO.

---

Flow 3: NetSuite Item Fulfilment to Walmart EDI 856 and EDI 810

Item Fulfilment to EDI 856 (The Most Compliance-Critical Flow)

The Walmart EDI 856 ASN must be transmitted before the physical shipment arrives at the Walmart DC, within 30 minutes of carrier scan. This is the most chargeback-prone compliance requirement.

The trigger chain: 3PL carrier scan → eZintegrations receives shipment event → NetSuite item fulfilment posted → EDI 856 generated and validated → 856 transmitted via AS2.

NetSuite item fulfilment creation:

POST /services/rest/record/v1/itemFulfillment
Content-Type: application/json

{
  "createdFrom": {
    "id": "{sales_order_id}",
    "type": "salesOrder"
  },
  "tranDate": "2026-01-30",
  "shipStatus": { "id": "C" },
  "shipCarrier": { "id": "{carrier_id}" },
  "trackingNumbers": [
    {
      "trackingNumber": "1Z9W4872..."
    }
  ],
  "item": {
    "items": [
      {
        "itemIsFulfilled": true,
        "quantity": 480,
        "orderLine": 1
      },
      {
        "itemIsFulfilled": true,
        "quantity": 355,
        "orderLine": 2
      }
    ]
  }
}

Note: line 2 ships 355 units instead of the 360 ordered (5-unit short on Berry Gloss). This partial shipment quantity is the actual shipped quantity, which determines the 856 carton-level content.

856 pre-transmission validation: Before the 856 is transmitted, Level 2 validates carton totals against the NetSuite item fulfilment quantities. Discrepancies are held and ops team is alerted. Valid 856 is transmitted within 15 minutes of carrier scan.

NetSuite Invoice to EDI 810

When NetSuite creates the invoice from the item fulfilment (via billing run or auto-billing), eZintegrations generates and transmits the EDI 810:

Key 810 fields from NetSuite invoice:

• BIG03 (Invoice Number) ← NetSuite tranId
• BIG05 (PO Number) ← NetSuite otherRefNum (the Walmart PO number stored at sales order creation)
• IT1 segments ← NetSuite invoice line items (shipped quantities × agreed prices)
• TDS (Total Invoice Amount) ← NetSuite total

The pricing compliance check: Before generating the 810, Level 2 verifies that each line item price in the NetSuite invoice matches the agreed price from the original Walmart 850. If any price differs, the 810 is held and an exception is raised. An 810 price that does not match the 850 price generates a Walmart Code 10 deduction (price difference). This validation prevents the most common Walmart AR deduction for beauty brands.

---

Flow 4: Walmart Settlement Reconciliation in NetSuite

This is the most painful and most neglected flow for Walmart-NetSuite integration. Walmart pays via EFT every few weeks, with a remittance advice (available via Walmart’s EIPP system or HighRadius) that breaks down:

• Gross invoice amounts paid
• OTIF deductions (3% of COGS on non-compliant cases)
• SQEP deductions (packaging and ASN accuracy fines)
• Short payment claims (shortage in received quantity vs. invoiced quantity)
• Pricing adjustments (Code 10 deductions)
• Promotional allowances and deductions

The Manual Process (and Why It Fails)

Without automation, the finance team:

1. Downloads the remittance advice from Walmart HighRadius or EIPP
2. Matches each payment line to the corresponding NetSuite invoice
3. For each deduction, creates a NetSuite journal entry or credit memo
4. Posts each deduction to the appropriate GL account (OTIF → 696000 Compliance Fines, SQEP → 696001 Packaging Compliance, Code 10 → 800001 Revenue Reversal)
5. Clears the NetSuite AR balance for each invoice (full payment or partial with deduction)

For 18 Walmart invoices per quarter with an average of 3-4 deduction lines each: this is a 3-5 hour manual process per settlement cycle.

The Automated Settlement Reconciliation

eZintegrations downloads the Walmart remittance advice from HighRadius (via API or structured file) and processes each payment and deduction automatically.

NetSuite journal entry for OTIF deduction:

POST /services/rest/record/v1/journalEntry
Content-Type: application/json

{
  "tranDate": "2026-03-28",
  "memo": "Walmart OTIF Deduction - PO 4500882411 - Q1 2026",
  "lines": {
    "items": [
      {
        "account": { "id": "696000" },
        "debit": 4250.00,
        "memo": "OTIF Fine: 3% of COGS on 2 non-compliant cases"
      },
      {
        "account": { "id": "130000" },
        "credit": 4250.00,
        "memo": "Clear AR: Invoice INV-2026-WM-0441"
      }
    ]
  }
}

NetSuite customer payment for invoice settlement:

POST /services/rest/record/v1/customerPayment
Content-Type: application/json

{
  "customer": { "id": "{walmart_customer_id}" },
  "tranDate": "2026-03-28",
  "payment": 187450.00,
  "apply": {
    "items": [
      {
        "internalId": "{invoice_id_1}",
        "apply": true,
        "amount": 187450.00
      }
    ]
  }
}

GL mapping for Walmart deduction types:

Walmart Deduction Type	NetSuite GL Account	Account Name
OTIF fine (3% COGS)	696000	Walmart Compliance Fines
SQEP packaging fine	696001	Walmart SQEP Fines
Code 10 (price difference)	800001	Revenue Reversal – Walmart
Shortage claim	412000	Freight and Shortage Claims
Promotional allowance	720000	Marketing – Walmart
Early payment discount	692000	Sales Discounts

Deduction dispute workflow: If Level 3 detects that a deduction appears invalid (e.g., an OTIF fine on a shipment where the 856 timestamp confirms on-time delivery), the deduction is flagged for dispute rather than auto-posted. The ops team receives the flagged deduction with the 856 transmission timestamp and delivery confirmation as supporting evidence for the HighRadius dispute submission.

---

Beauty Brand-Specific NetSuite Configuration for Walmart

Walmart as a NetSuite Customer

Create a single NetSuite customer record for Walmart (e.g., customer ID WALMART-US). This customer represents all Walmart store POs. The NetSuite customer record stores:

• Payment terms (Walmart typically pays in 30-45 days with early payment discount options)
• Shipping method (Walmart-routed carrier vs. prepaid supplier)
• Sales channel classification (for channel P&L reporting in NetSuite)
• EDI partner identifier (Walmart’s ISA sender ID for AS2 routing)

For multi-DC Walmart orders (Walmart has multiple distribution centres across the US), a single WALMART-US customer with ship-to address per PO (from the 850 N1/N3/N4 segments) works cleanly. No separate customer per DC.

NetSuite Item Setup for Walmart

For each item sold to Walmart, the NetSuite item record needs:

• upcCode: the retail UPC (what Walmart uses in the 850 PO1 segment)
• Custom field custitem_walmart_item_no: Walmart’s internal item number (from Retail Link)
• Case pack quantity in the NetSuite units of measure (for carton-level 856 generation)
• Walmart-specific pricing: a NetSuite price level WALMART_WHOLESALE set to the agreed cost per unit

NetSuite Subsidiary and Class for Walmart Revenue

For beauty brands running NetSuite OneWorld (multi-subsidiary), Walmart orders should post to:

• The correct subsidiary (e.g., US Beauty - Retail)
• The correct class (e.g., Walmart Channel) for channel-level P&L reporting
• The correct department (e.g., Retail Sales)

These classifications are set in the NetSuite sales order template for Walmart orders and applied automatically at order creation.

Payment Terms and Discount Configuration

Walmart’s standard payment terms include a 2% early payment discount for payment within 10 days (2/10 Net 45 or similar, confirm with your Walmart buyer). NetSuite payment terms must match the terms in the Walmart 850 ITD segment exactly. If they do not match, the 810 invoice will conflict with Walmart’s system, generating a Code 10 deduction.

---

Before vs After: Manual Walmart-NetSuite vs Automated

Process Step	Manual Walmart-NetSuite	Automated with eZintegrations
850 PO capture	EDI portal check, manual download	AS2 reception: instant, 24 by 7
UPC-to-NetSuite item mapping	Manual lookup or spreadsheet	Reference dataset auto-applied per PO line
NetSuite sales order entry	Manual: 25 to 45 minutes per PO	SuiteTalk REST auto-creates in seconds
Inventory check before 855	Manual NetSuite check then acknowledge	SuiteQL query executed before 855 generation
EDI 855 acknowledgment	Manual generation in EDI portal	Auto-generated with validated quantities
EDI 846 inventory update	Scheduled batch or manual update	Triggered by every NetSuite inventory event
Item fulfilment in NetSuite	Manual creation after 3PL notification	Auto-created from 3PL shipment event
EDI 856 ASN timing	Manual with risk of late ASN	Auto-triggered within 30 minutes of carrier scan
856 pre-validation	None	Level 2 validation of quantity versus 855 before transmit
NetSuite invoice creation	Manual billing run with intervention	Auto-created from item fulfilment
EDI 810 invoice	Manual generation from invoice	Auto-generated on invoice creation
810 price validation	None; discrepancies discovered later	Level 2 validation against 850 before transmit
Walmart settlement download	Manual download from portal	API or file-based automatic download on settlement date
Deduction-to-invoice matching	Manual quarterly exercise taking hours	SuiteQL matching using PO reference automatically
NetSuite journal entries	Manual posting per deduction type	Auto-posted based on GL mapping rules
AR clearing	Manual payment application	Auto-cleared via customer payment record
Dispute identification	Often missed or delayed	Level 3 AI flags invalid deductions automatically

---

Step-by-Step: A Walmart Valentine’s Day PO Through the Full NetSuite Cycle

Here is the complete automated cycle for Lumière Cosmetics’ Valentine’s Day promotional PO from Walmart.

Setup: Lumière uses NetSuite OneWorld. Walmart customer record: WALMART-US. Walmart fulfilment subsidiary: US Beauty - Retail. 3PL is DHL Supply Chain Memphis.

January 22, 9:14 AM: Walmart EDI 850 arrives. Walmart transmits PO 4500882411 via AS2: 480 units of Rose Gloss (UPC 847654321001 at 6.99),360unitsofBerryGloss(UPC847654321002at6.99), 120 Valentine’s gift sets (UPC 847654321025 at $18.99). MABD: February 5. EDI 997 auto-sent. Time: under 5 seconds.

January 22, 9:14 AM: NetSuite sales order created. UPC lookup: 847654321001 → NetSuite item ID 4821, 847654321002 → item ID 4822, 847654321025 → item ID 4830 (kit). SuiteTalk REST POST /salesOrder call:

• entity: WALMART-US
• otherRefNum: "4500882411"
• shipDate: "2026-02-05" (MABD)
• 3 line items with quantities and 6.99/18.99 rates

NetSuite response: SO-2026-WM-4882 created. Time: 2-3 seconds.

January 22, 9:14 AM: Inventory check and 855 generation. SuiteQL: Rose Gloss available 620 units (480 ordered: sufficient), Berry Gloss available 290 units (360 ordered: SHORT by 70 units), Valentine’s gift sets 140 units (120 ordered: sufficient). 855 acknowledges: Rose Gloss 480, Berry Gloss 290, Valentine’s sets 120. SO-2026-WM-4882 updated: Berry Gloss line quantity adjusted to 290. 855 transmitted within 5 minutes. Walmart updates PO 4500882411 for Berry Gloss to 290.

January 30, 2:14 PM: DHL ships. DHL picks and packs. Carrier scan at 2:14 PM. DHL push API fires at 2:17 PM.

January 30, 2:17 PM: NetSuite item fulfilment posted. SuiteTalk REST POST /itemFulfillment:

• createdFrom: SO-2026-WM-4882
• Line 1: Rose Gloss 480 units fulfilled
• Line 2: Berry Gloss 290 units fulfilled (partial, 70 units not fulfilled)
• Line 3: Valentine’s sets 120 units fulfilled
• trackingNumbers: ["1Z9W4872..."]

NetSuite item fulfilment IF-2026-WM-0441 created. Time: 2 seconds.

January 30, 2:17 PM: EDI 856 ASN triggered and validated. Level 2 generates 856 with carton-level SSCC-18 records. Pre-transmission validation: carton totals match NetSuite fulfilment quantities. 856 transmitted at 2:29 PM (12 minutes after DHL push event, well within Walmart’s 30-minute requirement).

January 30 (end of day): NetSuite invoice created. NetSuite billing run creates invoice INV-2026-WM-0441:

• Rose Gloss: 480 × 6.99=3,355.20
• Berry Gloss: 290 × 6.99=2,027.10
• Valentine’s sets: 120 × 18.99=2,278.80
• Total: $7,661.10

January 30 (end of day): EDI 810 transmitted. Level 2 checks: all three line prices (6.99,6.99, $18.99) match the original 850 prices. No discrepancy. 810 transmitted. Invoice reference: INV-2026-WM-0441, PO reference: 4500882411.

February 4: Goods arrive at Walmart Kansas City DC. On-time (MABD February 5). OTIF on-time: compliant.

March 28 (Q1 settlement): Walmart EFT payment arrives. Walmart pays 7,512.28againstthe7,661.10 invoice. Remittance shows one deduction: 148.82OTIFfineonadifferentPO(PO4500879003whichwaslateinJanuary).PO4500882411ispaidinfull(7,661.10) with no deductions.

March 28 (settlement reconciliation, automated):

• CustomerPayment created: $7,661.10 applied to INV-2026-WM-0441. Invoice cleared.
• JournalEntry created for OTIF deduction on PO 4500879003: Debit GL 696000 (Compliance Fines) 148.82,CreditAR148.82.
• Level 3 checks: was PO 4500879003’s 856 transmitted on time? Yes (transmitted 18 minutes after carrier scan). Flag the OTIF deduction as potentially disputable. Alert sent to ops team with 856 timestamp evidence.

Total ops team involvement: reviewing the Berry Gloss shortage flag (January 22, 2 minutes) and reviewing the flagged OTIF dispute (March 28, 10 minutes to review 856 evidence and submit dispute). Everything else automated.

---

Key Outcomes and Results

Sales order entry time: from 25-45 minutes per Walmart PO (manual NetSuite entry) to under 30 seconds (automated SuiteTalk REST). At 18 POs per quarter: 8-14 hours recovered quarterly.

OTIF compliance: automated 856 timing (within 15 minutes of carrier scan), inventory-validated 855 acknowledgment, and 810 price validation against 850 eliminate the three primary causes of Walmart chargebacks for beauty brands. Beauty brands report reaching 97-99% OTIF within one full quarter of automated EDI operation.

Settlement reconciliation time: from 3-5 hours per quarterly settlement cycle (manual journal entries, deduction matching, AR clearing) to under 30 minutes (automated deduction parsing, GL mapping, and AR clearing). Exception review for flagged disputes takes an additional 10-30 minutes.

Code 10 deduction prevention: the 810 price validation step, which checks each invoice line against the original 850 price before transmission, prevents the most common AR deduction for beauty brands at Walmart. Manual 810 generation frequently carries incorrect promotional prices that differ from the 850.

OTIF dispute recovery: automated dispute flagging (when a deduction appears on a shipment with a confirmed on-time 856) gives the finance team actionable evidence for HighRadius disputes. Beauty brands typically recover 20-40% of flagged deductions when properly evidenced.

EDI 846 accuracy: continuous NetSuite-to-Walmart inventory updates (triggered by every NetSuite inventory event) prevent Walmart from placing POs against stock that has already sold through other channels. The Walmart oversell scenario described in the multi-channel guide is directly addressed by this flow.

---

How to Get Started

Step 1: Configure NetSuite for Walmart

Set up a NetSuite customer record for WALMART-US. Confirm the NetSuite item records include upcCode values (Walmart UPC barcodes) for every item in the Walmart assortment. Create the Walmart-specific price level (WALMART_WHOLESALE) in NetSuite with agreed costs per item. Configure NetSuite payment terms to match the Walmart 850 ITD segment payment terms exactly. Create GL accounts for Walmart deduction categories if not already present (Compliance Fines 696000, SQEP Fines 696001, Revenue Reversal 800001).

Step 2: Import the Walmart NetSuite Integration Template

Go to the Automation Hub and import the Walmart NetSuite Integration template. The template includes: AS2 EDI 850 reception and ANSI X12 parsing, UPC-to-NetSuite item lookup, SuiteTalk REST POST /salesOrder, inventory check via SuiteQL, EDI 855 generation and transmission, EDI 846 inventory update triggered by NetSuite events, 3PL shipment event to NetSuite item fulfilment, EDI 856 with pre-transmission validation, EDI 810 with 850 price validation, and settlement deduction parsing with NetSuite journal entry posting.

Step 3: Build the UPC-to-NetSuite Item Mapping Table

Export your NetSuite item list with upcCode values. Cross-reference against your Walmart Retail Link item catalog (UPCs and Walmart item numbers). Build the mapping table: UPC → NetSuite item internalId, with case pack quantities and Walmart item numbers. For display-ready cases and gift sets: map the gift set UPC to the NetSuite kit item. Upload to the eZintegrations reference dataset. Allow 1-3 hours for 30-80 items.

Step 4: Configure AS2 Credentials and NetSuite Authentication

Add your Walmart AS2 credentials (Supplier ISA ID, Walmart AS2 endpoint, SSL certificate) and NetSuite TBA credentials (Account ID, Consumer Key, Consumer Secret, Token ID, Token Secret) to the eZintegrations credential vault. Configure the Walmart Supplier ID for EDI 855, 856, and 810 header segments. Set up the settlement source: HighRadius API credentials or SFTP location for remittance advice files. Configure the GL account mapping for deduction types.

Total configuration time: 4-6 hours from template import to live Walmart-NetSuite integration.

---

FAQs

1. How does Walmart EDI integrate with NetSuite for beauty brands using eZintegrations

eZintegrations receives Walmart EDI 850 purchase orders via AS2 maps each UPC to the corresponding NetSuite item using a reference dataset and creates a NetSuite sales order using SuiteTalk REST. Inventory is validated via SuiteQL before generating the EDI 855 acknowledgment. When the 3PL ships a NetSuite item fulfilment is created and the EDI 856 ASN is transmitted within minutes with pre validation. The EDI 810 invoice is generated from the NetSuite invoice with price validation against the original 850. Walmart deductions such as OTIF SQEP and Code 10 are automatically parsed and posted as NetSuite journal entries to the correct GL accounts.

2. How long does it take to set up Walmart NetSuite integration

Setup typically takes four to six hours from template import to live integration. NetSuite item and customer setup takes one to two hours UPC mapping takes one to three hours credential configuration takes thirty to sixty minutes GL mapping takes thirty minutes and testing takes one to two hours. New Walmart suppliers must also account for EDI certification which can take one to three weeks.

3. Does eZintegrations work with NetSuite and Walmart EDI simultaneously

Yes, the platform supports Walmart EDI documents including 850 855 856 810 and 846 over AS2 along with NetSuite SuiteTalk REST APIs for all corresponding transactions. Sales orders fulfilments invoices inventory queries journal entries and payments are all handled within a single integrated workflow with consistent item mapping across all documents.

4. How does settlement reconciliation work between Walmart and NetSuite

Walmart settlement remittance is downloaded and parsed automatically. Each deduction is matched to the corresponding NetSuite invoice using purchase order references. Journal entries are created for each deduction using predefined GL mappings and a customer payment is recorded for the net amount received. Invalid deductions are identified and flagged for dispute rather than automatically posted.

5. What is EDI 846 and how does it prevent Walmart overselling

EDI 846 is the inventory advice document sent to Walmart showing available stock levels per UPC. eZintegrations updates the 846 after every NetSuite inventory event and on a scheduled cycle ensuring Walmart always has accurate inventory data. This prevents Walmart from placing purchase orders based on outdated stock levels reducing the risk of overselling and compliance issues.

---

Walmart Pays in EDI. NetSuite Speaks REST. eZintegrations Translates Both.

The Walmart-NetSuite gap is not just a connectivity problem. It is a translation problem: Walmart’s 850 PO segment structure to NetSuite’s sales order JSON. Walmart’s MABD to NetSuite’s ship date. Walmart’s UPC to NetSuite’s internal item ID. Walmart’s settlement deduction codes to NetSuite’s GL account numbers.

Each translation is well-defined once you build the mapping. The problem is building all of them, maintaining them as your Walmart assortment grows, and running them 24/7 with pre-transmission validation for every EDI document.

eZintegrations provides all of it: the AS2 EDI connection, the ANSI X12 parsing, the SuiteTalk REST integration, the UPC mapping, the inventory validation, the 856 pre-validation, the 810 price check, and the settlement GL posting.

Import the Walmart NetSuite Integration Template from the Automation Hub. Or book a free demo with your Walmart Supplier ID, NetSuite account ID, and Walmart item count. We will walk through the UPC mapping and EDI AS2 configuration in the session.

For Walmart EDI compliance context, see the Walmart EDI guide for beauty brands. For multi-channel context (Walmart + Amazon in one ERP), see the multi-channel order sync guide.