How Sable works
How Sable works.
A walkthrough of the Sable platform - from spec sheet to live trading partner in under two weeks.
Sable sits between your business systems and your trading partners. One connection in, every protocol out.
Sable Mapping
Stop building mappings from scratch.
Every retailer publishes a spec sheet describing exactly how they want their EDI documents formatted. Different field requirements, different validation rules, different code lists. Implementing one of these used to mean a 2-3 week engineering project.
Sable parses the spec sheet automatically. X12 implementation guides, EDIFACT subset specifications, Peppol BIS profiles, custom JSON schemas. Sable identifies the document types covered, extracts the field requirements, and generates a mapping draft.
You review the draft in a visual editor. Source fields from your ERP on the left, target fields from the trading partner on the right. Drag to connect. Adjust transformations. Add conditional logic where needed. Sable validates as you build.
When the mapping is complete, you push it to staging. Sable runs synthetic transactions against the trading partner's test environment. Errors are flagged with the specific field and validation rule that failed. Most mappings clear staging within 2-3 days.
Sable Routing
Every protocol your trading partners speak.
Your trading partners use whatever protocol they decided was best 5-15 years ago. Sable handles the protocol layer so your team doesn't have to.
If the partner needs AS2, Sable sends AS2. If they need Peppol, Sable sends Peppol. Same source data. Different transports. No engineering work on your side.
Sable Network
Pre-built connections to 340+ trading partners.
The hardest part of EDI isn't the technology. It's that every trading partner implements the standards differently. A Walmart 850 PO is not the same as a Target 850 PO is not the same as a Costco 850 PO. All three are valid X12. All three need different mappings.
Sable maintains a network of pre-built adapters for the trading partners that matter most. Major retailers, hotel chains, foodservice distributors, healthcare networks, government procurement systems. When your customer is already in the network, onboarding takes hours. Not weeks.
The network grows weekly. Customer requests for new partners get prioritised. Most new adapters are built within 5 business days.
Sable Monitor
Visibility into every transaction.
EDI fails silently. A document gets rejected, the trading partner moves on, you find out three weeks later when the chargeback hits.
Sable monitors every transaction in real-time. Failed documents are flagged immediately. Validation errors include the specific field and the rule that failed. Retry logic runs automatically. If a document requires human attention, the right person gets notified.
All transactions are logged for audit. Compliance teams can pull a full history per partner, per document type, per date range. Tax authorities get clean records. Disputes get resolved with data, not arguments.
Sable Catalogue
Per-customer product and pricing management.
Wholesale distributors run different catalogues for different customers.
Customer A buys 2,000 SKUs at one set of prices. Customer B buys 800 at a different set with their own product codes. When prices change, those catalogues need to update across every affected trading partner.
Today most distributors manage this in spreadsheets. The spreadsheets are always slightly wrong. Wrong data flows through correct integrations and creates chargebacks.
Sable Catalogue replaces the spreadsheet with a managed data layer. Define which products each customer can buy, at what price, with what product codes. Connect it to your ERP so the product master stays in sync. When anything changes - price update, new product, discontinued SKU - Sable identifies every affected trading partner and queues the update automatically.
The update goes out in the right format for each partner. Their product codes, their required fields, their validation rules. You don't touch it.
Connects to: NetSuite, SAP, Microsoft Dynamics 365, Oracle, Xero, MYOB, Pronto, Cin7, Acumatica, Sage X3.
Outputs via: X12 832, EDIFACT PRICAT, Peppol Catalogue BIS, JSON product feeds, flat CSV.
3 trading partners updated · 0 errors · propagation complete
Supported protocols
Every transport your trading partners speak.
Native AS2, AS4, SFTP, Peppol Access Point, REST, GraphQL, and traditional VAN bridge mode.
| Protocol | Used by | Sable support |
|---|---|---|
| AS2 | US/EU retailers, healthcare | Native |
| AS4 | Peppol network | Native |
| SFTP | Foodservice, wholesale, logistics | Native |
| Peppol Access Point | EU, ANZ, Singapore, Malaysia government | In progress |
| REST API | Modern procurement systems | Native |
| GraphQL | Newer ecommerce platforms | Native |
| FTPS | Legacy retailers | Native |
| Traditional VAN | Long-tail trading partners | Bridge mode |
Document coverage
200+ document types across X12, EDIFACT, and Peppol BIS.
Plus extensions for country-specific compliance flavours.
850 PO, 855 PO Acknowledgment, 856 ASN, 810 Invoice, 820 Payment, 832 Catalogue, 846 Inventory Inquiry, 852 Product Activity, 940 Warehouse Shipping Order, 945 Warehouse Shipping Advice, 997 Functional Acknowledgment, plus 200+ additional transaction sets.
ORDERS, ORDRSP, DESADV, INVOIC, PAYORD, PRICAT, INVRPT, CONTRL, plus full coverage of D.96A, D.01B, D.07B, D.16A subsets.
Invoice, Credit Note, Order, Order Response, Despatch Advice, Catalogue. Country-specific extensions for Australia, New Zealand, Germany, France, Italy, Poland, Singapore.
Stop building integrations. Start trading.
See how Sable cuts your trading partner onboarding from months to days.