EDI (EDIFACT, ANSI X12, AS2)

Trade with a customer or a supplier who mandates EDI without running a second purchasing system beside Kabaido.

Send purchase orders out and take acknowledgements and invoices back through your own EDI translator.

Status	Template: A prepared recipe on a generic path, which you finish.
Kind	Supplier networks and EDI
For	Source
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.

What you get

Trade with a customer or a supplier who mandates EDI without running a second purchasing system beside Kabaido.

In Settings then Integrations, open the entry and follow its steps:

Step 1.
Agree the document set and the message versions with the trading party.
Step 2.
Add an outbound endpoint here pointed at your translator, which maps the signed JSON to the shape it needs.
Step 3.
Add an inbound endpoint with the acknowledgement and invoice actions and give it its URL.
Step 4.
Run one live document each way and check the order moves with it.