Amazon + CycleForge
Amazon orders arrive through the Selling Partner API and land in the same queue as every other channel — so the floor works one list, not one list per marketplace.
Orders, with the detail the floor needs
Sold orders sync from Seller Central with their SKU and FBA item detail attached, which is the part that decides whether a picker can actually find the unit. They land in the outbound queue alongside eBay, Shopify, and Square orders, rendered identically — the channel becomes a label on the row rather than a separate workflow to learn.
Buyer address detail is fetched deliberately, because shipping a physical box requires it. Amazon treats that data as restricted, and CycleForge requests it only where fulfilment genuinely needs it.
Several seller accounts, one queue
Organizations frequently run more than one Amazon account — a main storefront, a liquidation account, a second marketplace region. Each is connected and tracked separately, and a sync pass walks all of the active ones.
Failures are reported per account rather than collapsed into one status. If one account needs re-authorizing, you find out which one, and the others keep importing.
Health checks that actually check
Connection health is not a guess at whether stored credentials look present. For each active account, CycleForge exchanges the stored refresh token and makes a real call to Amazon — a cheap marketplace-participation probe that touches no customer data. If the token has been revoked or the grant has lapsed, the connection reports unhealthy with the account name and the actual error.
What it does not do
- It does not create or manage listings. The Amazon connection is an order channel. Listing and catalog work stays in Seller Central.
- It does not push stock or pricing back to Amazon. Quantities live in your inventory backend; CycleForge does not currently write them out to the channel.
- It does not manage FBA inbound shipments. FBA items are recognised on orders, but creating and routing FBA shipment plans is separate work in CycleForge, not something the SP-API connection performs for you.
Connecting it
Connection is OAuth against your own Seller Central account, with credentials stored encrypted per organization and per seller account. Connect from Settings → Integrations, adding each seller account you want synced.