Spec Sheet to Live Connection: A Walkthrough

This is a step-by-step walkthrough of taking a retailer's EDI spec sheet and going live in production. Using Sable. Based on a real onboarding flow for an X12 850/856/810 trading relationship with a major grocery retailer.

Names changed. Numbers real.

Day one: the spec sheet arrives

The retailer's EDI team sends over their implementation guide. This one is 84 pages. PDF. Version 4.3, dated February 2026.

The guide covers four transaction sets: 850 (Purchase Order), 855 (PO Acknowledgement), 856 (Advance Shipment Notice), and 810 (Invoice). Standard X12 4010 base, with retailer-specific extensions.

First task: upload the implementation guide to Sable.

Sable's document parser reads the implementation guide. It identifies the four transaction sets, extracts the mandatory and conditional field requirements for each, maps the qualifier codes and code set references, and generates a draft mapping from the retailer's required fields to a canonical internal schema.

This takes four minutes.

The mapping draft is not perfect. It is 80% accurate. Some conditional fields require human judgement about how they map to the ERP's data model. Some qualifier codes need confirmation against the ERP's code sets. The draft is a starting point, not a finished product.

Day one continued: reviewing the mapping

The visual mapping editor opens. Left column: source fields from the ERP (NetSuite, in this case). Right column: target fields from the retailer's 850 implementation guide, organised by segment.

The parser has auto-connected 31 of the 38 required fields. The remaining seven require manual connection.

Three of the seven are straightforward: date format fields where the ERP uses a different format than the retailer requires. A transformation rule handles these — convert from YYYY-MM-DD to YYMMDD at the segment level.

Two are conditional fields that depend on order type. A conditional logic rule routes them correctly based on the BEG02 qualifier.

Two require a question to the ERP team: the retailer's implementation guide requires fields that are not in the standard NetSuite order record. The team confirms the data exists in a custom field. Mapped.

All 38 fields connected. Validation passes. The 850 map is done.

Repeat for 855, 856, and 810. The 855 is simple — most fields are echoed from the 850. The 856 is the most complex: the ASN requires hierarchical loops for shipment, order, and item level data, plus UCC-128 SSCC label generation. The 810 is straightforward.

Total time for all four maps: six hours across day one and the morning of day two.

Day two: testing begins

The retailer's test environment accepts submissions Monday to Friday, 8am to 5pm. Response times are one business day.

First submission: a synthetic 850 based on a sample purchase order. Sent via AS2 to the retailer's test endpoint.

The 997 Functional Acknowledgement arrives four hours later. No errors on the 850.

Second submission: the 855 acknowledging the synthetic PO. Accepted.

Third submission: the 856 ASN with SSCC labels. Two errors.

Error 1: the SSCC label format is correct but the qualifier in the TD1 segment is wrong. The implementation guide specifies a specific value that differs from the base X12 standard. Fix: update the qualifier in the mapping. Five minutes.

Error 2: the CTT segment count is wrong. The parser counted line items before applying a quantity split rule that the retailer uses for catch-weight products. Fix: add a segment count recalculation after the split rule runs. Twenty minutes.

Resubmit the 856. Accepted.

Submit the 810 invoice. Accepted first time.

Day three and four: production validation

Before going live in production, Sable runs a parallel test: send a real purchase order through the Sable integration in test mode alongside the existing manual process. Compare the documents produced.

Two purchase orders arrive from the retailer on day three. Both processed through Sable in test mode. Both produce valid documents that match what the existing process would have produced, with one improvement: the ASNs are generated in real time at pick confirmation rather than in an end-of-day batch. The ASNs arrive at the retailer 4 hours earlier than the current process.

No discrepancies. Sign-off from the ops team.

Day five: go live

Production credentials configured. AS2 connection authenticated. First live purchase order arrives.

850 received and acknowledged in Sable. Confirmation sent to the ERP. 997 sent to the retailer within 30 seconds of receipt.

Goods picked. 856 ASN generated at pick confirmation, transmitted immediately. 997 received from the retailer confirming ASN accepted.

Goods delivered. 810 invoice generated and transmitted. 997 received.

First complete order cycle: zero errors. ASN delivered before goods. Invoice matched PO exactly.

Total time from spec sheet to first live transaction: nine business days.

What made this fast

Three things compressed the timeline.

First, the automated parsing eliminated the spec-reading phase. Reading an 84-page implementation guide manually and extracting all mandatory fields, qualifier codes, and validation rules takes two to three business days for an experienced EDI specialist. Automated parsing does it in minutes.

Second, the pre-built AS2 connector meant transport configuration was a credential setup, not a development project. No AS2 server to build, no certificate exchange process to engineer from scratch.

Third, the retailer was a common trading partner with a well-documented implementation guide. The parser had seen similar guides before. The accuracy on the initial draft was higher than it would be for a novel or poorly documented partner.

For a less common trading partner with a more complex or poorly formatted implementation guide, the same process takes two to three weeks rather than nine days. Still materially faster than the industry average.

What the monitor shows after 30 days

Transaction volume: 847 documents across 204 purchase orders.

Failed documents: 3 (all 997 retries due to trading partner test environment timeout, not data errors).

Chargeback incidents: 0.

ASN compliance rate: 100%.

Average time from PO receipt to 997 acknowledgement: 22 seconds.

The integration is running clean. The retailer scorecard for this supplier moved from 91% to 97% OTIF in the first month.

This walkthrough describes a standard Sable onboarding flow. Your timeline will vary based on trading partner complexity and ERP configuration. Most common trading partner connections go live in under two weeks.