So, when you’re starting a growing Amazon business on NetSuite, the truth is that the integration is the simple part. The problems that always crop up at scale are always the data design on top of it — mapping settlements into your GL, how the inventory is exchanged between FBA and FBM, and how a refund is treated when it arrives 3 weeks after the settlement closes.

If done correctly, your integration can become a growth machine. If you get it wrong, you will be reconciling spreadsheets at the end of each month, rather than making decisions.

Why Most Integrations Break Before They Scale

Amazon’s payment system is not ERP-friendly. All referral benefits, FBA pick and pack, advertising offsets, refunds and reserves are waived and all earnings are paid out as a nett amount, on a bi-weekly basis. However, most ERP applications will only mark up the sales at the order level. The net outcome is that you will have a recurring issue where you feel you are making money, but you’re not.

A 2023 report from Accenture entitled ERP Integration Horror Stories reveals that more than 55% of mid-market ecommerce companies have experienced “persistent reconciliation gaps” as their greatest challenge after ERP goes live. It’s nothing to do with the amount of data. It’s an accounting model problem.

In low order volumes, teams are using paper to cover this up. Once the volume is increased (for example, 5,000 orders per month or more), those modifications become work part-time, and the data is so messy that it’s not worth using for serious business decisions.

This can be exacerbated by inventory drift. FBA stock is stored and shipped by Amazon, FBM stock is stored in your own warehouse. If there are no sync rules that clearly define the boundaries of the two, then both NetSuite and Amazon will display different numbers, and no one will have a reliable answer.

What a Properly Designed Integration Actually Looks Like

There are four questions to consider before touching a connector or middleware platform:

1. Is it individual Orders or a Summary of Orders by Settlement Period?
2. Will you be tracking buyers as individuals or will you be tracking an “Amazon Customer” record?
3. Who owns the inventory in NetSuite vs. Amazon?
4. What will the results of the Amazon settlements be when they are entered into NetSuite?

These are not questions of technique. They’re accounting and operational design decisions, and all of your integration issues that you will see downstream are a reflection of whether you were answering them on purpose or because you didn’t.

The settlement accounting model is the most important of these. When it is done correctly, this works as follows: You import the Amazon settlement report, add gross sales revenue as a separate GL line item in the clearing account, add refunds as a separate GL line item in the clearing account, add the FBA fees as a separate GL line item in the clearing account, and then match the net deposit to your bank feed. Each settlement will reset the clearing account to zero. Real margins are shown in your P&L. A bank reconcile will run automatically.

If you don’t have this model, your revenue line is inflated, your cost lines are deflated and your finance team is having to do a lot of manual calculations to work out Amazon’s fee model every fortnight.

Choosing the Right Integration Approach

The three viable alternatives are middleware (Celigo, Boomi, MuleSoft), a full custom integration or a combination of both. There’s no right or wrong answer — the choice depends on your stage of revenue and complexity of your operations.

The middle-ware tools are the easiest to deploy, and work well with common order and inventory management. The problem with them is that they lack settlement logic. The majority of connectors were designed to work with order sync, not with Amazon’s settlement accounting model, so you’ll most likely need custom scripting on top of the middleware you use — or get back to manual reconciliation.

Custom integrations allow you to have complete control over the data mapping, error handling, and accounting logic. The best fit is for enterprises that are large in size and/or have multiple entities and currencies. There’s a trade-off, of course, which is that you’ll have to pay more up front and you’ll always need the technical ownership.

For brands with $2M to $15M in revenue, a hybrid solution where the orders are handled by the middleware and the settlements by custom logic is a good fit. It doesn’t over-engineer but does get the job done.

According to a 2022 NetSuite partner survey conducted by SuiteWorld, companies employing hybrid integration strategies for marketplace connections experienced 40% quicker monthly close cycles than those relying on off-the-shelf middleware integration. The key differentiator mentioned was the settlement accounting layer.

Inventory Sync: The Part That Gets Ignored Until It Is Too Late

FBA and FBM inventory must be viewed as two distinct pools, and must be synced with their own set of sync rules. For FBM, NetSuite needs to be the lead system — it’s this that pushes the available quantity to Amazon in near real time. Amazon is the trusted leader in the FBA market and all movements in and out of Amazon (inbound and outbound shipments, removals, and damaged stock) should be returned to NetSuite on a regular batch schedule.

The most frequent structural error is to run both on the same shared inventory pool. It can result in the creation of phantom availability, overselling and the eventual degradation of your Amazon seller metrics due to a cancellation rate. One such brand that has a recurring stockout issue, but not increased safety stocks, resolved it recently by untangling their stock management logic in integration and using NetSuite as the FBM quantity master. The number of cancellations decreased and their seller rating increased in 90 days.

Error Handling Is Not Optional

There is no neat integration that works for all time. APIs time out. SKUs go missing. Settlement files are frequently in non-standard formats.Settlement files come in strange formats. It returns post following periods of settlement. Brittle integration is an integration that you can see what broke, know why, and repair without manual data clean up, while scalable integration is an integration that you cannot see what broke, you don’t understand why, and you don’t fix it without manual data clean up.

The very least, your integration should include idempotency keys to avoid redundant order creation, an exception dashboard to identify failed syncs, missing records, and settlement variances in a single location, and not an infinite number of retries. If you are not getting a diagnosis from your current system, then suspect that something is amiss.

Decision Framework by Revenue Stage

Under $1M: Begin with middleware. Make it simple, but don’t postpone the settlement accounting model – it’s much harder to add correctly than do it right from the beginning.

$1M to $10M: $10M or more: Adopt a blended strategy. Address settlement accounting and inventory logic before volume does. This is where manual workarounds came to a halt.

$10M and above, or Multi-entity: Invest in a solution that is heavily tailored or a custom solution of $10M or more. The trade-offs for a badly designed integration — lost weeks of finance team time, reporting mistakes and late closes — always outweigh the cost of a well-designed integration. Gartner’s 2024 ERP Integration Market Guide states that companies that deploy purpose-built integration layers for marketplace data experience 30% lower total cost of ownership over five years, relative to companies that only deploy generic iPaaS connectors.

How to Know If Your Integration Is Working

The answer to that question is a simple test – are the Amazon payouts the same as NetSuite before adjustment? Is the inventory the same in all systems? When you’ve left go-live is it getting to your monthly close more quickly, or not? Are your team able to see errors in real-time and deal with them without data reconciliation project?

If it fails the answer to any of those is no, the systems are linked, but the integration is not.

The aim was not to connect two platforms! It was designed to create a process that is running clean, growing with your business and providing the information you need as you make decisions. That’s the only one worth building.