Amazon NetSuite Integration: A 2026 Planning Guide

Short answer

An Amazon NetSuite integration moves orders, inventory and money between Amazon's Selling Partner API (SP-API) and NetSuite. A packaged connector covers the standard flows and is the right start for many sellers. A custom build pays off when you sell across several marketplaces or subsidiaries, need settlements reconciled line by line, or have NetSuite customisations a connector cannot see. Whichever you choose, two Amazon deadlines apply now: the old settlement reports are removed on 11 November 2026, and the current Orders API (v0) has to be replaced by Orders API v2026-01-01 by 27 March 2027.

The Amazon and NetSuite facts below were checked against Amazon's SP-API documentation and Oracle's NetSuite help center on 28 October 2026.

What has to flow, and which way

Before anyone compares tools, list the flows. In most Amazon NetSuite projects they come down to five:

Then decide what each flow becomes in NetSuite. Do FBA orders arrive as cash sales or as sales orders with item fulfilments? One customer record per buyer, or one per marketplace? Which subsidiary, currency and location does each Amazon store map to? These are accounting decisions first. Get them signed off by whoever closes the books, because changing them after go-live means reposting history.

Connector or custom build

Oracle sells its own NetSuite Connector with marketplace connectors for Amazon; its help center documents, for example, a Vendor Central setup that you request through your NetSuite account manager and authorize with Login with Amazon. Several integration platforms offer Amazon connectors too.

A connector is usually the better choice when you run one or two Amazon accounts, your NetSuite setup is close to standard, and summary-level settlement postings satisfy your finance team.

A custom build earns its cost when:

• you sell in many marketplaces, regions or subsidiaries and each needs its own mapping rules;
• finance wants each fee, refund and reimbursement matched to its order, not a single journal per payout;
• your NetSuite account has custom records, approval workflows or SuiteScript logic the integration must respect;
• Amazon is one channel of several, and Walmart, Shopify or a B2B portal must post into NetSuite the same way;
• you need to own the code, so an Amazon API change is a ticket for your team, not a wait for a vendor's roadmap.

There is also a middle path worth considering: keep a connector for orders and stock, and build only the settlement reconciliation, which is where packaged tools are weakest.

Orders into NetSuite

Amazon introduced the Orders API v2026-01-01 this year and scheduled six v0 operations for deprecation and removal: getOrders, getOrder, getOrderBuyerInfo, getOrderAddress, getOrderItems and getOrderItemsBuyerInfo. Integrations on v0 must migrate by 27 March 2027. According to the migration guide:

• searchOrders replaces getOrders, and getOrder now returns the items as well;
• buyer and address data come from getOrder with the includedData parameter (BUYER, RECIPIENT) instead of separate calls;
• Restricted Data Tokens are no longer needed for personal data in the new version; access depends on the roles assigned to your application;
• the pagination token expires after 24 hours, statuses move to upper case (Canceled becomes CANCELLED), and fulfilment channels read MERCHANT and AMAZON instead of MFN and AFN.

Each of these touches NetSuite mapping code: status filters, the field that decides cash sale or sales order, the address on the fulfilment record. If you run a connector, ask the vendor for its v2026-01-01 date in writing. If you run your own code, budget the migration now, before the first quarter of 2027 fills up.

For the import itself, make it idempotent on the Amazon order ID, store the raw Amazon payload next to the NetSuite record for audit, and import orders in a state that lets NetSuite reject a bad mapping without losing the order.

FBA inventory

Stock held in Amazon's fulfilment centres should appear in NetSuite as its own location, never merged with your warehouse. Amazon is the source of truth for that location: read it on a schedule, post the difference as an adjustment with a reason code, and keep inbound shipments separate so stock in transit is not counted twice. For seller-fulfilled offers the direction reverses: NetSuite owns the quantity and pushes it to Amazon. Mixing the two directions on one SKU is a reliable way to create phantom stock.

Settlements and payouts

