Shopify B2B - NetSuite implementation guide

A complete implementation guide for merchants and support teams deploying the Celigo Shopify B2B – NetSuite integration template (NA) and (EU).

The following video explains the Shopify B2B - NetSuite integration template

Just getting started? Start here

If you want companies, locations, contacts, catalog pricing, and orders up and running, follow sections in order.

What this template does

The Shopify B2B – NetSuite template connects your Shopify Plus B2B storefront to NetSuite so that both systems share a single, accurate version of your business data. Companies and their locations managed in NetSuite appear in Shopify automatically. B2B orders placed by buyers flow into NetSuite as Sales Orders. Catalogs and pricing tiers sync from NetSuite price levels. Fulfillments, payments, and refunds update both systems without manual entry.

What merchants gain

• Sales teams stop manually creating NetSuite customers for every new B2B buyer. Every Shopify company and location lands in NetSuite automatically.
• Operations teams stop keying orders by hand. Every B2B order placed in Shopify lands in NetSuite within minutes.
• Finance teams get accurate payment capture: Shopify order payments create NetSuite Customer Payments and apply them to the correct invoice.
• Merchandising manages price levels in NetSuite and publishes them as Shopify Catalogs automatically — with per-location catalog assignments.
• Warehouse teams close the fulfillment loop: Item Fulfillments posted in NetSuite mark Shopify orders as shipped and send tracking notifications to buyers.

Who this guide is for

This guide is written for:

• Merchants and store owners who are setting up the integration themselves or overseeing an implementation.
• Support teams who need to understand how each flow works in order to diagnose issues and answer merchant questions.
• NetSuite administrators who are preparing NetSuite for the integration (bundle installation, roles, saved searches).

B2B data model: how the two platforms map to each other

Before you begin, understand how Shopify B2B entities correspond to NetSuite records. This mapping drives everything — connections, flow behavior, and how lookups work.

All 16 flows at a glance

The template ships with 16 flows grouped across 9 modules. All flows are disabled by default — you enable them in a specific order after completing setup. Section First-time enablement walks through the exact sequence.

#	Flow Name	Direction	Trigger
Products
1	Shopify products to NetSuite item ID map (add or update)	SHP → NS	On-demand / Scheduled
Companies
2	NetSuite customer to Shopify company (add or update)	NS → SHP	Scheduled
3	Shopify companies and locations to NetSuite (add or update)	SHP → NS	Scheduled
Locations
4	NetSuite locations to Shopify locations (add or update)	NS → SHP	Scheduled
5	NetSuite locations to Shopify locations (delete)	NS → SHP	Scheduled
Contacts
6	Shopify contacts to NetSuite contacts (add or update)	SHP → NS	Scheduled
7	NetSuite contacts to Shopify contacts (add or update)	NS → SHP	Scheduled
Orders
8	Shopify B2B order to NetSuite sales order (add)	SHP → NS	Scheduled
Shipments
9	NetSuite fulfillment to Shopify fulfillment (add)	NS → SHP	Scheduled
Catalogs & Pricing
10	NetSuite price level catalogs to Shopify catalogs (add or update)	NS → SHP	Scheduled
11	NetSuite price level catalogs to Shopify companies and locations	NS → SHP	Scheduled
12	NetSuite product price level to Shopify catalog product price	NS → SHP	Scheduled
13	Remove locations from catalogs	NS → SHP	Scheduled
Payments
14	Shopify payments to NetSuite customer payments (add)	SHP → NS	Scheduled
15	NetSuite payments to Shopify payments (add)	NS → SHP	Scheduled
Refunds
16	Shopify refund to NetSuite credit memo (add)	SHP → NS	Scheduled

Prerequisites

Complete every item in this section before installing the template. Skipping prerequisites is the single most common cause of errors on new installations.

NetSuite requirements

Shopify requirements

• A Shopify Plus plan — B2B features are exclusive to Shopify Plus.
• B2B / Wholesale features enabled — Shopify Admin > Settings > Markets > B2B should be active.
• An Admin API access token with the following scopes: read_orders, write_orders, read_customers, write_customers, read_products, write_products, read_fulfillments, write_fulfillments. Create a Custom App in Shopify Admin > Apps > Develop apps.
• Your store URL noted — the yourstore.myshopify.com domain.

