Manufacturing · Food Manufacturing

EDI and API Integration for Animal Feed Manufacturers

Feed manufacturers formulate to customer nutrition programs and deliver by bulk truck and bag to farms, dealers and integrators. ECOM connects orders, ingredient purchasing and invoices to your ERP so formulation, delivery and billing stay in step.

View all manufacturing industries

What this covers

Products and business models in animal feed

Products

  • Poultry, swine, cattle and dairy feed
  • Pet and specialty animal feed
  • Premixes and supplements
  • Bulk, tote and bagged formats

Business models

  • Mills delivering to farms and integrators
  • Dealer and retail networks
  • Premix supply to other feed makers

Scenarios

Where animal feed 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.

  • Formulation-based orders

    The problem
    Orders often specify a formula or program rather than a simple item, which the ERP has to interpret.
    How ECOM helps
    ECOM maps formula and program references on customer orders to ERP formulas and routes.
    What you gain
    Orders post as the program the customer meant, not as a generic item.

    Talk to an EDI/API Expert about formulation-based orders Share a sample 850 Purchase Order and 862 Shipping Schedule, or describe what goes wrong, and we will show how it would map to your ERP.

  • Bulk route delivery

    The problem
    Deliveries are scheduled by route to farms, with ticket and weight reconciliation.
    How ECOM helps
    ECOM maps delivery tickets and weights into the ERP and the 810 so tickets and invoices can be compared.
    What you gain
    Weight differences are reviewed before billing.

    Talk to an EDI/API Expert about bulk route delivery 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.

  • Commodity ingredient buying

    The problem
    Corn, soy and minerals are bought on contracts and spot, and must reconcile to receipts.
    How ECOM helps
    ECOM maps supplier orders, confirmations, ship notices and invoices (850, 855, 856, 810) for corn, meals and minerals into your ERP.
    What you gain
    Contract and spot purchases reconcile to receipts.

    Talk to an EDI/API Expert about commodity ingredient buying 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 animal feed manufacturers

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

Integrators and large producers
Order by program and schedule.
Dealers and retail feed stores
Order bagged feed.
Grain and ingredient suppliers
Supply on contract and spot.
Pet and specialty brands
Order premixes and bases.
Truck and rail carriers
Move bulk and bagged product.

Typical workflow

Where ECOM connects your systems and trading partners

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

  1. Integrator, dealer or producer→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
  2. Integrator, dealer or producer→Your plant and ERP 862 Shipping Schedule Delivery schedule by farm or route, where a large producer sends it.
  3. Your plant and ERP→Integrator, dealer or producer 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  4. Your plant and ERP→Integrator, dealer or producer 856 Advance Ship Notice Delivery quantity and lot where a customer asks.
  5. Your plant and ERP→Integrator, dealer or producer 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 Corn, soybean meal, minerals and additive purchases.
  7. Ingredient supplier→Your plant and ERP 855 Purchase Order Acknowledgment The supplier confirms quantities and dates for grain, protein meals, minerals and additives.
  8. Ingredient supplier→Your plant and ERP 856 Advance Ship Notice Ingredient loads with quantity, lot and ticket, used to plan receiving and formulation.
  9. Ingredient supplier→Your plant and ERP 810 Invoice The supplier’s invoice for grain, protein meals, minerals and additives, matched to the order and the receipt.
  1. Orders by program

    Orders (850) and releases (862) post to the ERP against formulas and routes.

  2. Buy ingredients

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

  3. Mill and load

    Production follows the formula; delivery tickets record loaded weight.

  4. Ship notice and ticket

    The 856 or delivery ticket data reports lot and quantity.

  5. Invoice

    The 810 bills delivered quantity and program 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 animal feed manufacturers
850 Purchase Order You receive The customer order: items, quantities, prices, ship-to and requested dates.
862 Shipping Schedule You receive Delivery schedule by farm or route, where a large producer sends it.
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 Delivery quantity and lot where a customer asks.
810 Invoice You send Bills for what was shipped, tied to the order and the ship notice.
850 Purchase Order (supplier side) You send Corn, soybean meal, minerals and additive purchases.
855 Purchase Order Acknowledgment (supplier side) You receive The supplier confirms quantities and dates for grain, protein meals, minerals and additives.
856 Advance Ship Notice (supplier side) You receive Ingredient loads with quantity, lot and ticket, used to plan receiving and formulation.
810 Invoice (supplier side) You receive The supplier’s invoice for grain, protein meals, minerals and additives, matched to the order and the receipt.

Other exchanges you may meet

  • Delivery ticket and weight files
  • Grain settlement files from suppliers

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

Formulas, routes and tickets

Feed is made to a formula and delivered on a route. The order, formula, delivery ticket and invoice have to agree, and ingredient receipts must reconcile to purchase contracts.

  • 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
  • Feed formulation software
  • Scale and ticketing systems
  • Route scheduling

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 integrator, dealer or producer, 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 feed formulation software 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 animal feed manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Delivery ticket weight differs from invoiceA comparison of the ticket weight with the 810 can flag a difference for review before billing.
Ingredient receipt exceeds purchase contractPurchasing can be alerted to over-delivery.

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 formula-based orders be integrated?

The formulation and program logic stay in your ERP or formulation software. The integration brings the customer’s order or schedule into that system and returns confirmations, delivery tickets and invoices.

Can small dealers and farms connect without EDI?

Often through a portal or files, so you can serve small dealers and farms without requiring EDI of each.

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 animal feed 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.