Manufacturing · Food Manufacturing
EDI and API Integration for Sauce, Dressing and Condiment Manufacturers
Sauce, dressing and condiment makers sell small retail packs and large foodservice formats from the same plant. ECOM connects customer orders, shipping documents and invoices to your ERP across both channels.
What this covers
Products and business models in sauce, dressing and condiment
Products
- Sauces, dressings and marinades
- Ketchup, mustard and mayonnaise
- Salsa and dips
- Foodservice jugs, pails and packets
Business models
- Brands for retail
- Foodservice and portion-pack supply
- Private label and co-packing
Scenarios
Where sauce, dressing and condiment manufacturers 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.
-
Retail and foodservice formats
- The problem
- One recipe may exist in bottles, packets, jugs and totes, each with its own item number and unit of measure.
- How ECOM helps
- ECOM maps each retail and foodservice format (bottle, packet, jug, tote) to its own ERP item and unit of measure.
- What you gain
- The same recipe is ordered, shipped and invoiced in the unit each customer expects.
Talk to an EDI/API Expert about retail and foodservice formats Share a sample 850 Purchase Order, 856 Advance Ship Notice and 810 Invoice, or describe what goes wrong, and we will show how it would map to your ERP.
-
Promotional orders
- The problem
- Retail promotions drive heavy volume for specific pack sizes.
- How ECOM helps
- ECOM posts promotional orders to the ERP as they arrive and can alert planners when a promoted pack size exceeds plan.
- What you gain
- Filling and packing plans can respond to promotional volume in time.
Talk to an EDI/API Expert about promotional orders Share a sample 850 Purchase Order and 860 Purchase Order Change Request, or describe what goes wrong, and we will show how it would map to your ERP.
-
Ingredient and glass supply
- The problem
- Bottles, closures and ingredients are bought in volume; late supplier shipments halt filling lines.
- How ECOM helps
- ECOM maps supplier 855s and 856s for bottles, closures and ingredients into your ERP and can flag a late shipment against a fill date.
- What you gain
- Purchasing sees a late glass or closure shipment before the filling line runs out.
Talk to an EDI/API Expert about ingredient and glass supply Share a sample 850 Purchase Order, 855 Purchase Order Acknowledgment and 856 Advance Ship Notice, or describe what goes wrong, and we will show how it would map to your ERP.
Who you connect with
Trading relationships for sauce, dressing and condiment manufacturers
Typical relationships. Which of them apply, and how each one wants to connect, depends on your business.
- Grocery and club retailers
- Order retail packs on promotion cycles.
- Foodservice distributors
- Order large formats and portion packs.
- Quick-service chains
- Place orders through their distributors with specific item rules.
- Ingredient, glass and closure suppliers
- Their ship notices drive line schedules.
- Carriers and 3PLs
- Warehouse and freight movement.
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 sauce, dressing and condiment manufacturers, not one partner's confirmed requirements. Each trading partner publishes its own guide; confirm the details with that partner.
- Retailer or foodservice distributor→Your plant and ERP 850 Purchase Order Orders by pack format and unit of measure, including promotional quantities.
- Retailer or foodservice distributor→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
- Your plant and ERP→Retailer or foodservice distributor 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
- Your plant and ERP→Retailer or foodservice distributor 856 Advance Ship Notice Describes what is shipping, how it is packed and how it is labeled.
- Your plant and ERP→Retailer or foodservice distributor 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
- Your plant and ERP→Packaging and ingredient supplier 850 Purchase Order Purchase orders for bottles, closures and ingredients with quantities and requested delivery dates.
- Packaging and ingredient supplier→Your plant and ERP 855 Purchase Order Acknowledgment The supplier confirms quantities and dates for bottles, closures and ingredients.
- Packaging and ingredient supplier→Your plant and ERP 856 Advance Ship Notice Bottle, closure and ingredient deliveries that gate filling schedules.
The diagram draws the exchanges between the lanes shown. Motor-carrier and warehouse documents (940, 945) are listed in the table below with the direction each travels.
Orders by pack format
Orders (850) and changes (860) post by item and unit of measure.
Plan filling and ingredients
Open orders drive filling schedules; supplier orders (850), confirmations (855) and ship notices (856) keep inputs on time.
Pick and label
Warehouse release (940/945) and pallet labels follow the customer’s rules.
Ship notice
The 856 describes pallets, cases and dates.
Invoice and deduct
The 810 follows; promotion and pricing differences are researched against the order.
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 sauce, dressing and condiment manufacturers |
|---|---|---|
| 850 Purchase Order | You receive | Orders by pack format and unit of measure, including promotional quantities. |
| 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. |
| 850 Purchase Order (supplier side) | You send | Purchase orders for bottles, closures and ingredients with quantities and requested delivery dates. |
| 855 Purchase Order Acknowledgment (supplier side) | You receive | The supplier confirms quantities and dates for bottles, closures and ingredients. |
| 856 Advance Ship Notice (supplier side) | You receive | Bottle, closure and ingredient deliveries that gate filling schedules. |
Other exchanges you may meet
- GS1 pallet and case labels
- Distributor item-data and pricing files
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
Formats, units and dates
The same sauce ships as 12-count retail cases and as a one-gallon jug. Units of measure and conversions have to be right in orders, ship notices and invoices, and best-before dates on shipping data should match the cases.
Shelf life and expiration
Grocery and foodservice customers set minimum remaining shelf life at receipt, so ship notices and labels often have to carry production or expiration dates that match the cases on the pallet.
Lots and recalls
Lot codes tie finished goods to ingredients and production runs. When a customer or the plant needs to trace a lot, the lot on the ship notice is the link between your records and theirs.
Connected systems
Systems that send and receive this data
Documents are only useful when they reach the systems that run the business.
- ERP
- Filling-line scheduling
- Warehouse management
- Distributor portals
ERP integration guides: SAP S/4HANA · Oracle NetSuite · Microsoft Dynamics 365 Business Central · Infor CloudSuite Industrial (SyteLine) · Epicor Kinetic · SAP Business One · 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 retailer or foodservice distributor, and agree which documents, versions and data are in scope.
Map to your systems
Map each document to the fields in your ERP and filling-line scheduling 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 sauce, dressing and condiment manufacturers
| Exception | Example handling, once configured |
|---|---|
| Unit-of-measure mismatch on an order line | The line can be held for review rather than posted with the wrong quantity. |
| Closure shipment late | A late supplier 856 or an overdue expected date can be flagged to purchasing before the line is due to run out. |
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
Can foodservice and retail orders share the same integration?
They share your ERP, but each customer’s documents, item numbers and rules are mapped separately so a distributor’s jug order and a retailer’s case order both post correctly.
How are promotions handled?
Promotional orders arrive as purchase orders and changes, and the ERP sees them as soon as they are received.
Can lot and expiration data travel with the ship notice?
Where the trading partner asks for it, lot, production date and expiration data can be included in the advance ship notice from your ERP or warehouse system. Which fields, at which level of the shipment, is set by the partner’s implementation guide, so ECOM confirms it with the guide during setup.
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 sauce, dressing and condiment manufacturers
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.