Integration platform · EDI + API

Every system you run.
Every partner you trade with.
One pipe.

EDIpipe connects your ERP, storefronts, warehouse and finance systems to the retailers, carriers and marketplaces you trade with — native X12 EDI and modern APIs on one connection base. Bring your own systems; you don't need ours.

Scope map: your ERP, storefront, warehouse and finance systems connect through EDIpipe to retailers, carriers, marketplaces and EDI networks
Fig. 01 — What EDIpipe connects: your systems on the left, your trading partners on the right

One connection base carries both worlds: the systems you run your business on, and the partners whose formats, portals and networks you have to satisfy. A connector built on the shared base works for every customer on it.

61connectors ready to connect today
108systems in the shared catalog
850 · 940 · 945 · 997X12 transactions supported natively today
26X12 transaction sets on the published roadmap

Connect once. Trade everywhere.

Three steps, no middleware project. Most connections are credential handshakes and a mapping review — not a six-month integration engagement.

STEP 01

Connect

Pick a system from the catalog, authorize it, and we verify the connection against the real platform — not a simulator.

STEP 02

Map

Fields are mapped once, visually, between your system's documents and your partner's format — EDI guidelines and API schemas alike.

STEP 03

Monitor

Every transmission is logged with its acknowledgement status. Failures alert you before your partner's chargeback does.

Capability map: connectors, APIs and flows, native X12 EDI, mapping and monitoring arranged on one connection base
Fig. 02 — Five capabilities, one connection base

Connectors, API flows, the native X12 engine, the mapping layer and the transmission monitor are not separate products bolted together — they are five faces of the same base, so a mapping you build for an API flow is the same mapping your EDI traffic uses.

A catalog that starts at 61 — and keeps growing

The catalog is shared with the Docklify platform: a connector added on either side is available on both. Cards are tagged by where they run.

Sh
ShopifyCommerce

Connect your Shopify store to pull orders and products and keep inventory and fulfillment data moving via the Shopify API.

AvailableShared
Ne
NetSuiteERP & Finance

Connect NetSuite and run automated flows across orders, customers, inventory, and invoices.

AvailableShared
WM
Walmart MarketplaceCommerce

Connect Walmart Marketplace to pull orders and exchange items, inventory, and fulfillment data via its API.

AvailableShared
SS
SAP S/4HANAERP & Finance

Connect SAP S/4HANA and read order and customer data via its OData API.

AvailableShared
AS
Amazon SP-APICommerce

Connect Amazon Seller Central via SP-API to pull orders and manage listings, inventory, and fulfillment data.

AvailableShared
QO
QuickBooks OnlineERP & Finance

Connect QuickBooks Online and run automated flows across customers, invoices, items, and payments.

AvailableShared
Tr
TrueCommerceEDI & Networks

Connect to the TrueCommerce EDI network to send and receive EDI documents with your trading partners.

AvailableShared
Fe
FedExLogistics & Carriers

Rate, book, and track FedEx shipments and print labels via its API.

AvailableShared

See the full catalog →

How a connection goes live: five steps

Every connection follows the same five steps, and our team runs them with you. You pick the system and provide the credentials; the mapping is worked through together, and nothing goes live until it has been previewed against sample documents and tested end to end with your partner.

Onboarding flow: pick a system, authorize, map fields, test and certify, go live
Fig. 03 — The onboarding path every connection follows
Native X12 EDI

Real EDI, without renting someone else's network

Our own translation engine speaks X12 directly — no per-document black box, no mystery mapping fees. Every interchange is recorded raw in the transmission log, with its mapped document and acknowledgement status attached. (A side-by-side raw↔mapped comparison viewer is in build.)

Translation engine, built in-house. X12 4010/5010 dictionaries, three-layer validation, automatic 997 functional acknowledgements and TA1.

SFTP and file channels live today. Poll, pick up, deliver — with store-before-delete safety so a file is never lost in transit.

AS2 direct connectionsIN BUILDCertificate lifecycle and MDN handling are in build — SFTP and VAN mailboxes cover most partners in the meantime.

VAN mailbox access. Already on a VAN? We connect to your mailbox; we don't make you switch networks to switch software.

Templates that accumulate. Retailer guidelines pre-built from the official implementation guides — Walmart, Kohl's, CVS, Macy's and Best Buy Canada 850s are drafted and ready to certify against your first live order.

ISA*00* *00* *ZZ*YOURCO *ZZ*WALMART *251115*1430*U*00501*000000001*0*P*>~ GS*PO*YOURCO*WALMART*20251115*1430*1*X*005010~ ST*850*0001~ BEG*00*SA*PO-10482**20251115~ N1*ST*EASTVALE DC*92*DC01~ PO1*1*240*EA*18.50**UP*003459871209~ CTT*1~ SE*6*0001~ GE*1*1~ IEA*1*000000001~ → 997 functional acknowledgement: received, accepted

Every transmission, accounted for

EDI fails silently in most stacks — a purchase order vanishes and you find out from a chargeback. On EDIpipe every send is tracked against its acknowledgement; when one goes missing, the alert, the retry and the dead-letter queue are part of the pipe, not a separate tool.

Monitoring flow: transmission sent, acknowledgement tracked, failure alert, retry or dead letter, resolved
Fig. 04 — What happens to a transmission, including when something goes wrong

Starts with trade. Built for every industry.

The connection base doesn't care what industry a system belongs to. New industries arrive as new catalog sections — same base, same pipe.

Retail & logistics

Our home turf: marketplaces, retailers, 3PL warehouses, carriers and drayage — the full order-to-delivery chain, live today.

Live

Explore retail & logistics →

CRM & revenue systems

Customer and pipeline data flowing into the same pipe — orders meeting the accounts they belong to. First connectors in build.

In build

See the CRM roadmap →

Manufacturing

Production ERPs already connect (Epicor, SAP, Acumatica). Dedicated manufacturing flows — forecasts, ASNs, supplier EDI — are next.

In build

See manufacturing →

Pricing

EDIpipe pricing is being finalized. Structure will follow connections and document volume — no per-mapping surprises. Talk to us for early-access terms.

Talk to us