Manufacturing · Food Manufacturing

EDI and API Integration for Spice, Seasoning and Food Ingredient Manufacturers

Spice, seasoning and ingredient makers sell small retail jars and bulk ingredients to other manufacturers. ECOM connects both kinds of orders, supplier shipments and invoices to your ERP so lots and specifications travel with the product.

View all manufacturing industries

What this covers

Products and business models in spice, seasoning and food ingredient

Products

  • Spices, herbs and seasoning blends
  • Rubs, mixes and flavorings
  • Food colors, extracts and additives
  • Bulk and custom ingredients

Business models

  • Retail brands in grocery
  • Ingredient supply to food manufacturers
  • Custom blending to a customer specification

Scenarios

Where spice, seasoning and food ingredient 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.

  • Customer-specific specifications

    The problem
    Ingredient buyers order against specs and may expect certificates of analysis with each lot.
    How ECOM helps
    ECOM maps customer specifications and test results (863 where the customer asks for them) from your ERP or lab system to each shipment.
    What you gain
    Customers receive the certificate data they expect with each lot.

    Talk to an EDI/API Expert about customer-specific specifications Share a sample 850 Purchase Order, 863 Report of Test Results and 856 Advance Ship Notice, or describe what goes wrong, and we will show how it would map to your ERP.

  • Global sourcing

    The problem
    Raw spices arrive from many origins with long lead times, so supplier shipment visibility matters.
    How ECOM helps
    ECOM maps supplier 856s for long-lead raw material shipments into your ERP, and can flag a missing confirmation or ship notice against a blend date.
    What you gain
    Purchasing sees supply risk to a blend date while an alternative can still be found.

    Talk to an EDI/API Expert about global sourcing 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.

  • Small-lot custom blends

    The problem
    Frequent changes in custom blends make order changes and acknowledgments critical.
    How ECOM helps
    ECOM maps customer forecasts (830) and order changes (860) into the ERP so frequent changes to custom blends reach planners.
    What you gain
    Blend changes reach production planning without re-keying.

    Talk to an EDI/API Expert about small-lot custom blends Share a sample 830 Planning Schedule with Release Capability, 860 Purchase Order Change Request and 855 Purchase Order Acknowledgment, or describe what goes wrong, and we will show how it would map to your ERP.

Who you connect with

Trading relationships for spice, seasoning and food ingredient manufacturers

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

Food manufacturers
Order ingredients against specifications and release schedules.
Grocery retailers
Order retail jars and packs.
Foodservice distributors
Order large containers.
Raw spice and ingredient suppliers
Supply from domestic and imported sources.
Carriers and ocean forwarders
Move imports and outbound freight.

Typical workflow

Where ECOM connects your systems and trading partners

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

  1. Food manufacturer or retailer→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
  2. Food manufacturer or retailer→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  3. Food manufacturer or retailer→Your plant and ERP 830 Planning Schedule with Release Capability Forecast from ingredient customers, where shared, to plan blends and raw material buys.
  4. Your plant and ERP→Food manufacturer 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→Food manufacturer or retailer 856 Advance Ship Notice Lot data tied to the customer’s specification.
  6. Your plant and ERP→Food manufacturer or retailer 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  7. Your plant and ERP→Food manufacturer or retailer 863 Report of Test Results Test results for a lot, where a customer asks for results in electronic form.
  8. Your plant and ERP→Raw material supplier 850 Purchase Order Purchase orders for raw materials with quantities and requested delivery dates.
  9. Raw material supplier→Your plant and ERP 856 Advance Ship Notice Raw material quantities with the supplier’s lot, used to check receipts against the specification and plan blends.
  1. Receive the order or release

    Orders (850), changes (860) and, for larger customers, forecasts (830) post to the ERP.

  2. Confirm lot and lead time

    Confirmations (855) state quantities and ship dates.

  3. Buy raw materials

    Orders to suppliers (850) and their ship notices (856) gate blend schedules.

  4. Ship with lot data

    The 856 carries the lot, and a certificate of analysis can accompany the shipment where the customer expects it.

  5. Invoice

    The 810 follows 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 spice, seasoning and food ingredient 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.
830 Planning Schedule with Release Capability You receive Forecast from ingredient customers, where shared, to plan blends and raw material buys.
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 Lot data tied to the customer’s specification.
810 Invoice You send Bills for what was shipped, tied to the order and the ship notice.
863 Report of Test Results You send Test results for a lot, where a customer asks for results in electronic form.
850 Purchase Order (supplier side) You send Purchase orders for raw materials with quantities and requested delivery dates.
856 Advance Ship Notice (supplier side) You receive Raw material quantities with the supplier’s lot, used to check receipts against the specification and plan blends.

Other exchanges you may meet

  • Certificate of analysis files or portals
  • GS1 labels for retail packs

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

Specifications, lots and certificates

Ingredient customers manage supplier quality closely. The lot on the ship notice, the specification identifier and any certificate of analysis need to tie together. The certificate content comes from your quality system.

  • 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
  • Quality management
  • Warehouse management
  • Customer 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 food manufacturer 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 quality management 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 spice, seasoning and food ingredient manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Order references a superseded specificationThe mismatch can be held for sales review.
Raw material delayA missing 855 or 856 against a blend date can be flagged to purchasing as a supply risk.

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 certificates of analysis be exchanged electronically?

Where a customer asks for them in electronic form and your quality system produces them, they can be exchanged as test results or files according to the customer’s process.

Do ingredient customers use EDI?

Many larger food manufacturers do, often with forecasts and releases; smaller ones order by email or portal. ECOM supports different capabilities.

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 spice, seasoning and food ingredient 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.