4. Trading Partners
Adding a Trading Partner
Go to Partners → Add Partner. You will need:
- Partner name and contact email.
- Their ISA Sender ID (ISA06) and your ISA Receiver ID (ISA08) for this partner.
- Connection type (SFTP, AS2, or API webhook).
- Transaction sets this partner sends/receives.
- Preferred output mode (EDI or API JSON).
ISA IDs (Interchange Sender/Receiver IDs)
ISA IDs are 15-character alphanumeric identifiers that tell the EDI network who sent a document and who should receive it. Each trading partner relationship uses a unique pair: your sender ID and the partner's receiver ID.
You can find your ISA IDs in Settings → EDI Configuration. If you don't have ISA IDs, SignalEDI will provision them for you during onboarding.
Connection Types
| Type | Description | Plan Required |
|---|---|---|
| SFTP | Secure FTP push/pull. SignalEDI polls your SFTP server or pushes to your partner's server. | Starter+ |
| AS2 | HTTP-based EDI transport with MDN receipts. Required by most major retailers (Walmart, Target, Amazon). | Growth+ |
| API Webhook | SignalEDI POSTs processed JSON to your endpoint on each transaction. The simplest modern option. | All plans |
| VAN (via AS2) | Connect to a Value-Added Network through our AS2 gateway. | Growth+ |
Onboarding Timeline
SignalEDI can prepare account setup and technical configuration in days, not weeks. However, getting certified with a major trading partner takes longer because their internal processes control the timeline — not SignalEDI.
| Phase | Who controls it | Typical duration |
|---|---|---|
| SignalEDI account + ISA setup | You + SignalEDI | Days, not weeks |
| Partner contact & intake form | Trading partner | 1–2 weeks |
| Test transaction exchange | Both parties | 1–2 weeks |
| Partner certification | Trading partner | 2–4 weeks |
| Go live | Both parties | Day of approval |
Production Readiness Checklist
Before sending live partner traffic, confirm these items in the dashboard or with your managed onboarding owner.
- Partner ISA IDs, document types, and transport are saved on the trading-partner record.
- A sample file or API payload has passed validation for each required transaction set.
- Webhook URL, signature secret, or SFTP/AS2 endpoint is configured and tested.
- Acknowledgement handling is agreed: 997/999/277 status appears in the transaction lifecycle.
- Support path, SLA tier, audit-log needs, retention tier, and BAA/DPA review are understood before production PHI or regulated data moves.
Still have questions?
Our support team typically responds within a few hours during business hours.
Contact support