Celigo requirements

• An active Celigo integrator.io account. Contact your Celigo account manager if you are unsure whether your subscription supports marketplace templates.
• Only account owners in integrator.io can configure connections. Ensure the person performing setup has account owner permissions in Celigo.

Install the Template

Find the template in the Celigo marketplace

In Celigo integrator.io, click Marketplace in the left navigation. Search for "Shopify B2B NetSuite" or browse Shopify templates. Click the Shopify B2B – NetSuite Integration Template tile.

Configure connections

During installation, Celigo will prompt you to configure three connections. All must be fully authorized before any flow can run.

Connection 1 — NetSuite (Token-Based Authentication)

Field	Value
Account ID	Your NetSuite Account ID (e.g., 1234567). Visible in the URL when logged in: https://XXXXXX.app.netsuite.com — the number before .app.
Consumer Key	From the Integration record created in prerequisites.
Consumer Secret	From the Integration record created in prerequisites.
Token ID	From the Access Token created in prerequisites.
Token Secret	From the Access Token created in prerequisites.

Click Test Connection — must show green before saving.

Connection 2 — Shopify B2B Store (read)

Type: HTTP / GraphQL. Used for reading data from Shopify (companies, orders, contacts).

Field	Value
Base URI	https://{your-store}.myshopify.com/admin/api/2025-07/graphql.json
Authentication	Token — enter Bearer {your-admin-api-token}

Connection 3 — Shopify B2B Store (write)

Type: HTTP / GraphQL. Used for write operations back to Shopify (fulfillments, catalog updates, payment status). Uses the same store URL and token as Connection 2.

Initial Setup

Before you enable any transactional flow, you must run the Products setup flow and complete the integration-level settings. This section is the most important part of a new installation — getting it right prevents a category of hard-to-diagnose errors later.

Step	Action	Where
1	Run the Products (Item ID Map) flow	Celigo — flow dashboard
2	Configure integration-level settings	Celigo — integration Settings tab
3	Configure Orders flow group settings	Celigo — Flows tab > Orders gear icon
4	Configure Refunds flow group settings	Celigo — Flows tab > Refunds gear icon
5	Configure Catalogs & Pricing flow group settings	Celigo — Flows tab > Catalogs gear icon

Step 1 · Build the item ID map

The very first action after installation is to run the Shopify products to NetSuite item ID map (add or update) flow. This flow reads your Shopify product catalog and creates cross-reference records in NetSuite that map each Shopify product variant (by SKU) to its corresponding NetSuite item internal ID.

This mapping is the structural backbone of the integration. Every order flow depends on these records to resolve Shopify line items into NetSuite item records. Without them, order imports will fail because NetSuite cannot identify which item is on each order line.

Configure Settings

The integration's Settings page controls how data moves between Shopify and NetSuite. Most settings are configured once at go-live and rarely changed. This section explains each setting group, what each field does, and what happens if you leave it at its default.

Each field in the Settings form is tagged with one of three labels:

Label	Meaning
Required	Must be set before the related flow can be enabled. Celigo will block enablement until these are configured.
Optional	Can be left at its default in most implementations.
Conditional	Optional in the form but becomes effectively required when a specific scenario applies. The scenario is noted inline. Skipping a Conditional field when your scenario applies is one of the most common causes of silent data issues post go-live.

Integration-level settings (General)

In the integration, click the Settings tab, then the gear icon. These settings apply globally across all flows.

Setting	Tag	What it does
Default Payment Terms	Optional	The Shopify payment terms template applied to companies synced from NetSuite when no terms exist on the NetSuite Customer. Options: Due on receipt, Due on fulfillment, Within 7 / 15 / 30 / 45 / 60 / 90 days, Fixed date. Choose to match your standard B2B credit terms.
Default Contact Role	Optional	Role assigned to contacts at a Shopify Location. Ordering only — the contact can place orders but cannot manage the account. Location admin — full administrative rights. Most implementations start with "Ordering only".
NetSuite Tax Code	Required	A non-inventory item representing the tax code applied to Sales Orders. Select from the dropdown. Required — every order sync will fail if this is blank.

Location settings

