FBA and FBM orders, inventory, inbound shipments, and settlement reports flowing into NetSuite so the marketplace is a channel, not a second set of books.
Amazon brings orders, and it brings its own way of doing things: Fulfilled by Amazon stock sitting in Amazon’s warehouses, settlement reports every two weeks that net fees, refunds, and reimbursements against sales, and returns that arrive before anyone has seen the order. Left unconnected, finance reconciles settlements by hand and operations never quite knows how much FBA stock is really available. A properly built integration treats Amazon as one channel in NetSuite: orders post, FBA becomes a location, inbound shipments become transfers, and every settlement lands as a deposit that matches the bank.
NetSuite Connector. Oracle’s own connector covers Amazon alongside Shopify, eBay, and Walmart, with standard order, inventory, and fulfillment flows. It is the lowest-friction route for a seller with one marketplace account and conventional processes.
Celigo. The deepest prebuilt Amazon library: FBA and FBM orders, inventory by fulfillment channel, inbound shipment tracking, returns, and settlement-report reconciliation with fees broken out by type. The usual choice for sellers on several marketplaces or several Amazon regions, and for anyone who also needs Shopify or a 3PL on the same NetSuite account.
Custom build on Amazon’s Selling Partner API. Full control and ownership, at the cost of building and maintaining it, including keeping pace with Amazon’s API changes. It makes sense when the seller’s process is unusual or a single flow, typically settlement posting, needs to sit alongside a connector.
Consule recommends based on your marketplaces and regions, FBA versus FBM mix, order volume, and who will own the integration after go-live.
Settlements posted as one number. Amazon pays the net of sales, fees, refunds, and reimbursements. If the integration posts sales and ignores the settlement report, finance is left explaining the difference to the bank every fortnight. Settlements are designed in from the start.
FBA stock treated as your stock. Inventory in Amazon’s warehouses is not available for your other channels, and it moves on Amazon’s timetable. It needs its own location in NetSuite, fed by Amazon.
ASINs that drift from SKUs. Variations, bundles, and relisted products break a naive one-to-one mapping. Consule maps ASIN to SKU explicitly, including kits.
Every flow, field by field, in a mapping document your team signs off: how FBA and FBM orders post, which location holds FBA stock, how ASINs map to SKUs and kits, and how each settlement line type is accounted for.
Connector configured or scripts written to the mapping, in a sandbox, with error handling and alerting so a failed record is visible within minutes rather than at month-end.
Live-shaped cases: an FBA order, an FBM order, a multi-unit return, an inbound shipment, and a real settlement report reconciled to the penny. Finance signs off before go-live.
Cutover timed around your business cycle, hypercare for the first week, and ongoing monitoring and change requests under the Consule CARE program.
Selling on Amazon from a plant or a warehouse?
Consule’s clients are manufacturers and distributors, which shapes the integration: FBA replenishment competes with wholesale orders for the same stock, kits and bundles have to be costed correctly, and the same NetSuite account usually runs Amazon, a Shopify store, EDI customers, and a 3PL. We design the Amazon flow as one part of that picture.
Not out of the box. Oracle’s NetSuite Connector and Celigo both provide prebuilt Amazon integrations built on Amazon’s Selling Partner API, and custom integrations are possible. All need mapping decisions and configuration.
The settlement report is broken into its components: product sales, shipping, fees by type, refunds, reimbursements, and adjustments. Sales are matched to the orders already posted, fees hit expense accounts, and the net posts as a deposit that matches the bank transfer.
As a dedicated location. Inbound shipments to Amazon post as transfer orders, Amazon reports on-hand quantities back to that location, and FBA orders consume from it. Your other channels never see FBA stock as available.
Yes. Each marketplace region maps to its own channel and, with OneWorld, to the right subsidiary and currency. Celigo supports multiple Amazon regions; custom builds can as well.
