SAP S/4HANA & Amazon Integration

Yes. The connector supports both fulfilment models. For FBM, it pushes shipment, tracking and carrier status back to Amazon. For FBA, it creates an automatic Stock Transfer Order in SAP S/4HANA when goods land in an Amazon warehouse, simulating a physical-to-virtual plant transfer, and pulls the daily FBA Inventory Report back into SAP.

APPSeCONNECT connects to SAP S/4HANA through its OData, BAPI and IDoc interfaces, with BAPI calls made via RFC. Amazon orders are created in SAP S/4HANA through BAPI or IDoc, depending on your setup. The connector works with SAP S/4HANA on-premise, Private Cloud and Public Cloud landscapes.

No. APPSeCONNECT provides a public Amazon Marketplace app, so you authorise access instead of registering your own SP-API developer profile. All communication with Amazon runs through Amazon SP-API with OAuth 2.0, and the connector respects SP-API rate limits by batching calls and applying adaptive back-off.

Yes. Amazon sandbox accounts can be used to test the integration before go-live. User acceptance testing often works best with live test data, because it reflects your real ASIN mappings, fees and fulfilment flows. The integration guide's setup notes cover SAP connection setup, SP-API readiness and field mapping.

Yes. For FBM orders, the connector can fetch customer delivery details when shipping labels and documents must be prepared in SAP S/4HANA. Those details support shipment documents, and the connector then pushes shipment, tracking and carrier status back to Amazon so the order closes correctly in Seller Central.

APPSeCONNECT posts each Amazon fee, FBA charge and refund as Condition Types on the SAP sales order. Fees, commissions and refunds can be kept as separate heads for clearer profitability checks, and a settlement-by-settlement reconciliation report shows finance the matched and unmatched lines in one view.

The connector respects SP-API rate limits by batching calls, applying adaptive back-off and using Amazon notifications to reduce unnecessary API calls. Failed records retry automatically on a schedule you choose, and CloudWatch monitoring alerts your team before a problem becomes a missed order, which matters most during peak seasons.

You choose. Data can sync on a schedule, or be triggered by events through Amazon's Notification API and SAP IDocs. Inventory moves from SAP S/4HANA to Amazon Seller Central in near real time, while the daily FBA Inventory Report is pulled back into SAP to keep available stock accurate.

Every record is tracked in Sync Info. Failed entries retry automatically and can be resynced safely, and email alerts surface anything still unresolved. CloudWatch monitoring also flags issues early, so your team can fix a mapping or data problem before it becomes a missed order or an unreconciled settlement.

The Amazon integration is built for SAP S/4HANA on-premise, Private Cloud and Public Cloud. In each case the connector uses SAP's OData, BAPI and IDoc interfaces. One tenant can handle many SAP company codes and many Amazon marketplaces, so the integration scales across legal entities as you grow.

Customers, products and ASINs, pricing and promotions, inventory and FBA stock, sales orders, shipments, and fees and settlements all sync. New Amazon orders create a default or one-time customer in SAP S/4HANA, and ASINs map to the SAP Item Master once, so later product and price changes publish to Amazon automatically.

The integration uses Amazon SP-API with OAuth 2.0 through APPSeCONNECT's public Amazon Marketplace app, so you don't need to register as an SP-API developer. Orders are picked up through SP-API or the Notification API on a scheduled or triggered basis, then checked before they map to SAP S/4HANA fields.