The EDI platform your trading partners never have to think about.
One runtime for X12, EDIFACT, AS2, AS4,
OFTP2, and SFTP - with built-in 997/999
acknowledgments, MDN verification, and an immutable audit trail. Onboarding a new partner
is a config change, not a project.
- Built by Microsoft V-TSP consultants
- ·
- Microsoft Solutions Partner
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.
A purchase-to-payment cycle, end-to-end. Same pattern, every partner.
One representative buyer↔seller flow in X12 - same acknowledgments, correlation, and audit trail across every partner. EDIFACT runs the identical lifecycle.
The transactions your industry actually runs on.
Pre-built maps and partner profiles for the X12 transaction sets that dominate each vertical, plus full EDIFACT coverage. Hover any transaction to see it light up across industries.
Retail / e-commerce
- 850 Purchase Order
- 855 PO Ack
- 856 ASN
- 810 Invoice
- 820 Payment / Remit
- 940 Warehouse Shipping Order
- 945 Warehouse Shipping Advice
- 832 Price / Sales Catalog
- 846 Inventory Inquiry / Advice
- 870 Order Status Report
Logistics / transportation
- 204 Motor Carrier Load Tender
- 214 Shipment Status
- 210 Freight Details & Invoice
- 211 Motor Carrier Bill of Lading
- 990 Response to Load Tender
- 858 Shipment Information
- 404 Rail Carrier Shipment Info
- 410 Rail Carrier Freight Details
- 322 Terminal Operations
- 240 Motor Carrier Package Delivery
Healthcare X12
- 270 Eligibility Inquiry
- 271 Eligibility Response
- 276 Claim Status Inquiry
- 277 Claim Status Response
- 278 Healthcare Services Review
- 820 Premium Payment
- 834 Benefit Enrollment
- 835 Claim Payment / Remit
- 837 P/I/D Healthcare Claim
- 999 Implementation Ack
Manufacturing / automotive
- 830 Planning Schedule
- 862 Shipping Schedule
- 866 Production Sequence
- 869 Order Status Inquiry
- 824 Application Advice
- 850 Purchase Order
- 856 ASN (HDR / Tier-1)
- 832 Sales Catalog
- 846 Inventory Advice
- 997 Functional Ack
From CW-001 envelope spec to live trading. In days, not weeks.
The pipeline below applies to every partner, regardless of standard or transport. The longest step is usually waiting on the partner’s test environment - not your work.
- Import partner envelope spec (ISA/GS qualifiers, version, IDs)
- Configure AS2 endpoints, certs, MDN preferences
- Set retention and ACK preferences (997, 999, TA1)
- Select pre-built map for the partner’s transaction variant
- Apply partner-specific deltas (segment qualifiers, custom loops)
- Configure code-list translations and unit-of-measure normalization
- Send test transactions through the sandbox endpoint
- Verify 997/999 round-trip, MDN signing & encryption
- Partner sign-off captured in the audit trail
- Promote partner profile to production (config-only, no rebuild)
- Enable production routing; monitor first transactions live
- Partner appears in the operator UI for end-to-end tracking
Standard partners complete this pipeline in 3–5 business days. Heavily customized partners extend the Match Maps step, but rarely the others.
Built for the industries that live and die by EDI.
The same runtime, tuned to the transaction sets and partners each vertical depends on.
850 · 855 · 856 · 810
Onboard big-box and marketplace partners without forking orchestrations.
204 · 214 · 210
Motor-carrier flows with 997 reconciliation and AS2 + SFTP + VAN.
830 · 862 · 856
Planning and shipping schedules for JIT and tier-1 supply chains.
Built for the realities of EDI operations.
Pre-built maps and partner profiles turn onboarding into a config change. The longest step is usually waiting on the partner’s test environment - not the work on your side.
997/999 acknowledgments, MDN verification, and an immutable audit trail mean nothing slips through unreconciled - your trading partners and internal auditors both pass.
Twenty trading partners, reviewed by a senior architect. Written audit in one week.
A written audit of your trading-partner posture.
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.
- Written audit within 5 business days of intake
- Reviewed by a senior EDI architect - not a generalist
- No cost, no obligation. NDA on file before any partner data is reviewed.
- Result is yours to share internally with partners or auditors
What EDI directors ask before signing.
Can we run Art2link alongside our existing EDI platform during cutover?
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.
What about our partner-specific map variants? Walmart wants one 856, Target wants another.
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.
How are 997s and 999s handled, and what happens when one is missing?
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.
Do you support VAN connectivity for partners that aren’t on AS2?
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.
What does the partner audit actually look like as a deliverable?
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.
Try the Starter Plan, free, in your subscription.
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.