Integration combo
Magento to NetSuite integration
Magento (Adobe Commerce) is a serious enterprise storefront with a lot of moving parts: stores, websites, customer groups, attribute sets. Connecting it to NetSuite without breaking the catalogue or the accounting takes care. We design, build and support the Magento-to-NetSuite integration as a Patchworks Partner Agency, moving orders and customers into NetSuite as the system of record and lifting inventory, pricing, tax and fulfilment back into Magento as one connected estate.
Flow shape
Order sync: Magento to NetSuite
How a Magento order lands as a NetSuite Sales Order with store-view attribution, customer-group pricing and subsidiary routing in place from the first run.
- Trigger Magento Order placed sales_order webhook
- Extract Patchworks Fetch detail items, addresses, attributes
- Transform Patchworks Map store view channel, currency, subsidiary
- Decision Patchworks Customer exists? NetSuite lookup by email / group
- Transform Patchworks Enrich line items configurable / bundle expansion
- Action NetSuite Create Sales Order via SuiteTalk / RESTlet
- Writeback Magento Update order NetSuite reference, status
Illustrative only. The diagram above shows how an integration of this shape works in concept. It is not a screenshot or export of the actual Patchworks process flow; the production flow has more nodes, more branches and more error handling than a marketing page can usefully render.
What we sync
7 synchronisations between Magento and NetSuite.
Only the data flows that both platforms actually support. Each section below describes what’s in scope, the gotchas we watch for, and how the flow is shaped inside Patchworks.
- 01
Order sync
Magento NetSuite
Orders raised in Magento flow into NetSuite on creation, status change and edit. The flow normalises Magento's order schema into the record shape NetSuite expects, including line-level discounts, taxes, gift cards, shipping methods and multi-currency. Partial cancellations and post-capture edits are handled with idempotent updates so NetSuite stays the system of record without double-counting. Edge cases that come up most often on this pair: backorders, pre-orders, subscription rebills and orders placed through guest checkout with no matching customer record on the destination side.
- 02
Inventory sync
NetSuite Magento
Stock levels in NetSuite push to Magento on a schedule, on movement events, or both. The flow handles multi-location and multi-warehouse split, safety stock buffers, in-transit and committed quantities, and channel-specific availability rules. Where Magento has its own location model we map NetSuite's locations onto it explicitly rather than relying on default behaviour. Throttling protects both sides during bulk recalculations; deltas only during normal operation. The goal is one source of truth for sellable inventory across the estate, with NetSuite retaining authority.
- 03
Product sync
NetSuite Magento
Product master data syncs from NetSuite to Magento on publish, with channel-aware enrichment so Magento only receives the attributes it can act on. Variants, option sets, media, locale-specific copy, category mappings and metafield or extension data are handled explicitly. New SKUs flow in; deprecated SKUs are flagged rather than hard-deleted so historical orders stay intact. Where Magento has channel-specific requirements that NetSuite does not natively model (typing rules, required attributes, image dimensions), the integration enforces them at the boundary rather than asking the merchandising team to.
- 04
Pricing sync
NetSuite Magento
Price lists in NetSuite push to Magento with currency, tax-class and customer-group awareness intact. Promotional pricing, contract pricing and tiered B2B pricing are handled as first-class concepts rather than overrides applied at the storefront. Where NetSuite runs effective-dated pricing, the flow coordinates the cutover so Magento's catalogue switches at the same instant as the finance side rather than drifting by hours. Currency rounding and display-tax rules are reconciled at the integration boundary to avoid the classic 1p / 1c off-by-one that haunts multi-currency rollouts.
- 05
Customer sync
Magento NetSuite
Customers created or updated in Magento flow into NetSuite with a stable cross-system identifier so the same shopper isn't fragmented into duplicates across the estate. Addresses, marketing preferences, B2B account hierarchies, tax exemption flags and channel attribution are mapped explicitly rather than left to NetSuite's defaults. Where NetSuite is the customer system of record (CRM or ERP) we publish back into Magento so storefront personalisation and segmentation reflect the canonical state. GDPR deletion and rectification are propagated across the integration in both directions.
- 06
Refund sync
NetSuite Magento
Refund decisions raised in NetSuite push into Magento as the financial event they are, with original payment method, partial-versus-full handling, tax recalculation and currency intact. The flow waits on inspection outcome where the merchant policy requires it rather than firing on RMA creation. Refunds against gift cards, multi-tender orders and marketplace orders (where the marketplace owns the refund execution) each take a different path; the integration picks the right one based on the original order's tender mix rather than a single default rule.
- 07
Tax sync
NetSuite Magento
Tax codes, tax classes and jurisdiction rules in NetSuite push to Magento so the storefront or marketplace charges what finance will actually post. VAT groups, reverse-charge B2B handling, marketplace-of-record tax (where the channel collects on the seller's behalf) and US sales-tax nexus are each modelled explicitly. The integration validates that Magento's tax calculation matches NetSuite's before publishing a price; mismatches are flagged loudly rather than left to surface at month-end on a VAT return.
Typical delivery
8 to 12 weeks for a standard delivery.
Up to 5× faster using PatchBuddy- Weeks 1 to 2 Discovery: Magento store hierarchy, attribute sets, customer groups, NetSuite record-type mapping.
- Weeks 3 to 6 Build: order, customer, inventory, pricing, tax and fulfilment flows in Patchworks.
- Weeks 7 to 8 Integration testing against NetSuite sandbox and a staged Magento store.
- Weeks 9 to 10 UAT with operations and finance; sign-off on configurable products and customer-group edge cases.
- Weeks 11 to 12 Cutover and hyper-care; transition into support retainer with monitoring and SLA.
Patchworks delivery
How Patchworks shapes Magento to NetSuite.
Magento's website / store / view hierarchy doesn't map one-to-one onto NetSuite's subsidiary / channel model, and integrations that skip that translation tend to ship correctly only for the first merchant they're built for. We build the Magento-to-NetSuite flows in Patchworks with explicit mapping between Magento store views and NetSuite channels, attribute sets and item records, and customer groups and price lists. The runbook covers the edge cases each merchant's catalogue surfaces.
Got more connectors that need to live in this flow? A 3PL, a marketplace, returns, a PIM, anything. We can do it. Most live integrations end up larger than a pair, all built and supported as one estate. More on multi-platform estates →
Our Patchworks practiceQuestions
Common questions.
-
01 Does the integration support Magento configurable and bundle products?
Yes. Configurable products are expanded into their underlying simple SKUs on the way into NetSuite so item ledger and inventory stay accurate. Bundle pricing is preserved at the order level for revenue recognition. -
02 How are Magento store views mapped to NetSuite?
Each store view maps explicitly to a NetSuite channel (and subsidiary, where OneWorld is in play). We agree the mapping during scoping rather than relying on defaults, so multi-market operations land in the right place from day one. -
03 Can customer-group pricing be driven from NetSuite?
Yes. NetSuite can be the source of truth for customer-group pricing, with the integration publishing into Magento price-list structures. The inverse pattern (Magento-native pricing) is also supported where it fits the operation. -
04 What about Magento B2B features?
Company accounts, requisition lists, quotes and shared catalogues are supported. Where you use Adobe Commerce B2B features they map onto NetSuite customer hierarchies and contact records via the same flows that handle B2C orders. -
05 Do you support Magento-to-NetSuite under SLA after go-live?
Yes. The same team that builds the integration runs it under retainer. Monitoring on every shipped flow, on-call cover, monthly health checks and tiered response SLAs from £750/month.
Get in touch
Tell us what you’re trying to connect.
And what’s in the way. We will tell you whether we are the right people to do it. Drop us a line below, or open the chat in the corner of the screen.
Direct: contact@ecirql.com
Message sent
Thanks. We’ll be in touch.
Your message is in our inbox. A human will read it and reply within a working day. For anything urgent, drop us a line at contact@ecirql.com or open the chat in the corner of the screen.