Native X12 EDI

Native X12, no middleman network.

Most EDI products rent you a seat on someone else's network and charge per document for the privilege. EDIpipe's translation engine is ours — it runs on the same connection base as our API connectors, speaks X12 directly to your partners, and shows you every raw message it touches.

EDI message flow: a retailer 850 purchase order is translated and mapped into your system, and a 997 acknowledgement returns to the retailer
Fig. 01 — The life of an 850: in as X12, out as your document, confirmed by 997

A purchase order arrives as raw X12. The engine validates it in three layers — envelope, structure, and your partner's implementation guideline — maps it into the document shape your ERP or WMS already speaks, and returns a 997 functional acknowledgement automatically. The raw message, its validation result and its acknowledgement are recorded together in the transmission log — nothing moves untracked.

The engine

Built in-house, in the same codebase as the connector base — not licensed, not wrapped, not a third-party service behind an API.

CODEC

X12 translation core

ISA/GS/ST envelope handling for 4010 and 5010, element-level dictionaries, and control-number discipline that keeps interchange, group and transaction counts consistent.

VALIDATION

Three-layer validation

Syntax, structure, and partner-guideline rules are checked as separate layers, so a rejection tells you exactly which layer failed and where in the segment it happened.

ACK

997 + TA1, automatic

Functional acknowledgements are generated and matched automatically; outbound sends are tracked until the partner's 997 lands — or the alert fires.

MAPPING

Visual mapping, sample preview

Map X12 segments to your documents in a visual editor, and preview the result against sample documents before a partner ever sees traffic. (The in-product raw↔mapped comparison viewer is in build.)

DISPATCH

Idempotent outbound pipeline

Every outbound document is recorded before it is sent, mapped, dispatched and matched to its acknowledgement — a retry can never silently double-send an order or an ASN.

Transaction sets — what runs today, what's next

The full roadmap is 26 transaction sets across retail, warehouse and transportation. We publish the status of every set; nothing below is dressed up.

SetTransactionDirectionStatusNotes
850Purchase OrderInboundSupported todayRetailer and buyer purchase orders, mapped to your order documents.
940Warehouse Shipping OrderInboundSupported todayShipping orders received, three-layer validated and recorded in the transmission log.
945Warehouse Shipping AdviceOutboundSupported todayShipment confirmations generated from your warehouse documents.
997Functional AcknowledgementBothSupported todaySent and received automatically for every interchange — with TA1 at the envelope level.
855Purchase Order Acknowledgement—In buildNow in build on the native engine.
856Advance Ship Notice (ASN)—In buildNow in build on the native engine.
AS2AS2 direct transport (certificates + MDN)—In buildNow in build on the native engine.
810 · 846 · 943 · 944 · 947Invoices, inventory inquiry and warehouse transfer/receipt adviceRoadmapSequenced after the sets now in build; guideline work starts from the official implementation guides.
204 · 990 · 214 · 210Transportation: load tender, response, shipment status, freight invoiceRoadmapSequenced after the sets now in build; guideline work starts from the official implementation guides.
852 · 867 · 861 · 820Product activity, POS resale reporting, receiving advice, payment/remittanceRoadmapSequenced after the sets now in build; guideline work starts from the official implementation guides.
830 · 832Planning schedule / forecast and price-sales catalogRoadmapSequenced after the sets now in build; guideline work starts from the official implementation guides.

Channels: how documents move

LIVE TODAY

SFTP & file channels

We poll your SFTP drop or a local file directory, and we store every file before anything is deleted at the source — a crash mid-pickup can never lose a document.

LIVE TODAY

Your VAN mailbox

On a VAN already? We connect to your mailbox and work through it. We don't operate our own VAN network, and we won't make you switch networks to switch software.

IN BUILD

AS2 direct

Direct AS2 with per-partner certificates, managed certificate lifecycle and MDN receipts is in build. Until it lands, SFTP and VAN mailboxes cover most partners.

LIVE TODAY

EDI networks as connectors

SPS, Rithum, Cleo, TrueCommerce and B2B Gateway are connectors in the catalog — if your trading relationship already runs through a network, it joins the same pipe and the same transmission log as your native traffic.

Templates that accumulate

Retailer EDI programs run on implementation guidelines, and the guidelines are public. We pre-build transaction templates from the official guides — Walmart (Sam's Club DSV), Kohl's, Best Buy Canada, CVS and Macy's 850s are drafted today. A template is certified against your first live exchange with that partner; once certified, it becomes part of your template library, and your ISA identifiers, mappings and message history export with you if you ever leave.

Monitoring & intervention

The transmission log records every interchange with its acknowledgement status. Failed sends alert on thresholds you set; retries and replays run through the same idempotent pipeline, and dead letters stay visible until a human clears them.

Monitoring flow: transmission sent, acknowledgement tracked, failure alert, retry or dead letter, resolved
Fig. 02 — Transmission lifecycle, including the failure branch