Amazon
Live connector
Sell on Amazon.
Sync it everywhere else.
One operations layer for FBA and FBM together — built on the Selling Partner API. Stock, orders and listings sync across every Amazon marketplace and every other channel you run.
APISP-API · Notifications · Feeds
SyncEvent-driven · seconds typical
MarketplacesNA · EU · FE regions
item photo
184
#SKU-3091845 · Live
Vintage Hamilton Khaki Field Auto · 38mm · Black Dial
$429.00
listed
×4in stock
184watching
82rank
BrandHamilton
MovementAutomatic
Case38 mm · steel
Variations4 SKUs · all synced
Recent activity
−0:02
↓
Orders
order.paid
HAM-38-BLK · qty 1 · $429
−0:04
↑
Inventory
stock.update
HAM-38-BLK · 4 → 3
−0:18
↑
Inventory
price.update
OMG-SS-41 · $1,495 → $1,420
−1:42
↓
Orders
order.paid
ROL-OYS-36 · qty 1 · $612
−3:08
↑
Fulfilment
tracking.add
ORD-58821 · UPS 1Z9A…
Connector
Live · SP-API
Fulfilment
FBA · FBM · seller-fulfilled Prime
Marketplaces
All regions · one inbox
Listings
ASIN match + new listings
Multi-account
Unlimited Seller accounts
What actually syncs
Both directions.
Every field that matters.
Seven first-class data types across Amazon's Selling Partner API and notification topics. No flat-file feed crontab, no Seller Central swivel-chair.
Amazon
bidirectional
SalesChannelHub
Amazon
→
SalesChannelHub
Orders & buyers
SP-API · Orders + Notifications
SalesChannelHub
→
Amazon
FBM stock levels
SP-API · Listings patchListings
SalesChannelHub
→
Amazon
Listings & content
SP-API · Listings Items
SalesChannelHub
→
Amazon
Price changes
SP-API · Listings patchListings
SalesChannelHub
→
Amazon
FBM tracking
SP-API · Orders confirmShipment
Amazon
→
SalesChannelHub
FBA inventory
SP-API · FBA Inventory
Amazon
→
SalesChannelHub
Returns & reimbursements
SP-API · Reports
Three things Amazon sellers told us
Amazon is the volume.
It's running it next to everything else that hurts.
01
"FBA shows 40 units, our warehouse shipped the FBM ones, and Amazon oversold anyway."
FBA and FBM stock are tracked as one picture. FBM availability decrements with every channel; FBA levels are pulled back in.
FBA + FBMone stock picture
02
"A late FBM shipment tanked our Order Defect Rate before anyone noticed."
Handling-time SLAs are enforced at allocation, and account-health signals surface in the dashboard as they land.
Liveaccount-health widgets
03
"Re-pricing the same SKU across three Amazon marketplaces is three logins."
One canonical record; price and content patch out to every marketplace through the SP-API in one action.
3 regionsone price change
The listing flow
Every Amazon field, in one form.
Patched through the SP-API.
Variations, attributes, browse nodes and offer data — managed in the master catalogue and patched out to every Amazon marketplace.
Listing
Variations4
Attributes23
Offer
Fulfilment
Compliance
Synced 8 seconds ago
Handling-time SLA — same-day
Sponsored Products linked — 4.2%
Buy Box eligible
Amazon listing #SKU-3091845 · Pushed via SP-API · Listings Items · SalesChannelHub product HAM-KFA-38
Inventory sync
A stock count that holds FBA and FBM together.
FBA levels are pulled in from the FBA Inventory API; FBM availability is patched out as every channel sells. One number, two fulfilment methods, no double-count.
FBA + FBM unified
FBA quantities are read back continuously while FBM stock is published from your warehouses — shown as one picture.
Per-channel buffer
Hold units back from Amazon FBM while a reorder lands — protects your metrics without manual hold-backs.
Throttle-aware
Updates respect the SP-API's rate quotas and back-pressure — never queues for hours, never trips a throttle.
Reservations during pick
FBM stock decrements at allocation, not at label — no double-sells while orders sit unpicked.
Sync timeline · last 30s
5.8s avg latency
−30s−20s−10snow
Amazon
Amazon
Shopify
Walmart
delivered
retried
Orders & fulfilment
From order notification to tracking number.
One pipeline, four steps.
Every FBM order flows through the same fulfilment pipeline as eBay, Shopify and Walmart — FBA orders are read back for a complete picture.
01
Order notification arrives
SP-API · Notifications
The order event lands on our queue. Buyer, address, items and fees captured against the canonical order.
02
Allocated to a warehouse
Engine · routing rules
Picks the location that satisfies all lines with the fewest splits, respecting the Amazon handling-time SLA.
03
Picked, packed, labelled
Floor · pick + carrier
Lands on a wave pick list. Carrier rates compared, label printed, the order marked picked.
04
Shipment confirmed to Amazon
SP-API · confirmShipment
Carrier and tracking confirmed back. Counts toward the on-time-shipment metric automatically.
Order #11–13427–58821
tobias_rh · Amazon buyer
Paid · ready to pick
handle by Thu 6:00 PM
Item
Hamilton Khaki Field Auto · 38mm · Black
HAM-38-BLK · SKU-3091845
HAM-38-BLK · SKU-3091845
Buyer paid
$429.00
+ $0 ship · −$33.27 fees
+ $0 ship · −$33.27 fees
Ship to
Portland, OR 97211
USPS Ground Advantage · 3 day
USPS Ground Advantage · 3 day
Allocation
PDX · A2-12-3
1 unit reserved · pick wave 12:30 PM
1 unit reserved · pick wave 12:30 PM
Amazon-only reports
The metrics Amazon grades you on.
Right next to your stock count.
Order Defect Rate, late-shipment rate, FBA sell-through and Buy Box share — surfaced as first-class widgets, not buried in Seller Central.
Account health
Order Defect Rate
0.3%
−0.1 pts vs last 30d
Account health
Late shipment rate
1.1%
target 4%
Account health
Valid tracking rate
99%
target 95%
Sponsored
Advertising ACoS
14%
−2 pts WoW
Listing quality
Buy Box share
88%
store median · 79%
FBA
FBA sell-through
71%
+5 pts WoW
What changes day one
What it looks like before
and after the connector.
Manual in Seller Central
SalesChannelHub
Stock decrement after a sale
✕flat-file feed · usually overnight
✓seconds · event-driven
FBA + FBM together
✕two screens, never agree
✓one unified stock picture
Re-price across 3 marketplaces
✕three logins, one SKU
✓one patch · every region
Tracking back to Amazon
✕confirm shipment by hand
✓auto · counts toward metrics
Order Defect Rate alerting
✕noticed when it is too late
✓live widget · pings in seconds
Two Seller accounts
✕two browser profiles
✓two accounts · one inbox
Setup
Five minutes from sign-in
to first synced listing.
Authorise over the Selling Partner API. No middleware, no per-connection fee.
01
Authorise the SP-API
One Login-with-Amazon consent grants the Selling Partner scopes. We never see your Seller Central password.
SP-API · LWA OAuth
02
Pick the marketplaces
Choose which Amazon marketplaces (US, CA, UK, DE…) the connector should manage. All regions supported.
SP-API · Marketplace IDs
03
Match existing listings
We pull your listings and match them to your catalogue by SKU or ASIN. Conflicts surfaced for review.
SP-API · Listings Items
04
Subscribe to notifications
Order and inventory notifications subscribe automatically. Bidirectional sync from the next minute on.
SP-API · Notifications
Asked before every Amazon seller switches
Six questions.
Honest answers.
Yes. FBA levels are read back from the FBA Inventory API while FBM availability is published from your warehouses — shown as one stock picture so neither oversells.
All of them — North America, Europe and Far East regions. Each marketplace is its own offer, but the catalogue underneath is one record set.
It is designed to protect them. Handling-time SLAs are enforced at allocation, tracking is confirmed automatically, and account-health signals surface the moment they arrive.
Yes. Each Seller account connects separately with its own orders and metrics, but the canonical catalogue is shared.
Yes. SF Prime orders route through the same pipeline with their tighter handling SLA enforced at allocation.
No. The first sync matches your live listings to the catalogue by SKU, then ASIN. Matched listings stay the same listing on Amazon — we just attach our record.
Amazon
·
and seven other channels, the same way.
Sell everywhere.
Manage once.
A 14-day trial, no credit card, no sales call. Authorise the Selling Partner API in five minutes and watch your first listing sync.
Connector · live · SP-API
Built by sellers · honest pricing