Manufacturing · Food Manufacturing

EDI and API Integration for Candy and Chocolate Manufacturers

Seasonal retail programs and year-round replenishment put heavy order volume and fixed delivery windows on candy makers. ECOM connects your ERP and warehouse to retailers, distributors and 3PLs so orders, ship notices and invoices flow without re-keying.

View all manufacturing industries

What this covers

Products and business models in candy and chocolate

Products

  • Chocolate bars, bagged candy and gum
  • Seasonal and gift assortments
  • Hard, gummy and sugar confectionery
  • Display shippers and counter units

Business models

  • Brand owner selling to grocery, mass, drug and convenience channels
  • Private label and co-packing for retail brands
  • Seasonal programs packed to a retailer’s specification

Scenarios

Where candy and chocolate 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.

  • Seasonal order peaks

    The problem
    Holiday programs arrive as large orders with firm in-store dates. A quantity or date change has to reach production and the warehouse before the load is built.
    How ECOM helps
    ECOM maps the retailer’s 850 and 860 into your ERP and can compare a late change with the pick already released to your warehouse or 3PL (940), so the planner is told to amend the pick or reship.
    What you gain
    Planners see a changed holiday quantity or in-store date when it posts, not when the truck is loaded.

    Talk to an EDI/API Expert about seasonal order peaks Share a sample 850 Purchase Order, 860 Purchase Order Change Request and 940 Warehouse Shipping Order, or describe what goes wrong, and we will show how it would map to your ERP.

  • Display and mixed-pallet shipments

    The problem
    Display shippers and mixed pallets must be described accurately in the ship notice, or receiving cannot match the pallet to the order.
    How ECOM helps
    ECOM maps the display, pallet and carton structure from your ERP and WMS into the 856, so each shipper and mixed pallet is described the way the retailer receives it.
    What you gain
    Receiving can match what is on the dock to the notice, which helps avoid refused pallets and short-ship disputes.

    Talk to an EDI/API Expert about display and mixed-pallet shipments Share a sample 856 Advance Ship Notice and 945 Warehouse Shipping Advice, or describe what goes wrong, and we will show how it would map to your ERP.

  • Date-coded, heat-sensitive goods

    The problem
    Retailers and distributors may check dates on receipt, so production dates and lots on the paperwork have to match the cases on the pallet.
    How ECOM helps
    ECOM can carry lot or date data from your WMS into the 856 and compare it with scanned case labels where those scans are available.
    What you gain
    Mismatches between paperwork and cartons can be reviewed before the notice goes out.

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

  • Seasonal item and inventory changes

    The problem
    Holiday and Easter lines are added, dropped or re-priced late in the planning cycle, and available inventory shifts week to week.
    How ECOM helps
    ECOM sends item data and available inventory (846) to the customers that accept it and maps their orders back to the current item set in your ERP.
    What you gain
    Customers order against what you can ship, so fewer orders need to be corrected after they arrive.

    Talk to an EDI/API Expert about seasonal item and inventory changes Share a sample 846 Inventory Inquiry/Advice, 850 Purchase Order 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 candy and chocolate manufacturers

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

Grocery, mass and drug retailers
Send purchase orders, set item and packing rules, and may require GS1-128 labels and ship notices.
Convenience and club channels
Often order through distributors or direct, with their own item numbers and order cycles.
Distributors and brokers
Resell to smaller accounts and may report sales and inventory.
Ingredient and packaging suppliers
Cocoa, sugar and packaging suppliers whose orders and ship notices drive your production.
3PLs and carriers
Warehouse shipments and freight, sometimes temperature-controlled in warm months.

Typical workflow

Where ECOM connects your systems and trading partners

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

  1. Grocery or mass retailer→Your plant and ERP 850 Purchase Order Seasonal and replenishment orders with in-store dates and display quantities.
  2. Grocery or mass retailer→Your plant and ERP 860 Purchase Order Change Request Late quantity and date changes during seasonal programs.
  3. Your plant and ERP→Grocery or mass retailer 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  4. Your plant and ERP→Warehouse or 3PL 940 Warehouse Shipping Order Tells the warehouse or 3PL what to pick and ship.
  5. Warehouse or 3PL→Your plant and ERP 945 Warehouse Shipping Advice Confirms what the warehouse actually shipped.
  6. Your plant and ERP→Grocery or mass retailer 856 Advance Ship Notice Describes display shippers, mixed pallets and lot or date codes where the partner asks.
  7. Your plant and ERP→Grocery or mass retailer 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  8. Your plant and ERP→Grocery or mass retailer 846 Inventory Inquiry/Advice Available inventory ahead of a seasonal program.
  1. Receive the seasonal or replenishment order

    The 850 arrives from the retailer or distributor with items, quantities, ship-to and requested dates, and posts to the ERP as a sales order.

  2. Confirm and adjust

    An 855 confirms what you can ship and when. Order changes (860) are reconciled before the pick is released.

  3. Release to the warehouse

    The ERP or WMS sends the pick to your warehouse or 3PL (940) and receives the shipment confirmation (945).

  4. Send the ship notice

    Cartons and pallets are described in the 856, with lot or date information where the partner asks, matching the GS1-128 labels.

  5. Invoice and reconcile

    The 810 follows the shipment. Short-ships and deductions are traced back to the order, the ship notice and the label.

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 candy and chocolate manufacturers
850 Purchase Order You receive Seasonal and replenishment orders with in-store dates and display quantities.
860 Purchase Order Change Request You receive Late quantity and date changes during seasonal programs.
855 Purchase Order Acknowledgment You send The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
940 Warehouse Shipping Order You send Tells the warehouse or 3PL what to pick and ship.
945 Warehouse Shipping Advice You receive Confirms what the warehouse actually shipped.
856 Advance Ship Notice You send Describes display shippers, mixed pallets and lot or date codes where the partner asks.
810 Invoice You send Bills for what was shipped, tied to the order and the ship notice.
846 Inventory Inquiry/Advice You send Available inventory ahead of a seasonal program.

Other exchanges you may meet

  • GS1-128 shipping labels and SSCC pallet identification
  • GDSN or retailer item-setup portals for new items and seasonal 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

Dates, lots and heat-sensitive shipments

Confectionery customers check production and best-before dates on receipt, and summer shipping can add temperature requirements. Lot and date data on the ship notice should match the cases and labels so receiving does not reject the load.

  • 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
  • Warehouse management
  • Retailer item portals
  • Carrier or 3PL systems

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 grocery or mass 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 warehouse 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 candy and chocolate manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Seasonal order changed after pick releaseA configured comparison of the 860 against the warehouse order already sent can flag the change for review, so the team decides whether to amend the pick or reship.
Ship notice date does not match case labelsA check of lot or date data on the 856 against the scanned case labels, where those scans are available, can hold the notice for review before it 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 seasonal retailer programs run without manual order entry?

Orders and changes that arrive by EDI are translated and posted to your ERP without re-keying once the connection is configured. Your team handles exceptions, such as a changed quantity after pick release, instead of re-keying every order.

Do candy shipments need GS1-128 labels?

Many retailers require them, but each retailer’s guide sets its own label rules. ECOM helps map the label data to the 856 so the labels and the ship notice agree.

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 candy and chocolate 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.