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

Operational EDI reference

EDI Idempotency: Safe Retries Without Duplicate Decisions

Use a business request key plus a request hash so timeouts can retry without duplicate validation or conflicting content.

Use the free validator See batch and API plans

Direct answer

Direct answer

EDI workflows retry because networks and downstream systems fail. Idempotency makes the retry deterministic: the caller supplies a unique key, the gateway stores it under the tenant with a hash of the meaningful request, and the completed response is replayed. Reusing the key with different content returns a conflict. The reservation and request record must be race-safe so two simultaneous retries cannot both consume quota.

Why a parser is not enough

The useful unit is not a file that parses; it is a business document with a known decision, an owner, a source trail and a matched downstream response. This page connects the technical structure to that operating workflow.

What the control should check

  1. 01Scope the key by workspace.
  2. 02Hash payload, format, filename and retention choice.
  3. 03Insert the request claim under a unique constraint.
  4. 04Replay the stored response for the same hash.
  5. 05Return conflict for different content under the same key.

Working example

dispatch-1042 + hash A → result 01 / dispatch-1042 + hash B → 409 conflict

The excerpt is intentionally compact. Use the working validator or authenticated gateway with the complete interchange to obtain a decision.

Failure modes worth catching

  • A transport receipt is mistaken for business acceptance.
  • Control identifiers are regenerated between validation and submission.
  • A warning has no owner and becomes a recurring manual investigation.
  • The document is checked alone even though the truth exists in a purchase order, label or acknowledgement.

Put it into the dispatch workflow

  1. 1Validate the source document before transport.
  2. 2Block deterministic failures and assign every review item.
  3. 3Release with a recorded owner and timestamp.
  4. 4Match functional and application acknowledgements.
  5. 5Reconcile confirmed outcomes back into fixtures and rules.
Use batch validation and acknowledgement tracking

Questions

Implementation answers

Does Shipment Sentry replace my EDI provider?

No. It sits before the existing transport as a validation and evidence sidecar.

What does cleared mean?

The document has no blocking finding in the current rule pack. It is not a guarantee of trading-partner or receiving acceptance.

How are repeat requests kept safe?

The API requires an idempotency key, stores only a token hash, scopes every record to one workspace and rejects reuse with different content.

Sources and limits

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

Keep investigating

Related EDI controls

View the library
Add an EDI API gate without rebuilding partner operations Connect Business Central records to controlled EDI delivery Send EDI over AS2 without mistaking HTTP success for delivery proof Connect validated invoices to a certified Peppol access point Turn EDI partner testing into a versioned release gate Give EDI users reports that lead back to transaction evidence