Integration combo
NetSuite to Amazon Seller Central integration
Selling on Amazon is half the work. Reconciling Amazon back into the ERP without losing the trail is the other half. Our NetSuite to Amazon Seller Central integration runs the listings, the inventory, the order ingest and the settlement reconciliation as one connected flow, so the finance team sees Amazon revenue land in the right GL accounts and the operations team sees Amazon orders alongside the rest of the channel mix. We deliver and support the integration as a certified Patchworks Partner Agency.
Flow shape
Order ingest: Amazon Seller Central to NetSuite
How an Amazon order lands as a NetSuite Sales Order with the marketplace-of-record tax treatment, channel attribution and settlement linkage in place from the first run.
- Trigger Amazon Order notification MWS / SP-API polling
- Extract Patchworks Fetch order detail items, address, fees
- Transform Patchworks Apply MoR tax rule marketplace-of-record VAT / sales tax
- Decision Patchworks FBA or seller-fulfilled? routes to different downstream flows
- Transform Patchworks Map to NetSuite SO channel = Amazon, attribution fields
- Action NetSuite Create Sales Order linked to channel and subsidiary
- Writeback Amazon Acknowledge ready-to-ship / dispatch SLA clock
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 Amazon Seller Central.
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
Amazon Seller Central NetSuite
Orders raised in Amazon Seller Central flow into NetSuite on creation, status change and edit. The flow normalises Amazon Seller Central'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 Amazon Seller Central
Stock levels in NetSuite push to Amazon Seller Central 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 Amazon Seller Central 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 Amazon Seller Central
Product master data syncs from NetSuite to Amazon Seller Central on publish, with channel-aware enrichment so Amazon Seller Central 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 Amazon Seller Central 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 Amazon Seller Central
Price lists in NetSuite push to Amazon Seller Central 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 Amazon Seller Central'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
Amazon Seller Central NetSuite
Marketplace settlement reports from Amazon Seller Central 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 (UK / EU / US), FBA vs seller-fulfilled mix, tax-of-record handling.
- Weeks 2 to 4 Build: listing, inventory, order, fulfilment and settlement flows in Patchworks.
- Weeks 5 to 6 Integration testing against the Amazon sandbox and NetSuite, including settlement reconciliation.
- Week 7 UAT with operations and finance; sign-off on FBA edge cases and chargeback handling.
- Week 8 Cutover and hyper-care; transition into support retainer with monitoring and SLA.
Patchworks delivery
How Patchworks shapes NetSuite to Amazon Seller Central.
Amazon's seller APIs change often and rarely warn you. The Patchworks connector abstracts the moving parts so the merchant-side flows stay stable when Amazon shifts a schema or deprecates an endpoint. We build NetSuite-to-Amazon delivery directly in Patchworks: product publication, inventory sync per marketplace, order ingest, fulfilment writeback for on-time-dispatch SLA, and settlement reports reconciled line by line against NetSuite transactions and item-fulfilment records.
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 Amazon marketplaces?
Yes. Each marketplace (Amazon.co.uk, Amazon.de, Amazon.com, and so on) maps to its own NetSuite channel and subsidiary where appropriate. Listings, inventory and orders are scoped per marketplace, with shared product master data where it makes sense. -
02 How does settlement reconciliation work?
Amazon settlement reports import line by line. Each line matches to the underlying NetSuite transaction (order, refund, adjustment, fee) or surfaces as an unmatched item for finance review. Nothing is silently dropped, and the GL impact is itemised rather than lumped into a single 'marketplace fees' bucket. -
03 Do you support FBA inventory?
Yes. FBA inventory is modelled as a distinct NetSuite location with its own availability rules. Sellable inventory at FBA is published back to Amazon listings; movement between FBA and merchant locations is logged so the operations team sees the full stock picture. -
04 What happens when Amazon updates the SP-API?
The Patchworks connector absorbs most schema and endpoint changes without the merchant-side flows needing rework. Where a change is structural, the support retainer covers the upgrade work within the same agreement rather than as a separate procurement. -
05 Do you support NetSuite-to-Amazon 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.