Skip to content
ERP Builders

Integration · Commerce

Amazon ERP integration that reconciles to the penny

Selling on Amazon creates two hard problems for finance and operations: keeping stock accurate across FBA and your own warehouses, and reconciling settlements that net sales against dozens of fee types, refunds and reimbursements.
Integration flow from Amazon through an integration layer with queueing, mapping and retries into ERPSOURCEAmazonwebhook · RESTINTEGRATION LAYERValidate + mapQueue (idempotent)Retry w/ backoffDead-letter + alertSYSTEM OF RECORDERPorders · stock · ledgerINBOUND (ORDERS, CUSTOMERS)OUTBOUND (STOCK, STATUS, INVOICES)

Overview

What this integration is for

We integrate Amazon through the Selling Partner API (SP-API), using order data, inventory reports and settlement reports to keep the ERP accurate.

01Data

What data syncs, and in which direction

Data synchronised between Amazon and the ERP
EntityDirectionNotes
Orders (FBM)App → ERPMerchant-fulfilled orders imported for picking and shipping.
Shipment confirmationERP → AppTracking and carrier posted back for FBM orders.
Orders (FBA)App → ERPFBA sales recorded to deduct stock held at Amazon and record revenue.
Inventory levels⇄ BothFBM quantities pushed to Amazon; FBA inventory pulled from reports.
Inbound FBA shipmentsERP → AppTransfers to Amazon fulfilment centres tracked as stock in transit.
Settlements & feesApp → ERPSettlement reports split into sales, fees, refunds and reimbursements.

02Use cases

Common use cases

01

FBA inventory visibility

Stock at Amazon shown as a separate location in the ERP.

02

Settlement reconciliation

Payouts matched to orders and fees automatically.

03

Multi-marketplace selling

Several Amazon regions alongside other channels.

03 — Architecture

API architecture

SP-API is rate-limited per operation, so the integration combines event notifications with scheduled polling of orders and report requests. Reports (inventory, settlements, returns) are requested, downloaded and parsed asynchronously.

Settlement data is posted to a clearing account in the ERP, with fees mapped to expense accounts, so the bank payout reconciles against a single balance.

Integration flow from Amazon through an integration layer with queueing, mapping and retries into ERPSOURCEAmazonwebhook · RESTINTEGRATION LAYERValidate + mapQueue (idempotent)Retry w/ backoffDead-letter + alertSYSTEM OF RECORDERPorders · stock · ledgerINBOUND (ORDERS, CUSTOMERS)OUTBOUND (STOCK, STATUS, INVOICES)

04Reliability

Authentication, errors and retries

01

Authentication

A registered SP-API application authorised by the seller account through Login with Amazon (LWA) OAuth, with refresh tokens stored securely and access tokens refreshed automatically.

02

Error handling

Throttling responses are expected and handled. Orders with unmapped SKUs or ASINs are held for review. Report parsing errors are logged with the report ID for reprocessing.

03

Retry strategy

Operation-specific rate limits are respected with backoff and token-bucket pacing. Failed report downloads are retried; settlements are reprocessed idempotently by settlement ID.

05 — Data mapping

Field mapping essentials

Field mapping between Amazon and the ERP
AmazonERP
AmazonOrderIdSales order reference
SellerSKU / ASINProductSKU mapping table per marketplace
MarketplaceIdSales channel / company
Settlement fee typesExpense accountsMapped once, applied automatically
FulfillmentChannelWarehouse (own vs FBA)

06 — Automation

Automation opportunities

  • Post settlement journals automatically when reports become available
  • Create replenishment transfers to FBA based on sales velocity
  • Alert on stranded or unfulfillable FBA inventory
  • Flag reimbursement-eligible lost or damaged units for claims

07 — Security

Security considerations

Refresh tokens are stored encrypted. Amazon's data protection policy restricts how buyer personal information may be stored; we design data retention to comply with it.

Related

Where this integration fits

Insights

Related reading

ERP Integrations2 min read

RFID Integration with Odoo: A Practical Architecture

How to integrate RFID readers with Odoo inventory: middleware design, mapping EPCs to products and serials, receiving and counting flows, performance and what to build vs buy.

FAQ

Frequently asked questions

Can the ERP manage FBA stock?

Yes, as a separate warehouse location updated from Amazon inventory and order data.

How are Amazon fees recorded?

Settlement reports are parsed and fees posted to mapped accounts, reconciling to the payout.

Do you support multiple marketplaces?

Yes, with per-marketplace mapping for currency, tax and SKUs.

Next step

Connecting Amazon to your ERP?

Tell us your volumes, channels and data rules. We will outline the architecture and the risks before anything is built.