Setting	Tag	What it does
Create Location for Company	Conditional	When on, creates a Shopify Location using the parent Company's own address in addition to any sub-customer locations. Enable when NetSuite Customers have a meaningful address on the parent record that buyers should use for shipping.
Billing Same as Shipping	Optional	Sets billing address equal to shipping address for locations. Enable for customers who always bill and ship to the same address.
Editable Shipping Address	Optional	Whether buyers can change their shipping address at checkout. Enable for flexibility; disable to enforce fixed ship-to addresses for strict procurement scenarios.
Checkout to Draft	Conditional	Creates Shopify orders as Draft Orders pending merchant review. Enable when your business requires order approval workflows before fulfilment begins.
Main Contact Selection	Optional	Controls which contact becomes the main contact for a Company. Oldest Internal ID — uses the Contact with the lowest NetSuite Internal ID. Primary Contact role — uses the Contact tagged with the "Primary Contact" role. If your NetSuite data does not have a consistent Primary Contact role set, use "Oldest Internal ID".

Orders flow group settings

On the Flows tab, click the gear icon on the Orders module row.

Setting	Tag	What it does
Assign Order to Location	Optional	When on, Sales Orders are created under the Sub-Customer (Location). When off, all orders land on the parent Customer (Company). Recommended: on — most B2B operations track orders at the delivery-site level.
NetSuite Discount Item	Conditional	The Other Charge item representing Shopify discounts on Sales Orders. Select the item you created in prerequisites. Required if any B2B orders use discount codes or price adjustments.

Refunds flow group settings

On the Flows tab, click the gear icon on the Refunds module row.

Setting	Tag	What it does
Create Return for Refund	Conditional	When on, creates a Return Authorization in NetSuite before the Credit Memo (full returns workflow). When off, creates the Credit Memo directly from the invoice. Enable for formal returns processes; leave off for simple refund-only workflows.
NetSuite Adjustment Item	Required	The Non-Inventory item used for shipping refunds and other adjustments that don't match a product line. Select the item created in prerequisites. Required — the refunds flow will error on every record without this.

Catalogs & Pricing flow group settings

On the Flows tab, click the gear icon on the Catalogs & Pricing module row.

Setting	Tag	What it does
Default State	Optional	All Products — new Catalogs are pre-populated with every published product. Empty — new Catalogs start with no products; you add them separately. Use Empty for fine-grained product access control; use All Products for standard open-catalog B2B setups.
Autopublish	Conditional	When on, any newly created Shopify product is automatically added to all existing Catalogs. Enable for setups where all B2B customers always access your full product range.

Flows: Products

Flows: Companies

Companies are the foundation of the B2B data model. All other entities (Locations, Contacts, Orders) depend on Companies being in sync first.

Flows: Locations

Flows: Contacts

Flows: Orders

The Orders flow is B2B-only by design. It filters Shopify orders to only those placed through the B2B portal — identified by the presence of a purchasingEntity (company + location). Regular consumer orders from the same store are automatically excluded.

What this flow maps

Shopify data	NetSuite field
Line items (SKU + qty + price)	Sales Order lines — items resolved via Product Item ID Map
Line-level discount allocations	Discount line per item (negative, uses Discount Item)
Header-level discount	Single header discount line (negative, uses Discount Item)
Shipping cost	Shipping charge line
Shipping discount	Shipping discount line (negative)
Gift card applied	Gift Card Certificate line (negative, reduces total)
Payment terms (purchasingEntity)	Terms on Sales Order
Note + PO number	Memo: "Note text - PO: PO-12345"
Tax lines per item	Stored in etailOrderCustomData for Refunds flow downstream
Currency	Order currency

Flows: Shipments

Flows: Catalogs & Pricing

This module maps NetSuite Price Levels to Shopify Catalogs and keeps product prices within each catalog in sync. Run flows in order A → B → C. Flow D runs independently to clean up stale assignments.

Flows: Payments

Flows: Refunds

Enable this module last — it requires NetSuite invoices to already exist for orders. If enabled before the Orders flow has run, every record will error with "No Invoice found".

Routing logic

Refund type	Shopify trigger	NetSuite outcome
Product refund	One or more line items refunded	Return Authorization (if "Create Return for Refund" is on) + Credit Memo against the original invoice
Shipping refund	Shipping line refunded, no items	Credit Memo with Adjustment Item representing the shipping amount
Other adjustment	No items, no shipping (manual refund)	Credit Memo with Adjustment Item for the refund amount

