Manufacturing · Packaging, Paper and Printing
EDI and API Integration for Rigid Container, Bottle and Closure Manufacturers
Rigid container, bottle and closure makers supply glass, plastic and metal packaging to fillers and brand owners on tight release schedules. ECOM connects forecasts, releases, pallet shipments and invoices to your ERP so filling lines are not starved.
What this covers
Products and business models in rigid container, bottle and closure
Products
- Glass and plastic bottles and jars
- Closures, caps and dispensers
- Metal cans and tins
- Tubes and specialty containers
Business models
- Manufacturers supplying fillers
- Stock container distributors
- Custom molded and decorated containers
Scenarios
Where rigid container, bottle and closure 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.
-
Just-in-time delivery to lines
- The problem
- Fillers depend on timely deliveries.
- How ECOM helps
- ECOM posts line releases (862) and builds the 856 at the pace the filler needs, with status events for the trucks.
- What you gain
- Deliveries line up with the filler’s schedule.
Talk to an EDI/API Expert about just-in-time delivery to lines Share a sample 862 Shipping Schedule, 856 Advance Ship Notice and 214 Transportation Carrier Shipment Status Message, or describe what goes wrong, and we will show how it would map to your ERP.
-
Mold, decoration and spec versions
- The problem
- Custom containers carry mold and decoration versions.
- How ECOM helps
- ECOM carries mold, decoration and spec versions from orders to notices.
- What you gain
- The version shipped is the version ordered.
Talk to an EDI/API Expert about mold, decoration and spec versions Share a sample 850 Purchase Order and 856 Advance Ship Notice, or describe what goes wrong, and we will show how it would map to your ERP.
-
Pallet configuration
- The problem
- Pallet layers and counts are specified by the customer.
- How ECOM helps
- ECOM builds the 856 with the pallet counts and layer configuration the customer specifies.
- What you gain
- Pallets ship in the configuration the line is set up to receive.
Talk to an EDI/API Expert about pallet configuration Share a sample 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 rigid container, bottle and closure manufacturers
Typical relationships. Which of them apply, and how each one wants to connect, depends on your business.
- Beverage, food, beauty and household brands
- Send forecasts and releases for the containers they fill and set pallet and delivery rules.
- Contract fillers
- Order containers for their lines and are sensitive to late or incorrect deliveries.
- Distributors of stock containers
- Order smaller quantities of standard bottles and closures.
- Resin, glass batch and metal suppliers
- Supply raw materials whose price and lead time shape your build.
- Truckload carriers
- Deliver pallets to filling plants on appointments.
Partner guides: Manufacturer guides · Distributor guides · Carrier guides
Typical workflow
Where ECOM connects your systems and trading partners
The pattern below is typical for rigid container, bottle and closure manufacturers, not one partner's confirmed requirements. Each trading partner publishes its own guide; confirm the details with that partner.
- Filler or brand owner→Your plant and ERP 830 Planning Schedule with Release Capability Planning forecasts and planned releases from the customer, used to plan production and materials. Planning information, not a firm order.
- Filler or brand owner→Your plant and ERP 862 Shipping Schedule Release quantities and delivery times to each line.
- Filler or brand owner→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
- Filler or brand owner→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
- Your plant and ERP→Filler or brand owner 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
- Your plant and ERP→Filler or brand owner 856 Advance Ship Notice Pallet count, layer configuration and production lot.
- Your plant and ERP→Filler or brand owner 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
- Your plant and ERP→Material supplier 850 Purchase Order Purchase orders for resin, glass and closures with quantities and requested delivery dates.
- Material supplier→Your plant and ERP 856 Advance Ship Notice Resin, glass and closure shipments with lot and quantity, used to plan receiving and molding or forming runs.
The diagram draws the exchanges between the lanes shown. Motor-carrier and warehouse documents (204, 990) are listed in the table below with the direction each travels.
Receive forecasts and releases
Forecasts (830) inform what to make; release schedules (862) supplement them with what ships and when.
Take orders and changes
Orders (850) and changes (860) post to the ERP.
Ship by pallet
Tenders (204/990) and ship notices (856) describe pallets, layers and lots.
Invoice
The 810 follows shipment and ties to the release.
Buy materials
Resin, glass and metal orders (850) and supplier notices (856) keep production on schedule.
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 rigid container, bottle and closure manufacturers |
|---|---|---|
| 830 Planning Schedule with Release Capability | You receive | Planning forecasts and planned releases from the customer, used to plan production and materials. Planning information, not a firm order. |
| 862 Shipping Schedule | You receive | Release quantities and delivery times to each line. |
| 850 Purchase Order | You receive | The customer order: items, quantities, prices, ship-to and requested dates. |
| 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. |
| 204 Motor Carrier Load Tender | You send | Tenders a truck shipment to a motor carrier. |
| 990 Response to a Load Tender | You receive | The motor carrier’s acceptance or decline of the tender. |
| 856 Advance Ship Notice | You send | Pallet count, layer configuration and production lot. |
| 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 resin, glass and closures with quantities and requested delivery dates. |
| 856 Advance Ship Notice (supplier side) | You receive | Resin, glass and closure shipments with lot and quantity, used to plan receiving and molding or forming runs. |
Other exchanges you may meet
- Customer vendor-managed inventory programs
- papiNet where used
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
Line-side delivery and pallet detail
A late or wrong pallet stops a filling line. The pallet configuration, layer count and production lot on the ship notice should match what is on the truck, and custom containers carry mold and decoration versions that must be right.
Customer specifications
Packaging and print are made to a customer’s specification, so orders carry specs, artwork or version identifiers that must match what is produced and shipped.
Releases and vendor-managed stock
Customers often issue scheduled releases or have supplier-managed stock at their plants, so forecasts, releases and consumption data matter.
Connected systems
Systems that send and receive this data
Documents are only useful when they reach the systems that run the business.
- ERP
- Production scheduling
- Warehouse management
- Customer portals
ERP integration guides: SAP S/4HANA · Infor CloudSuite Industrial (SyteLine) · Epicor Kinetic · QAD MFG PRO · Microsoft Dynamics 365 Business Central · Oracle NetSuite · 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 filler or brand owner, and agree which documents, versions and data are in scope.
Map to your systems
Map each document to the fields in your ERP and production 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 rigid container, bottle and closure manufacturers
| Exception | Example handling, once configured |
|---|---|
| Release not acknowledged by the due date | The missing acknowledgment can be flagged for review so a filler is not surprised by a missed delivery. |
| Pallet count on the notice differs from the load | A comparison of the 856 pallet count with the load plan or scans can flag a difference for review before the truck leaves. |
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 vendor-managed inventory be supported?
Where a customer shares consumption and inventory, that data can be integrated with your replenishment planning. How replenishment is triggered remains your planning decision.
Can releases arrive daily?
Release frequency is the customer’s choice. The integration handles whatever cadence they send and updates your ERP as each release arrives.
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 rigid container, bottle and closure 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.