Manufacturing · Food Manufacturing

EDI and API Integration for Frozen Meal and Prepared Food Manufacturers

Frozen meal and prepared food makers combine many ingredients, strict dates and retail program orders. ECOM connects customer orders, ingredient suppliers and cold-chain shipments to your ERP so production and shipping documents agree.

View all manufacturing industries

What this covers

Products and business models in frozen meal and prepared food

Products

  • Frozen entrees and meals
  • Refrigerated prepared foods
  • Appetizers, sides and handhelds
  • Meal kits and foodservice trays

Business models

  • Branded frozen meals for retail
  • Private label and co-manufacturing
  • Foodservice and institutional supply

Scenarios

Where frozen meal and prepared food 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.

  • Many ingredients per product

    The problem
    Each meal draws on dozens of ingredient and packaging suppliers, so supplier acknowledgments and ship notices matter to the schedule.
    How ECOM helps
    ECOM maps supplier 855s and 856s for ingredient and packaging orders into your ERP and can flag a critical ingredient with no confirmation as the run date approaches.
    What you gain
    Purchasing finds a missing confirmation before the shortage reaches the line.

    Talk to an EDI/API Expert about many ingredients per product 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.

  • Lot genealogy

    The problem
    A finished lot ties to ingredient lots. That link lives in production systems, but the customer-facing lot has to reach the ship notice.
    How ECOM helps
    ECOM carries the customer-facing finished lot and date from your production system onto the 856. The link from finished lot to ingredient lots stays in your production system.
    What you gain
    The lot the customer sees on the notice matches the cases on the pallet.

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

  • Retailer programs and slotting

    The problem
    New items and promotions require item data and early order planning.
    How ECOM helps
    ECOM maintains item data and cross-references for each retailer program and loads promotional orders into planning.
    What you gain
    A new program is set up once, and promotion volume reaches planners early.

    Talk to an EDI/API Expert about retailer programs and slotting Share a sample 832 Price/Sales Catalog, 850 Purchase Order and 830 Planning Schedule with Release Capability, or describe what goes wrong, and we will show how it would map to your ERP.

Who you connect with

Trading relationships for frozen meal and prepared food manufacturers

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

Grocery and club retailers
Order by purchase order and expect ship notices and labels.
Foodservice and institutional buyers
Order cases and trays through distributors.
Ingredient and packaging suppliers
Dozens of inputs with release schedules.
Cold storage and 3PLs
Hold and ship frozen inventory.
Refrigerated carriers
Move product at temperature.

Typical workflow

Where ECOM connects your systems and trading partners

The pattern below is typical for frozen meal and prepared food manufacturers, 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→Retail or foodservice customer 856 Advance Ship Notice Finished-goods lots and dates at the customer’s required level.
  5. Your plant and ERP→Retail or foodservice customer 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  6. Your plant and ERP→Ingredient supplier 850 Purchase Order Orders for ingredients and packaging with delivery dates.
  7. Ingredient supplier→Your plant and ERP 855 Purchase Order Acknowledgment The supplier confirms quantities and dates for ingredients and packaging.
  8. Ingredient supplier→Your plant and ERP 856 Advance Ship Notice Ingredient and packaging quantities, lots and arrival dates, used to plan receiving ahead of the production run.
  9. Retail or foodservice customer→Your plant and ERP 830 Planning Schedule with Release Capability Forecast from a larger customer, where shared, to plan ingredients.
  1. Orders and forecasts

    Customer orders (850) and changes (860) post to the ERP; forecasts (830) inform ingredient planning where used.

  2. Order ingredients

    Purchase orders (850) to suppliers with confirmations (855) and ship notices (856).

  3. Produce and freeze

    Production consumes ingredient lots and creates finished lots.

  4. Ship with lots and dates

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

  5. Invoice

    The 810 follows shipment and ties to 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 frozen meal and prepared food manufacturers
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.
856 Advance Ship Notice You send Finished-goods lots and dates at the customer’s required level.
810 Invoice You send Bills for what was shipped, tied to the order and the ship notice.
850 Purchase Order (supplier side) You send Orders for ingredients and packaging with delivery dates.
855 Purchase Order Acknowledgment (supplier side) You receive The supplier confirms quantities and dates for ingredients and packaging.
856 Advance Ship Notice (supplier side) You receive Ingredient and packaging quantities, lots and arrival dates, used to plan receiving ahead of the production run.
830 Planning Schedule with Release Capability You receive Forecast from a larger customer, where shared, to plan ingredients.

Other exchanges you may meet

  • GS1-128 case and pallet labels
  • Retailer portals for 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

Ingredients, lots and dates

Production, not integration, creates lot genealogy. What the integration does is make sure ingredient receipts and finished-goods shipments use the same identifiers your systems hold, and that the lot and date on the ship notice are the ones on 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
  • Manufacturing execution
  • Warehouse management
  • Supplier 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 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 manufacturing execution 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 frozen meal and prepared food manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Ingredient order not acknowledgedA configured rule can flag a critical ingredient order with no 855 as the run date approaches.
Case lot differs from ship notice lotA comparison of case-label scan data with the lot on the 856, where scans are available, can hold the notice for review.

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 supplier ship notices help our production schedule?

Yes. Supplier ship notices and confirmations post to the ERP, giving planners expected receipt dates rather than assumptions. Suppliers without EDI can use a browser or document conversion.

Is each retailer’s data format different?

Retailers share the same core documents but set their own rules, so ECOM maps each retailer’s guide to your ERP data separately.

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 frozen meal and prepared food 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.