Product guides
Complete the next SignalEDI task
Guide 1 · 45 seconds
Get your data into SignalEDI
The mapping draft is only as good as the data it sees. A genuine export, even a messy one, teaches Signal more than a tidied-up example.
Open guide →Guide 2 · 46 seconds
Confirm your mapping
Confirm one flagged column and Signal remembers it for future files from this partner.
Open guide →Guide 3 · 50 seconds
Send your first document
It uses the same validation, acknowledgements, and errors. The difference is where the document ends up.
Open guide →Guide 4 · 30 seconds
Get into your account
Trading partner records and audit logs are tied to the account that created them, and moving them later creates avoidable account work.
Open guide →Guide 5 · 55 seconds
Add the partner who set your deadline
Signal uses the source document to resolve identifiers and requirements. Confirm leading zeros in the resolved profile before certification.
Open guide →Guide 6 · 35 seconds
Know which mode you are in
Include the acknowledgement. That short test catches most mapping, envelope, and connection problems before live traffic.
Open guide →Guide 7 · 60 seconds
Understand what came back
If nothing arrives within the partner SLA, Signal flags it. Silence often points to a connection problem rather than a document problem.
Open guide →Guide 8 · 50 seconds
Fix a rejected document and resend it
Partners treat it as a duplicate and may reject it again, which can make a correct field fix look unsuccessful.
Open guide →Guide 9 · 50 seconds
Get events into your own system
Signature verification is the boundary between a trusted event receiver and an endpoint that accepts untrusted requests.
Open guide →Guide 10 · 40 seconds
Know something is wrong before your partner calls
When an SLA breach matters, the notification path should already be configured and tested.
Open guide →Guide 11 · 45 seconds
Stop rekeying orders and invoices
A wrong item match is much less expensive to correct before it reaches your books or commerce records.
Open guide →