ERP integration

Your ERP already runs the business.Now let it run the data.

Oracle NetSuite holds your finance, inventory and orders. Supply Lens connects it to your storefronts, marketplaces, warehouses and trading partners, so sales orders, purchase orders, invoices, stock and despatches move between them without anyone rekeying.

2-way
Sync
Hub
Every channel
99.9%
Uptime
NetSuite
Shopify
Magento
Retailer EDI
Marketplaces
Mintsoft
3PL & carriers
Xero
Peppol
Into NetSuite Out of NetSuite
Core capabilities

One hub. Every channel. In sync.

Supply Lens sits around NetSuite, moving orders in from your channels and pushing stock, invoices and despatches back out, so your ERP and everything connected to it stay aligned.

  • Sales orders from every channel created in NetSuite automatically
  • Purchase orders synced between NetSuite and your suppliers
  • Stock levels kept in step across storefronts and warehouses
  • Invoices and credit notes raised and shared
  • Despatch confirmations and tracking flowed back to each channel
  • Customer and product records matched across systems
  • Multi-company and multi-currency setups supported
Supply Lens to NetSuite: live flow Live
Order lands from your storefront
Shopify order · 3 items · £84.00
ORDER IN
Validated and mapped
SKUs, tax codes and customer matched
PROCESSING
Sales order created in NetSuite
Posted against the right subsidiary, ready to fulfil
CREATED
Despatched and invoiced
Tracking recorded, invoice raised
DESPATCHED
Everything in step
Stock, invoice and status updated across systems
SYNCED
NetSuite as the hub

Inbound from commerce.
Outbound to fulfilment and finance.

NetSuite is where the numbers should be true. Everything either feeds it or reads from it, and the integration's job is to keep that direction of travel clear rather than letting two systems both think they are in charge.

Into NetSuite
  • Sales orders from storefronts and marketplaces, with the customer matched to the right record rather than created again
  • Retailer purchase orders arriving as orders your team can pick, with the buyer's own reference carried through
  • Goods receipts from the warehouse against the purchase order that raised them
  • Stock adjustments and counts from the systems that physically hold the inventory
  • Payments and settlement from the channels that collect the money
Out of NetSuite
  • Fulfilment instructions to your warehouse or 3PL, with the right location and shipping method
  • Stock levels back to every sales channel, so you are not selling what you do not have
  • Despatch confirmations and tracking to customers and to retailer trading partners
  • Invoices to your finance stack, and to the network where a buyer expects e-invoicing
  • Product and pricing updates out to the channels that list them
Edge cases handled

ERP integrations break on detail.

Tax codes, multi-company setups and mismatched records are where most connections fall over. These are the four we hear about most, in the words customers use.

"Orders posted to the wrong company in our NetSuite setup."

Each channel is mapped to the right company, dimension and location at the Supply Lens layer, so every order lands in the correct place rather than a catch-all account.

"Tax was wrong on marketplace orders and our VAT return didn't add up."

Tax codes are resolved per channel and per market before the order is posted, so VAT is right on the way in rather than corrected by hand later.

"A SKU on the storefront didn't exist in NetSuite."

Unmatched items are caught before posting. The order goes to an exception queue with a clear note, so nothing is guessed at or created by accident.

"Stock updated in two places at once and the numbers fought each other."

NetSuite is treated as the system of record for the fields you choose, so there is one source of truth and updates never overwrite each other.

What you'll need

Live in weeks, not quarters.

Supply Lens handles the connection and the mapping. You provide access to NetSuite and confirm how your channels, companies and products map. Agreeing that is what takes the time, and it is worth doing properly.

  • NetSuite API access and environment details
  • The channels and systems you want connected
  • Company, dimension and location structure
  • Product and SKU list to map against
  • Tax code and pricing rules per channel
  • Which fields NetSuite owns as the record
1
Scope
API access, company structure and channels confirmed.
2
Configure
Mapping, tax rules and sync direction built in staging.
3
Test
Orders posted end to end, stock and invoices checked.
Go live
Enabled channel by channel, with monitoring active from the first order.

Ready to make NetSuite the hub it's built to be?

Tell us which systems you are running and what is still being done by hand. Twenty minutes is usually enough to size it.