NetSuite B2B ecommerce: Shopify Plus + Celigo, SuiteCommerce or native?

NetSuite businesses usually have the budget for a proper B2B store, and they feel the fees more than anyone, because every route to one adds a licence on top of NetSuite’s own. Connect Shopify Plus through Oracle’s connector or Celigo, buy SuiteCommerce from Oracle, or use a B2B platform that integrates with NetSuite directly. Each has a different cost, and a different set of things it doesn’t carry across.

This guide prices all four from published sources as of October 2026, and covers the NetSuite limits that decide whether your store keeps up: shared concurrency, SuiteCommerce’s cart limit and the end of SOAP integrations. We make TierCommerce, which integrates natively with NetSuite, so we’re not neutral; every figure is linked.

The four routes, priced

Shopify Plus itself is A$3,700 a month on a three-year term or A$4,000 on one year in Australia.^[4] A B2B setup also uses Celigo’s flows quickly, because customers, items, prices, stock, orders, fulfilments and invoices each need one, so price the larger plan. Our Shopify Plus B2B cost guide adds the apps.

What Oracle’s Shopify connector carries for B2B

Oracle’s connector is the natural choice if you want the ERP vendor to own the sync. Its documentation sets out how B2B works, and four points matter to a wholesaler:^[5]

• Catalogues are assigned per company, not per location. A customer whose branches buy at different prices needs another approach.
• Catalogues are built by hand. Each is a custom record in NetSuite with a price level and any fixed-price overrides, rather than generated from the pricing you already hold per customer.
• Credit limits and units of measure aren’t mentioned. Check how a buyer’s available credit and pack sizes would reach the store.
• Marking invoices paid looks back 90 days. Payments made in NetSuite are pushed back to Shopify only for transactions from the last 90 days.

None of these stops a store working. They decide how much of your pricing the store can show without your team maintaining it twice.

What each NetSuite route syncs

Price is only half the comparison. The other half is which of your NetSuite data actually reaches the store, and who keeps it working when NetSuite, Shopify or your business changes.

What your customers can do on each route

The routes differ in more than price. This is every B2B feature your customers would use, on each platform that reaches NetSuite.

NetSuite concurrency: the limit every integration shares

NetSuite doesn’t limit requests a minute. It limits how many can run at once across the whole account, and every integration on the account shares the same pool:^[6]

Each SuiteCloud Plus licence adds 10 slots, up to the tier’s maximum, and Oracle prices it by quote. On a Standard account, a 3PL integration and a CRM sync can leave the store with three slots. When every slot is busy, NetSuite refuses the next request, and an integration that doesn’t queue and retry drops it.

Try your own account. Requests per order and seconds per request are examples; time a few of your own orders to replace them.

SuiteCommerce: two limits to know

SuiteCommerce runs on NetSuite’s own data, so there’s no sync to fail. Two documented limits matter for wholesalers:

• Long orders. Oracle describes a “soft limit of 100 unique items” in the cart, and says that above it there’s “no guarantee the order will go through”.^[7] Distributors’ replenishment orders often run past 100 lines.
• Upgrades on Advanced. SuiteCommerce Advanced is an unmanaged bundle, so unlike SuiteCommerce it doesn’t update itself; your partner upgrades it.^[8] Budget for that work every year.

The end of SOAP integrations

Oracle is retiring NetSuite’s SOAP web services. 2025.2 is the last SOAP endpoint, new integrations should use REST from 2026.1, and all SOAP integrations stop working at release 2028.2.^[9] Many older connectors and custom integrations still use SOAP. Ask any vendor, connector or agency which NetSuite API their integration uses, and when it moves to REST.

What each route costs over three years

Using published figures, excluding GST and before payment fees:

In a planning model we published for NetSuite businesses, a custom NetSuite portal came to about A$183,000 over five years against A$400,000 or more for SuiteCommerce Advanced.^[11] The pattern holds across every route: the licences, not the build, decide the long-run cost.

Which route suits which business

• Shopify Plus with Oracle’s connector suits retailers already selling to consumers on Shopify that add a few trade customers on price-level pricing.
• Shopify Plus with Celigo suits businesses that need custom flows and have someone to own them.
• SuiteCommerce suits businesses committed to NetSuite for the long term, with shorter orders and a partner on hand.
• A native B2B platform suits wholesalers whose revenue is mostly trade, with customer and contract pricing in NetSuite, long orders and buyers who pay on account.

TierCommerce’s NetSuite integration brings items, stock by location, customers, price levels, quantity pricing and item-specific prices into the store, and sends sales orders and payments back over SuiteTalk REST, batched and queued around NetSuite’s governance limits. See TierCommerce for NetSuite or compare TierCommerce and SuiteCommerce. To see a working store, book a demo.

Questions to ask any NetSuite route

1. Does it sync customer-specific item prices, or only price levels? Per company, or per location too?
2. How many concurrency slots will it use at our busiest hour, and how does it queue when they’re full?
3. Does it use SOAP anywhere? When does it move to REST?
4. What happens to an order with 300 lines?
5. How far back can it apply online payments to invoices?
6. What does it cost over three years, including upgrades?