Amazon NetSuite Integration: Celigo Setup, FBA vs MFN, and Settlement Reconciliation

What the Celigo Amazon NetSuite Integration Does

Celigo's Amazon–NetSuite Integration App connects Amazon Seller Central to NetSuite using Amazon's SP-API. The core function: Amazon orders arrive in NetSuite automatically as Sales Orders, inventory flows from NetSuite back to your Amazon listings, and fulfillment tracking pushes from NetSuite to Amazon for merchant-fulfilled orders. Every two weeks, Amazon's settlement reports reconcile against NetSuite so your channel P&L stays accurate.

This covers the standard Seller Central (third-party seller) use case. If you also sell as a first-party supplier through Amazon Vendor Central, that is a separate EDI-based integration — 850 purchase orders, 856 advance ship notices, 810 invoices — not covered by the Celigo app. See our Amazon NetSuite integration service page for full scope details.

What Gets Synced

FBA vs MFN: Different Flows in NetSuite

Most Amazon sellers run a mix of FBA and MFN — and the integration needs to handle both correctly without conflating their downstream logic in NetSuite.

Merchant Fulfilled Network (MFN)

Your warehouse picks, packs, and ships the order. The integration creates a Sales Order in NetSuite when the Amazon order comes in. When your team creates an Item Fulfillment in NetSuite, the tracking number and carrier are automatically pushed back to Amazon, closing the order on Amazon's side and triggering the customer notification. Late or missing tracking uploads affect your seller performance metrics, so this push needs to be reliable.

Fulfilled by Amazon (FBA)

Amazon's warehouses pick, pack, and ship. The integration still creates a Sales Order in NetSuite to record the revenue, but no fulfillment action is taken from your side. FBA inventory (stock sitting in Amazon's warehouses) is separate from your NetSuite on-hand quantity — FBA stock syncs back to NetSuite for internal reporting, but Amazon controls what the listing displays. The downstream accounting — FBA storage fees, fulfilment fees — shows up in the settlement, not the order itself.

Settlement Reconciliation: The Part Most Integrations Get Wrong

Amazon pays every two weeks. The settlement is a net figure that bundles together: order revenue, FBA fulfilment fees, referral fees, advertising spend deducted at payout, returns and refunds, and any adjustments Amazon made during the period. The gross order value and the actual cash received are significantly different.

Mapping this to NetSuite accurately requires a deliberate design decision upfront — one that most connector-only setups leave to the client to figure out post-go-live:

• Order-level reconciliation — one journal entry per order, allocating fees against each Sales Order. More granular P&L reporting, more complex to configure and maintain.
• Summary reconciliation — one journal entry per settlement period, capturing total revenue, total fees, and net payout. Simpler to configure; most mid-market teams use this approach for one to three marketplaces.

Whichever approach your finance team chooses, it needs to be agreed before configuration begins — not discovered post-launch when the books don't balance.

SKU Consistency: The Hidden Blocker

SKU is the linking field between Amazon and NetSuite. The integration matches an Amazon order line to a NetSuite item using SKU. If your SKUs have been maintained inconsistently across both systems — trailing spaces, case mismatches, legacy formats from a migration, variants that were added differently on each side — the integration will produce unmatched records on day one.

A SKU consistency audit before go-live is not optional. Export all active SKUs from Amazon Seller Central and all active items from NetSuite, compare them, and resolve discrepancies before the integration runs. This typically surfaces issues in 20–40% of item catalogs and takes one to two weeks to clean up depending on catalog size.

How the Setup Works

The Celigo Amazon NetSuite Integration App installs from the Celigo Marketplace. Setup follows this sequence:

1. NetSuite prep — install the Celigo SuiteApp bundle, create a dedicated integration user with a Token-Based Authentication credential (never use an admin account), and confirm the correct roles and permissions are in place.
2. Amazon connection — connect via SP-API using your Seller Central credentials. Seller ID, MWS Auth Token, or SP-API Client ID/Secret depending on which generation of the connector you're using.
3. Scope and mapping — configure which flows to enable (orders, inventory, fulfilment, returns, settlements), map Amazon data to NetSuite record types, and handle any custom fields or subsidiary routing your NetSuite instance uses.
4. Sandbox testing — run the integration against real Amazon test orders and your NetSuite sandbox. Test MFN and FBA orders separately. Test a return. Run a mock settlement reconciliation.
5. Production cutover — phased go-live with monitoring. Watch the first two live order cycles closely before treating the integration as fully autonomous.

Timeline and Cost

Single marketplace (US Seller Central), standard configuration: 4–8 weeks implementation, $8,000–$20,000 with a certified partner. Celigo platform licensing adds $1,500–$3,000/month.