Enable Flows and Schedule

Enabling flows in the wrong order is the most common cause of errors on new installations. This section covers which flows depend on which, the recommended first-time enablement sequence, and how to set schedules for production operation.

Dependency order

Flow	Depends on	Notes
Products (Item ID Map)	Items in NetSuite with matching SKUs	Run first, before every other module.
Companies (NS → Shopify)	Nothing (NS as source)	Run before Locations and Contacts.
Companies (Shopify → NS)	Nothing	Independent direction; can run simultaneously.
Locations (Create/Update)	Companies in both systems	Sub-Customers must have a parent Customer.
Locations (Delete)	Locations (Create/Update) has run	Detects inactivated Sub-Customers.
Contacts (Shopify → NS)	Companies in NetSuite	Contacts link to existing Customer records.
Contacts (NS → Shopify)	Companies and Locations in Shopify	Role assignments require Locations to exist.
Orders	Item ID Map, Companies, Locations in both systems	The most dependent flow — all setup must be complete.
Shipments	Order flow has created the NS Sales Order	Reads NetSuite Item Fulfillment records.
Catalogs A (Create/Update)	Nothing (NS as source)	Run before Catalogs B and C.
Catalogs B (Assign)	Catalogs A has run	Requires Catalogs to exist in Shopify first.
Catalogs C (Prices)	Item ID Map, Catalogs A	Requires Shopify products and Catalogs to exist.
Catalogs D (Remove)	Catalogs B has run	Cleanup flow; runs independently.
Payments (Shopify → NS)	Order flow + invoices in NetSuite	Requires open invoice to apply payment against.
Payments (NS → Shopify)	Order flow (order must exist in Shopify)	Enable with the Shopify → NS direction.
Refunds	Order flow + invoices in NetSuite	Enable last — requires NetSuite invoices to exist.

First-time enablement sequence

Follow this sequence when enabling flows for the first time on a new installation. Complete each group before moving to the next.

Scheduling best practices

Flow group	Recommended schedule	Reason
Products (Item ID Map)	Daily / On-demand	Run manually before go-live. Schedule daily after that, plus re-run whenever new products are added.
Companies (both directions)	Every 15–30 min	Core entity — keep it frequent for near-real-time company management.
Locations (Create/Update)	Every 15–30 min	Location changes should stay near-real-time.
Locations (Delete)	Every 30–60 min	Deletions are rare — less frequent schedule is fine.
Contacts (both directions)	Every 15–30 min	Role assignments and contact changes should stay in sync promptly.
Orders	Every 5–15 min	Orders are time-sensitive — keep this as frequent as your plan supports.
Payments (both directions)	Every 15–30 min	Payment status should resolve promptly after orders are placed.
Shipments	Every 15–30 min	Buyers expect shipping notifications quickly after fulfillment.
Catalogs A & B	Every 1–4 hours	Catalog structure changes infrequently — hourly is sufficient.
Catalogs C (Prices)	Every 30–60 min	Price changes should reflect in Shopify within the hour.
Catalogs D (Remove)	Every 1–2 hours	Cleanup flow — less urgent, hourly is fine.
Refunds	Every 15–30 min	Refunds should post to NetSuite promptly to keep AR accurate.

Coexistence with the Shopify – NetSuite Integration App

This B2B template can run alongside Celigo's Shopify – NetSuite Integration App (D2C). They serve different customer segments and can complement each other — but you must configure each to process only its intended orders.

This template (B2B)	Shopify – NetSuite IA (D2C)
Already filters to B2B orders only (orders with a purchasingEntity)	Must add filter: exclude orders where purchasingEntity is not null
Handles Companies, Locations, Contacts, Catalogs	Handles D2C customers, standard orders
Fully customizable — you own it	Centrally maintained by Celigo
Not centrally maintained by Celigo	Can share the same Shopify store

To add the filter to the Integration App: open the Orders export in the Shopify-NetSuite IA, go to the Filter section, and add a condition: purchasingEntity is null. This ensures the IA processes only consumer orders with no company association.

Troubleshooting

