Amazon SP-API Integration

Connect Amazon Seller Central to ReplenishRadar via the official SP-API. FBA inventory, orders, inbound shipments, and fees — synced securely.

Not Another Screen Scraper

I need to say this upfront because the Amazon tools space is full of products that scrape Seller Central. They log into your account with your credentials, parse HTML pages, and pray Amazon does not change a div class.

That approach breaks constantly. It violates Amazon's Terms of Service. And it puts your account at risk.

ReplenishRadar connects through the official Selling Partner API. Amazon built SP-API as the replacement for MWS specifically so third-party tools would stop scraping. We were built on SP-API from day one -- no legacy MWS migration, no scraping fallbacks.

What We Sync

Data Type SP-API Endpoint How We Use It
FBA Inventory Inventory API Current stock levels at Amazon fulfillment centers
Orders Orders API + SQS Sales velocity, demand forecasting, revenue tracking
Inbound Shipments Fulfillment Inbound API Track inventory you have sent to FBA
Fee Estimates Fees API Factor storage and fulfillment costs into reorder decisions

We pull FBA inventory and inbound shipment data on your regular sync schedule. Orders are different -- they come through a streaming pipeline.

SQS Streaming: Why Orders Arrive Fast

Most inventory tools poll Amazon's Orders API on a timer. Hit the endpoint, get recent orders, wait, repeat. The problem is Amazon rate-limits these calls aggressively, and if you poll too infrequently, you miss velocity spikes.

We use Amazon's SQS notification system instead. When an order is placed on your Amazon listing, Amazon pushes a notification to our SQS queue. We consume these events every 2 minutes.

The difference matters. Polling means your data is as stale as your polling interval plus whatever backoff Amazon's rate limiter imposes. SQS means we get order events pushed to us in near real-time. Your sales velocity numbers stay current, and your reorder point calculations use today's data, not yesterday's.

The Authorization Flow

Connecting your Amazon account takes about three minutes.

  1. Click "Connect Amazon" in ReplenishRadar
  2. We redirect you to Amazon's authorization page (Seller Central login)
  3. You approve the specific permissions we request
  4. Amazon issues us a refresh token
  5. First sync starts -- FBA inventory, order history, inbound shipments

We store the refresh token encrypted at rest. We never see your Seller Central password. Amazon's own authorization server handles the credential exchange.

If you revoke access later, go to Seller Central > Apps & Services > Manage Your Apps. One click and we lose access immediately.

What We Can and Cannot Do

I want to be specific here because permissions matter.

Read access (always on):

  • FBA inventory quantities and condition
  • Order history and order details
  • Inbound shipment status and tracking
  • Fee estimates per ASIN

Write access (only when you ask):

  • Creating FBA inbound plans -- this only happens when you click "Create Inbound Plan" in ReplenishRadar. We do not create plans automatically or without your explicit action.

We do not modify your listings. We do not change your prices. We do not alter your FBA settings. Read the data, run the math, give you recommendations. That is the boundary.

Amazon Compliance

Amazon has strict rules for SP-API developers. We follow them.

Your order data and customer information are handled per Amazon's Data Protection Policy. We do not sell your data, share it with other sellers, or use it for anything beyond powering your ReplenishRadar account. PII from orders (buyer names, addresses) is not stored longer than Amazon permits.

This is not a legal footnote -- I have seen tools get their SP-API access revoked, and every seller connected to them lost their integration overnight. We take compliance seriously because the alternative is your data pipeline disappearing.

Multiple Amazon Accounts

If you run more than one Amazon seller account, connect them all. Each account counts as one store toward your plan limit -- Standard supports 2, Growth supports 5, Scale supports 10. Each account syncs independently. I have talked to sellers who manage separate accounts for different brands or product lines. All of them show up in one dashboard with unified forecasting across the portfolio.

Sync Frequency by Plan

Plan Inventory Sync Order Sync (SQS) Inbound Tracking
Standard ($99/mo) Every 30 min Every 2 min Every 30 min
Growth ($199/mo) Every 15 min Every 2 min Every 15 min
Scale ($499/mo) Every 5 min Every 2 min Every 5 min

Notice that SQS order sync is every 2 minutes on all plans. That is because it is event-driven -- the cost does not scale with frequency the way polling does. Your FBA inventory and inbound data follow your plan's sync interval.


Learn More:

Common Questions

Ready to prevent stockouts?

Start your 14-day free trial. Full access to all features.
Start Free Trial
14-day free trialCancel anytimeSupport responds within 24 hours