Manufacturing · Food Manufacturing

EDI and API Integration for Meat and Poultry Processors

Meat and poultry processors sell by weight, ship perishable product and answer to tight lot traceability. ECOM connects customer orders, shipment data and invoices to your ERP so weights, lots and dates move correctly from plant to receiving.

View all manufacturing industries

What this covers

Products and business models in meat and poultry processing

Products

  • Fresh and frozen beef, pork and poultry
  • Further-processed and cooked items
  • Deli and sliced meats
  • Case-ready retail packs

Business models

  • Processors supplying retail and foodservice
  • Further-processing and co-packing
  • Export and ingredient sales

Scenarios

Where meat and poultry processors 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.

  • Variable-weight cases

    The problem
    Orders are in cases or pounds, but shipped weight varies. Ship notices and invoices must report the actual weight.
    How ECOM helps
    ECOM maps shipped weights from your ERP and scale data into the 856 and 810, so variable-weight cases are described and billed by actual weight.
    What you gain
    Orders in cases, invoices in pounds and the notice agree, which avoids price and quantity disputes.

    Talk to an EDI/API Expert about variable-weight cases Share a sample 856 Advance Ship Notice and 810 Invoice, or describe what goes wrong, and we will show how it would map to your ERP.

  • Lot traceability and recalls

    The problem
    A recall depends on tying a lot to its customers. The lot on the ship notice is part of that link.
    How ECOM helps
    ECOM carries lot and pack-date data from your production and WMS systems to the 856.
    What you gain
    The lot on the paperwork supports the link from a lot to its customers if a recall question arises.

    Talk to an EDI/API Expert about lot traceability and recalls Share a sample 856 Advance Ship Notice, or describe what goes wrong, and we will show how it would map to your ERP.

  • Very short shelf life

    The problem
    Fresh product must be shipped and received quickly; late data stops a load at the dock.
    How ECOM helps
    ECOM sends the 856 as soon as the load is built and the data is released, with status events (214) following from the carrier.
    What you gain
    Product is not held at the dock because the paperwork arrived late.

    Talk to an EDI/API Expert about very short shelf life Share a sample 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.

Who you connect with

Trading relationships for meat and poultry processors

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

Grocery and club retailers
Order case-ready and bulk product with strict receiving rules.
Foodservice distributors and restaurants
Order by case, often daily.
Livestock and poultry suppliers
Settlements and delivery data from producers.
Packaging and ingredient suppliers
Film, trays and seasonings.
Refrigerated carriers
Move product at temperature.

Typical workflow

Where ECOM connects your systems and trading partners

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

  1. Retail or foodservice customer→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
  2. Retail or foodservice customer→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  3. Your plant and ERP→Retail or foodservice customer 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  4. Your plant and ERP→Refrigerated carrier 204 Motor Carrier Load Tender Tenders a truck shipment to a motor carrier.
  5. Refrigerated carrier→Your plant and ERP 990 Response to a Load Tender The motor carrier’s acceptance or decline of the tender.
  6. Refrigerated carrier→Your plant and ERP 214 Transportation Carrier Shipment Status Message Shipment status events from the motor carrier.
  7. Your plant and ERP→Retail or foodservice customer 856 Advance Ship Notice Shipped lot, production or pack date and weights by case or pallet where required.
  8. Your plant and ERP→Retail or foodservice customer 810 Invoice Billing on actual shipped weight rather than ordered cases.
  9. Your plant and ERP→Retail or foodservice customer 812 Credit/Debit Adjustment Adjustments for weight differences or claims.
  1. Orders by case and weight

    Orders (850) and changes (860) post to the ERP, which holds the case, unit and weight rules for each item.

  2. Pack, weigh and label

    The plant captures actual weights and lots as cases are packed.

  3. Tender the load

    Loads are tendered (204), accepted (990) and tracked (214).

  4. Ship notice with lots and weights

    The 856 reports lots, dates and weights at the level the customer requires.

  5. Invoice on actual weight

    The 810 bills shipped weight and ties back to the order and ship notice.

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 meat and poultry processors
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 Shipped lot, production or pack date and weights by case or pallet where required.
810 Invoice You send Billing on actual shipped weight rather than ordered cases.
812 Credit/Debit Adjustment You send Adjustments for weight differences or claims.

Other exchanges you may meet

  • GS1-128 labels with lot, date and weight
  • Customer portals for compliance and item data

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

Weights, lots and recalls

Meat and poultry combine variable weights with traceable lots. The shipping system captures weights and lots, the ship notice reports them and the invoice bills them. If a recall occurs, the lot on the shipping record is the link between your production data and each customer’s receipts. Recall processes themselves remain yours.

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

  • Variable weights

    Meat, cheese, seafood and some produce ship by actual weight. Orders are in cases or pounds, invoices follow shipped weight, and the ship notice has to report what actually left the dock.

Connected systems

Systems that send and receive this data

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

  • ERP
  • Plant weighing and labeling systems
  • Warehouse management
  • Transportation management

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 retail or foodservice 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 and plant weighing and labeling 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 meat and poultry processors

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Shipped weight outside toleranceA tolerance check of shipped weight against the order can flag a variance for review before billing.
Lot missing on a ship notice lineA required-field check on the 856 can hold a line with no lot for review before the notice is sent.

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

Can EDI handle variable-weight items?

Yes, when the customer’s guide defines how the actual quantity and weight are reported. The weights come from your plant or warehouse system and are mapped to the ship notice and invoice.

Does ECOM help with recalls?

ECOM exchanges the shipment and lot information your systems capture. Recall decisions, notifications and regulatory steps are your quality team’s process.

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 meat and poultry processors

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.