This section covers the most common issues across all flow modules. For each issue, the fastest path to diagnosis is to open the failing record in the Celigo flow dashboard, examine both the source payload and the error response, and identify which step failed (export, lookup, transformation, or import). Each stage has different root causes.

Companies not syncing

• Check subsidiary assignment. If your NetSuite account uses subsidiaries and the customer's subsidiary does not match the expected value, the import may fail or create a duplicate. Verify the subsidiary mapping in the customer import step.
• Check for ampersands in company names. Shopify GraphQL rejects & in names. The template auto-converts & to "And" — if errors persist, check the company name in NetSuite and re-run the Companies flow.
• Check payment terms format. NetSuite term names must match Shopify's supported formats exactly. See the note in the Companies flow section above.

Locations not syncing

• Verify sub-customers are enabled in NetSuite (Setup > Company > Enable Features > CRM tab). If not enabled, the Locations flow cannot create Sub-Customer records and will error.
• Verify Companies have synced first. A Sub-Customer requires a parent Customer. If the Companies flow hasn't run or errored, Locations will fail with a "parent not found" error.

Orders not syncing

• Check for "No customer record found for Location" errors. This means the Locations flow hasn't yet synced those locations. Run the Locations flow, then retry the failed order records.
• Check for Item ID map gaps. If the order contains a line item with no matching NetSuite item (no Item ID map record), the import step will fail. Locate the failing SKU in the error log and create or re-run the Products flow to generate a map record for it.
• Verify the order has a purchasingEntity. The flow filters for B2B orders only. Consumer orders placed without a company association will not be picked up by this flow — they belong to the D2C Integration App.

Contacts not assigned to all locations

• Check the Default Contact Role setting is configured in integration settings.
• Review the Contacts flow run history for role assignment step errors. The assignment step runs after contact create/update — errors there will not fail the whole flow but will skip the assignment.

Catalog prices not updating

• Run the Products flow first. Catalogs C (Prices) depends on the Item ID Map being populated. If a Shopify variant has no map record, its price will not be updated. Run the Products flow and then re-run Catalogs C.
• Run Catalogs A before Catalogs C. The Catalog must exist in Shopify before prices can be written to it. Confirm Catalogs A has run successfully.

Refund errors

• Check "No Invoice for #[order] found" errors. The refunds flow looks up the original invoice by Shopify Order ID. Check the NetSuite Sales Order status — ensure your order-to-invoice workflow has run for this order, then retry.
• Check etailOrderCustomData on the Sales Order. The refunds flow reads this field (populated by the Orders flow) to apply per-line tax rates to the Credit Memo. If the Orders flow errored or was disabled when the original order came through, this field may be missing. Re-run the Orders flow for the affected order to re-populate it, then retry the refund.

OAuth token expirations

• Shopify Admin API tokens can become invalidated after an app uninstall/reinstall or changes to API scopes. When this happens, every flow using the Shopify connection will fail with an authentication error. Regenerate the access token in Shopify Admin > Apps > Develop apps, then update the Celigo connection.
• Only the account owner in Celigo can update connection credentials. Ensure the person who has access to both Shopify and the Celigo account is available if this occurs. Include this in your operations runbook.
• NetSuite TBA tokens do not expire automatically but should be rotated on a regular cadence (every 90–180 days is standard for security compliance). Schedule token rotation as a recurring maintenance task.

General debugging approach

1. Find the failing record. In the Celigo flow dashboard, open the flow run that contains the error and locate the specific record(s) that failed. Each failed record has a detailed error log.
2. Identify the failing step. Export failures indicate a connection or query issue. Lookup failures indicate a missing or non-matching record in the target system. Transformation failures indicate a mapping or scripting error. Import failures indicate a payload or permissions issue.
3. For lookup failures: Find the saved search referenced by the failing step. Preview that search in NetSuite with the same filter values the flow used. If the search returns no results, the problem is the underlying data — the record does not exist or does not match the expected criteria.
4. For transformation failures: Check any handlebars expressions in the mapping for typos, missing field references, or fields that are null in the source payload. The flow dashboard shows the source payload for each failing record — use it to verify which fields are actually populated.
5. Fix before retrying in bulk. Retrying records against an unresolved root cause generates noise in your error logs and can create partial records. Resolve the underlying issue first, then retry.