Skip to content
EDI iTradeNetwork, Inc. Fresh Taste Produce (via iTrade Network)

Channel

iTradeNetwork, Inc.Fresh Taste Produce (via iTrade Network)

Fresh Taste Produce (via iTrade Network) is one of iTradeNetwork, Inc.'s 1 EDI trading channels. It supports 3 document types including X12 850, X12 860, X12 810.

Documents
3 transactions
Standards
X12 + EDIFACT
Transport
AS2 · SFTP · API

Document catalog

EDI documents we support for iTradeNetwork, Inc. Fresh Taste Produce (via iTrade Network)

3 EDI transactions ready to integrate.

Document flow on this channel

How documents flow on Fresh Taste Produce (via iTrade Network)

This channel carries all 3 of iTradeNetwork, Inc.'s document types.

Order-to-cash

Partial on this channel
  1. 850 Purchase Order
  2. 855 Purchase Order Acknowledgment not on Fresh Taste Produce (via iTrade Network)
  3. 856 Ship Notice / Manifest (ASN) not on Fresh Taste Produce (via iTrade Network)
  4. 810 Invoice

Network onboarding

Fresh Taste Produce (via iTrade Network) is routed through iTradeNetwork

Stacksync maintains a certified iTradeNetwork connection covering 8 trading partners across 8 channels. Onboarding with iTradeNetwork, Inc. on this channel reuses that connection — no separate VAN contract or certification cycle.

iTradeNetwork is a cloud supply chain network for the food and beverage industry, focused on perishables. Its order management platform connects grower-shippers, manufacturers, and distributors with foodservice operators and grocery retailers; the vendor cites reach into 8 of the top 10 North American foodservice distributors and 13 of the top 20 North American grocers for perishables. Suppliers trade purchase orders, acknowledgments, ship notices, and invoices across the network.

Connecting via iTradeNetwork
  1. A buyer on the network (foodservice distributor or grocery retailer) sponsors the supplier, who sets up an iTradeNetwork account and receives iTN's EDI specifications for the required document set.
  2. Establish connectivity; iTrade's EDI appendix defines AS2, FTP, HTTP, and VAN connections.
  3. Map internal order, shipment, and invoice data to iTN document specifications (typically 850, 855, 856, and 810).
  4. Exchange test documents, using compliance checking and functional acknowledgments, until the buyer approves production cutover.

Testing: iTradeNetwork does not publish a formal certification program. Its EDI appendix defines compliance checking (validating documents against specifications) and functional acknowledgments as part of document exchange, and suppliers are expected to validate each document type against iTN specifications with their sponsoring buyer before production.

Timeline: No public setup timeline. Duration depends on the sponsoring buyer's document set and testing scope; a mapped machine-to-machine connection takes longer than portal-based trading.

Most-traded documents on iTradeNetwork
  • 810 8 ch
  • 850 8 ch
  • 855 7 ch
  • 860 1 ch
  • 867 1 ch

Ready to automate your iTradeNetwork, Inc. EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.