Amazon + NetSuite Integration: FBA, Seller Central, and Settlement Reconciliation

Disclosure: Some links in this article are affiliate links. We may earn a commission if you purchase through them, at no extra cost to you. We only recommend solutions we've vetted through real client implementations.

Selling on Amazon while running NetSuite as your ERP creates a unique set of integration challenges that don't exist with other sales channels. Amazon isn't just a marketplace — it's a fulfillment network (FBA), a lending platform, an advertising engine, and a financial institution that holds your money for two weeks before settling. Getting all of that data into NetSuite accurately is critical for brands that want to understand their true profitability on Amazon.

In our work with ecommerce brands doing $2M–$50M+ on Amazon, the number one complaint we hear is: "We have no idea how much money we're actually making on Amazon after all the fees." That's a direct result of poor integration between Amazon and NetSuite. When settlement data doesn't reconcile, when FBA fees aren't properly allocated, and when advertising costs aren't connected to order-level margin, you're flying blind.

This guide covers the complete Amazon-to-NetSuite integration landscape: Seller Central vs. Vendor Central, FBA inventory management, settlement reconciliation, multi-marketplace setups, and the connector options that make it all work.

Key Takeaways

• Seller Central and Vendor Central require fundamentally different integration approaches — don't assume one connector handles both
• Settlement reconciliation is the hardest part — Amazon deducts 30+ fee types before paying you, and each one needs to map to a GL account in NetSuite
• FBA inventory is Amazon's inventory, not yours — track it in NetSuite as a separate location, but understand the reconciliation challenges
• Multi-marketplace selling adds currency, tax, and entity complexity that most connectors handle poorly out of the box
• Plan for $15K–$40K in implementation costs and $8K–$25K/year in connector licensing

Seller Central vs. Vendor Central: How Does the Integration Differ?

This is the first question you need to answer, because it fundamentally changes your integration architecture.

Seller Central (3P) Integration

With Seller Central, you're selling directly to customers through Amazon's marketplace. You own the customer relationship (sort of), set your prices, and handle customer service. Orders come to you, and you fulfill them — either yourself (FBM/Merchant Fulfilled) or through Amazon (FBA).

Data flows for Seller Central:

• Orders: Amazon → NetSuite (as sales orders). Each Amazon order creates a sales order in NetSuite with the customer's shipping address and order details.
• Inventory: NetSuite → Amazon (available quantity updates). If you're doing FBM, you need to keep Amazon's inventory count in sync with your warehouse.
• Settlements: Amazon → NetSuite (biweekly settlement reports map to bank deposits). This is the complex one.
• Returns: Amazon → NetSuite (return authorizations, refund processing).
• FBA inventory: Amazon → NetSuite (inventory adjustment reports, inbound shipment tracking).

Vendor Central (1P) Integration

With Vendor Central, Amazon is your customer. They issue purchase orders, you ship to their fulfillment centers, and they pay you on net-30 to net-90 terms. The integration looks more like a traditional B2B/EDI flow.

Data flows for Vendor Central:

• Purchase Orders: Amazon → NetSuite (as purchase orders or sales orders, depending on your setup).
• ASN (Advance Ship Notices): NetSuite → Amazon (shipment confirmations with carton-level details).
• Invoices: NetSuite → Amazon (against POs, for payment).
• Remittance: Amazon → NetSuite (payment matching against invoices).
• Chargebacks: Amazon → NetSuite (shortage claims, compliance penalties, co-op deductions).

Key difference: Vendor Central integration is essentially EDI-style communication. Seller Central integration is marketplace transaction processing. They require different connectors, different data models, and different reconciliation approaches.

Brands Running Both

Many brands operate as both 1P and 3P sellers on Amazon. In this case, you need two separate integration flows and need to ensure orders from each channel are tagged appropriately in NetSuite for accurate reporting. Typically, you'll set up separate sales channels or classes in NetSuite.

How Do You Handle FBA Inventory in NetSuite?

FBA inventory management is where Amazon integration gets genuinely complicated. Once you send inventory to Amazon's fulfillment centers, you lose direct control over it. Amazon moves it between warehouses, damages it, loses it, and charges you fees for all of the above.

Setting Up FBA as a NetSuite Location

