The Amazon adapter is built for sellers who want Amazon operations visible inside the CRM, not in a separate marketplace tab. It connects through Login with Amazon, stores encrypted per-seller SP-API tokens, and uses only non-PII roles. The implementation is complete for the EU region and open to connect; the adapter is in beta.
Beta status and scope
The adapter works — you can connect a seller account today. OAuth, connection testing, order import, product import, FBA stock reference, price/MFN-stock push, shipment confirmation, MFN cancellation, Buy Box pricing and catalog enrichment are implemented. Beta: available to connect today; the channel’s capabilities are still being refined. Every write direction to Amazon is off by default and is armed by the workspace owner after a dry-run preview. Buyer PII is intentionally out of scope: names, addresses and messages are not requested.
Real workflows covered
Orders become CRM orders
Every 15 minutes the adapter checks Amazon for updated orders, imports the order, line items, marketplace status and order total into the shared CRM order pipeline, and updates existing orders idempotently instead of duplicating them.
Catalog stays connected by SKU
Amazon listings can be imported into the CRM catalog in one click. Existing SKUs are linked; new SKUs become draft CRM products with title, listing price, main image and ASIN, so the team can review them before they sync back.
CRM can update Amazon
For products already listed on Amazon, the CRM can push current prices and MFN stock back to matching listings by SKU. FBA stock is never overwritten by the CRM; it is read from Amazon as a reconciliation reference.
Capabilities, row by row
The same matrix the CRM shows inside the workspace — nothing here is promised that the adapter does not do.
- Orders arrive in the CRMWorks
New and updated orders are imported with line items, amounts and the platform's order id.
Polled every 15 minutes through the Orders API (v2026-01-01). Amazon offers no order webhook, so a new order can take up to 15 minutes to appear.
- Order status follows the platformWorks
When the platform changes an order's status or payment, the CRM order follows — until a manager sets the status by hand.
Amazon's fulfillment status is mapped to the CRM status (unshipped → confirmed, shipped → shipped, cancelled or unfulfillable → cancelled) and a payment row is recorded from the order total.
- CRM status goes back to the platformWith a condition
Marking an order shipped or cancelled in the CRM is reported to the platform.
Merchant-fulfilled (MFN) orders only: “shipped” with a tracking number confirms the shipment on Amazon, “cancelled” sends a cancellation feed. FBA orders are shipped and cancelled by Amazon itself. Both directions are off by default and armed by the workspace owner.
- Parcel trackingWith a condition
Carrier and tracking number for the shipment are visible on the order.
Amazon's order model ends at “shipped” — Amazon reports no parcel movement. Tracking comes from the CRM's own carrier integrations: Nova Poshta, DHL, UPS, SAT and Delivery update CRM-created shipments automatically; other carriers stay untracked.
- Delivery confirmedPlatform does not expose it
The CRM learns that the buyer has received the parcel.
Amazon has no “delivered” order status and no buyer receipt confirmation anywhere in its Selling Partner API; the shipment-tracking API needs a role (Amazon Fulfillment) the app does not hold.
- Buyer messages in the InboxPlatform does not expose it
Questions buyers send through the platform appear in the unified inbox and can be answered from the CRM.
Amazon's Messaging API can only SEND templated messages — no operation reads what a buyer wrote. Amazon conversations can never reach the inbox; answer them in Seller Central.
- Buyer contact detailsNot built yet
Buyer name, phone, email and address are stored on the order and the customer card.
Deliberately not requested: buyer data would put the adapter under Amazon's restricted-data programme. Orders arrive with an Amazon order id and a buyer alias only; the buyer's name and address stay in Seller Central.
- Import listings into the catalogWorks
Existing listings are pulled into the CRM catalog, matched by SKU or barcode, with a review queue for the rest.
Seller listings are imported through the Listings Items API, matched by SKU, capped per run with an honest “truncated” result; the rest waits in the review queue.
- Price and stock pushWorks
CRM price and stock are pushed to the channel's existing listings.
Off by default; the owner arms it after a dry-run preview. Price is pushed only when the product's price-list currency matches the marketplace; stock only for merchant-fulfilled listings — FBA quantity stays Amazon-managed and is shown as a read-only reference. A stock change in the CRM reaches Amazon within seconds (real-time fan-out); the hourly sync remains the reconciliation.
- Create listings from the CRMWith a condition
A CRM product can be published to the channel as a new listing.
Publishes CRM products to Amazon: one at a time from the product card, or a selection from the channel page — by warehouse, brand or category, up to 100 at once. Amazon first validates each listing and answers in its own words without creating anything; only the products it accepted are published, and only after a confirmation. Off by default — the owner picks the marketplace, sees what would happen, and only then turns it on. One condition: the product's category must carry an Amazon product type, because that is the schema Amazon validates against and the CRM will not invent one. A product with no barcode is accepted only under a separate approval the seller requests in Seller Central; EU stores also need the account's GPSR manufacturer details.
- Returns and refundsNot built yet
Buyer returns and refunds initiated on the platform are recorded on the CRM order.
Return reports exist in the Reports API but need Amazon's restricted roles (Direct-to-Consumer Shipping / Amazon Fulfillment), which the app deliberately does not request — they would pull the adapter into the restricted-data programme, like buyer contacts. Returns are handled in Seller Central.
- Channel analyticsWith a condition
Sales, prices and competition on the channel are visible inside the CRM.
Buy Box status, competitor prices and the Featured Offer Expected Price are checked on demand from a linked product. Sales metrics (Sales API) are reachable but not built yet.
How a seller would use it
- 1
Connect the seller account
Create an Amazon adapter in Settings → Integrations → Platform adapters, then authorize the seller account through Amazon Seller Central.
- 2
Verify access
Run Test connection to confirm that the CRM can see the seller id, region and marketplaces before turning on operational sync.
- 3
Run controlled syncs
Use product import, inventory/catalog sync and per-product Amazon actions from the CRM, then move to live sync only after the seller verification pass.
Frequently asked questions
Does Obriym import buyer personal data?
No. The Amazon adapter imports non-PII order data only: order id, statuses, line items and totals. Buyer names, addresses and messages are not requested.
How is Amazon access protected and retained?
Every CRM account requires two-factor authentication. Amazon tokens are encrypted, seller authorization must be renewed every 365 days, disconnect erases the token immediately, and non-PII Amazon records are deleted after 18 months.
Can the CRM create new Amazon listings?
No. The current adapter updates existing Amazon listings matched by SKU. Creating brand-new listings on Amazon is not built yet.
Can the CRM read messages Amazon buyers send me?
No — and not by our choice. Amazon's SP-API only lets an app send pre-defined messages to buyers; there is no operation that reads buyer-to-seller messages. Amazon conversations stay in Seller Central and never appear in the CRM inbox.
Does CRM stock overwrite FBA stock?
No. FBA stock is read from Amazon for reconciliation. The CRM only pushes stock for merchant-fulfilled listings.
What happens to imported Amazon products?
Existing SKUs are linked to their Amazon listing. New SKUs are created as draft CRM products so the team can review title, price, image and ASIN before activation.
Is this available for live sellers now?
Beta: available to connect today; the channel’s capabilities are still being refined.
Review Amazon inside the same sales workspace
Orders, product links, stock references, prices and fulfillment actions stay visible next to the rest of your CRM work.
Start for free