Manufacturing · Food Manufacturing
EDI and API Integration for Fruit and Vegetable Processors
Fruit and vegetable processors take in seasonal crops and sell year-round canned, frozen and fresh-cut product. ECOM connects grower and supplier data, customer orders and shipment documents to your ERP so seasonal peaks do not become manual work.
What this covers
Products and business models in fruit and vegetable processing
Products
- Canned and jarred fruit and vegetables
- Frozen fruit and vegetables
- Fresh-cut and packaged produce
- Dried fruit, purees and concentrates
Business models
- Processors buying from growers and selling to retail and foodservice
- Private label packing
- Ingredient supply to other manufacturers
Scenarios
Where fruit and vegetable processors 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 intake
- The problem
- Harvest weeks bring large inbound volume and settlements with growers, followed by a year of shipments against stored inventory.
- How ECOM helps
- ECOM maps grower and supplier ship notices and invoices into your ERP so intake and settlement agree during the harvest rush.
- What you gain
- Receipts and grower invoices reconcile without manual re-entry during the busiest weeks.
Talk to an EDI/API Expert about seasonal intake 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.
-
Lot and harvest traceability
- The problem
- Customers may ask for growing region or harvest lot, which has to be carried from intake to ship notice.
- How ECOM helps
- ECOM carries growing region or harvest lot from intake to the outbound 856 where the customer’s guide asks for it.
- What you gain
- The detail a customer asks for is on the notice and matches stored inventory.
Talk to an EDI/API Expert about lot and harvest traceability Share a sample 856 Advance Ship Notice, or describe what goes wrong, and we will show how it would map to your ERP.
-
Mixed pack sizes and retailer item numbers
- The problem
- Cans, pouches, bags and club packs each have their own item data.
- How ECOM helps
- ECOM maintains the item cross-reference for cans, pouches, bags and club packs at each retailer.
- What you gain
- Orders post to the correct pack item without manual lookup.
Talk to an EDI/API Expert about mixed pack sizes and retailer item numbers Share a sample 850 Purchase Order and 846 Inventory Inquiry/Advice, or describe what goes wrong, and we will show how it would map to your ERP.
Who you connect with
Trading relationships for fruit and vegetable processors
Typical relationships. Which of them apply, and how each one wants to connect, depends on your business.
- Growers and cooperatives
- Deliver crops with weights, grades and settlements.
- Grocery and club retailers
- Order year-round with date and label rules.
- Foodservice distributors
- Order large-format packs.
- Packaging suppliers
- Cans, lids, film and cartons.
- Carriers and rail
- Move inbound crop and outbound product.
Partner guides: Retailer guides · Distributor guides · 3PL and logistics guides
Typical workflow
Where ECOM connects your systems and trading partners
The pattern below is typical for fruit and vegetable processors, not one partner's confirmed requirements. Each trading partner publishes its own guide; confirm the details with that partner.
- Retail or foodservice customer→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
- Retail or foodservice customer→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
- 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.
- Your plant and ERP→Retail or foodservice customer 856 Advance Ship Notice Lot and pack or harvest date where the guide asks.
- Your plant and ERP→Retail or foodservice customer 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
- Your plant and ERP→Retail or foodservice customer 846 Inventory Inquiry/Advice Inventory positions for stored seasonal packs.
- Grower or supplier→Your plant and ERP 856 Advance Ship Notice Supplier ship notices for crop and packaging deliveries.
- Grower or supplier→Your plant and ERP 810 Invoice The supplier’s invoice for crops and packaging, matched to the order and the receipt.
Intake and settlement
Grower and supplier deliveries are recorded; supplier ship notices (856) and invoices (810) reconcile to receipts.
Process and store
Production creates lots that are stored for sale through the year.
Orders arrive
Customer orders (850) and changes (860) post to the ERP against stored inventory.
Ship notice
The 856 reports lots, pack dates and quantities.
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.
| Document | Direction | What it carries for fruit and vegetable processors |
|---|---|---|
| 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 | Lot and pack or harvest date where the guide asks. |
| 810 Invoice | You send | Bills for what was shipped, tied to the order and the ship notice. |
| 846 Inventory Inquiry/Advice | You send | Inventory positions for stored seasonal packs. |
| 856 Advance Ship Notice (supplier side) | You receive | Supplier ship notices for crop and packaging deliveries. |
| 810 Invoice (supplier side) | You receive | The supplier’s invoice for crops and packaging, matched to the order and the receipt. |
Other exchanges you may meet
- Grower settlement files
- GS1 case and pallet labels
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
Seasons, lots and storage
Processors pack once and sell for a year, so inventory by lot, pack date and location matters. Orders drawn months later still need the original lot and date on shipping documents.
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.
Variable weights
Meat, cheese, seafood and some produce ship by actual weight. Orders are in cases or pounds, invoices follow shipped weight, and the ship notice has to report what actually left the dock.
Connected systems
Systems that send and receive this data
Documents are only useful when they reach the systems that run the business.
- ERP
- Intake and scale systems
- Warehouse management
- Grower payment systems
ERP integration guides: SAP S/4HANA · Oracle NetSuite · Microsoft Dynamics 365 Business Central · Infor CloudSuite Industrial (SyteLine) · Epicor Kinetic · SAP Business One · All ERP guides
Onboarding and monitoring
From first requirement to daily exception handling
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.
Map to your systems
Map each document to the fields in your ERP and intake and scale systems so the data posts without re-keying.
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.
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.
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 fruit and vegetable processors
| Exception | Example handling, once configured |
|---|---|
| Inventory for a lot is exhausted | An order against a depleted lot can be flagged for review before commitment. |
| Supplier invoice weight differs from receipt | A variance can be routed to purchasing. |
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.
Services: Trading partner onboarding · ERP integration · API integration · Fully managed EDI · Supply chain visibility · Mapping and translation
Frequently asked questions
Can grower data be integrated?
Grower deliveries, settlements and invoices can be exchanged in the formats the growers or cooperatives support, including files and portals, and posted to your ERP.
How are pack dates and lots reported?
From your warehouse and production systems to the ship notice, at the level each customer’s guide requires.
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 fruit and vegetable processors
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.