If we move our storefront off SuiteCommerce to Shopify but keep NetSuite as the ERP, what integration work actually changes vs. staying on SuiteCommerce?
Moving the storefront off SuiteCommerce to Shopify adds an integration layer that did not exist before. SuiteCommerce reads NetSuite records directly; Shopify holds its own copies and syncs them. Celigo's Shopify to NetSuite template ships 32 flows, all scheduled rather than real time, and all disabled by default (Celigo, September 2026).
The architectural change in one sentence
SuiteCommerce is a storefront rendered from NetSuite's own database. Shopify is a separate system of record for commerce that has to be kept in agreement with NetSuite. You are not swapping a front end. You are introducing a second source of truth and taking on the job of keeping the two consistent.
Everything below follows from that.
What genuinely disappears
- The SuiteCommerce build and its release cadence. SuiteCommerce, SuiteCommerce Advanced and SuiteCommerce MyAccount are still actively released; the 2026.1.0 release covers all three and requires Node.js 20.10.0 (per Oracle NetSuite documentation, September 2026). That is a real front-end engineering practice with its own upgrade obligations, and it goes away.
- Waiting on NetSuite for storefront changes. Merchandising, theme work and landing pages stop being ERP-adjacent projects.
- A category of performance work. A storefront rendering from an ERP has a performance ceiling that a dedicated commerce platform does not.
What appears, and this is the part to budget
| New workstream | Why it exists | What it looks like in practice |
|---|---|---|
| Catalog sync | Shopify needs its own product records | Item to product mapping, matrix items to variants, images, metafields |
| Inventory sync | Shopify decrements its own inventory; NetSuite decrements its own | Scheduled reconciliation, oversell tolerance, per-location mapping |
| Order sync | Orders originate in Shopify, must land in NetSuite | Sales order or cash sale creation, customer matching, payment mapping |
| Fulfillment sync | NetSuite fulfils, Shopify has to tell the customer | Tracking numbers back to Shopify, partial fulfilments |
| Pricing and customer-specific pricing | NetSuite price levels are not a Shopify concept | For B2B, Shopify catalogs and price lists replace NetSuite price levels |
| Customer self-service | SuiteCommerce MyAccount showed live NetSuite data | Shopify customer accounts show Shopify data; ERP-held history needs a plan |
| Refunds, returns, credit memos | Two systems now have opinions about money | Mapping refunds to credit memos, deciding which system initiates |
Celigo's Shopify to NetSuite D2C template is a useful yardstick because it is a published inventory of this surface: 32 pre-built flows, of which 14 run Shopify to NetSuite, 13 run NetSuite to Shopify, 3 are on-demand setup flows, and the rest are internal. All are scheduled, not real time, and "all flows are disabled by default" (per Celigo documentation, September 2026). Oracle's own NetSuite ERP Connector is live on the Shopify App Store from $199.92/month and syncs "products, customers, inventory, sales orders and fulfillment info" (verified September 2026).
Thirty-two flows is the honest scope of "keep NetSuite, move the storefront." It is not a plugin.
The latency change nobody stages for
On SuiteCommerce, an inventory number on a product page is a NetSuite number, read live. On Shopify it is a Shopify number that agrees with NetSuite as often as your sync runs. Celigo's flows are scheduled. Shopify's Admin API allows 100 GraphQL points per second on standard plans, 200 on Advanced, 1,000 on Plus and 2,000 on enterprise (per Shopify developer docs, September 2026), which is generous but does not make a scheduled flow real time.
The practical consequences, which should be decided by the business and not discovered by it:
- Oversell tolerance. How many units are you willing to sell that you do not have, in exchange for not blocking the storefront on an ERP call? There is an answer and it is not zero.
- Buffer stock. A per-SKU safety margin held back from Shopify is the standard mitigation and it costs you sales on your fastest movers.
- Which system is authoritative on price. Pick one. Two systems both allowed to change price is the single most expensive ambiguity on this list.
What changes for B2B specifically
If SuiteCommerce was serving wholesale customers with contract pricing, that logic lived in NetSuite price levels and was read live. On Shopify it becomes Shopify B2B catalogs and price lists, maintained in Shopify and kept in agreement with NetSuite. That is a genuine data-ownership decision, not a migration step, and it deserves its own conversation with sales before anyone writes a sync.
Two adjacent constraints worth knowing before you scope it: Shopify lists Subscriptions as incompatible with B2B, and Net 45 is a native Shopify payment-terms template while non-template day counts, early-payment discounts and conditional terms are not (per Shopify, September 2026).
When NOT to make this move
- When SuiteCommerce is working and the complaint is aesthetic. A theme is cheaper than an integration layer.
- When NetSuite is also being upgraded or re-implemented. One system of record changes at a time.
- When nobody will own the integration after go-live. Thirty-two scheduled flows with no owner is an outage with a delay fuse.
- When the real goal is leaving NetSuite. If the destination is a different ERP, doing the storefront first means building an integration you intend to throw away.
The Deploi point of view
Our own position, from building on Shopify. Separate from the facts above.
- Our take: Budget the integration as the project, not as a line in the storefront project. The storefront is the visible half and the cheaper half. The thirty-two-flow surface between Shopify and NetSuite is the half that determines whether this migration is judged a success in month six.
- What our NetSuite integration decision record doesn't cover: that record asks whether to build or buy the connector once the decision to connect is made. This page is about what the connection has to carry in the specific case where the storefront is leaving SuiteCommerce, which changes the inventory of flows and adds the customer-self-service and contract-pricing questions the generic case does not have.
- Where we disagree: SuiteCommerce-to-Shopify content is overwhelmingly written by people selling the storefront build, and it frames NetSuite as "retained," as though retention were free. Retaining NetSuite while moving the storefront is the most integration-heavy configuration available. It is often the right call, and it is never the cheap one.
- What this page adds: that SuiteCommerce is still actively released in 2026 and therefore not a forced migration, that the published Celigo template's 32 scheduled flows are the honest scope of the integration layer, and that the SuiteCommerce MyAccount surface is one of the things NetSuite lists as unsupported under Multi-Subsidiary Customer.
Reviewed by Martin Dejnicki, Director of SEO & AI Search. Facts verified 2026-09-14.
Where we worked this out
Our decision records