Receiving an EDI order is only half the job. Someone still has to get it into the system that runs your business. EDI Connections connectors deliver each document directly into your ERP, mapped to the import format your ERP expects and sent over a secure connection you already trust.
ST*850*0001~ BEG*00*SA*PO-10482**20261012~ N1*ST*Acme Store #212*92*212~ PO1*1*24*EA*12.50**VP*NW-1001~ PO1*2*10*CS*48.00**VP*NW-2040~ CTT*2~
Orders reach your ERP as soon as they are accepted, not when someone has time to type them in.
Item numbers, quantities, prices and ship-to locations come from the EDI document itself, so there are no typos to chase later.
Every delivery is logged with its time and result, so you can always answer the question "did the order make it in?"
We record your ERP system and the settings it needs, such as company, business unit or partner identifiers.
A data map translates the EDI document into the layout your ERP's import expects. Maps are versioned and reusable.
Delivery runs over SFTP, AS2 or an HTTPS API. Credentials are kept on the secured connection, never inside the map.
Test and production connectors are kept separate, so trial orders never reach your live ERP.
Every attempt is logged. A redelivery requires explicit confirmation, which protects you from duplicate orders.
Captures your client, logical system and IDoc partner settings, so orders enter through SAP's standard inbound processing.
Targets your business unit or subsidiary through the import process or REST resource your Oracle environment uses.
Delivers to the legal entity and data entity or API page you specify in your Dynamics environment.
Loads orders into the right company or entity using the import template your Sage system expects.
Not on this list? Most ERPs can import files or accept API calls, and that is all a connector needs. See how we add one →
Connectors are built from parts: an ERP profile, a data map and a transport. To support a new ERP, we add a profile and build a map from its import specification. The delivery, logging and safety controls are already in place and already tested.
Which system you run, how it accepts orders today, and which trading partners you want connected first.
Our team maps the EDI document to your ERP's import format and sets up the connection details.
Real orders from your trading partners are delivered to your test ERP first. You check them before anything goes live.
When the orders look right in your ERP, you approve the switch to production.
The production connector is turned on. Every delivery is logged and visible, and our team watches for anything that needs attention.
| Document | Into your ERP | Status |
|---|---|---|
| 850Purchase order | Incoming orders are delivered to your ERP as sales orders, ready to fulfill. | Available now |
| 855 · 856 · 810Ack · Ship notice · Invoice | The same connector framework extends to acknowledgments, ship notices and invoices, based on what your ERP can import and export. | Scoped per engagement |
We'll show you how your orders would arrive in it and what a connection would take. If we haven't connected to your ERP before, we'll tell you so and show you the plan.