Amazon Vendor Central
For brands selling to Amazon as a first-party (1P) supplier — where Amazon is the buyer and you are the vendor. Kayan pulls Purchase Orders from Amazon automatically and helps you reconcile remittance payments.
How this integration works
In a 1P Vendor relationship, Amazon issues Purchase Orders to you, and you fulfill them. Amazon then pays you on net terms (typically net 30 or net 60 after delivery confirmation). This is different from a Seller Central (3P) relationship, where you list products on the Amazon marketplace and handle fulfillment yourself — Kayan also supports Seller Central, as a separate connection with its own order and settlement flow. See below.
Kayan connects to the Amazon Selling Partner API (SP-API) to pull Standard Purchase Orders. For each PO, Kayan creates:
- A B2B sales order — linked to an auto-provisioned “Amazon (Integrated)” customer.
- A SKU mapping — Kayan matches Amazon ASINs to your internal product variants using the SKU field.
- An expected payment forecast — the anticipated remittance date (delivery date plus net terms) is added to your AR and cash-flow forecast.
Prerequisites
- An active Amazon Vendor Central account for the marketplace you sell into.
- Permission in Vendor Central to authorize third-party applications.
No developer account needed
Kayan is a published application on the Amazon Selling Partner Appstore, so you do not register an SP-API application or handle client secrets and refresh tokens yourself. You authorize Kayan from Amazon and the credentials are issued and stored encrypted for you.Connecting Amazon Vendor Central
You can start from either side — both routes end at the same Amazon consent screen.
- 1
From Kayan: open Settings → Integrations → Amazon
Choose your marketplace country and net terms, then click “Connect with Amazon”. Kayan defaults to the Egypt marketplace (ARBP9OOSHTCHU) on the EU endpoint — change the country if your Vendor account is in a different region.
- 2
From Amazon: click “Authorize now” on the Kayan listing
In Vendor Central, open the Appstore listing for Kayan and start the authorization. You will be asked to sign in to Kayan first so the authorization is attached to the right organization.
- 3
Approve the consent screen
Amazon shows exactly which data Kayan is requesting — Retail Procurement Orders. Approving returns you to Kayan with the connection active.
- 4
Map your SKUs
Kayan matches Amazon vendor SKUs to your product variants. Anything it cannot match is listed under SKU mapping; unmatched SKUs are not added to sales orders until you map them.
What the first sync covers
Amazon caps Purchase Order queries to a seven-day window, so the first poll picks up the last seven days of activity rather than a full historical backfill. Older orders need to be entered manually if you want them in Kayan.Purchase Order polling
Amazon does not push webhooks for Purchase Orders on the Vendor (1P) API. Kayan polls the SP-API on a scheduled interval to detect new and updated POs. Each PO is ingested idempotently — running the poll multiple times does not create duplicate orders.
New POs typically appear in Kayan within one polling cycle. Standard POs that are cancelled or changed in Vendor Central are reflected on the next poll.
Remittance reconciliation
Amazon does not provide an API endpoint for actual payment data for 1P Standard accounts. Instead, Kayan supports manual remittance reconciliation using the CSV export from Vendor Central's Remittances report:
- 1
Download the remittance CSV from Vendor Central
In Amazon Vendor Central, go to Payments → Remittances, select the payment, and export the CSV.
- 2
Upload to Kayan
In Kayan, go to Settings → Integrations → Amazon and upload the CSV under Payment reconciliation.
- 3
Review matches
Kayan matches each remittance line to a PO by the PO number. Matched lines show the expected vs. actual amount. Unmatched or variance lines are flagged for review.
- 4
Confirm the remittance
On confirmation, Kayan posts the settlement journal entry: Dr Cash + Dr Amazon Deductions = Cr Accounts Receivable. The PO forecast is marked as settled.
Deductions
Amazon routinely deducts co-op fees, chargebacks, and freight allowances from remittances. These are posted to a dedicated Amazon Deductions expense account (account 6760) so you can track them separately in your P&L.Region support
Kayan's Amazon Vendor integration has been tested with the Egypt marketplace (Vendor Central at vendorcentral.amazon.me). The SP-API endpoint used is the EU region (sellingpartnerapi-eu.amazon.com). Other marketplace IDs and regions can be configured manually during the connection setup — contact support if you need assistance with a non-Egypt marketplace.
Seller Central (3P)
Seller Central is a separate, independently connectable integration from Amazon Vendor Central — you can run either or both. Where Vendor Central is a 1P wholesale relationship with Amazon as your buyer, Seller Central is 3P: you sell directly on the Amazon marketplace and Amazon disburses your net proceeds on its own settlement schedule.
- Connect once — orders then sync automatically on a recurring poll. There is no manual PO acceptance step, unlike Vendor.
- Each order posts revenue and cost of goods sold, and draws inventory from the org's default location for merchant-fulfilled (MFN) orders, or an auto-provisioned “Amazon FBA” location for Amazon-fulfilled (AFN) orders.
- An order that references a SKU Kayan can't map is held, in full, in a “needs mapping” state, visible on the Seller Central sync status panel — it never partially ingests.
- Amazon's settlement reports import automatically on their own schedule and post per-order fee journal entries against an auto-provisioned Amazon aggregator — there is no CSV to download or upload, unlike the Vendor remittance flow.
Connecting Seller Central
Go to Settings → Integrations → Amazon, open the Seller Central tab, and connect with Amazon. Sync status, including any orders held for SKU mapping, shows on that same page.