Channel-independent routing
Route retailer EDI files the same way over SFTP, email and webhooks
Partner codes are configured once and then reused in paths, filenames, recipients and API payloads.
Direct answer
Direct answer
Retailer file routing is safest when the sender declares the destination explicitly. SFTP accepts /inbound/documents/PARTNER/file or PARTNER__file. Email accepts workspace+PARTNER at the private inbound domain or a prefixed attachment. The API requires partner_code on every document. Unknown, inactive and conflicting codes are quarantined; content-based retailer guessing is intentionally unavailable.
Why mapping needs a controlled workflow
A single routing contract reduces operational training and integration code. More importantly, it creates the same tenant, partner, pack-version and idempotency evidence regardless of how the file arrived, making support and audit investigation channel-independent.
What the control should check
- 01Authenticate the channel before accepting the declared route.
- 02Normalize partner codes to the documented uppercase alphabet.
- 03Reject ambiguous recipient and filename codes that disagree.
- 04Enforce the 1,000-file limit before starting work.
- 05Return a per-file disposition and deterministic output name.
- 06Keep callback payloads metadata-only and HMAC signed.
Working example
SFTP /inbound/documents/WALMART-US/dispatch.csv
EMAIL workspace+WALMART-US@in.shipmentsentry.com
API {"partner_code":"WALMART-US","file_name":"dispatch.csv",...}The code selects a workspace-owned route. It is not an authentication secret and cannot cross tenant boundaries.
Failure modes worth catching
- An allowlisted sender uses a recipient code for another workspace.
- Two routing hints disagree and the system silently chooses one.
- A 1,000-file retry creates duplicate work.
- Multiple source files overwrite one output filename.
Put it into the dispatch workflow
- 1Create a partner route and copy its code.
- 2Choose the channel that fits the producing system.
- 3Attach the code at the documented routing boundary.
- 4Review outputs and quarantines in one control room.
- 5Use the same code when moving the integration to another channel.
Questions
Implementation answers
Can email contain multiple partners?
Yes. Prefix each attachment PARTNER__filename.edi; a plus-tagged recipient provides a default only when an attachment has no prefix.
What does the API return?
It returns a result per document and safely replays the same response when the idempotency key and meaningful request hash match.
Can callbacks receive the converted customer payload?
No. Completion callbacks are signed and metadata-only by design; outputs stay in the authenticated channel response or result location.
Sources and limits
Reviewed 2026-07-19. Public references cannot establish every partner-specific rule. Current implementation guides and agreements remain controlling.
Keep investigating