Skip to content
Independent EDI conversion and validation software. Retailer names identify interoperability targets; no retailer endorsement is implied.
Shipment Sentry
Start routing

One intake / many partner routes

Run one conversion gateway across retailer and trading-partner formats

Drop a mixed batch once. An explicit partner code selects the versioned route, output renderer and validation pack for each file.

Configure a source mapping See batch and API plans

Direct answer

Direct answer

A multi-retailer EDI converter must keep routing explicit. Shipment Sentry uses a partner folder, PARTNER__ filename prefix, plus-tagged email address or partner_code API field. It never infers the retailer from business payload contents. Each of up to 1,000 files receives an independent converted, blocked or quarantined result, so one unknown route cannot poison the rest of the batch.

Why mapping needs a controlled workflow

The scalable asset is the confirmed canonical mapping, not another retailer-specific import script. Once a source layout maps to purchase order, shipment, item, quantity, unit, container and dates, multiple routes can render their own envelopes and identifiers while retaining the same source evidence.

What the control should check

  1. 01Resolve exactly one active tenant-scoped partner route per file.
  2. 02Pin pack version and output format on every processing record.
  3. 03Keep credentials and partner identifiers encrypted and isolated by route.
  4. 04Do not charge quota for unknown partner codes that never run validation.
  5. 05Return a batch manifest with every input and disposition.
  6. 06Sign callback metadata without transmitting raw customer payloads.

Working example

inbound/WALMART-US/orders.csv → results/WALMART-US/orders.856
inbound/AMAZON-UK/orders.xlsx → results/AMAZON-UK/orders.json
inbound/UNKNOWN/orders.xml → quarantine/UNKNOWN/orders.xml

Folder names are illustrative. The same partner-code contract works with email attachment prefixes and API document objects.

Failure modes worth catching

  • Payload heuristics route a supplier file to the wrong retailer.
  • One malformed file aborts all other partner outputs.
  • A shared sender identifier leaks across routes.
  • A retry duplicates quota or output because it lacks an idempotency key.

Put it into the dispatch workflow

  1. 1Create the partner routes and assign memorable codes.
  2. 2Confirm each source layout against the route that will receive it.
  3. 3Upload a mixed batch with one explicit code per file.
  4. 4Process and validate every item independently.
  5. 5Collect outputs, quarantine reasons and optional signed completion callback.
Confirm a mapping and route the first batch

Questions

Implementation answers

How many partner routes are catalogued?

Thirty-three starter route packs are catalogued. Amazon and Walmart have verified public base packs; all others remain partner-guide-required before production use.

Can one batch contain different partners?

Yes. Every file or API document carries its own partner code and receives an independent output or quarantine result.

Does Shipment Sentry replace AS2, VAN or retailer submission APIs?

No. It converts, validates and routes around your existing submission transport.

Sources and limits

Reviewed 2026-07-19. Public references cannot establish every partner-specific rule. Current implementation guides and agreements remain controlling.

Keep investigating

Related EDI controls

View the library
EDI mapping software that remembers the business identity behind every code Convert Excel to EDIFACT DESADV without a brittle one-off script Convert SAP IDoc to X12 856 ASN without a brittle one-off script Convert Excel to Walmart 856 without a brittle one-off script Convert Excel to Amazon ASN without a brittle one-off script Convert Excel to X12 856 ASN without a brittle one-off script