NetSuite Amazon Integration: Order Sync and Fulfilment Guide

Emanuel Vassiliadis

ERP Implementation and Development Consultant

Originally published: May 27, 2026

Last updated: May 27, 2026

NetSuite Amazon integration connects your Amazon Seller Central account to NetSuite ERP so that orders, inventory levels, and financial data sync between the two platforms automatically. For businesses selling on Amazon at scale, the integration removes the manual work involved in getting Amazon order data into your finance and fulfillment systems, and gives you an accurate view of stock across all your channels in one place.

Selling on Amazon is straightforward at low volumes. As volume grows, the operational gap between what Amazon shows you in Seller Central and what your ERP knows about becomes a real cost. Orders need to reach your fulfillment workflow. Inventory levels need to stay accurate across Amazon and every other channel you sell through. Revenue from Amazon needs to land in your books correctly, net of fees and after reconciliation with Amazon's settlement reports. A NetSuite implementation partner with ecommerce operations experience designs that data flow correctly from the start, avoiding expensive corrections after go-live.

Without a proper integration, that work is manual. 

"Spreadsheets are like the spider web trying to glue them all together. It all comes back to that same thing." - Tiernan O'Connor, Director of Customer Engagement

The operational cost of managing Amazon manually does not show up cleanly in any single line of your P&L, but it shows up in headcount, in errors, and in the management time spent resolving discrepancies.

Australian businesses selling on Amazon.com.au, or Australian wholesalers and manufacturers selling on Amazon in international markets, are operating in a marketplace that now accounts for a significant share of the $18.9 billion Australians spent through online marketplaces in 2025, according to the Australia Post eCommerce Report 2026. Connecting that channel to your ERP properly is not a nice-to-have at meaningful volume; it is an operational requirement.

What data syncs between Amazon and NetSuite

Four core data types move between Amazon Seller Central and NetSuite in a standard integration.

Orders flow from Amazon to NetSuite as sales orders. Both FBA (Fulfilment by Amazon) and FBM (Fulfilment by Merchant) orders sync, though they follow different paths through your NetSuite fulfillment workflow. FBA orders are fulfilled by Amazon's warehouse network; NetSuite receives them for financial recording and inventory accounting purposes. FBM orders trigger your own picking, packing, and despatch process within NetSuite.

Inventory syncs from NetSuite to Amazon for FBM listings, where your own stock feeds the Amazon channel. For FBA inventory, Amazon holds the stock and NetSuite receives inventory position updates from Amazon. Keeping both views accurate, particularly when stock is split between your warehouse and Amazon's fulfillment centres, requires specific configuration and clear rules about which system is authoritative for which inventory pool.

Pricing can be managed in NetSuite and pushed to Amazon listings, or managed directly in Seller Central. Most businesses manage pricing in Seller Central for their Amazon channel specifically, since Amazon's pricing tools and competitive repricing features operate independently of the ERP. The integration typically handles order data rather than serving as the primary channel for price management.

Financial data, including Amazon settlement reports, fee deductions, and net revenue figures, syncs to NetSuite for reconciliation and financial reporting. This is the area where the integration earns its keep for finance teams: automating the reconciliation of Amazon's fortnightly settlement reports against sales orders and inventory movements in NetSuite.

FBA versus FBM: how the integration handles each

The distinction between Fulfilment by Amazon and Fulfilment by Merchant matters significantly for how the integration is designed.

FBA means Amazon warehouses, picks, packs, and ships your products. Your role in the fulfilment process ends when you send stock to Amazon's fulfilment centres. In NetSuite, FBA orders arrive from Amazon as closed sales orders for financial recording. Inventory movements, including the transfer of stock from your warehouse to Amazon's fulfillment centres, need to be tracked as inventory transfers in NetSuite so your stock position remains accurate.

FBM means you manage fulfillment from your own warehouse. Amazon takes the order and passes it to you. The integration creates a NetSuite sales order that enters your standard pick, pack, and despatch workflow. Confirmation of despatch flows back to Amazon to update the order status in Seller Central. FBM requires more integration work but gives you direct control over the fulfilment process and keeps your warehouse operations within NetSuite.

Many businesses run both FBA and FBM simultaneously, using FBA for their top-selling SKUs and FBM for slower-moving or oversized items. The integration needs to handle both models and route each order type correctly.

Settlement reconciliation: the finance team's main use case

