Amazon is rarely the first channel a growing brand adds, and it’s rarely the simplest to reconcile. Whether you sell through Seller Central, ship wholesale to Amazon through Vendor Central, or run both at once, the order data itself isn’t the hard part of this integration — Amazon’s settlement reports are.
Two programs, two different data models
Seller Central and Vendor Central aren’t variations on the same integration. They’re two different relationships with Amazon. Seller Central orders are individual marketplace transactions you fulfill (or Amazon fulfills for you). Vendor Central orders are wholesale purchase orders Amazon issues to you as a supplier, complete with its own acceptance windows and chargeback rules. If you run both programs, they get scoped and mapped separately in NetSuite: one behaves like a marketplace sales channel, the other behaves like a large B2B customer with its own PO and invoicing workflow.
Settlement reports are where the general ledger goes wrong
Amazon doesn’t pay out order by order. Each settlement period, it bundles referral fees, FBA fulfillment fees, storage fees, refunds, and reserve holds into a single deposit. If that deposit lands in NetSuite as one lump sum against revenue, your gross sales, fee expense, and refund lines all end up misstated — even though the net cash figure looks fine. Doing this correctly means unwinding the settlement report line by line: referral fees post to a fee account, FBA charges post to fulfillment expense, refunds hit a refund account, and reserves get tracked as a holdback rather than disappearing into the deposit total.
FBA inventory isn’t the same thing as warehouse inventory
If you use Fulfilled by Amazon, the on-hand quantity Amazon reports doesn’t always reflect what’s actually sellable. Inbound shipments still in transit, units placed in reserve, and stock pending disposal can all skew the number Amazon shows you. A NetSuite sync that treats Amazon’s FBA on-hand figure as ground truth will eventually cause an oversell in one direction or a false stockout in the other — especially for merchants sharing the same inventory pool between FBA, merchant-fulfilled orders, and other channels. We build reconciliation logic that checks FBA-reported inventory against actual movement rather than trusting it outright.
Returns don’t map one-to-one with orders
Amazon returns rarely mirror the original transaction cleanly. A customer can return part of a multi-item order, Amazon can issue a refund with no physical return at all, or a return can show up weeks after the settlement period that contained the original sale. The integration needs a returns path that doesn’t assume symmetry between what shipped and what comes back — and doesn’t silently drop the refund into whatever period it happens to land in.
Brands running both programs need a consolidated view, not two silos
Some brands sell direct to consumers through Seller Central while also supplying Amazon wholesale through Vendor Central for the same product line. When that’s the case, the two data streams still need to land somewhere finance can see them together — total Amazon revenue across both programs, total Amazon-related fees, total Amazon returns — even though the underlying transaction types are structurally different in NetSuite. We typically keep the sales order and PO workflows separate at the transaction level but roll both up to shared reporting classes or segments, so “how is Amazon doing” has one answer instead of two half-answers that have to be added together manually every time someone asks.
How we scope it
Before touching API credentials, we ask which programs you actually run, how FBA and merchant-fulfilled inventory overlap with your other channels, and how your team currently books Amazon fees in the chart of accounts. Vendor Central customers get a separate conversation entirely, since PO acceptance and chargebacks behave nothing like Seller Central’s referral-fee model. That scoping step matters more here than on most marketplace integrations, because Amazon’s settlement structure is genuinely more layered than a typical order feed — and it’s the part that determines whether your books actually close cleanly each month, not just whether orders show up in NetSuite.
If you’re running Amazon alongside other channels and want the specifics for your setup, the full Amazon integration guide covers what syncs, what doesn’t, and how Vendor Central is handled separately from Seller Central. Or get in touch if you’re ready to scope it.