Amazon ↔ NetSuite. settled to the cent.
We connect Seller Central, FBA and Vendor Central to NetSuite through Amazon's SP-API. Orders and refunds post as transactions, FBA stock lands on its own inventory location, and every settlement report is broken into sales, fees, reimbursements and advertising so the deposit reconciles exactly.
Design targets we build and monitor against — not averaged client results.
Amazon is a channel, a warehouse and a bank. Most integrations only handle the first.
Amazon doesn't pay you per order — it pays you per settlement. If your ERP doesn't understand that, your revenue never ties out.
What moves, and which way.
Every flow below is scoped in the mapping workshop — you switch on the ones you need and leave the rest. Direction is a decision, not a default.
| Record | Direction | Trigger | Latency | How we handle it |
|---|---|---|---|---|
| Seller Central orders (FBM) | Amazon → NetSuite | SP-API Orders polling / notifications | 5–15 min | Creates NetSuite Sales Orders per marketplace, with buyer PII retrieved through a restricted data token only where it's needed to ship. |
| FBA orders & shipments | Amazon → NetSuite | Order + shipment events | 5–15 min | FBA orders post and auto-fulfill from the FBA location, so revenue recognition and inventory relief happen without a human touching them. |
| FBA inventory | Amazon ↔ NetSuite | Scheduled inventory & ledger reports | Hourly or daily | Fulfillable, reserved, inbound and unfulfillable quantities mapped to NetSuite locations, with adjustments for discrepancies. |
| Inbound shipments | NetSuite → Amazon | Transfer Order in NetSuite | On approval | Replenishment to FBA raised as a NetSuite transfer order and tracked against the Amazon inbound shipment plan until receipt. |
| Settlements & fees | Amazon → NetSuite | Settlement report available | Per settlement period | Sales, refunds, referral fees, FBA fees, storage, advertising, reimbursements and adjustments split into GL lines that sum to the deposit. |
| Refunds & returns | Amazon → NetSuite | Refund event / returns report | Near real-time | Credit Memos with the fee reversal detail, plus restock to the correct location for sellable returns. |
| Listings & pricing | NetSuite → Amazon | Item or price change in NetSuite | Scheduled | Item master, price and quantity pushed through the Listings and Feeds APIs so NetSuite stays the source of truth. |
| Vendor Central EDI | Amazon ↔ NetSuite | 850 PO received | Per document | Purchase orders become Sales Orders; ASNs and invoices flow back. Chargebacks and shortages tracked against the original PO. |
The detail that decides it.
A sample of the mapping we agree before building. The real document covers every field on every record — and it's yours whether or not you continue with the build.
| Amazon field | NetSuite target | Rule |
|---|---|---|
| AmazonOrderId | Sales Order → custbody_amazon_order_id | Idempotency key across every marketplace. |
| MarketplaceId | Subsidiary / location / currency | Each marketplace routes to the right entity, price list and tax registration. |
| OrderItem.SellerSKU | Item internal ID | SKU and ASIN cross-reference maintained in NetSuite, not in a spreadsheet. |
| ItemPrice / ItemTax / Promotion | Rate, tax detail and discount lines | Tax collected by Amazon as marketplace facilitator is booked as pass-through, not as your liability. |
| Settlement transaction types | Fee, refund and reimbursement GL accounts | Every Amazon transaction type maps to an account you choose — new types raise an exception rather than silently posting. |
| FulfillmentChannel (AFN/MFN) | Fulfillment location | Separates FBA and merchant-fulfilled stock so availability and COGS stay correct. |
| Shipment tracking | Item Fulfillment | Carrier and tracking written back for MFN orders so support can answer 'where is it'. |
| Reimbursement ID | Other income / inventory adjustment | Lost and damaged reimbursements reconciled against the inventory they relate to. |
Built to be trusted.
Seller Central, FBA and Vendor Central wired into NetSuite — orders, FBA inventory, settlements and chargebacks.
Multi-marketplace order sync
One pipeline covering every marketplace you sell in, each routed to the right subsidiary, currency and tax treatment.
Settlement reconciliation engine
Settlement reports decomposed into GL postings that sum to the deposit — with a variance report when they don't.
FBA inventory truth
Fulfillable, reserved, inbound and unfulfillable quantities mapped to NetSuite locations, reconciled against the inventory ledger.
Fee-aware profitability
Referral, FBA, storage and advertising costs attached to the SKU that incurred them, so channel margin is a report, not a project.
Vendor Central support
EDI 850 / 856 / 810 flows into NetSuite with chargeback and shortage tracking against the original PO.
Rate-limit resilient
SP-API quotas respected with backoff and report polling, so a throttled call never turns into a missing order.
APIs we build on.
No screen scraping, no CSV drops on an FTP server at 3am. First-party APIs, authenticated properly, rate-limit aware.
The 20% that breaks connectors.
We scope these explicitly rather than discovering them in production. If one applies to you, say so on the call.
- Commingled inventory and stranded / unfulfillable stock
- Removal orders, disposals and reimbursement matching
- Multi-Channel Fulfillment shipping your Shopify orders from FBA
- Marketplace-facilitator tax across US states and EU VAT
- Settlement periods that straddle month end
- A-to-Z claims, SAFE-T reimbursements and chargebacks
- Fee schedule changes that introduce new transaction types
- Buyer PII handling and data-retention rules under Amazon's policies
- Vendor Central shortages, price claims and compliance chargebacks
- Currency conversion and Amazon Currency Converter deposits
How we ship it.
5–9 weeks typical for the core flows, including a parallel run. Nothing goes live until both systems agree on the same numbers.
Channel & finance audit
We review your marketplaces, fulfillment mix and last two settlement periods, and agree how every Amazon transaction type should post.
Sandbox build
Built against a NetSuite sandbox with real historical reports replayed through it, so reconciliation is proven before go-live.
Backfill & tie-out
We backfill a defined history and reconcile it against your books until the variance is explained to the cent.
Cutover & hypercare
Go live with alerting on missing orders, failed reports and unmapped fee types, plus two weeks of hypercare.
Yours when we leave.
Source code, infrastructure, documentation and training. You can run, extend or replace this without calling us.
Amazon ↔ NetSuite
Fixed-scope build, quoted after the mapping workshop. Typically 5–9 weeks typical for the core flows.
Reply within 1 business day · No commitment
The fine print.
Still deciding between building and buying? Book a 30-minute call — we'll tell you which one you are, including when the answer is “keep your connector”.
Do you post every Amazon order individually, or summarize?
Either. High-volume sellers usually post summarized daily revenue with SKU detail and keep individual orders only where fulfillment needs them. Others want a Sales Order per order for support and returns. We pick with your controller, because it changes how the close works.
Can you make Amazon and Shopify share one inventory pool?
Yes — that's the common ask. NetSuite becomes the allocator, with per-channel buffers and rules for who gets the last unit. We often build the Shopify and Amazon connections together for exactly this reason.
How do you handle marketplace-facilitator tax?
Tax Amazon collects and remits is booked as pass-through and excluded from your own liability, with the jurisdiction detail retained for audit. Getting this wrong is one of the most expensive integration mistakes we're asked to remediate.
We already use a connector for Amazon. Can you just fix the settlements?
Yes. Settlement reconciliation is the flow prebuilt connectors most often leave partial, and it can be built as a standalone module alongside whatever is already running.
Does this cover Vendor Central as well as Seller Central?
Yes. Vendor Central runs on EDI rather than SP-API, so it's a separate workstream — 850 purchase orders in, 856 ASNs and 810 invoices out, with chargeback tracking. We work with your existing VAN or recommend one.
How long does it take?
Orders, inventory and settlements for a single marketplace typically run 5–9 weeks. Extra marketplaces are mostly configuration; Vendor Central EDI adds a workstream.
Pairs well with.
Most clients wire two or three systems at once — it's cheaper than doing them one at a time, and the mapping work overlaps.
Ready to build a store that actually converts?
Book a free 30-minute strategy call and discover how we can transform your Shopify store.