SFTP
Partner folders or filenames
/inbound/documents/WALMART-US/asn.csvReceive outputs under the same partner code with cleared, blocked and quarantine lanes plus a batch manifest.
EDI orders, shipments and invoicing
One source file in. The right retailer file out.
Create and validate partner-ready orders, shipments and invoices. Review what needs attention, approve the document, and track its delivery from one workspace.
Start with a free validation. Set up delivery when you’re ready.
Run SS-260716-0842BLOCKED
Score64
Errors2
Warnings1
HL parent does not exist
segment 18 · HL02
References HL 9 before that parent is defined.
SSCC check digit is invalid
segment 21 · MAN02
GS1 source · exact remediation included
Rule pack 2026.07.2011 checks passed
SOURCE: Amazon current · X12 base · GS1
European e-invoice tools
UBL and CII now get the same rule-level preflight surface.
No retailer guessing
Every document carries an explicit partner code
Confirm once
Reviewed structured mappings make repeat layouts automatic
Fail one, not all
Every batch returns an independent result per file
Beyond shipment preflight
A clear path from order to acceptance.
Orders, changes and warehouses
Retain and structurally validate X12 850, 855, 860, 865, 940, 945, 846 and 810 alongside shipments. Group records by business reference and review the current partner requirements before release.
Explore the document chainControlled delivery and recovery
Keep test and production records distinct. Claim an approved outbound document through the API, deliver through the SFTP adapter, and record receiver evidence. Investigate uncertain delivery before retrying.
Plan an EDI integrationTraceable mapping and responses
Retain mapping revisions and immutable document evidence. Correlate individual 997, 999 and 824 responses using partner routes and controls. Track business acceptance separately from file transfer.
Understand acknowledgmentsCreate orders and invoices
Generate X12 850 and 810, EDIFACT ORDERS and INVOIC, or Peppol UBL invoices from reviewed commercial details. Keep line items, decimal totals and source evidence together.
Explore invoice validationNative AS2 and Peppol delivery
Sign and encrypt AS2 messages and verify signed synchronous receipts. Submit validated UBL invoices through a configured Storecove access point and retain Peppol delivery evidence.
See connection requirementsReconciled ERP drafts
Import approved orders and invoices into Business Central, then read back references, items, quantities and totals before recording success. Preserve uncertain outcomes for investigation.
Understand ERP integration
The conversion gate
Three decisions before a file leaves.
Source analysis, partner rendering and output validation share one deterministic path across the website, SFTP, email and API.
- 01 / MAP
Can source fields become shipment truth?
Inspect headings and values, propose a mapping, and require confirmation before the first automated release.
- 02 / ROUTE
Which partner pack owns this output?
Resolve the explicit code inside the workspace and render X12 856, EDIFACT DESADV or Amazon shipment JSON.
- 03 / VERIFY
Is the generated file safe to return?
Validate the generated output immediately, isolate failures, and return a per-file receipt and traceable rule-pack version.
One batch contract
Drop 1,000 files. Route 1,000 decisions.
A bad Target file does not block a valid Walmart file. Missing codes and first-seen source layouts move to quarantine; confirmed siblings keep processing and receive their partner output.
Tagged recipient or attachment
workspace+AMAZON@in.shipmentsentry.comAuthorize exact senders. Route attachments by plus tag or PARTNER__filename; large result sets return as one safe ZIP.
API + callback
Code on every document
"partner_code": "TESCO-UK"Idempotent batch responses include every decision; optional signed callbacks report completion without exposing document payloads.
Partner truth stays explicit: Amazon and Walmart packs have public first-party implementation evidence. Other retailer routes apply universal X12 or EDIFACT controls and remain marked “partner guide required” until your current authorized guide is configured.
Product-led reference library
Every guide ends in a check you can run.
Practical examples and clear checks for the documents your partners expect.
Implementation guide
Browse the complete EDI library →
Amazon ASN errors: isolate the failing layer before changing the mapping
Diagnose Amazon ASN parser, envelope, hierarchy, SSCC, quantity, label, and shipment-reference errors with exact locations and corrective steps.
Open guide → Implementation guideAmazon EDI 856: validate the shipment, not only the syntax
Build and validate an Amazon Vendor EDI 856 ASN with correct envelopes, HL hierarchy, purchase orders, SSCCs, shipment references, and tests.
Open guide → Implementation guideAmazon EDI testing: exercise the failures a happy-path 856 cannot show
Test Amazon EDI syntax, business rules, document reconciliation, negative fixtures, retries, acknowledgements, and operator correction before go-live.
Open guide → Implementation guideAmazon Vendor EDI transaction sets work as one order-to-cash chain
Understand the Amazon Vendor order-to-cash EDI chain and the cross-document checks that catch failures no single-file validator can see.
Open guide → Implementation guideAmazon multi-PO pallet ASN: preserve every order-to-carton relationship
Model a multi-PO pallet with Shipment, Order, Tare, Pack, and Item parentage, then validate common crossed-order and SSCC errors.
Open guide → Implementation guideAmazon Receive Accuracy: find document-versus-shipment mismatches before dispatch
Reduce preventable Amazon receiving discrepancies by reconciling ASN quantities, cartons, labels, purchase orders, and transportation references.
Open guide →The first proof asset
A human-reviewed readiness audit when software alone is not enough.
For a new mapping or expensive recurring issue, get the payload, hierarchy, identifiers, test evidence and risk register reviewed as one implementation pack.
See the $499 audit →Audit output / PDF + call
- Rule-sourced findings with exact locations
- Hierarchy and identifier risk map
- Accepted and rejected test fixtures
- Dispatch-gate checklist for your team
- 30-minute findings walkthrough
Start with the file on your desk