Supplier networks and EDI
EDI (EDIFACT, ANSI X12, AS2)
Send purchase orders out and take acknowledgements and invoices back through your own EDI translator.
Where it stands today
Template
A prepared recipe on a generic path, which you finish.
- What you get
- Trade with a customer or a supplier who mandates EDI without running a second purchasing system beside Kabaido.
- What moves
- Out: purchase orders and their changes, as signed JSON. In: acknowledgements and supplier invoices. Kabaido does not speak EDIFACT, ANSI X12 or AS2 on the wire: your translator sits between and does that part.
- What you hand over
- Whatever your translator and the trading party require. Kabaido's side is a signed outbound endpoint and a tokenised inbound URL, both created here.
Set it up
- 1Agree the document set and the message versions with the trading party.
- 2Add an outbound endpoint here pointed at your translator, which maps the signed JSON to the shape it needs.
- 3Add an inbound endpoint with the acknowledgement and invoice actions and give it its URL.
- 4Run one live document each way and check the order moves with it.