Connecting Amazon

Amazon uses a Bring-Your-Own App model — each tenant registers their own SP-API application and provides pre-issued credentials. There is no browser OAuth redirect.

Prerequisites

1

In Seller Central → Apps & Services → Develop Apps, create a new SP-API developer application. Copy your LWA Client ID and LWA Client Secret.

2

Authorize the app in Seller Central to generate an LWA Refresh Token. The token is displayed once — copy it immediately. It is not recoverable.

3

Note your Seller ID (also called Merchant ID) from Seller Central settings. Select the SP-API region that matches your marketplace: EU, NA, or FE.

Amazon uses three separate SP-API regions — EU (sellingpartnerapi-eu.amazon.com), NA (sellingpartnerapi-na.amazon.com), and FE (sellingpartnerapi-fe.amazon.com). Each region requires separate credentials and a separate configuration row.

Configuring credentials in Sugibana

1

In the Sales Channels page, click Configure on the Amazon region card (EU, NA, or FE). Enter your Seller ID, LWA Client ID, LWA Client Secret, and Refresh Token.

2

Select ACTIVE status and click Save Credentials. The secret and refresh token are AES-encrypted immediately — they are never stored in plaintext or returned to the client.

3

After saving, use the Marketplace toggles to enrol specific marketplaces (e.g. Amazon.de, Amazon.co.uk) for order sync and stock push independently.

4

Click Refresh enrollment to verify Seller Central participation. A green Active badge on each marketplace row confirms the connection is working.

You can configure all three regions independently. Only regions where you actively sell need to be configured.

Order import

1

Orders are polled every 5 minutes via the SP-API Orders endpoint using LastUpdatedAfter. No manual action is required once the marketplace toggle is On.

2

Verify orders are appearing in the Orders page. New orders in Amazon Seller Central typically appear in Sugibana within 5–10 minutes.

Amazon status mapping: Unshipped / PartiallyShipped / Pending → Unshipped; Shipped → Shipped (reservation converted); Canceled → Cancelled (reservation released).

Stock push

1

Enable stock push per marketplace using the Stock toggles on the region card. The Stock toggle is per-marketplace and independent of the Order sync toggle.

2

Once enabled, any change to a SKU's available stock triggers an outbox event which is routed to the SP-API Listings Items API via the adapter_channel_sync n8n workflow. Verify pushes appear in marketplace_stock_pushes.

Never call Amazon SP-API inventory write endpoints directly from application code. All stock changes must flow through the outbox pipeline in n8n.

LWA token rotation

1

LWA access tokens are cached with a 5-minute buffer and expire after 1 hour. The auth sub-workflow refreshes automatically — no manual action is needed under normal operation.

Amazon LWA refresh tokens have no hard expiry. Annual rotation is recommended as a security practice. A rotation deadline is tracked in the Incidents panel when applicable.