The modern Amazon API, not legacy MWS
CanShip uses Amazon's Selling Partner API (SP-API) for orders, inventory, and shipment confirmation. Built for the API model Amazon supports going forward, not the legacy MWS path that's being deprecated.
Amazon SP-API native. FBM orders flow into the same fulfillment queue as your Shopify orders, so your team picks Amazon and Shopify side by side without switching screens. Built for Canadian Amazon sellers shipping from a real warehouse.
Amazon's seller metrics are unforgiving. CanShip's Amazon integration is built around the order-to-confirmation timing Amazon actually requires, not just 'we can read your orders.'
CanShip uses Amazon's Selling Partner API (SP-API) for orders, inventory, and shipment confirmation. Built for the API model Amazon supports going forward, not the legacy MWS path that's being deprecated.
Sell on multiple Amazon marketplaces under a single CanShip operator account. Orders from each marketplace flow into the same fulfillment queue. Inventory writes back to each marketplace independently. No duplicate setup, no separate logins.
Same pick workflow. Same pack workflow. Same carriers. Your team doesn't switch screens between channels. Amazon orders are first-class in the fulfillment queue, not exceptions to the Shopify flow.
Order acknowledgment, on-time shipment, valid tracking, and proof-of-delivery all matter for your seller account health. CanShip times each step to keep your On-time Shipment Rate, Valid Tracking Rate, and ODR within Amazon's thresholds.
After every pick, available inventory writes back to each connected Amazon marketplace based on the inventory rules you set per channel. No oversells across Amazon and Shopify, no manual sync.
The moment a shipping label prints, CanShip confirms shipment to Amazon with the carrier and tracking number. Amazon's Valid Tracking Rate counts shipments confirmed within Amazon's window; we hit it consistently.
From CanShip's Channels page, click Connect Amazon. You'll be redirected to Seller Central to authorize the SP-API connection (Login with Amazon flow). Approve the requested scopes, you're back in CanShip with credentials stored securely.
CanShip detects which Amazon marketplaces your seller account is registered for (CA, US, MX, EU). Pick the ones you want connected. You can add more later, no need to disconnect to add a marketplace.
Place a test order on one of your connected marketplaces (or use Amazon's sandbox). It appears in CanShip's fulfillment queue. Pick, pack, ship. Amazon receives the shipment confirmation in real time. Total setup time: about fifteen minutes.
Most WMS treat Shopify as primary and Amazon as 'also supported.' CanShip puts Amazon orders in the same queue, with the same pick/pack workflow and the same shipping options. Your team doesn't think about the channel.
Canadian sellers expanding into the US shouldn't need a second WMS instance. CanShip handles multi-marketplace under one operator account, with per-marketplace inventory rules and shipping defaults.
On-time Shipment Rate, Valid Tracking Rate, Order Defect Rate, Cancellation Rate. Falling behind on any of these can lose you the Buy Box or suspend your account. CanShip's Amazon flow times each step to stay inside Amazon's thresholds.
Breakthrough Studio's brands ship Amazon FBM through CanShip every day. When Amazon changes a metric threshold, an SP-API endpoint, or a shipping requirement, we feel it before customers do.
Amazon SP-API integration is included starting on the Grow plan ($299 CAD/mo). Free and Starter are Shopify-focused channels. Brands selling enough Amazon volume to need WMS-grade fulfillment are typically on Grow anyway.
One CanShip operator account can connect to multiple Amazon marketplaces (CA, US, MX, EU, and beyond as Amazon adds new ones). No per-marketplace upgrade fees, no separate billing.
We'd rather flag the practical limitations up front than have you discover them mid-peak. The two below cover almost all real-world questions Amazon sellers ask.
CanShip handles Amazon FBM (Fulfilled by Merchant), where you ship from your warehouse. FBA orders, where Amazon ships from their fulfillment centers, don't flow through CanShip because they don't need to. Your FBM and FBA inventory stay separate, as they should.
Amazon throttles SP-API calls per seller account, especially during peak season. CanShip queues, retries, and respects backoff windows. Sustained high-volume bursts can hit Amazon-side delays; we surface throttle status in the dashboard so you can see it happening.
No, by design. FBA orders ship from Amazon's fulfillment centers, not your warehouse, so they don't touch CanShip. Your FBA and FBM inventory stay separate. CanShip only handles the FBM side, which is where the WMS work is.
Yes. Connect Amazon.ca, Amazon.com, Amazon.com.mx, Amazon.fr, Amazon.de, and any other supported Amazon marketplace under one CanShip operator account. Inventory rules and shipping defaults are configured per marketplace.
About fifteen minutes including a test order. The SP-API authorization in Seller Central is the longest step, and that's mostly clicking through Amazon's approval prompts.
On-time Shipment Rate, Valid Tracking Rate, Order Defect Rate, and Cancellation Rate are all metrics Amazon uses to evaluate seller health. CanShip times order acknowledgment, shipment confirmation, and tracking writeback to keep these inside Amazon's thresholds.
Yes. That's how it's designed. Amazon and Shopify orders sit in the same fulfillment queue with the same pick and pack workflow. Your team doesn't switch screens. Inventory writes back to each channel independently after every pick.
We've migrated brands off ShipHero, ShipStation, ShipBob, and Extensiv. Migration assistance is included on every paid plan, with a dedicated specialist for the first 30 days. Talk to us about your current setup before you switch.
Live demo using a CanShip environment that's yours to drive. Connect a sandbox Amazon account, place a test order, watch it move through the fulfillment queue alongside Shopify orders. Most calls wrap in 30 to 45 minutes.