NetSuite EDI Integration with Celigo: A Practical Guide

NetSuite EDI integration means automatically exchanging business documents — purchase orders, advance ship notices, and invoices — between NetSuite and your retail trading partners or suppliers. With Celigo, this runs through a two-component architecture: an EDI translation hub handles X12 or EDIFACT document parsing; Celigo B2B Manager handles the NetSuite side, mapping translated data into sales orders, item fulfillments, and customer records automatically. For a full overview of what Entech delivers on Celigo for NetSuite EDI, see our Celigo NetSuite EDI integration service page.

How Celigo connects to NetSuite for EDI

Celigo B2B Manager does not process raw X12 or EDIFACT files. Instead, it connects to a third-party EDI translation hub via API or file-based integration. The hub receives EDI documents from your trading partners — retailers, 3PLs, or suppliers — and converts them into a standardized format Celigo can read. Celigo then maps that data into NetSuite records: an 850 purchase order becomes a sales order, an 856 advance ship notice gets written back out after item fulfillment, and so on.

The critical design point: you need both components. The EDI hub manages trading partner connectivity, document translation, compliance, and transport protocols. Celigo manages the NetSuite side — record creation, field mapping, error handling, and outbound data flow back to the hub. These roles do not overlap; neither product replaces the other.

Most wholesale distributors already have an EDI hub relationship — with SPS Commerce, TrueCommerce, DiCentral, or a VAN like OpenText — before they implement Celigo. If you don't, selecting and onboarding your EDI hub is step one. Celigo cannot substitute for it.

EDI document types in a NetSuite wholesale environment

Six EDI transaction sets cover the majority of wholesale distribution flows. Each maps to specific NetSuite record types that Celigo creates or updates.

850 Purchase Order → NetSuite Sales Order. When a retailer places an order, their system sends an EDI 850. Celigo maps each line item to a NetSuite sales order, applying item cross-references from the trading partner configuration. This is the highest-volume inbound transaction for most distributors, and the one where item-code mismatches cause the most failures.

856 Advance Ship Notice → NetSuite Item Fulfillment. After you ship, NetSuite creates an item fulfillment record. Celigo reads that record and generates an EDI 856, sending it back to the retailer via the hub. Timing matters: the 856 must fire after the shipment is confirmed in NetSuite, not when the order is picked or packed. Retailers penalize late or early ASNs — configure the trigger carefully.

810 Invoice → NetSuite Invoice. Some retailers expect an EDI 810 invoice rather than a PDF. Celigo reads the NetSuite invoice record after fulfillment and generates the 810. Payment terms on the NetSuite invoice — Net 30, Net 60 — map directly to the 810 invoice terms field.

855 PO Acknowledgement. When you receive an 850, many retailers require an 855 confirming receipt and whether you can fulfill each line. Celigo can generate the 855 from NetSuite automatically after the sales order is created, or after a manual review step if your team needs to check available stock first.

940/945 Warehouse Orders (for 3PL distributors). If you use a third-party warehouse, the 940 (warehouse shipping order) goes from your system to the 3PL when you need to ship, and the 945 (warehouse shipping advice) comes back confirming the shipment. Celigo maps the 940 from a NetSuite item fulfillment and writes the 945 back into NetSuite to update the fulfillment record with actual ship quantities and tracking.

997 Functional Acknowledgement. The 997 is an automatic confirmation that a document was received without structural errors. Celigo and your EDI hub typically handle 997 generation automatically — configure it once per trading partner and it fires for every inbound transaction. If a 997 is not received, the sending party retransmits, which causes duplicate order problems downstream.

Setting up NetSuite EDI integration with Celigo

Setup follows a consistent sequence regardless of how many trading partners you're onboarding. The most common mistake is trying to onboard multiple trading partners simultaneously before the first one is stable.

