Manufacturing · Beverage Manufacturing
EDI and API Integration for Wine and Spirits Producers
Wine and spirits producers sell through distributors, importers and direct channels, often by allocation. ECOM connects distributor orders, shipments and sales reports to your ERP so allocations, lots and invoices are handled consistently.
What this covers
Products and business models in wine and spirits
Products
- Wine by vintage and varietal
- Spirits, liqueurs and ready-to-drink cocktails
- Limited and allocated releases
- Bulk wine and spirits for other producers
Business models
- Wineries and distilleries selling through distributors
- Importers and brand owners
- Direct-to-consumer alongside wholesale
Scenarios
Where wine and spirits producers lose time and margin
Recurring problems for this kind of business, how ECOM connects the systems and documents involved, and what you gain. Bring your own example and we will work through it with you.
-
Allocation and limited releases
- The problem
- Scarce releases are divided among distributors, so orders must be matched to allocations.
- How ECOM helps
- ECOM compares incoming orders with the allocation held in your ERP and can hold orders above a distributor’s allocation for review.
- What you gain
- Scarce releases are divided by the rules you set, not by whoever ordered first.
Talk to an EDI/API Expert about allocation and limited releases Share a sample 850 Purchase Order and 846 Inventory Inquiry/Advice, or describe what goes wrong, and we will show how it would map to your ERP.
-
Vintage and lot detail
- The problem
- Vintage, lot and bottling details are part of the item and have to match on shipping documents.
- How ECOM helps
- ECOM carries vintage, lot and bottling data from your ERP to the 856.
- What you gain
- The detail on the paperwork matches the item that shipped.
Talk to an EDI/API Expert about vintage and lot detail Share a sample 856 Advance Ship Notice, or describe what goes wrong, and we will show how it would map to your ERP.
-
Layered distribution
- The problem
- Importers, distributors and retailers each handle product in sequence.
- How ECOM helps
- ECOM maps importer, distributor and warehouse documents (including 852 and 867) so each tier reports to the same ERP.
- What you gain
- Depletion and inventory data from each layer reach one place.
Talk to an EDI/API Expert about layered distribution Share a sample 852 Product Activity Data, 867 Product Transfer and Resale Report and 945 Warehouse Shipping Advice, or describe what goes wrong, and we will show how it would map to your ERP.
Who you connect with
Trading relationships for wine and spirits producers
Typical relationships. Which of them apply, and how each one wants to connect, depends on your business.
- Distributors and importers
- Order, allocate and report sales.
- Retail and on-premise accounts
- Order through the distributor in most markets.
- Glass, closure and label suppliers
- Packaging with long lead times.
- Bulk and contract producers
- Supply or bottle under contract.
- Carriers and bonded warehouses
- Move and hold product.
Partner guides: Retailer guides · Distributor guides · 3PL and logistics guides
Typical workflow
Where ECOM connects your systems and trading partners
The pattern below is typical for wine and spirits producers, not one partner's confirmed requirements. Each trading partner publishes its own guide; confirm the details with that partner.
- Distributor or importer→Your plant and ERP 850 Purchase Order Orders matched against allocation by item and vintage.
- Distributor or importer→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
- Your plant and ERP→Distributor or importer 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
- Your plant and ERP→Carrier or bonded warehouse 940 Warehouse Shipping Order Tells the warehouse or 3PL what to pick and ship.
- Carrier or bonded warehouse→Your plant and ERP 945 Warehouse Shipping Advice Confirms what the warehouse actually shipped.
- Your plant and ERP→Distributor or importer 856 Advance Ship Notice Describes what is shipping, how it is packed and how it is labeled.
- Your plant and ERP→Distributor or importer 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
- Your plant and ERP→Distributor or importer 846 Inventory Inquiry/Advice Available inventory by item and vintage.
- Distributor or importer→Your plant and ERP 852 Product Activity Data Sales and inventory data from the customer, used for replenishment and planning.
- Distributor or importer→Your plant and ERP 867 Product Transfer and Resale Report Distributor resale reporting where provided.
Orders against allocation
Orders (850) and changes (860) post to the ERP and are checked against allocation.
Confirm and release
Confirmations (855) and warehouse release (940/945).
Ship notice
The 856 reports cases, vintage or lot and pallet detail.
Invoice
The 810 follows shipment.
Inventory and sales reporting
Inventory (846) and distributor sales reports (852/867) feed planning and allocation.
EDI and API exchanges
The documents behind the workflow
X12 transaction sets typical for this workflow, with what each carries here. Select a code for the full transaction reference.
| Document | Direction | What it carries for wine and spirits producers |
|---|---|---|
| 850 Purchase Order | You receive | Orders matched against allocation by item and vintage. |
| 860 Purchase Order Change Request | You receive | Changes to open orders: quantities, dates or cancellations. |
| 855 Purchase Order Acknowledgment | You send | The order acknowledgment: confirms the order or reports differences from what was requested, including dates. |
| 940 Warehouse Shipping Order | You send | Tells the warehouse or 3PL what to pick and ship. |
| 945 Warehouse Shipping Advice | You receive | Confirms what the warehouse actually shipped. |
| 856 Advance Ship Notice | You send | Describes what is shipping, how it is packed and how it is labeled. |
| 810 Invoice | You send | Bills for what was shipped, tied to the order and the ship notice. |
| 846 Inventory Inquiry/Advice | You send | Available inventory by item and vintage. |
| 852 Product Activity Data | You receive | Sales and inventory data from the customer, used for replenishment and planning. |
| 867 Product Transfer and Resale Report | You receive | Distributor resale reporting where provided. |
Other exchanges you may meet
- Distributor-specific portals
- Regulatory reporting handled outside the integration
Where a trading partner offers an API, a portal or file exchange instead of EDI, ECOM scopes that connection alongside the EDI ones. Functional acknowledgments (997 or 999) report validation results, including rejection; they do not prove business acceptance or ERP posting. Which acknowledgments and business responses each partner expects is confirmed with that partner.
Operational detail
Allocation, vintage and bonded storage
An item can be a vintage with a limited quantity. Allocation logic belongs in your ERP; the integration makes sure orders arrive in a form that logic can use and returns confirmations and inventory.
Mixed pallets and promotions
Beverage orders are often promotional, seasonal and built from several packages and flavors. Order changes and promotional quantities need to reach production and the warehouse before a load is built.
Distributor and retailer channels
Many beverages reach shelves through distributors, so orders, inventory and sales data may flow through a different partner than the retailer.
Connected systems
Systems that send and receive this data
Documents are only useful when they reach the systems that run the business.
- ERP
- Winery or distillery production systems
- Bonded warehouse systems
- Direct-to-consumer platforms
ERP integration guides: SAP S/4HANA · Oracle NetSuite · Microsoft Dynamics 365 Business Central · Infor CloudSuite Industrial (SyteLine) · SAP Business One · Epicor Kinetic · All ERP guides
Onboarding and monitoring
From first requirement to daily exception handling
Confirm the requirement
Obtain each partner's implementation guide or specification, for example from your distributor or importer, and agree which documents, versions and data are in scope.
Map to your systems
Map each document to the fields in your ERP and winery or distillery production systems so the data posts without re-keying.
Test with the partner
Exchange test documents and review the results with the partner before go-live, including changes, cancellations and error cases, not only the simple order.
Validate, acknowledge and monitor
A 997 or 999 reports the validation result of the document as received, including rejection; it does not show that the business accepted the content or that your ERP posted it. Business responses are separate: an 855 for orders, an 824 for application errors. Monitoring can show what is late, missing or rejected, once it is set up with you.
Resolve exceptions
Which failures and late documents are watched, who is alerted and how each is resolved are agreed during onboarding. Rejected or unacknowledged documents can then go to the people who can fix them, with the document and the reason in view.
Example exceptions for wine and spirits producers
| Exception | Example handling, once configured |
|---|---|
| Order exceeds allocation for a distributor | The order can be held for review. |
| Vintage on ship notice differs from order | A comparison of the vintage on the 856 with the order can hold the notice for review. |
Illustrative examples of exceptions a team in this industry may need to review. Each check compares data from your ERP, WMS, trading partner documents or scans, where those are available. Which conditions are checked, who is alerted and what happens next are configured with you during onboarding. This is not a screenshot of a live system or a list of built-in checks.
How ECOM helps
ECOM products and services that apply
Each partner connects in the way it can support. These products cover the connections and visibility manufacturers need most.
-
PRISM-EDI
Exchange of schedules, orders, ship notices and invoices with customers and suppliers in X12 or EDIFACT, translated to and from your ERP.
-
PRISM-WebEDI
Browser-based purchase orders, acknowledgments, ship notices and invoices for suppliers without EDI systems.
-
PRISM-SmartConvert
Supplier confirmations, invoices and customer orders that arrive as PDFs, emails or scans converted into ERP-ready data.
-
PRISM-SCV
Monitoring of transactions and exceptions across customer and supplier documents.
Services: Trading partner onboarding · ERP integration · API integration · Fully managed EDI · Supply chain visibility · Mapping and translation
Frequently asked questions
Who handles regulatory reporting?
Your compliance team. The integration exchanges orders, shipments, inventory and invoices; it does not replace licensing, tax or label compliance.
Can direct-to-consumer orders connect too?
Orders from ecommerce platforms can be integrated with the same ERP. That is a separate connection from the wholesale distributor flows.
Do beverage companies sell through retailers and distributors with the same documents?
The core order, ship notice and invoice documents are similar, but distributors often add inventory, sales and promotion data and use their own item numbers. Each partner publishes its own guide, so the set is confirmed per partner.
Do you need our trading partner's implementation guide to start?
It helps, but you can start without one. Tell us who you trade with and which systems you run, and we will help obtain and review each partner's requirements. The guide, not this page, decides the exact documents, versions and rules for that partner.
Talk to an EDI/API expert about wine and spirits producers
Share your trading partners, your ERP, a sample document or the problem that keeps recurring. A completed specification is not needed: a partner guide, a rejected document or a description of the issue is enough to start.