EDI Integrations for NetSuite

by Rico Andrade
August 16, 2018

Electronic Document Interchange (EDI) has helped companies eliminate paper-based communications by automating and streamlining business-to-business (B2B) communications for over 30 years. The use of standard EDI formats throughout the supply chain — from manufacturers, distributors, retailers, fulfillment providers, and other trading partners — has allowed retail companies to fulfill orders faster, cheaper, and with fewer errors.

EDI Integrations with integrator.io

Celigo’s integrator.io platform allows EDI files to be integrated with any other application that is supported by integrator.io. Currently, EDI files can be sent and received via FTP. Support for AS2 (Applicability Statement 2) will be available by the end of 2018.

Celigo’s integrator.io supports all EDI X12 documents that are commonly used in the retail supply chain. Additionally, we support over ten vendor-specific EDI formats today with more being added all the time. If you need integration with a format that is not currently supported, the Celigo Product team will quickly build out the template at no cost to you. Please ask your Celigo Account Executive for more information.

EDI Integrations for NetSuite

Celigo has worked with hundreds of NetSuite companies to automate order and fulfillment processes between retailers, distributors, manufacturers, and fulfillment providers. Listed are some common EDI integrations that are used by retailers who use NetSuite as their ERP system.

Supplier Orders

A company typically uses these EDI integration flows for NetSuite when communicating with manufacturers, distributors, and other suppliers:

  • Supplier’s Invoice (EDI 810) becomes a NetSuite Invoice
  • Supplier’s Price/Sales Catalog (EDI 832) becomes NetSuite Item
  • Supplier’s Inventory Update (EDI 846) becomes a NetSuite Inventory Adjustment
  • NetSuite Purchase Order becomes a supplier Purchase Order (EDI 850)
  • Supplier’s PO Acknowledgement (EDI 855) updates NetSuite Purchase Order
  • Supplier’s ASN (EDI 856) becomes a NetSuite Item Receipt

Outsourced Fulfillment (3PL)

A company typically uses these EDI integration flows for NetSuite when communicating with third-party logistics providers (3PL):

  • NetSuite Sales Order becomes a 3PL Warehouse Shipping Order (EDI 940)
  • 3PL Warehouse Shipment Advice (EDI 945) updates NetSuite Sales Order
  • 3PL Inventory Adjustment Advice (EDI 947) updates NetSuite Inventory
  • NetSuite Transfer Order becomes a 3PL Warehouse Stock Transfer Shipment Advice (EDI 943)
  • 3PL Warehouse Stock Transfer Receipt Advice (EDI 944) updates NetSuite Transfer Order

Drop Shipping

A company that fulfills orders as a drop shipper typically uses these EDI integration flows for NetSuite:

  • Retailer Purchase Order (EDI 850) becomes a NetSuite Purchase Order
  • NetSuite sends PO Acknowledgement (EDI 855) to Retailer
  • NetSuite Sales Order fulfillment sends Advance Ship Notice (EDI 856) to Retailer
  • NetSuite Items is sent as Price/Sales Catalog (EDI 832) to Retailer
  • NetSuite Inventory is sent as Inventory Update (EDI 846) to Retailer
  • NetSuite Invoice is sent as Invoice (EDI 810) to Retailer

To learn more about EDI integrations for NetSuite, see NetSuite Automation Across Applications.

Related Posts

Share This