Integration

Magento to
NetSuite

Multi-store Magento rarely maps cleanly onto an ERP. Store views, customer groups, configurable products and per-market tax all have to land somewhere specific in NetSuite. Supply Lens decides that at the mapping layer rather than leaving it to a default.

Talk to the team NetSuite overview →

2-4weeks

Typical time to live

5min

Sync frequency

99.9%

Uptime SLA

Supply Lens live flow monitor Live

Magento order 300114982 received Store view: uk_en · trade group · €214.00 ORDER IN

Configurable products resolved 3 child SKUs matched · group price applied · tax €35.67 PROCESSING

NetSuite SO-11420 created EU subsidiary · EUR · Rotterdam location CREATED

Shipment created in Magento DPD 05481923771 · customer notified SHIPPED

Stock pushed per store view uk_en: 64 · nl_nl: 64 · de_de: 0 (not stocked) STOCK SYNC

Core capabilities

Everything the flow needs.
Nothing it doesn't.

Supply Lens handles the complete order to fulfilment loop between Magento and NetSuite, including the Magento structures that have no direct equivalent on the ERP side.

Magento orders create NetSuite sales orders against the right subsidiary
Store views and websites mapped to subsidiary, currency and location
Configurable and bundle products resolved to the SKUs NetSuite holds
Customer groups mapped to NetSuite categories and price levels
Guest and registered checkout handled with different customer rules
Stock pushed back per store view, not as one global figure
Magento shipments created from NetSuite item fulfilment, with tracking
Magento credit memos mirrored as NetSuite credit memos

Integration flow summary

Magento order placed

Order state and status trigger

TRIGGER

Supply Lens resolves it

Store view, group price, child SKUs, tax

TRANSFORM

NetSuite sales order

Right subsidiary and currency

CREATE

Shipment to Magento

Created with tracking, customer notified

SYNC

Stock per store view

Source selection respected

ONGOING

Optional flows

Switch on what you need.

Beyond the core order flow, Supply Lens can activate additional sync layers depending on how your Magento estate is set up.

Product & attribute sync

Push items from NetSuite into Magento, including attribute sets and the parent to child structure configurable products need.

Multi-source inventory

Magento MSI sources mapped to NetSuite locations, so availability reflects the warehouse that actually serves each store view.

Credit memos & returns

Magento credit memos and RMAs mirrored into NetSuite against the original order, with part refunds handled as part refunds.

Customer group pricing

Magento customer groups and tier prices driven from NetSuite price levels, so trade and retail see the right numbers.

Part invoicing

Magento part invoices reconciled against NetSuite billing, so an order invoiced in two goes does not post twice.

Manual sync mode

Trigger syncs by hand as well as automatically, which helps during replatforming, testing or high value order review.

Configuration

Set up your rules, not ours.

Magento's website, store and store view hierarchy has no direct equivalent in NetSuite, so the mapping has to be designed rather than assumed. These are the settings you control.

Order trigger rules

Magento separates order state from status. Choose which combination triggers import, and whether pending payment orders wait or post immediately.

Store view to subsidiary mapping

Each website or store view routed to a NetSuite subsidiary, currency and location. Set once, then every order from that view lands correctly.

Product structure resolution

Decide whether a configurable parent or its child SKU posts to NetSuite, and how bundle and grouped products expand. Unmapped items go to an exception queue.

Customer groups and tax classes

Magento customer groups and product tax classes mapped to NetSuite categories, price levels and tax codes, per market.

Store view mapping example

Magento store view NetSuite subsidiary

uk_en→UK Ltd · GBP

nl_nl→EU BV · EUR

de_de→EU BV · EUR

trade_uk→UK Ltd · trade price level

Order import

State: processing

Stock sync

Every 5 minutes, per source

Shipment push

On item fulfilment

Product sync

Not enabled

OFF

Configurable products

Post child SKU

CONFIG

Subsidiary routing

By store view

CONFIG

Edge cases handled

The messy bits are covered.

Magento estates accumulate structure over years. These are the four we are asked about most, in the words customers use.

"The configurable parent SKU went to NetSuite instead of the variant."

Which level posts is a setting rather than a guess. Configurable parents, children, bundles and grouped products each have an explicit rule, so the ERP receives the SKU it actually stocks.

"Every store view posted into one subsidiary and the currencies were wrong."

Store views are mapped to subsidiary, currency and location before anything is written. A Dutch order lands in the EU entity in euros rather than converted into a UK catch-all.

"Trade customers were charged retail prices on the storefront."

Magento customer groups map to NetSuite price levels, so the group a customer belongs to decides what they pay and both systems agree on the figure.

"Guest checkout created a new NetSuite customer every single time."

Guest and registered checkout get separate rules. Guests can be matched on email, posted to a channel account or created individually, whichever your finance team prefers.

What you'll need

Live in weeks, not quarters.

Supply Lens handles the technical setup. You provide access and confirm how your store views, products and customer groups map. Agreeing that is what takes the time, and it is worth doing properly.