Senda · EDI add-on · On request
Purchase orders,
proofread.
When a customer sends a purchase order as an X12 850 or an EDIFACT ORDERS message, Senda checks the interchange and names anything wrong with it in plain words. Once you have reviewed the order, one step turns it into a Senda order, every line included.
Then it writes the ship notice and the invoice back from the same records, and reads your partner's acknowledgments, so you know what they accepted.
Sold on request and switched on per company. There is no published price; we scope it with you.
- Receives
- X12 850 · EDIFACT ORDERS
- Sends
- X12 856 and 810 · EDIFACT DESADV and INVOIC
- Both ways
- X12 997 · EDIFACT CONTRL
- Connection
- Yours: a VAN, an AS2 gateway or an EDI translator
- Terms
- An add-on, on request, per company
Fig. 1 · Sample
One purchase order, before and after.
A purchase order as it arrives, an X12 850 marked where its numbers land, and the Senda order it becomes once someone has reviewed it. Each numbered mark appears on both sheets.
What it reads and writes
Four documents, in both directions.
X12 850EDIFACT ORDERS
Received
Purchase order
Checked when it arrives, with each problem it finds named in plain words. You review it, and one step turns it into a Senda order with its customer, ship-to and lines.
EDIFACT directories D96A and D01B
X12 856EDIFACT DESADV
Sent
Advance ship notice
Written from a Senda shipment, with its container and seal numbers, its bill of lading number, and the purchase order and line references.
X12 810EDIFACT INVOIC
Sent
Invoice
Written from a Senda order, from the values already on it.
X12 997EDIFACT CONTRL
Both ways
Functional acknowledgment
Senda acknowledges what it receives, and reads your partner's acknowledgments to mark what you sent as accepted or rejected.
Checked on arrival
Every problem, named.
Before a purchase order becomes anything, Senda checks the interchange it came in: that its envelopes add up, that nothing required is missing, and that it came from a trading partner you have set up.
Anything wrong comes back as a sentence that names the segment and what was expected, so you can take it straight to the partner who sent it.
Nothing becomes an order until someone has looked at it. When the purchase order reads right, one step turns it into a Senda order.
SE01 says 12 segments but transaction set 0001 has 11.
GE01 says 2 transaction sets but group 4417 has 1.
Getting the files there
Over the connection you already have.
Senda doesn't run a VAN or an AS2 connection. Your partners' files travel the way they travel today, through the connection you have, or by hand.
- Your trading partner
- Your VAN, AS2 gateway or EDI translatorYours, not Senda's
- Senda
In the app
Upload an interchange when one arrives, and download what Senda writes to send it on.
System to system
Your VAN, AS2 gateway or EDI translator posts interchanges to Senda's API and collects the outbound ones, with an API key scoped to EDI.
Each partner, set up once
Its interchange IDs and qualifiers, the version it sends, and whether it is in test or in production.
Where it stops
What it will not do.
Worth knowing before you ask us about it.
Senda doesn't run a VAN or an AS2 connection. Your partners' files reach it through your own VAN, AS2 gateway or EDI translator, or you upload them.
EDI here means commercial documents between you and your trading partners, not customs filing. Senda files nothing with CBP: a customs entry goes to CBP through its ABI system, in CBP's own CATAIR format, and your broker files it.
Four kinds of document and no others: purchase orders in, ship notices and invoices out, acknowledgments both ways. No 855, 860, 820, 315 or any other transaction set.
Senda isn't certified by any retailer or authority. Where a partner asks to test first, you can keep that partner in test until you are both ready for production.
It's an add-on, sold on request and switched on per company. There is no self-serve switch and no published price.
Questions
What people ask us.
Do I need a VAN?
You need some way for your partners' files to reach you, and Senda doesn't provide one. If you already use a VAN, an AS2 gateway or an EDI translator, it can post interchanges to Senda's API and collect what Senda writes. If a partner sends you files another way, you can upload them.
Which standards does it read?
ANSI X12 and UN/EDIFACT. EDIFACT purchase orders are read in directories D96A and D01B. Each trading partner carries its own version setting: tell us what your partners send and we'll confirm it before the add-on is switched on.
Can Senda send my customs entry by EDI?
No. Customs filing is a different kind of EDI: an entry goes to CBP through its ABI system, in CBP's own CATAIR format, and your customs broker files it. Senda files nothing with CBP.
Is Senda certified by my retailer?
No. Senda isn't certified by any retailer or authority. If a partner wants to test before production, you can keep that partner in test while you work through it together.
What does it cost?
It's priced on request; there is no published price. Ask about it and we'll scope it with you around the partners you trade with.
EDI add-on
Bring one of your partners' purchase orders.
We'll read it with you in Senda, show you the order it becomes, and scope the add-on around the partners you trade with.