Create a dedicated inventory location in NetSuite called "Amazon FBA" (or separate locations per FBA warehouse if you need that granularity — most brands don't). This location represents inventory that's physically at Amazon but still belongs to you.

Inventory movements to track:

1. Inbound shipments: When you create an FBA shipment in Seller Central, create a corresponding inventory transfer in NetSuite from your warehouse to the FBA location. Track the shipment ID for reconciliation.

2. Received inventory: When Amazon confirms receipt (which may differ from what you shipped — damaged in transit, miscounts), adjust the FBA location quantity in NetSuite. The variance goes to a shrinkage or adjustment account.

3. Customer orders (FBA): When a customer order is fulfilled by FBA, NetSuite should reduce the FBA location quantity. This happens via the order sync — the sales order's fulfillment location should be set to the FBA location.

4. Removals: When you request inventory removal from FBA (returns to your warehouse, disposal), create an inventory transfer in NetSuite from FBA back to your warehouse or write it off.

5. Adjustments: Amazon periodically reports inventory adjustments — items found, items lost, items damaged. These need to become inventory adjustment records in NetSuite against the FBA location.

The FBA Inventory Reconciliation Challenge

Here's the honest truth: FBA inventory will never perfectly reconcile with NetSuite. Amazon's inventory reports are asynchronous, their receiving process has error margins, and their internal transfers aren't reported in real-time. The best you can achieve is reconciliation within 1–2% variance, with monthly adjustments to true up.

Our recommendation: Run a monthly FBA inventory reconciliation. Pull Amazon's Inventory Adjustment Report, compare to NetSuite's FBA location quantities, and book the variance to a dedicated "Amazon FBA Adjustment" account. Over time, this gives you visibility into how much inventory you're losing to Amazon's operations.

How Does Settlement Reconciliation Work?

Settlement reconciliation is the single most important — and most commonly botched — part of Amazon-NetSuite integration. Here's why it's hard.

Understanding Amazon Settlements

Amazon doesn't pay you per order. Every two weeks, they calculate everything you're owed, subtract everything you owe them, and deposit the net amount. A single settlement can contain thousands of line items across dozens of fee categories:

• Product charges: The selling price of items (what the customer paid for the product).
• Shipping charges: What the customer paid for shipping (if applicable).
• Gift wrap charges: If offered.
• Promotional rebates: Discounts you funded (coupons, Lightning Deals).
• Referral fees: Amazon's commission (typically 8–15% depending on category).
• FBA fees: Pick, pack, weight handling fees per unit.
• FBA storage fees: Monthly and long-term storage charges.
• FBA inbound fees: Charges for prepping, labeling, or non-compliant shipments.
• Refunds: Product refunds, shipping refunds, and the associated fee reversals.
• Advertising fees: Sponsored Products, Sponsored Brands, Sponsored Display.
• Subscription fees: Professional Seller account fee.
• Adjustments: Reimbursements for lost/damaged FBA inventory, A-to-Z claims.

Mapping Settlements to NetSuite

Each of these fee types needs to map to a specific GL account in NetSuite. A typical chart of accounts mapping looks like:

Amazon Fee Type	NetSuite GL Account
Product charges	Revenue (by product category)
Referral fees	Amazon Commission Expense
FBA fulfillment fees	Amazon FBA Expense
FBA storage fees	Warehouse Storage Expense
Advertising fees	Digital Advertising Expense
Promotional rebates	Promotions/Discounts (contra-revenue)
Refunds	Sales Returns

Two Approaches to Settlement Reconciliation

Approach 1: Order-Level Reconciliation

Sync every individual order from Amazon to NetSuite, then use the settlement report to reconcile the aggregate. This gives you order-level profitability but requires significantly more data volume and processing.

Each order creates a sales order and invoice in NetSuite. The settlement report is then used to create a journal entry or vendor bill for the aggregate fees, and you match the bank deposit to the settlement total.

Approach 2: Settlement-Level Reconciliation

Skip individual order sync and instead use the settlement report as the source of truth. Create a single journal entry per settlement that debits your bank account and credits revenue, with separate line items for each fee category.

This is simpler but gives you no order-level visibility in NetSuite. You'd rely on Amazon's reports for order-level detail.

Our recommendation: For brands doing more than $500K/year on Amazon, use order-level reconciliation. The visibility into order-level margin is worth the additional integration complexity.

How Do You Set Up Multi-Marketplace Integration?

If you sell on Amazon US, CA, UK, DE, FR, IT, ES, JP, or AU, each marketplace introduces additional complexity.

Currency Handling

Each marketplace settles in its local currency (USD, CAD, GBP, EUR, JPY, AUD). In NetSuite, you need:

• Multi-currency enabled on your NetSuite account.
• Exchange rates updated regularly (NetSuite can auto-update these).
• Currency-specific bank accounts (or a single multi-currency account) to receive settlements.
• Revenue recognized in local currency and consolidated to your base currency for reporting.

Entity Structure

Depending on your legal structure, international marketplaces may flow into:

• Same NetSuite subsidiary: If you're selling internationally under one legal entity.
• Separate subsidiaries: If you have local entities in each country (common for VAT purposes in the EU).
• Intercompany transactions: If inventory is held by one subsidiary but sold by another.

Tax Complexity

VAT in Europe and GST in Australia/Canada are fundamentally different from US sales tax. Amazon collects and remits VAT in many EU countries (Marketplace Facilitator rules), but the accounting entries still need to flow correctly in NetSuite. Make sure your connector handles the tax jurisdiction differences per marketplace.

Practical Setup

Most brands start with Amazon US, then expand to CA and UK. The integration should be architected for multi-marketplace from day one, even if you're only live on US initially. Retrofitting multi-marketplace support is painful and expensive.

What Are the Best Connector Options for Amazon + NetSuite?

Celigo

The most popular choice. Celigo offers pre-built flows for Amazon Seller Central that handle orders, inventory, settlements, and fulfillments. Multi-marketplace support is available but requires additional configuration per marketplace.

Cost: $12K–$25K/year plus $20K–$40K implementation.

Pipe17

Pipe17 specializes in marketplace and ecommerce integrations. Their Amazon connector handles the settlement reconciliation particularly well, with detailed fee-level mapping.

Cost: Based on order volume, typically $6K–$18K/year plus implementation.

Custom via Amazon SP-API

Amazon's Selling Partner API (SP-API) is well-documented and supports all the data you need. Building custom requires strong API development skills and ongoing maintenance.

Cost: $30K–$60K development plus $12K–$24K/year maintenance.

NetSuite Native (SuiteApps)

Several SuiteApps on NetSuite's marketplace offer Amazon integration. Quality varies significantly — evaluate based on settlement reconciliation capabilities, not just order sync.

Cost: $5K–$15K/year plus implementation.

Frequently Asked Questions

How do I handle Amazon returns in NetSuite?

Amazon processes returns and refunds, often before you receive the product back. Create a return authorization in NetSuite when the refund is issued, then process the credit memo. If you're FBA, you may never see the returned item — Amazon handles disposal or re-shelving. Adjust inventory accordingly.

Should I sync every Amazon order to NetSuite in real-time?

Not necessarily real-time. Amazon's order API has a 5–15 minute delay, and batch processing every 15–30 minutes is typically sufficient. Real-time sync adds complexity without significant business benefit for most brands.

How do I handle Amazon advertising costs in NetSuite?

Amazon Advertising costs can be synced separately via the Amazon Advertising API, or they appear in your settlement report. Either create a monthly vendor bill in NetSuite for advertising spend, or let the settlement reconciliation capture them as line items.

What about Amazon Lending or Amazon Capital loans?

Amazon Lending disbursements and repayments appear in your settlement reports. Map these to a loan liability account in NetSuite and track principal vs. interest separately.

Can I track profitability per Amazon ASIN in NetSuite?

Yes, if you're doing order-level sync with fee allocation. Each order line item's revenue, referral fee, and FBA fee can be mapped to give you gross margin per ASIN. This is one of the strongest arguments for order-level (vs. settlement-level) reconciliation.

What Should You Do Next?

Amazon is likely your most complex sales channel from an integration standpoint. The combination of FBA inventory management, multi-fee settlement reconciliation, and potential multi-marketplace expansion makes it significantly harder than integrating a direct-to-consumer Shopify store.

But the payoff is worth it. Brands that properly integrate Amazon with NetSuite can finally answer the question, "How much are we actually making on Amazon?" — and that insight often leads to strategic changes in product mix, advertising spend, and channel allocation that significantly improve overall profitability.

Take our free integration assessment to get a customized plan for your Amazon + NetSuite integration, including connector recommendations, timeline, and cost estimates tailored to your specific marketplace setup.