Amazon pays sellers on a fortnightly settlement cycle. Each settlement includes gross sales, Amazon fees (referral fees, FBA fees, advertising costs, and others), refunds, and adjustments. The net figure that reaches your bank account can differ significantly from your gross Amazon revenue.

Without an integration, reconciling the settlement report against your sales records and accounting for all the fee categories is a manual process. The settlement data is available from Amazon in CSV format, but mapping it to NetSuite journal entries, allocating fees to the correct accounts, and matching orders to payments requires either significant manual effort or a purpose-built process.

A properly configured NetSuite Amazon integration automates this reconciliation. Settlement data maps to NetSuite accounts. Fees are allocated to the correct expense categories. Revenue is recorded net or gross depending on your accounting treatment. Finance can close the Amazon channel accurately in the same timeframe as their other revenue streams.

For businesses selling across multiple Amazon marketplaces, including the US, UK, EU, and Australian markets, the reconciliation complexity multiplies. A multi-marketplace integration that handles currency conversion and marketplace-specific fee structures in NetSuite is a meaningful operational investment.

Connector options for NetSuite and Amazon

Three approaches cover most NetSuite Amazon integration requirements.

Oracle's native NetSuite Connector includes an Amazon integration that handles order sync, inventory, and basic settlement data for both FBA and FBM models. It is the most direct path for businesses with standard requirements and provides the tightest native integration between the two platforms.

Third-party middleware platforms are widely used for Amazon and NetSuite integrations, particularly for businesses selling across multiple Amazon marketplaces, running both FBA and FBM simultaneously, or needing more granular control over settlement reconciliation. These platforms typically offer pre-built Amazon connectors with more configuration options than the native solution.

For most Australian businesses with growing Amazon operations, this is the approach DWR recommends. 

Custom development using NetSuite's SuiteScript framework alongside Amazon's Selling Partner API is appropriate for complex or unusual requirements: businesses with bespoke inventory management workflows, those integrating Amazon alongside multiple other channels in a single data flow, or those needing custom settlement reconciliation logic that standard connectors do not support.

 "For a quarter of a headcount, it's probably worth getting a product that can double your output." - Tiernan O'Connor, Director of Customer Engagement

The integration investment is a headcount question. The manual processes it replaces, in order processing, inventory management, and settlement reconciliation, have a measurable cost. The business case for integration is almost always clearer than it first appears.

Common pitfalls

Inventory position errors are the most operationally disruptive problem. If FBA inventory movements, transfers from your warehouse to Amazon's fulfillment centres, are not recorded in NetSuite, your stock position becomes inaccurate. Over time this creates write-off surprises and unreliable inventory reporting. FBA inventory transfers need to be mapped as explicit transactions in NetSuite, not ignored.

Fee misallocation in settlement reconciliation is the most common finance problem. Amazon's fee structure includes multiple categories, and each needs to map to the correct NetSuite account. A generic approach that dumps all Amazon deductions into a single expense account produces inaccurate cost-of-sales and makes P&L analysis by channel meaningless.

Order lag can create fulfillment problems for FBM orders. If Amazon orders are not reaching NetSuite quickly enough, your warehouse picks and despatches late. Amazon penalises late despatch, which affects your seller metrics. Real-time or near-real-time order sync is the right default for FBM.

Multi-marketplace currency handling requires explicit configuration for businesses selling in international Amazon markets. Revenue, fees, and refunds denominated in foreign currencies need to be converted and recorded correctly in NetSuite against your base currency. This is straightforward to configure but easy to overlook during initial setup.

Making Amazon a connected channel

NetSuite Amazon integration makes Amazon a properly accounted channel in your business, not a manual reconciliation task. Orders reach fulfillment without rekeying. Inventory stays accurate across your warehouse and Amazon's fulfilment network. Settlement data lands in your books automatically.

For businesses using Amazon as a meaningful revenue channel, the integration pays for itself in the operational time it replaces. The settlement reconciliation alone, handled manually, can consume several hours of finance team time per fortnight. At any reasonable headcount cost, the numbers are straightforward.

DWR works with Australian wholesale distributors and manufacturers to design NetSuite integrations that connect their sales channels to their back office. You can review DWR's NetSuite integration service, explore NetSuite for wholesale distribution, and understand how NetSuite's warehouse management capabilities fit alongside your Amazon operations. Get in touch to discuss your specific requirements.

FAQs

Can NetSuite integrate with Amazon?
How does the integration handle FBA versus FBM orders?
How does Amazon settlement reconciliation work in NetSuite?
Can the integration handle multiple Amazon marketplaces?
What inventory data syncs between NetSuite and Amazon?

