API & ERP Integrations
Reliable connections between nopCommerce and your ERP, CRM, payment gateways, PIM and logistics providers.
Services
nopCommerce NetSuite Integration Services
We connect nopCommerce to Oracle NetSuite so items, prices, stock, customers and orders stay in step without re-keying. NetSuite stays the system of record, the store stays fast when NetSuite is busy, and every sync is logged and safe to re-run. We have built and run this integration for a B2B distributor on nopCommerce 4.80.
Where this helps
Situations that typically lead businesses to this kind of work.
- Web orders are typed into NetSuite by hand, and mistakes reach invoices and shipments.
- Stock on the storefront drifts from NetSuite locations, so customers order items that are out of stock.
- Trade customers have price levels and contract prices in NetSuite that the store cannot show.
- An older connector uses NetSuite SOAP web services, which stop working with NetSuite 2028.2.
Capabilities
What we deliver
Items and matrix items
Inventory items, matrix parents and children, and kits mapped to nopCommerce products, variants and attribute combinations by SKU.
Prices and price levels
Base price, price levels, quantity pricing and customer-specific item prices shown to the right customers in the store.
Stock by location
Available quantities from the NetSuite locations you choose, per warehouse in nopCommerce, with live checks at checkout if needed.
Customers and addresses
Customers, contacts and ship-to addresses kept in step, created in NetSuite only when there is an order or an approval.
Orders, quotes and fulfilment
Web orders sent as sales orders, cash sales or estimates, then item fulfilments and tracking numbers sent back to the customer.
Monitoring and retries
A queue with retries, so an order reaches NetSuite once, and an admin log that shows what failed and why.
For the technical detail on record ownership, B2B pricing, quote exports and retries, read our nopCommerce NetSuite integration guide.
See it in production: a B2B trade portal on nopCommerce, integrated with NetSuite, with contract pricing, live stock and quote export.
Options
Is there a NetSuite connector for nopCommerce?
Not an off-the-shelf one. The nopCommerce marketplace lists NetSuite as an integration that is not developed yet and refers store owners to solution partners. The large integration platforms that sell NetSuite connectors for other shopping carts do not offer one for nopCommerce either.
That leaves two realistic routes: a general integration platform with custom work on both ends, or an integration built as nopCommerce plugins that talk to NetSuite directly. We build the second. It runs inside your store, follows nopCommerce’s own events and services, and has no per-order fees.
- Plugins in your nopCommerce store, not a separate middleware subscription
- You own the source code and the documentation
- Works with nopCommerce 4.50 to 5.00 on SQL Server, MySQL or PostgreSQL
- Single-subsidiary and OneWorld accounts, with subsidiary and location rules per store
Data
What a nopCommerce NetSuite integration synchronises
Most projects start with the catalog flowing from NetSuite to the store and orders flowing back. Each record type gets its own schedule: stock changes often, so it syncs more often than product descriptions, and prices can be checked live for logged-in trade customers.
NetSuite usually owns item data, prices, stock and customer terms. The store usually owns web content such as descriptions, pictures and SEO fields. We write this down field by field before building, so nobody’s changes are overwritten by surprise.
- NetSuite to nopCommerce: items, matrix items, price levels, quantity pricing, customer item prices, stock by location, promotions
- nopCommerce to NetSuite: customers, contacts and addresses, sales orders, cash sales or estimates, payment details
- NetSuite to nopCommerce: order status, item fulfilments, tracking numbers, invoice status
- Optional: customer-specific catalogs, credit limits and terms for B2B accounts
How it connects
SuiteTalk REST, OAuth 2.0 and the end of SOAP web services
Oracle recommends SuiteTalk REST web services with OAuth 2.0 for new NetSuite integrations. 2025.2 is the last planned SOAP endpoint, and with the 2028.2 release SOAP web services will no longer be available, so SOAP-based integrations will stop working. We build on REST, use SuiteQL for fast bulk reads, and add a RESTlet only when a single call has to do work that REST records cannot.
If your store already has a NetSuite connector built on SOAP, plan the move now rather than in 2028. We can replace it in stages, record type by record type, while the old connector keeps running.
Weighing the API options on the nopCommerce side as well? See nopCommerce Web API and REST API options.
- SuiteTalk REST web services for records, with OAuth 2.0 machine-to-machine authentication
- SuiteQL queries for incremental reads of items, prices and stock
- RESTlets or SuiteScript only where a custom NetSuite endpoint is genuinely needed
- Signed webhooks from NetSuite (user event scripts or workflows) when the store should hear about changes instantly
Reliability
Keeping the store fast within NetSuite’s concurrency limits
NetSuite limits how many web service and RESTlet requests an account can run at the same time. The limit is shared by every integration on the account and depends on your service tier and SuiteCloud Plus licences. A store that calls NetSuite during every page view or checkout will hit it at the worst moment.
So checkout never waits on NetSuite. Orders go into a queue in the store and are sent in the background, with retries and backoff. Catalog syncs read in batches and only what changed. When a live stock or price check is needed, it has a short timeout and a safe fallback.
- Orders queued and exported in the background, sent to NetSuite exactly once
- Incremental syncs by last-modified date instead of full reloads
- Retry with backoff when NetSuite reports the concurrency limit
- An admin page showing each sync run, each order export and the NetSuite error text
Effort
What determines the effort and cost
NetSuite accounts are rarely configured the same way twice: custom fields and records, subsidiaries, locations, tax setups and approval workflows all change what the integration has to do. After a short discovery against your account and store, we give a fixed scope and quote for a first phase, usually catalog, stock and order export, and plan the rest as later phases.
- Number of record types and directions to synchronise
- B2B pricing rules: price levels, contract prices, promotions and quantity breaks
- OneWorld subsidiaries, multiple locations and currencies
- Custom fields, custom records and SuiteScript already in your account
- Whether an existing connector has to be replaced while it keeps running
Approach
How we approach it
- 01
Map the records
We agree which NetSuite records and fields each side owns, how items and customers are matched, and what happens on a conflict.
- 02
Build against a sandbox
The integration is built and tested against your NetSuite sandbox, with separate settings for sandbox and production.
- 03
Launch with visibility
Catalog sync runs first, then orders. You get the admin log, alerts and a runbook for your team.
Platform
nopCommerce versions we support
We build for and support nopCommerce 4.50 to 5.00. Each release runs on a specific .NET version, which sets the hosting a store needs and how much work an upgrade involves.
Stores on 4.40 or later upgrade the database automatically when the new release first starts. Plugins and the theme still need builds for the target version.
Planning a move between versions? Read our nopCommerce upgrade guide.
| nopCommerce | .NET runtime | Notes |
|---|---|---|
| 4.50 | .NET 6 | |
| 4.60 | .NET 7 | |
| 4.70 | .NET 8 | |
| 4.80 | .NET 9 | |
| 4.90 | .NET 9 | Previous release line, latest patch 4.90.8 |
| 5.00 | .NET 10 | Current release, 27 October 2026 |
Checked against the nopCommerce source code and release notes on 27 October 2026. Sources: nopCommerce releases on GitHub, Official upgrade documentation.
Questions
NetSuite Integration FAQ
Something else on your mind? Ask us directly.
Is there a ready-made NetSuite connector for nopCommerce?
No. The nopCommerce marketplace lists NetSuite as not developed yet, and the main integration platforms do not offer a nopCommerce connector. We build the integration as nopCommerce plugins that connect to NetSuite directly, and you own the code.
Which NetSuite APIs do you use?
SuiteTalk REST web services with OAuth 2.0 for records, SuiteQL for bulk and incremental reads, and RESTlets only where a custom endpoint is needed. We do not build new integrations on SOAP web services, which NetSuite removes with the 2028.2 release.
Our current connector uses SOAP web services. What should we do?
Plan to replace it before NetSuite 2028.2, when SOAP web services stop working. We can move it to REST in stages, one record type at a time, while the existing connector keeps running, so there is no big-bang switch-over.
Will the store slow down if NetSuite is slow or unavailable?
No. Orders are queued in nopCommerce and sent in the background, so customers can keep ordering. Catalog and stock syncs run as scheduled tasks. Any live checks against NetSuite have short timeouts and fall back to the last synced values.
Can trade customers see their NetSuite prices in the store?
Yes. Price levels, quantity pricing and customer-specific item prices can be synchronised or checked live, so each logged-in customer sees the price NetSuite would charge them. Retail shoppers keep seeing the standard price.
Do you support NetSuite OneWorld?
Yes. Each nopCommerce store can be tied to a subsidiary, its locations and its currency, and customers and orders are created in the right subsidiary.
Do we need a NetSuite sandbox?
It is strongly recommended. We build and test against the sandbox, keep its settings separate from production, and only connect production after a full test run. Without a sandbox we can still work, but changes must be tested more carefully in production.
Which nopCommerce versions do you support?
nopCommerce 4.50 to 5.00. If the store is older, we will tell you whether upgrading first is the better investment, because the integration then only has to be built once.
Related
Often combined with
B2B eCommerce Solutions
Customer-specific pricing, company accounts, approval flows and quick ordering for trade customers.
Enterprise Commerce Integrations
Commerce architecture that connects nopCommerce to ERP, PIM, WMS, CRM and identity systems.
Ready to plan your nopCommerce project?
Tell us about your storefront, ordering workflows or integrations by email, phone or WhatsApp. An outline is enough to start.