Manufacturing · Packaging, Paper and Printing

EDI and API Integration for Corrugated Box and Paperboard Packaging Manufacturers

Corrugated box and paperboard converters make packaging to customer specification, delivered on release schedules to plants and distribution centers. ECOM connects customer forecasts and releases, spec-driven orders, paper and board purchasing, and invoices to your ERP.

View all manufacturing industries

What this covers

Products and business models in corrugated box and paperboard packaging

Products

  • Corrugated boxes and displays
  • Folding cartons and paperboard
  • Point-of-purchase and retail-ready packaging
  • Pallet-ready and custom die-cut packaging

Business models

  • Converters supplying food, beverage and consumer goods makers
  • Sheet plants and box plants serving distributors
  • Display and retail-ready packaging for brands

Scenarios

Where corrugated box and paperboard packaging 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.

  • Spec and artwork versions

    The problem
    Each box has a spec and often artwork or a version number. Orders must reference the current one.
    How ECOM helps
    ECOM carries the spec, artwork or version reference from the order to the 855, 856 and 810 and holds an order that references a superseded version.
    What you gain
    The box produced matches the current spec.

    Talk to an EDI/API Expert about spec and artwork versions 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.

  • Releases against blanket orders

    The problem
    Customers issue releases for specific quantities and dates against a blanket order.
    How ECOM helps
    ECOM posts customer releases (862) against blanket orders (850) and tracks balances in the ERP.
    What you gain
    Releases are checked against the blanket and the production plan.

    Talk to an EDI/API Expert about releases against blanket orders Share a sample 862 Shipping Schedule, 850 Purchase Order and 856 Advance Ship Notice, or describe what goes wrong, and we will show how it would map to your ERP.

  • Paper price and supply swings

    The problem
    Containerboard prices and availability change, affecting quotes and invoices.
    How ECOM helps
    ECOM maps paper mill ship notices and invoices into the ERP.
    What you gain
    Paper supply and price changes reach quotes and costing.

    Talk to an EDI/API Expert about paper price and supply swings 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.

Who you connect with

Trading relationships for corrugated box and paperboard packaging manufacturers

Typical relationships. Which of them apply, and how each one wants to connect, depends on your business.

Food, beverage and consumer goods manufacturers
Send forecasts, releases and orders and set the specifications, artwork and delivery windows for each box.
Distributors and e-commerce fulfillers
Order stock-size boxes in smaller quantities and expect fast shipment.
Mills and paper merchants
Supply containerboard and paperboard whose price and availability shape quotes and lead times.
Ink, adhesive and plate suppliers
Supply consumables for printing and converting.
Truckload carriers
Deliver to customer plants and DCs on release dates and appointments.

Typical workflow

Where ECOM connects your systems and trading partners

The pattern below is typical for corrugated box and paperboard packaging manufacturers, not one partner's confirmed requirements. Each trading partner publishes its own guide; confirm the details with that partner.

  1. Packaging customer→Your plant and ERP 830 Planning Schedule with Release Capability Customer forecast for planning board and press time.
  2. Packaging customer→Your plant and ERP 862 Shipping Schedule Release quantities and dates for each shipment.
  3. Packaging customer→Your plant and ERP 850 Purchase Order Order with spec and artwork or version reference.
  4. Packaging customer→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  5. Your plant and ERP→Packaging customer 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  6. Your plant and ERP→Packaging customer 856 Advance Ship Notice Describes what is shipping, how it is packed and how it is labeled.
  7. Your plant and ERP→Packaging customer 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  8. Your plant and ERP→Paper mill or merchant 850 Purchase Order Purchase orders for paper rolls and linerboard with quantities and requested delivery dates.
  9. Paper mill or merchant→Your plant and ERP 855 Purchase Order Acknowledgment The supplier confirms quantities and dates for paper rolls and linerboard.
  10. Paper mill or merchant→Your plant and ERP 856 Advance Ship Notice Paper roll shipments with roll identifiers, grade, width and weight, used to plan receiving and tie rolls to production.

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.

  1. Forecasts and releases

    Customer forecasts (830) inform production planning; releases (862) supplement them with shipping quantities and dates.

  2. Orders and spec checks

    Orders (850) reference spec and version; changes (860) follow.

  3. Buy paper

    Mill orders (850) with confirmations (855) and notices (856).

  4. Ship and notify

    Tenders (204/990) and ship notices (856) by trailer and pallet.

  5. Invoice

    The 810 bills shipped quantity at the contract price.

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.

DocumentDirectionWhat it carries for corrugated box and paperboard packaging manufacturers
830 Planning Schedule with Release Capability You receive Customer forecast for planning board and press time.
862 Shipping Schedule You receive Release quantities and dates for each shipment.
850 Purchase Order You receive Order with spec and artwork or version reference.
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 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 paper rolls and linerboard with quantities and requested delivery dates.
855 Purchase Order Acknowledgment (supplier side) You receive The supplier confirms quantities and dates for paper rolls and linerboard.
856 Advance Ship Notice (supplier side) You receive Paper roll shipments with roll identifiers, grade, width and weight, used to plan receiving and tie rolls to production.

Other exchanges you may meet

  • papiNet for customers or suppliers in the paper and forest industry
  • Customer supplier portals

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

Specs, releases and paper supply

A box order refers to a spec and version, and the customer releases against it over time. Paper purchasing runs from the release plan, so changes in customer releases must reach purchasing.

  • 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.

  • Reels, rolls, pallets and weights

    Paper and film ship as reels or pallets, priced by weight or area. Quantities and units must agree across orders, shipments and invoices.

Connected systems

Systems that send and receive this data

Documents are only useful when they reach the systems that run the business.

  • ERP with packaging modules
  • Estimating and prepress systems
  • Warehouse management
  • Customer portals

Onboarding and monitoring

From first requirement to daily exception handling

  1. Confirm the requirement

    Obtain each partner's implementation guide or specification, for example from your packaging customer, and agree which documents, versions and data are in scope.

  2. Map to your systems

    Map each document to the fields in your ERP with packaging modules and estimating and prepress systems so the data posts without re-keying.

  3. 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.

  4. 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.

  5. 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 corrugated box and paperboard packaging manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Order references an outdated spec or artwork versionThe order can be held for customer service review so boxes are not printed to a superseded design.
Release exceeds the blanket order quantityThe release can be flagged for review before production so the blanket can be extended or the release adjusted.

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.

Frequently asked questions

Do packaging customers send releases by EDI?

Many do, especially larger food, beverage and consumer goods makers. Others use supplier portals, and ECOM supports that mix so releases reach your ERP however the customer sends them.

Does ECOM support papiNet?

Where a customer or supplier in the paper and forest industry uses papiNet, ECOM confirms the format during scoping and connects it alongside X12 or EDIFACT partners.

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 corrugated box and paperboard packaging 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.