Need Expert Guidance?

Our NetSuite consultants are here to help you make the right decision for your business.

1800 197 403

info@dwr.com.au

Schedule Consultation

Trusted by 200+ Australian BUsinesses

NetSuite Implementation

System Optimisation

Project Recovery

Ongoing Support

NetSuite Amazon Integration: Order Sync and Fulfilment Guide

NetSuite Amazon integration connects your Amazon Seller Central account to NetSuite ERP so that orders, inventory levels, and financial data sync between the two platforms automatically. For businesses selling on Amazon at scale, the integration removes the manual work involved in getting Amazon order data into your finance and fulfillment systems, and gives you an accurate view of stock across all your channels in one place.

Selling on Amazon is straightforward at low volumes. As volume grows, the operational gap between what Amazon shows you in Seller Central and what your ERP knows about becomes a real cost. Orders need to reach your fulfillment workflow. Inventory levels need to stay accurate across Amazon and every other channel you sell through. Revenue from Amazon needs to land in your books correctly, net of fees and after reconciliation with Amazon's settlement reports. A NetSuite implementation partner with ecommerce operations experience designs that data flow correctly from the start, avoiding expensive corrections after go-live.

Without a proper integration, that work is manual. 

"Spreadsheets are like the spider web trying to glue them all together. It all comes back to that same thing." - Tiernan O'Connor, Director of Customer Engagement

The operational cost of managing Amazon manually does not show up cleanly in any single line of your P&L, but it shows up in headcount, in errors, and in the management time spent resolving discrepancies.

Australian businesses selling on Amazon.com.au, or Australian wholesalers and manufacturers selling on Amazon in international markets, are operating in a marketplace that now accounts for a significant share of the $18.9 billion Australians spent through online marketplaces in 2025, according to the Australia Post eCommerce Report 2026. Connecting that channel to your ERP properly is not a nice-to-have at meaningful volume; it is an operational requirement.

What data syncs between Amazon and NetSuite

Four core data types move between Amazon Seller Central and NetSuite in a standard integration.

Orders flow from Amazon to NetSuite as sales orders. Both FBA (Fulfilment by Amazon) and FBM (Fulfilment by Merchant) orders sync, though they follow different paths through your NetSuite fulfillment workflow. FBA orders are fulfilled by Amazon's warehouse network; NetSuite receives them for financial recording and inventory accounting purposes. FBM orders trigger your own picking, packing, and despatch process within NetSuite.

Inventory syncs from NetSuite to Amazon for FBM listings, where your own stock feeds the Amazon channel. For FBA inventory, Amazon holds the stock and NetSuite receives inventory position updates from Amazon. Keeping both views accurate, particularly when stock is split between your warehouse and Amazon's fulfillment centres, requires specific configuration and clear rules about which system is authoritative for which inventory pool.

Pricing can be managed in NetSuite and pushed to Amazon listings, or managed directly in Seller Central. Most businesses manage pricing in Seller Central for their Amazon channel specifically, since Amazon's pricing tools and competitive repricing features operate independently of the ERP. The integration typically handles order data rather than serving as the primary channel for price management.

Financial data, including Amazon settlement reports, fee deductions, and net revenue figures, syncs to NetSuite for reconciliation and financial reporting. This is the area where the integration earns its keep for finance teams: automating the reconciliation of Amazon's fortnightly settlement reports against sales orders and inventory movements in NetSuite.

FBA versus FBM: how the integration handles each

The distinction between Fulfilment by Amazon and Fulfilment by Merchant matters significantly for how the integration is designed.

FBA means Amazon warehouses, picks, packs, and ships your products. Your role in the fulfilment process ends when you send stock to Amazon's fulfilment centres. In NetSuite, FBA orders arrive from Amazon as closed sales orders for financial recording. Inventory movements, including the transfer of stock from your warehouse to Amazon's fulfillment centres, need to be tracked as inventory transfers in NetSuite so your stock position remains accurate.

FBM means you manage fulfillment from your own warehouse. Amazon takes the order and passes it to you. The integration creates a NetSuite sales order that enters your standard pick, pack, and despatch workflow. Confirmation of despatch flows back to Amazon to update the order status in Seller Central. FBM requires more integration work but gives you direct control over the fulfilment process and keeps your warehouse operations within NetSuite.

Many businesses run both FBA and FBM simultaneously, using FBA for their top-selling SKUs and FBM for slower-moving or oversized items. The integration needs to handle both models and route each order type correctly.