Multi-marketplace (US + EU + CA): 8–12 weeks, $20,000–$40,000+. Each additional marketplace adds its own order feed, settlement currency, and tax rules.

With Vendor Central (EDI): separate project, 6–10 additional weeks and $15,000–$30,000+ depending on EDI volume and trading partner requirements.

What moves the number most: SKU catalog complexity, NetSuite customisation depth (custom fields, subsidiaries, location-based inventory), settlement reconciliation approach, and whether multi-marketplace scope was scoped at the start or added mid-build.

Common Errors and Fixes

Unmatched orders — "Item not found for SKU: [X]"

SKU exists in Amazon but not in NetSuite at that exact value. Usually a case mismatch, trailing space, or a new product added to Amazon without being created in NetSuite first. Fix with a SKU reconciliation pass and add a monitoring alert for new Amazon SKUs that fail to match.

Duplicate Sales Orders from retry logic

If the flow times out mid-write and retries, a second Sales Order can be created for the same Amazon order. Add an idempotency check on the Amazon Order ID as an external ID field before creating a new record in NetSuite.

Fulfillment tracking not pushing to Amazon (MFN)

Usually caused by the item fulfillment being created in NetSuite before the integration's trigger fires, or by a carrier code that doesn't map to an Amazon-recognized carrier value. Check the Celigo flow error log for the specific failure and confirm the carrier mapping table includes all carriers your warehouse uses.

Settlement reconciliation journal entries are out of balance

Fee categories from Amazon (FBA fees, referral fees, advertising, returns) that aren't mapped to NetSuite account codes produce unbalanced journal entries. Map every fee type in the settlement before go-live — not just the main revenue lines.

FAQs

How does Amazon NetSuite integration work?

Amazon NetSuite integration connects Amazon Seller Central to NetSuite using Celigo's prebuilt Integration App. Orders sync from Amazon to NetSuite as Sales Orders. MFN inventory in NetSuite updates Amazon listing quantities. Fulfillment tracking pushes from NetSuite back to Amazon for merchant-fulfilled orders. Amazon's bi-weekly settlement reports reconcile against NetSuite for accurate channel P&L. FBA and MFN orders require different downstream logic in NetSuite.

Does Celigo integrate with Amazon?

Yes. Celigo has a dedicated Amazon Seller Central Integration App for NetSuite covering orders (FBA and MFN), inventory sync, fulfillment confirmation, returns, and settlement reconciliation. It uses Amazon's SP-API and is one of Celigo's most established connector pairs for ecommerce brands on NetSuite.

What is the difference between FBA and MFN in a NetSuite integration?

FBA (Fulfilled by Amazon) orders are shipped by Amazon's warehouses — the integration creates a Sales Order in NetSuite but no fulfillment action is taken on your side. MFN (Merchant Fulfilled Network) orders require your warehouse to ship — the integration creates the Sales Order and, when fulfilment is confirmed in NetSuite, pushes tracking back to Amazon. Both flow through the same integration but have different downstream processes.

How long does Amazon NetSuite integration take to set up?

A standard single-marketplace Celigo Amazon NetSuite integration takes 4–8 weeks from kickoff to production. Multi-marketplace setups run 8–12 weeks. The main timeline driver is settlement reconciliation design and testing, plus SKU consistency resolution — not the order sync itself, which is typically working within the first two weeks.

How much does Amazon NetSuite integration cost?

Implementation with a certified Celigo partner runs $8,000–$20,000 for a standard single-marketplace setup. Multi-marketplace or custom settlement logic projects run $20,000–$40,000+. Celigo platform licensing adds $1,500–$3,000/month. Total first-year cost is typically $25,000–$55,000 including setup and licensing.

What is Amazon settlement reconciliation in NetSuite?

Amazon pays sellers bi-weekly — a net figure that bundles order revenue, FBA fees, referral fees, advertising deductions, refunds, and adjustments. Settlement reconciliation maps this payout to NetSuite journal entries so your Amazon channel P&L is accurate. The key design decision is order-level vs summary reconciliation. Most mid-market teams use summary reconciliation for simplicity. This is the part of the integration that connector-only setups most commonly skip or misconfigure.

Can Celigo handle both Amazon Seller Central and Vendor Central?

Celigo's Amazon Integration App covers Seller Central. Vendor Central (first-party selling to Amazon) uses EDI — 850 POs, 856 ASNs, 810 invoices — which requires a separate EDI integration project. If you operate in both channels, expect two separate builds with different timelines and costs.

Entech Solutions is a certified Celigo partner with 200+ integrations delivered, including multiple Amazon–NetSuite builds across mixed FBA and MFN seller models. If you are scoping an Amazon NetSuite integration — or replacing one that is not handling settlements correctly — see our Amazon NetSuite integration service page or contact us to talk through your setup before committing to an approach.