Integration combo
NetSuite to Mirakl integration
Mirakl powers a large share of the marketplaces UK and EU retailers sell into, and a growing share of the marketplaces they operate themselves. Connecting NetSuite to Mirakl carries the listings, the inventory, the orders and the settlements as one connected flow, so finance and operations see Mirakl revenue land in the right places without the reconciliation tax. We design, build and support the integration as a certified Patchworks Partner Agency.
Flow shape
Order ingest: Mirakl to NetSuite
How a Mirakl marketplace order lands as a NetSuite Sales Order with channel attribution, settlement linkage and SLA awareness from the first run.
- Trigger Mirakl Order notification Mirakl operator API poll
- Extract Patchworks Fetch detail items, address, commission
- Transform Patchworks Resolve channel operator, currency, tax rule
- Transform Patchworks Map to NetSuite SO channel = Mirakl operator
- Action NetSuite Create Sales Order with attribution fields
- Writeback Mirakl Acknowledge dispatch SLA clock starts
- Action Mirakl Send tracking on fulfilment, with carrier data
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
5 synchronisations between NetSuite and Mirakl.
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
Mirakl NetSuite
Orders raised in Mirakl flow into NetSuite on creation, status change and edit. The flow normalises Mirakl'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 Mirakl
Stock levels in NetSuite push to Mirakl 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 Mirakl 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 Mirakl
Product master data syncs from NetSuite to Mirakl on publish, with channel-aware enrichment so Mirakl 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 Mirakl 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 Mirakl
Price lists in NetSuite push to Mirakl 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 Mirakl'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
Settlement reconciliation
Mirakl NetSuite
Marketplace settlement reports from Mirakl reconcile against the order, refund and fee records on the NetSuite side. Each line in the settlement is matched to the underlying transaction or surfaced as an unmatched item for finance review; nothing is silently dropped. Marketplace-specific concepts (chargebacks, A-to-Z claims, FBA reimbursements, listing fees, referral fees) get their own GL account mapping rather than being lumped into a single 'marketplace fees' bucket. Period close becomes tractable instead of a week of spreadsheet detective work.
Typical delivery
5 to 8 weeks for a standard delivery.
Up to 5× faster using PatchBuddy- Week 1 Discovery: marketplace scope, category mapping, attribute requirements, SLA tier per operator.
- Weeks 2 to 4 Build: listing, inventory, order, fulfilment and settlement flows in Patchworks.
- Weeks 5 to 6 Integration testing against the Mirakl sandbox per operator, including settlement reconciliation.
- Week 7 UAT with operations and finance; sign-off on SLA handling and commission reporting.
- Week 8 Cutover and hyper-care; transition into support retainer with monitoring and SLA.
Patchworks delivery
How Patchworks shapes NetSuite to Mirakl.
Mirakl's operator API is consistent, but every marketplace running on it has its own category taxonomy, attribute requirements and service-level rules. We build the NetSuite-to-Mirakl flows in Patchworks with marketplace-specific category mapping and attribute enforcement at the boundary, plus settlement reconciliation that matches each line in the Mirakl report against a NetSuite transaction. The result is a multi-marketplace operation that doesn't drown finance at period close.
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 Can the integration handle multiple Mirakl operators?
Yes. Each operator maps to its own NetSuite channel and, where required, its own subsidiary. Listings, inventory and orders are scoped per operator, with shared product master data where it makes sense. -
02 How does settlement and commission reporting work?
Mirakl settlement reports import line by line. Commission, refunds, adjustments and fees each get their own GL mapping. Each line matches to the underlying NetSuite transaction or surfaces as an unmatched item for finance review. -
03 What about Mirakl's strict dispatch SLAs?
Fulfilment writeback is engineered around the operator's SLA. Carrier, service level and tracking number arrive on the same dispatch event so the SLA clock stops cleanly. Late shipments are flagged via monitoring before the operator does. -
04 How are category-specific attributes handled?
Each operator's category attributes are enforced at the integration boundary using a per-operator schema. Where the merchant's NetSuite item data is missing a required attribute, the listing flow blocks rather than publishing a non-compliant SKU. -
05 Do you support NetSuite-to-Mirakl 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: [email protected]
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 [email protected] or open the chat in the corner of the screen.