Importing Amazon orders into SAP Business One: your options
Amazon orders reach SAP Business One by one of four routes: exporting order reports from Seller Central and importing them into the ERP, a ready-made SP-API connector for SAP B1, an iPaaS platform, or an integration that pulls orders through the Amazon Selling Partner API (SP-API) and creates Sales Orders via the Service Layer or DI API, standalone or inside an integrated commerce platform. Which fits depends on order volume, fulfillment model (FBA or FBM), and how cleanly items, sales tax, and fees must land in the ERP.
Why do Amazon orders belong in the ERP?
A distributor selling through a B2B store and on Amazon has two order sources but one system of record. Inventory, accounting, and fulfillment meet in SAP Business One; until Amazon orders arrive there, someone re-keys them: slow, error-prone, unworkable at volume.
Then there is inventory. If the same SKU sells in your store and on the marketplace, B1 has to see both channels or one sells stock the other has committed. Automated import is the precondition for running Amazon cleanly beside your direct business, just as the store needs the platform’s ERP integration.
How do Amazon orders get into SAP Business One?
All four have their place. They differ in effort, timeliness, and how much Amazon-specific logic (fees, sales tax, FBA inventory) they handle cleanly.
| Approach | Strengths | Limits | Typical use |
|---|---|---|---|
| Seller Central reports (CSV) | Available today, no project; order reports load into B1 through the Data Transfer Workbench (DTW) | Delayed and error-prone; SKU and tax mapping must be right every run; no status feedback to Amazon | A few orders per week, marketplace trial |
| Ready-made SP-API connector for SAP B1 | Proven standard from several vendors; order pull, Sales Order creation, and ship confirmation prebuilt | License and maintenance fees; edge cases in tax, fees, or multi-warehouse logic need customization | Standard Amazon operations with meaningful volume |
| iPaaS / middleware | Amazon, store, and other channels on one platform; mapping maintained centrally | Another system to run and pay for; one more link that can fail | Multichannel landscapes: Amazon plus store, PIM, or 3PL |
| SP-API integration, custom or platform-integrated | Full control over mapping, tax logic, and error handling; official interfaces on both sides (SP-API, Service Layer/DI API) | Development project with ramp-up; operations and monitoring to plan | High volume, own processes, requirements standard connectors do not cover |
The same routes apply to your own store, compared in Connecting SAP Business One to an online store.
How the order import actually runs
Pull orders
The integration polls the SP-API Orders API on a schedule. Import only once an order is Unshipped (payment confirmed); Pending orders lack reliable amounts.
Map SKUs
Every Amazon SKU maps to a B1 Item Code, most robustly via a maintained table (SKU/ASIN ↔ Item). Unmapped lines go to an exception queue, never silently dropped.
Decide on the Business Partner
Common practice: one collective Business Partner per marketplace (say, “Amazon.com”) with the ship-to per order. One BP per end customer bloats master data and pays off only for Amazon Business orders needing company invoices.
Create the Sales Order in SAP Business One
The Sales Order is posted via Service Layer or DI API with the Amazon order ID as customer reference (which also blocks duplicates), prices as sold including shipping, and the right tax treatment: in most states Amazon collects and remits sales tax as marketplace facilitator, and the tax code must mirror that.
Confirm shipment and status
For FBM orders, ship confirmation and tracking go back to Amazon once the Delivery is posted; late confirmations hurt seller metrics. For FBA, Amazon ships and the import serves accounting and inventory.
Reconcile settlements and fees separately
Amazon pays out in batches and deducts referral, FBA, and other fees first. Treat this as its own process: settlement reports are matched to the payout period’s orders and posted against fee accounts, or ERP revenue and bank deposits never reconcile.
Where Amazon–B1 projects get stuck
Pulling orders is rarely the problem; the edges are. Four points to settle early:
And what does this have to do with the CS Order Suite?
The CS Order Suite, our B2B e-commerce platform, connects your own store to SAP Business One through a native adapter: items, inventory, customer-specific prices, and orders move with no intermediate system. The building blocks an Amazon import needs (item mapping, Sales Order creation via Service Layer or DI API, status feedback) run in production there.
We do not sell an off-the-shelf Amazon connector. If Amazon is your only channel into B1, a standard connector is the pragmatic choice. We fit when a B2B store and the marketplace are served from one B1 company and the import becomes part of an integration project.
Amazon and SAP Business One: short answers
Connecting Amazon and SAP Business One?
Bring your B1 setup, order volume, and fulfillment model; we look at which route makes sense for you. Pricing is something we cover personally.
Book a demo
CS Management & IT-Beratung GmbH
Ulrichsberger Str. 17 · 94469 Deggendorf · Germany