Nautilus syncs with Amazon Seller Central and Amazon FBA, showing your inventory in one place whether it's in your warehouse, in transit to FBA, or already at an Amazon fulfillment center. AI-driven replenishment forecasts when to send more stock.
Inventory data, where you need it.
Three things the Amazon integration does well, that you'd otherwise be doing by hand.
FBA-aware stock
Monitor Amazon-held inventory alongside warehouse counts in a single dashboard. Inbound shipments to FBA, allocated FBA stock, and unallocated FBA stock are all visible at the SKU level.
Replenishment alerts
The Nautilus forecast model predicts when each FBA SKU will go out of stock and recommends shipment quantities and timing. Recommendations factor in Amazon's restock limits and your historical lead times.
Multi-marketplace
Sync inventory across Amazon US, Canada, UK, EU, and Australia marketplaces. Cross-marketplace transfers (shifting stock from FBA US to FBA EU) are tracked end-to-end as in-transit inventory.
Bidirectional sync. No manual entry.
Data moves between Nautilus and Amazon in both directions, near-real-time.
- FBM inventory levels
- Shipment quantities to FBA
- Order fulfillment events
- Forecast values
- FBA inventory snapshots
- Order data
- Returns
- Restock limits
- Marketplace catalog
Four steps to live.
Under 10 minutes for most teams. The full health check takes longer but doesn't block sync.
Connect
Authenticate with one click. Nautilus uses OAuth — no API keys to copy, no credentials to store.
Map
Match your products, locations, and accounts. Nautilus auto-maps by SKU where possible.
Sync
Enable bidirectional sync. Changes in either system reflect in the other within 30 seconds.
Verify
Run the sync health check. Nautilus flags any mismatches before they become problems.
What the integration does, in numbers.
Amazon questions, answered.
How does this handle FBA restock limits?
Amazon's restock limits update weekly and vary by storage type. Nautilus reads the current limit from the SP-API on each replenishment cycle and caps suggested shipment sizes accordingly. If you're hitting limits frequently, the replenishment view surfaces this so you can request a limit increase.
Does this work with Amazon Vendor Central (1P), or only Seller Central (3P)?
Seller Central is fully supported. Amazon Vendor Central support is more limited and runs through a separate integration on enterprise plans; it handles PO confirmation, ASN generation, and inventory snapshots but not the FBA-style replenishment workflow.
What's the latency for FBA inventory updates?
Amazon's FBA inventory API has variable latency, typically 1 to 4 hours. Nautilus polls every 30 minutes and reconciles to the canonical state. For real-time accuracy on FBA-only items, you're limited by Amazon's API; for FBM and warehouse stock, sync is real-time.
How are AGL (Amazon Global Logistics) shipments tracked?
AGL shipments appear in Nautilus as in-transit inventory from your warehouse to an Amazon facility, with the AGL booking ID stored on the shipment. Once Amazon receives the inbound, the inventory moves to FBA stock and the in-transit row closes.
See Nautilus + Amazon running on real data.
30-minute walkthrough with a Nautilus engineer. We'll connect a sandbox of your Amazon account and show the sync live.