Amazon Seller Central

NS90: Integrate:

Amazon Seller Central (FBA and FBM) and NetSuite

Amazon FBA and FBM in NetSuite, with every settlement reconciled line by line.

NS90: Integrate connects Amazon Seller Central to NetSuite through MHI's integration service on NSIP. FBM and FBA orders, shipment confirmations, listing prices, inventory availability and FBA adjustments sync on a schedule, and each settlement is reconciled in an Oracle data hub before posting as payments, refunds and one balanced journal.

Plan my Amazon integration

See supported flows

System

Amazon Seller Central: Fulfilled by Amazon (FBA) and Fulfilled by Merchant (FBM)

Direction

Both ways: orders, FBA activity and settlements in; price, availability and shipments out

API

Amazon Selling Partner API (Orders, Reports, Feeds)

Run mode

Scheduled: orders every 15 min, inventory daily, settlements each cycle

Platform

NSIP + NSAW

Delivered

13 delivered · 1 in progress

WHY NOW

2 years

Amazon's API only keeps two years of orders

Amazon's order API doesn't return orders older than two years, and its inventory ledger keeps 18 months of history. Once that window passes, the detail behind old settlements, fees and adjustments can't be pulled again. NS90: Integrate lands every order, settlement line and FBA adjustment in an Oracle data hub first, so the history stays in your own environment for reconciliation, audit and analytics, long after Amazon stops serving it.

Source: Amazon Selling Partner API, Orders API overview and FBA report type values (developer-docs.amazon), accessed 13 Oct 2026

// Supported flows

Amazon flows delivered on NS90: Integrate

Each solid dot is a client project where MHI built the flow on NSIP. Hollow markers are flows in progress. FBA orders post as invoices; FBM orders follow the full order-to-cash cycle. Arrows show direction relative to NetSuite.

Master data

Transactions

Financial & reconciliation

Master data

NETSUITE

Listing price

NetSuite item price level → Amazon listing offer price

30 min

FBM inventory availability

NetSuite available across merchant locations − safety stock → Amazon listings availability

Daily

Customers

Amazon buyer → NetSuite customer, or default marketplace customers (FBA and FBM)

With each order

Transactions

NETSUITE

FBM orders

Amazon Orders API (merchant-fulfilled) → NetSuite sales order

15 min

FBM shipment confirmation

NetSuite item fulfillment → Amazon shipment confirmation

30 min

FBA orders

Amazon Orders API (Amazon-fulfilled, shipped) → NetSuite invoice

15 min

FBA inventory adjustments

Amazon inventory ledger (adjustments) → NetSuite inventory adjustment

Daily

FBM cancellations

Amazon cancelled order → NetSuite close sales order

In progress

Financial & reconciliation

NETSUITE

Settlement payments

Amazon settlement report (V2 flat file) → NetSuite customer payments

Each settlement

Settlement refunds

Amazon settlement refund lines → NetSuite credit memo + customer refund

Each settlement

Settlement journal and fees

Amazon settlement deposit, revenue, fees and variance → one balanced NetSuite journal entry

Each settlement

How it runs

Every Amazon Seller Central run is counted, checked and recoverable

Records land in the NS90 data hub in Oracle Autonomous Data Warehouse before they reach NetSuite, so each one can be checked, retried and traced.

Balance and Control

Checks before and after posting

Every settlement line must add up to the deposit total on Amazon's settlement report. Any difference is flagged for review before the settlement is relied on.

The settlement journal must balance, or it does not post.

Every settlement line must be classified as revenue, fee, tax or liquidation.

Marketplace facilitator tax must net to zero and is held out of revenue.

Totals round to two decimals, and any remaining difference posts to an Amazon variance account, so the journal always balances.

The journal is dated on the deposit date and carries the settlement ID, so its bank line matches the Amazon deposit in NetSuite bank reconciliation.

Self-healing

Record-level reprocessing

Payments, refunds and journals each have a retry flow that picks up failed records once the cause is fixed.

Orders are pulled by last-updated time with a lag offset, so late status changes are not missed.

Calls back off when Amazon throttles, and historical loads run in date-range chunks.

Alerts and visibility

Dashboards and monitoring

A settlement transaction report in NetSuite Analytics Warehouse shows how every line was matched and posted.

An observability dashboard shows runs, failures and records waiting by flow.

What we’ve learned

9 lessons from Amazon Seller Central projects on NS90: Integrate

Pull by last update, with a lag

Amazon orders change status after they are created. Pulling by last-updated time, a few minutes behind real time, catches every change. Pulling by creation time misses some.

Request buyer-data access at kickoff

Confirming FBM shipments with the current Orders API needs Amazon's approval for restricted buyer data. Approval can take weeks, so request it first and plan a fallback.

Load SKU cross-references before cutover

Missing seller SKUs are the most common cause of failed records, including FBA-prefixed SKUs and discontinued items still on recent orders.

Pick a clean settlement start date

Settlements that include orders from before go-live cannot match their invoices. A dated cutover, with earlier settlements held, keeps the first live settlement clean.

Confirm every marketplace and currency

Dormant Amazon stores in other countries can still produce settlements. Agreeing up front which marketplaces are in scope avoids surprises.

Use a few default Amazon customers

Posting Amazon orders to a small set of default customers keeps open invoices per customer within NetSuite's limits and keeps payment application fast.