Sell to large retail chains and trade B2B without re-entry
Exchange orders, shipments and invoices with retailers in the EDIFACT/EANCOM standard, publish your B2B catalog on the client portal and manage every sales order in a single inbox — all exposed through Zynvio's public API.
- EDIFACT / EANCOM
- AS2 · Peppol
- GS1 identification (GLN)
- B2B catalog on the portal
- UBL 2.1 & Facturae
- Public API v1
Sales orders
+ Respond to orderOpen orders
24
To respond
3
Shipments today
6
From the retailer's order to payment, without re-entry
The usual problems
Your retailer requires EDI
Large chains require EDIFACT exchange to work with you.
Orders by email/PDF
Orders that have to be keyed in by hand, with transcription errors.
Responding line by line
Confirming quantities order by order, by hand and without traceability.
Shipments without notice
Sending goods with no shipping notice or receiving confirmation.
Manual catalogs
Sending prices and stock to each customer separately.
Every partner is different
Each partner with its own way of exchanging data.
How Zynvio solves it
Retail EDI (EDIFACT/EANCOM)
Exchange with large retail in the EDIFACT/EANCOM standard (D96A), tested end to end.
Full order cycle
The retailer's order comes in, you respond with acceptance or line-by-line changes (confirmed quantities), notify the shipment and close with the receiving confirmation.
Partial shipments
Fulfill an order in several deliveries: each shipment updates the order automatically.
GS1 identification (GLN)
GLNs on your business, contacts, customers, suppliers and warehouses, with check-digit validation.
Reliable EDI messaging
Outbox with pull and ACK for your connector, deduplication and retries; inbound log and readable per-year numbering.
Sales order inbox
All your orders —EDI, portal or B2B— in one inbox: accept, modify or reject and convert to quote, invoice or delivery note.
B2B catalog on the portal
Publish products and services with prices and VAT: your customers build a cart and submit orders from their portal.
Orders to suppliers
Purchase requests from the supplier record: if your supplier uses Zynvio they land straight in their panel; if not, by email with PDF and confirmation.
Public API v1
EDI messaging and catalog exposed through the public API, with API keys and scopes per integration.
Structured invoicing
Facturae 3.2.1 and UBL 2.1 (EN 16931) for businesses, the Administration and European exchange.
AS2 & Peppol connectivity
Connect to each partner's network over AS2 or through the European Peppol network (B2B and B2G), with the connection operated by ZyngRoute.
Connect your tools via API
EDI messaging and the B2B catalog are exposed through the public API v1; managed connectivity comes from ZyngRoute.
- Public API v1 with API keys and scopes: orders, EDI messaging and B2B catalog.
- Outbox with pull and ACK for the external connector, with deduplication and retries; inbound message log.
- ZyngRoute, Zynvio's managed EDI connector (AS2/SFTP/VAN and the Peppol network), if you'd rather not operate the connectivity.
- Structured Facturae 3.2.1 and UBL 2.1 (EN 16931) invoices; CSV/Excel import and export with mapping profiles.
- Shopify, WooCommerce and Amazon integrations (order → invoice).
Automate your workflows
The cycle with each retailer moves forward on its own and leaves a trail.
- Incoming orders land straight in your sales order inbox.
- Each shipment updates the order automatically, partials included.
- Automatic retries and deduplication in EDI messaging.
- Readable per-year numbering of outbound documents.
Who it's for
Suppliers to large retail
Chains and supermarkets that require EDIFACT/EANCOM from their suppliers.
What you gain
EDIFACT/EANCOM EDI ready to deploy, tested end to end.
GS1 identification (GLN) validated on customers, suppliers and warehouses.
A single inbox for every sales order.
B2B catalog on the portal, no more price lists by email.
Public API v1 with API keys and scopes.
Frequently asked questions
Which EDI standard does Zynvio support?
EDIFACT with the EANCOM subset (D96A), the standard of European large retail. ANSI X12, predominant in North America, remains on the roadmap.
How does the order cycle with a retailer work?
The retailer's order lands in your inbox; you respond by accepting, rejecting or proposing line-by-line changes with confirmed quantities; you notify each shipment —partials included— and the cycle closes with the receiving confirmation.
How does Zynvio connect to my customer's EDI network?
Messages are made available in an outbox with pull and ACK that your connector consumes through the public API v1, with deduplication and retries. If you'd rather not operate the connectivity, ZyngRoute —Zynvio's managed EDI connector— takes care of transport (AS2, SFTP, VAN or the Peppol network), onboarding and certification with each retailer.
What is a GLN and where is it used?
The GLN (Global Location Number) is GS1's location identifier. Zynvio manages it on the business, contacts, customers, suppliers and warehouses, with check-digit validation.
What about my B2B customers who don't use EDI?
Publish your B2B catalog on the client portal: they browse products and services with prices and VAT, build a cart and submit orders that land in the same inbox. The public catalog API with tokens is available with the Inventory add-on, and with the Zynvio network documents flow portal to portal.
What structured invoice formats does it support?
Facturae 3.2.1 for businesses and the Administration, and UBL 2.1 (EN 16931) for European exchange.
Do you support Peppol?
Yes. Through ZyngRoute, Zynvio delivers and picks up invoices and documents over the European Peppol network (B2B and B2G), alongside AS2, SFTP or VAN transport with large-retail networks.
Explore more modules
Turn your operation into a connected system
Request a demo and see Zynvio in action.