Supplier networks and EDI
Proactis
Send purchase orders out to Proactis and take acknowledgements and invoices back.
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 Proactis without running a second purchasing system beside Kabaido.
- What moves
- Out: purchase orders and their changes, as signed JSON your middleware maps. In: acknowledgements and supplier invoices, on the inbound actions. Kabaido does not speak the wire formats itself: a translator sits between.
- What you hand over
- Whatever Proactis 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 shape with whoever mandates Proactis.
- 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.