Step 1: Choose and configure your EDI hub. Select a translation hub — SPS Commerce, TrueCommerce, DiCentral, or Cleo are the most common for NetSuite-based distributors — and onboard your trading partners there. The hub handles compliance mapping (each retailer's 850 has slightly different field requirements), transport setup, and AS2 or SFTP connection configuration. This step happens before any Celigo configuration begins.

Step 2: Install Celigo B2B Manager in NetSuite. Install the Celigo SuiteApp from the NetSuite marketplace. Create a dedicated integration role in NetSuite with read/write permissions on customers, items, sales orders, item fulfillments, and invoices. Do not use an administrator account for integration access — a scoped role limits blast radius if credentials are ever compromised.

Step 3: Configure trading partner profiles in Celigo. Each trading partner gets its own profile in Celigo B2B Manager. This profile contains the field mappings for that retailer's specific 850 format, their item identifier conventions (UPC, internal item code, vendor item number), and their acknowledgement requirements. Trading partner configuration is the most time-consuming part — each new partner adds roughly one week to the project timeline.

Step 4: Build the item cross-reference table. This is the most important and most commonly skipped step. Retailers use their own item codes in EDI files; NetSuite uses your internal IDs or SKUs. If Celigo cannot match a retailer's item code to a NetSuite item record, the sales order creation fails. Build a complete cross-reference lookup table before going live — one row per item per trading partner. Missing entries cause silent failures that only surface during production order processing.

Step 5: Test in sandbox with real EDI files. Run actual 850 files — not synthetic test data — through Celigo's sandbox environment connected to your NetSuite sandbox account. Verify that sales orders are created correctly, line items map accurately, and 856s and 810s generate and route back to the hub as expected. Real EDI files expose edge cases that test files miss: unusual item codes, multi-line orders, split shipments.

Step 6: Go live with one trading partner, then expand. Activate one trading partner at a time. Monitor the first 10–20 EDI cycles closely before adding the next partner. Most production issues appear in the first few real orders, not later. Sequential onboarding also makes it easier to attribute failures to a specific trading partner configuration rather than troubleshooting a global issue.

For a broader view of how Entech scopes and delivers these projects alongside other NetSuite integration work, see our Celigo implementation guide. If your environment also involves wholesale ecommerce or 3PL alongside EDI, the Celigo for wholesale distributors guide covers how those flows interact.

Common errors and how to fix them

Item code mismatch — "Item not found" on sales order creation. The most common error. The retailer's item code in the 850 does not match anything in the cross-reference table. Fix: add the missing mapping to the cross-reference table in Celigo. If a retailer uses multiple item identifiers across different order types, map all variants. Retailers periodically add new item codes without notice; build a monitoring alert for unmapped item failures rather than discovering them days later.

856 firing before fulfillment is confirmed. The advance ship notice is sent before the shipment is actually picked and confirmed in NetSuite, causing the retailer's system to mark the order as shipped while it is still in your warehouse. Fix: configure the 856 trigger to fire on item fulfillment status "Shipped" only. Do not trigger on sales order creation or picking status — the fulfillment record must exist and be marked shipped first.

Duplicate sales orders from re-transmitted 850s. Retailers sometimes retransmit 850s after a technical failure, and Celigo creates a new sales order for each transmission. Fix: configure a unique PO number check before creating a new sales order. If the retailer's PO number already exists in NetSuite as an external ID, update or skip the record rather than creating a duplicate. This deduplication step belongs in the flow logic, not as a manual cleanup task.

997 not received — hub reports unacknowledged documents. Celigo or the hub is not generating 997 acknowledgements for inbound 850s, causing the retailer's system to retransmit. Fix: confirm that 997 auto-generation is enabled in your hub's trading partner profile. Some hubs require explicit configuration per trading partner; it is not always on by default. Check the hub's transaction log before assuming the issue is on Celigo's side.

Timeline and cost

For a standard wholesale distributor connecting one or two retail trading partners, budget $12,000 to $20,000 in implementation services through a certified Celigo partner, with a 4 to 8 week timeline from kickoff to go-live on the first trading partner. Celigo B2B Manager subscription runs $1,500 to $3,000 per month depending on flow volume and partner count. EDI hub subscription fees are separate — typically $300 to $1,500 per month with per-transaction pricing on top, varying by provider.

What pushes the timeline out: heavily customized NetSuite item records, trading partners with unusual PO requirements, more than three new trading partners onboarding simultaneously, or a 3PL workflow requiring the 940/945 transaction set alongside the standard 850/856/810 flows.

For distributors with five or more trading partners to onboard, expect 8 to 16 weeks and $25,000 to $50,000 in implementation services. Trading partner onboarding is sequential — each partner requires its own configuration, item cross-reference mapping, test cycle, and sign-off — so the timeline scales linearly with partner count, not logarithmically.

Ongoing maintenance after go-live — new trading partner onboarding, retailer schema changes, Celigo version updates, and item record additions — typically runs $1,500 to $4,000 per month on a managed retainer. Treating the integration as set-and-forget is the most reliable way to accumulate production failures over time; retailers update their EDI requirements more frequently than most distributors expect.

Frequently Asked Questions

Does Celigo have a native EDI connector for NetSuite?

Celigo's B2B Manager product is purpose-built for EDI-to-NetSuite flows, but it is not a standalone EDI system. It connects NetSuite to a third-party EDI translation hub. The hub handles X12/EDIFACT document translation and trading partner connectivity; Celigo handles the NetSuite side — creating sales orders, item fulfillments, and invoices from the translated data.

Do I need a separate EDI hub if I use Celigo for NetSuite?

Yes. Celigo does not replace your EDI translation hub. You need both: the hub for document translation, AS2/SFTP transport, and trading partner compliance mapping, and Celigo to map the translated data into NetSuite records. If you do not have a hub relationship, selecting one is step one before any Celigo configuration begins.

What EDI documents does Celigo support with NetSuite?

Celigo B2B Manager supports the full range of standard wholesale EDI transactions: 850 PO → Sales Order, 856 ASN → Item Fulfillment, 810 Invoice, 855 PO Acknowledgement, 940/945 Warehouse Shipping Orders for 3PL flows, and 997 Functional Acknowledgements. The specific transactions configured depend on what your trading partners require and what your EDI hub translates.

How long does NetSuite EDI integration setup take with Celigo?

A standard setup for one or two trading partners typically takes 4 to 8 weeks from kickoff to go-live. Each additional trading partner adds roughly one week of configuration and testing. A full network of five or more partners typically runs 8 to 16 weeks. Custom NetSuite configurations — custom item records, multi-subsidiary, complex pricing logic — add two to four weeks.

How much does NetSuite EDI integration with Celigo cost?

Implementation through a certified partner runs $12,000 to $20,000 for a standard one-to-two trading partner project. Celigo B2B Manager subscription is $1,500 to $3,000 per month. EDI hub fees are separate, typically $300 to $1,500 per month. Larger projects covering five or more trading partners run $25,000 to $50,000 in implementation services.

Entech Solutions has delivered NetSuite EDI integrations on Celigo B2B Manager for wholesale distributors, CPG brands, and 3PL-dependent retailers. If you are onboarding a new retail trading partner, migrating from legacy EDI middleware, or troubleshooting an existing flow, get in touch — we'll give you a straight read on timeline, scope, and cost before any commitment. If EDI is one piece of a larger integration project, see our guide to ERP integration for wholesale distributors for the full picture — ecommerce, CRM, and 3PL alongside EDI.