One runtime for X12, EDIFACT, AS2, AS4,
OFTP2, and SFTP. Built-in 997/999 acknowledgments,
MDN/MIC verification, partner-specific envelopes, and an immutable audit trail your trading
partners and internal auditors will both pass. Onboarding a new partner is a config change —
not a project.
Every new partner means new envelopes, qualifiers, version differences, certs, and weeks of back-and-forth before the first successful transaction lands.
Walmart wants one variant of the 856. Target wants another. Amazon wants a third. The map matrix grows faster than the team can maintain it.
997s and 999s get dropped, mis-routed, or never reconciled. Operations finds out at month-end when a partner asks about a missing invoice.
“Did we send the 855?” “Did they ack our 856?” The answer requires a ticket, a screen-share, and 30 minutes of someone’s afternoon.
One representative buyer↔seller flow in X12. Same acknowledgments, same correlation,
same immutable audit trail across every partner in your network. EDIFACT
(ORDERS / ORDRSP / DESADV / INVOIC / REMADV) runs the identical lifecycle.
Pre-built maps and partner profiles for the X12 transaction sets that dominate each vertical — plus full EDIFACT coverage for international and automotive supply chains. Hover any transaction to see it light up across industries.
The onboarding pipeline below applies to every trading partner regardless of standard or transport. The longest single step is usually waiting on the partner’s test environment — not the work on your side.
Standard partners (those who follow the X12 implementation guide as published) complete this pipeline in 3–5 business days. Heavily customized partners with proprietary envelope variants extend the Match Maps step but rarely the others.
A national retailer onboarded 200+ trading partners onto Art2link in 4 months — cutting average per-partner onboarding from 3 weeks to 4 days, with no production outage during the transition.
A nationwide 3PL processes 2M+ EDI transactions/month across 1,200 trading partners — including X12 204/214/210 motor-carrier flows, with zero unreconciled 997s for the past 6 quarters.
An Art2link senior EDI architect reviews up to 20 of your trading-partner profiles and returns a written audit covering: envelope-spec gaps, ACK-handling exposure, AS2 certificate hygiene, map-variant sprawl, and the specific transactions most at risk of partner SLA penalties. The deliverable is yours regardless of whether you proceed with Art2link.
Yes. The methodology assumes parallel run on a partner-by-partner basis. New partners can come onto Art2link first; existing partners migrate in waves at your pace. The legacy platform keeps processing traffic until its last partner moves. We never recommend a big-bang EDI cutover.
Map variants are first-class. Each partner profile carries its own variant of every transaction set it exchanges. The base map is shared, the delta is partner-specific, and the maps match at runtime via the partner ID on the envelope. You don’t maintain N copies of the 856 map — you maintain one map plus N deltas.
Outbound transactions auto-expect 997s within a partner-configurable window (default 4 hours). Missing 997s raise an alert and the message moves into an unresolved state with the original envelope context preserved. 999s are supported for partners that require strict envelope validation. AS2 MDNs are correlated separately at the transport layer.
Yes. VAN passthrough is fully supported — Art2link sends and receives via the major VANs (Sterling Commerce, OpenText, IBM, Comdata, GXS Express). Many enterprises run AS2 with their top-tier partners and VAN for the long tail; one Art2link runtime serves both transport modes.
A written report (10–15 pages typically) covering each reviewed partner: envelope-spec adherence, ACK-handling configuration, transaction-set variant exposure, AS2 cert expiry & rotation posture, and a flagged-risks summary at the top. It’s designed to be readable by your internal stakeholders and shareable with partners under NDA if you choose.
Install the free Starter Plan from Azure Marketplace and onboard a single test partner through the platform before scoping the rest. No sales call required.