This is where most Amazon NetSuite integrations disappoint. One Amazon payout bundles sales, fees, advertising charges, refunds, reimbursements and reserves, often in more than one currency. Finance needs it to match the bank deposit to the cent and to trace every line back to an order.

The source data is changing. Amazon's settlement report types share the prefix GET_V2_SETTLEMENT_REPORT_DATA_. According to Amazon's changelog, on 11 November 2026 the XML Settlement Report (suffix XML) and the original Flat File Settlement Report (suffix FLAT_FILE) are removed for sellers in all marketplaces. The replacement is the Flat File V2 Settlement Report (suffix FLAT_FILE_V2), which carries the same information in fewer columns. There is no XML replacement. Any integration that still reads either removed report stops posting settlements in two weeks.

For transaction-level detail between payouts, the Finances API v2024-06-19 lists transactions and, in Amazon's words, helps determine which released transactions make up a payment. A robust design uses both: the settlement report as the record that must balance, and transactions to post activity before the payout closes.

In NetSuite, post each settlement as a clearing account that empties to zero when the deposit lands, with fees, refunds and reimbursements on their own accounts. If the clearing account does not empty, something upstream is wrong, and you find out on the day rather than at month end. We built this pattern for a multi-brand retailer reconciling marketplace payouts in NetSuite; the case study describes the matching logic.

Limits on both sides

Amazon. SP-API applies a token bucket per selling partner and application, with its own rate and burst for each operation. Throttled calls return 429, which is retryable with back-off. The x-amzn-RateLimit-Limit header shows the current limit when it is present, but Amazon says not to rely on it being there.

NetSuite. Concurrency is governed per account, and the limit covers web services and RESTlet requests combined. Oracle's help center states that the base limit depends on your service tier and that each SuiteCloud Plus license raises it by 10. Your Amazon integration therefore competes with every other integration in the account, including the bank feed and the warehouse system. Batch writes, keep one worker pool that respects the account limit, and schedule heavy imports away from month-end close.

Buyer data and access

Shipping addresses and buyer details are personal data. Amazon releases them only to applications approved for the matching restricted role, and its Data Protection Policy then governs how you store, encrypt and delete them. For accounting you rarely need them: a NetSuite customer per marketplace with the address on the fulfilment record is often enough, and keeps personal data out of the general ledger. If your process does need buyer data, plan the role approval early; it takes longer than the code. Our Amazon PII access service covers that process.

How we scope it

We start with a short audit: which flows exist today, which are manual, where the numbers disagree. Then we agree the accounting decisions with finance, decide connector, custom or the middle path, and build the settlement reconciliation against real payout files before anything goes live. It is the same approach we described for connecting SAP with Amazon, applied to NetSuite's data model.

Deltologic has built marketplace and ERP integrations since 2020; the marketplace integrations page lists the scope. If Amazon and NetSuite disagree in your books, or the November and March deadlines land on your integration, tell us what you run today. A senior engineer reads every brief and answers with a plan, not a sales deck.

Frequently asked questions

Is there a native Amazon NetSuite connector?

Oracle sells NetSuite Connector, which includes Amazon connectors, and several integration platforms offer Amazon connectors as well. They suit standard order and stock flows; a custom build fits multi-marketplace setups and line-level settlement reconciliation.

Which Amazon settlement report should a NetSuite integration use?

The Flat File V2 Settlement Report. Amazon removes the XML and the original flat file settlement reports for sellers on 11 November 2026, and there is no XML replacement.

When does the Amazon Orders API v0 have to be replaced?

Amazon asks integrations using Orders API v0 to migrate to Orders API v2026-01-01 by 27 March 2027. In the new version, searchOrders replaces getOrders and personal data no longer requires a Restricted Data Token.

How many API calls can NetSuite handle at once?

NetSuite limits concurrent web services and RESTlet requests per account. The base limit depends on the service tier, and each SuiteCloud Plus license adds 10, so an Amazon integration shares that capacity with every other integration in the account.