Settlement reconciliation: the finance team's main use case

Amazon pays sellers on a fortnightly settlement cycle. Each settlement includes gross sales, Amazon fees (referral fees, FBA fees, advertising costs, and others), refunds, and adjustments. The net figure that reaches your bank account can differ significantly from your gross Amazon revenue.

Without an integration, reconciling the settlement report against your sales records and accounting for all the fee categories is a manual process. The settlement data is available from Amazon in CSV format, but mapping it to NetSuite journal entries, allocating fees to the correct accounts, and matching orders to payments requires either significant manual effort or a purpose-built process.

A properly configured NetSuite Amazon integration automates this reconciliation. Settlement data maps to NetSuite accounts. Fees are allocated to the correct expense categories. Revenue is recorded net or gross depending on your accounting treatment. Finance can close the Amazon channel accurately in the same timeframe as their other revenue streams.

For businesses selling across multiple Amazon marketplaces, including the US, UK, EU, and Australian markets, the reconciliation complexity multiplies. A multi-marketplace integration that handles currency conversion and marketplace-specific fee structures in NetSuite is a meaningful operational investment.

Connector options for NetSuite and Amazon

Three approaches cover most NetSuite Amazon integration requirements.

Oracle's native NetSuite Connector includes an Amazon integration that handles order sync, inventory, and basic settlement data for both FBA and FBM models. It is the most direct path for businesses with standard requirements and provides the tightest native integration between the two platforms.

Third-party middleware platforms are widely used for Amazon and NetSuite integrations, particularly for businesses selling across multiple Amazon marketplaces, running both FBA and FBM simultaneously, or needing more granular control over settlement reconciliation. These platforms typically offer pre-built Amazon connectors with more configuration options than the native solution.

For most Australian businesses with growing Amazon operations, this is the approach DWR recommends. 

Custom development using NetSuite's SuiteScript framework alongside Amazon's Selling Partner API is appropriate for complex or unusual requirements: businesses with bespoke inventory management workflows, those integrating Amazon alongside multiple other channels in a single data flow, or those needing custom settlement reconciliation logic that standard connectors do not support.

 "For a quarter of a headcount, it's probably worth getting a product that can double your output." - Tiernan O'Connor, Director of Customer Engagement

The integration investment is a headcount question. The manual processes it replaces, in order processing, inventory management, and settlement reconciliation, have a measurable cost. The business case for integration is almost always clearer than it first appears.

Common pitfalls

Inventory position errors are the most operationally disruptive problem. If FBA inventory movements, transfers from your warehouse to Amazon's fulfillment centres, are not recorded in NetSuite, your stock position becomes inaccurate. Over time this creates write-off surprises and unreliable inventory reporting. FBA inventory transfers need to be mapped as explicit transactions in NetSuite, not ignored.

Fee misallocation in settlement reconciliation is the most common finance problem. Amazon's fee structure includes multiple categories, and each needs to map to the correct NetSuite account. A generic approach that dumps all Amazon deductions into a single expense account produces inaccurate cost-of-sales and makes P&L analysis by channel meaningless.

Order lag can create fulfillment problems for FBM orders. If Amazon orders are not reaching NetSuite quickly enough, your warehouse picks and despatches late. Amazon penalises late despatch, which affects your seller metrics. Real-time or near-real-time order sync is the right default for FBM.

Multi-marketplace currency handling requires explicit configuration for businesses selling in international Amazon markets. Revenue, fees, and refunds denominated in foreign currencies need to be converted and recorded correctly in NetSuite against your base currency. This is straightforward to configure but easy to overlook during initial setup.

Making Amazon a connected channel

NetSuite Amazon integration makes Amazon a properly accounted channel in your business, not a manual reconciliation task. Orders reach fulfillment without rekeying. Inventory stays accurate across your warehouse and Amazon's fulfilment network. Settlement data lands in your books automatically.

For businesses using Amazon as a meaningful revenue channel, the integration pays for itself in the operational time it replaces. The settlement reconciliation alone, handled manually, can consume several hours of finance team time per fortnight. At any reasonable headcount cost, the numbers are straightforward.

DWR works with Australian wholesale distributors and manufacturers to design NetSuite integrations that connect their sales channels to their back office. You can review DWR's NetSuite integration service, explore NetSuite for wholesale distribution, and understand how NetSuite's warehouse management capabilities fit alongside your Amazon operations. Get in touch to discuss your specific requirements.