Manufacturing · Packaging, Paper and Printing

EDI and API Integration for Paper, Pulp and Tissue Manufacturers

Paper, pulp and tissue mills sell reels, sheets, bales and finished tissue to converters, distributors and retailers by truck and rail. ECOM connects orders, reel and bale detail, freight and invoices to your ERP, with papiNet or X12 as each customer requires.

View all manufacturing industries

What this covers

Products and business models in paper, pulp and tissue

Products

  • Printing, writing and packaging papers
  • Market pulp
  • Tissue, towel and napkin products
  • Specialty and industrial paper

Business models

  • Mills selling to converters and distributors
  • Tissue brands selling to retailers
  • Merchants and brokers

Scenarios

Where paper, pulp and tissue 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.

  • Reels, rolls and weights

    The problem
    Quantities are weights or roll counts with tolerances.
    How ECOM helps
    ECOM maps reel and roll weights with tolerances onto the 856 and 810 and compares them with the order tolerance.
    What you gain
    Weight differences are reviewed before billing.

    Talk to an EDI/API Expert about reels, rolls and weights 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.

  • Rail and truck loads

    The problem
    Mills ship by railcar and truck with different documents.
    How ECOM helps
    ECOM keeps truck tenders (204/990) and railcar shipments apart; trucks use the motor-carrier transactions and railcars follow their own routing.
    What you gain
    Each mode is handled with the right documents.

    Talk to an EDI/API Expert about rail and truck loads Share a sample 204 Motor Carrier Load Tender, 990 Response to a Load Tender and 856 Advance Ship Notice, or describe what goes wrong, and we will show how it would map to your ERP.

  • papiNet versus X12

    The problem
    Some customers use papiNet and others X12 or EDIFACT.
    How ECOM helps
    ECOM supports papiNet and X12 or EDIFACT customers into the same ERP.
    What you gain
    Customers that use different standards share one order process.

    Talk to an EDI/API Expert about papiNet versus X12 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 paper, pulp and tissue manufacturers

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

Converters and printers
Order reels and sheets by grade, basis weight and width.
Distributors and merchants
Buy and resell paper and tissue in smaller lots.
Retailers (tissue)
Replenish finished tissue products under retailer rules.
Wood fiber and chemical suppliers
Supply the fiber and chemicals mills depend on.
Rail and truck carriers
Move reels and bales by railcar and truck, with different documents for each.

Typical workflow

Where ECOM connects your systems and trading partners

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

  1. Converter, distributor or retailer→Your plant and ERP 862 Shipping Schedule Supplements the 830: shipping and delivery quantities and dates that, under the partner’s rules, supersede the applicable shipping information in the 830. It does not replace the 830 or, on its own, authorize production resources.
  2. Converter, distributor or retailer→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
  3. Converter, distributor or retailer→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  4. Your plant and ERP→Converter, distributor or retailer 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  5. Your plant and ERP→Motor carrier 204 Motor Carrier Load Tender Tenders a truck shipment to a motor carrier.
  6. Motor carrier→Your plant and ERP 990 Response to a Load Tender The motor carrier’s acceptance or decline of the tender.
  7. Motor carrier→Your plant and ERP 214 Transportation Carrier Shipment Status Message Shipment status events from the motor carrier.
  8. Your plant and ERP→Converter, distributor or retailer 856 Advance Ship Notice Reel or bale ID, weight and grade per shipment.
  9. Your plant and ERP→Converter, distributor or retailer 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  10. Converter, distributor or retailer→Your plant and ERP 861 Receiving Advice/Acceptance Certificate Customer receipt used to reconcile weights.
  1. Receive orders and schedules

    Orders (850) and schedules (862) specify grade, width and quantity.

  2. Confirm and plan loads

    Acknowledgments (855) confirm grades and dates. Truck loads are then tendered to motor carriers (204/990); railcar shipments follow the railroad’s own routing process and are scoped separately.

  3. Ship with reel detail

    The 856 lists reels, weights and lots.

  4. Track delivery

    Status events (214) show arrival.

  5. Invoice by weight

    The 810 follows shipped weight and reconciles to the customer’s receipt (861).

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 paper, pulp and tissue manufacturers
862 Shipping Schedule You receive Supplements the 830: shipping and delivery quantities and dates that, under the partner’s rules, supersede the applicable shipping information in the 830. It does not replace the 830 or, on its own, authorize production resources.
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.
214 Transportation Carrier Shipment Status Message You receive Shipment status events from the motor carrier.
856 Advance Ship Notice You send Reel or bale ID, weight and grade per shipment.
810 Invoice You send Bills for what was shipped, tied to the order and the ship notice.
861 Receiving Advice/Acceptance Certificate You receive Customer receipt used to reconcile weights.

Other exchanges you may meet

  • papiNet messages for forest-product customers
  • Rail status messages

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

Reels, weights and standards

Reel identifiers and weights flow from the mill to the converter’s receiving system. Whether a customer uses papiNet or X12 is established during scoping, and rail and truck loads add different shipment documents.

  • 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
  • Mill production and roll tracking
  • Transportation 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 converter, distributor or retailer, and agree which documents, versions and data are in scope.

  2. Map to your systems

    Map each document to the fields in your ERP and mill production and roll tracking 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 paper, pulp and tissue manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Reel weight outside the toleranceA tolerance check of reel weight against the order can flag a difference for review before shipment, so the invoice and the customer’s receiving record agree.
Reel ID missing on a ship notice lineThe line can be held for review so the converter can match the reel to its receiving record.

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

Does ECOM support papiNet?

Where a trading partner requires papiNet, ECOM confirms and scopes it during discovery, alongside partners that use X12 or EDIFACT.

Can rail documents be integrated?

Rail messages and status can be integrated where the railroad or customer supports them. Shipping by rail is also covered on the rail freight page.

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 paper, pulp and tissue 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.