Manufacturing · Food Manufacturing

EDI and API Integration for Edible Oil and Fat Manufacturers

Edible oil and fat producers ship by tank truck, rail and drum as well as in bottles. ECOM connects bulk and packaged orders, shipment documents and invoices to your ERP so units, lots and quantities stay consistent.

View all manufacturing industries

What this covers

Products and business models in edible oil and fat

Products

  • Cooking and salad oils
  • Shortenings, margarine and spreads
  • Specialty fats for baking and confectionery
  • Bulk, tote and packaged retail oils

Business models

  • Bulk supply to food manufacturers
  • Foodservice and retail packaging
  • Commodity and contract sales

Scenarios

Where edible oil and fat 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.

  • Bulk and packaged units

    The problem
    Tank-truck gallons, drum counts and retail cases need clear unit conversions across orders and invoices.
    How ECOM helps
    ECOM maps units across tank-truck gallons, drums and retail cases on the order, 856 and 810, using the conversions held in your ERP.
    What you gain
    Quantities agree across order, ship notice and invoice.

    Talk to an EDI/API Expert about bulk and packaged units 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.

  • Contract and spot pricing

    The problem
    Pricing often follows commodity markets or contracts, so invoices must tie to the right price basis.
    How ECOM helps
    ECOM maps contract and price-basis references to the 810 and can compare the invoiced price with the contract basis in your ERP.
    What you gain
    A price difference can be reviewed before the invoice goes out.

    Talk to an EDI/API Expert about contract and spot pricing Share a sample 850 Purchase Order and 810 Invoice, or describe what goes wrong, and we will show how it would map to your ERP.

  • Lot and quality records

    The problem
    Customers expect lot data and, for some, certificates with each delivery.
    How ECOM helps
    ECOM sends lot data and, where the customer asks for it, certificate data (863) with each delivery.
    What you gain
    Lot and quality records reach the customer with the shipment.

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

Who you connect with

Trading relationships for edible oil and fat manufacturers

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

Food manufacturers and bakeries
Order bulk and tote quantities against specifications.
Foodservice distributors
Order packaged fry oils and shortening.
Grocery retailers
Order retail bottles and packs.
Crushers, refiners and suppliers
Provide crude and refined oil on contract.
Tank-truck and rail carriers
Move bulk product.

Typical workflow

Where ECOM connects your systems and trading partners

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

  1. Food manufacturer or distributor→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
  2. Food manufacturer or distributor→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  3. Your plant and ERP→Food manufacturer or distributor 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  4. Your plant and ERP→Carrier 204 Motor Carrier Load Tender Tenders a truck shipment to a motor carrier.
  5. Carrier→Your plant and ERP 990 Response to a Load Tender The motor carrier’s acceptance or decline of the tender.
  6. Carrier→Your plant and ERP 214 Transportation Carrier Shipment Status Message Shipment status events from the motor carrier.
  7. Your plant and ERP→Food manufacturer or distributor 856 Advance Ship Notice Bulk quantity loaded with lot and seal or compartment detail where the guide asks.
  8. Your plant and ERP→Food manufacturer or distributor 863 Report of Test Results Quality results for a lot shipped in bulk.
  9. Your plant and ERP→Food manufacturer or distributor 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  10. Food manufacturer or distributor→Your plant and ERP 861 Receiving Advice/Acceptance Certificate The customer’s record of what it received, used to reconcile bulk quantities.
  1. Orders by unit and delivery mode

    Orders (850) specify bulk or packaged units, destination and dates.

  2. Tender and load

    Bulk loads are tendered (204/990) and tracked (214).

  3. Ship notice and lot data

    The 856 reports the lot and quantity loaded, and test results (863) can follow where requested.

  4. Invoice on contract price

    The 810 uses the contract or market-based price basis.

  5. Reconcile receipts

    Customer receipts (861) and differences are matched to the shipment.

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 edible oil and fat 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.
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 Bulk quantity loaded with lot and seal or compartment detail where the guide asks.
863 Report of Test Results You send Quality results for a lot shipped in bulk.
810 Invoice You send Bills for what was shipped, tied to the order and the ship notice.
861 Receiving Advice/Acceptance Certificate You receive The customer’s record of what it received, used to reconcile bulk quantities.

Other exchanges you may meet

  • Contract and settlement files for commodity pricing
  • Certificate of analysis exchange

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

Bulk quantities and reconciliation

A tank load is measured at loading and at receiving, and small differences matter at commodity prices. The ship notice reports what was loaded, the customer reports what it received, and the invoice must settle on the agreed basis.

  • 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
  • Terminal and loading systems
  • Transportation management
  • Quality 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 food manufacturer or distributor, 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 terminal and loading 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 edible oil and fat manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Received quantity differs from loaded quantityA comparison of the customer’s received quantity with the loaded quantity can route the variance to customer service and finance.
Invoice price differs from contract basisA price check of the 810 against the contract basis in the ERP can hold the line for review before the invoice 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 bulk and packaged products share the same integration?

Yes. The ERP holds both; each customer’s order and units are mapped per its guide.

Does ECOM handle commodity price formulas?

Pricing logic stays in your ERP or pricing system. The integration carries the resulting price and quantity into the invoice and related documents.

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 edible oil and fat 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.