Overview

RepriceLab communicates with Amazon via the Selling Partner API (SP-API). Like any API integration, errors can occur due to throttling, authentication issues, or Amazon-side problems. RepriceLab logs all SP-API interactions in the Repricing Activity page so you can diagnose issues quickly.

Most errors are transient and resolve automatically on the next repricing cycle. This guide covers the most common errors and what to do when they persist.

SP-API throttling

What it is: Amazon limits how many API requests can be made per second and per minute — this is called throttling. When RepriceLab sends too many requests in a short window, Amazon returns a 429 Too Many Requests error.

Symptoms: Some products are not repriced in a given cycle. The Repricing Activity log shows SP-API errors for certain SKUs. Price updates appear delayed or intermittent.

What RepriceLab does: RepriceLab has built-in rate limit management with automatic retry and exponential backoff. Throttled requests are automatically retried in the next cycle. You do not need to take any action for occasional throttling.

Persistent throttling: If throttling is consistently affecting your account, it may indicate that you have multiple third-party tools connected to the same SP-API credentials simultaneously. Running two repricing tools at once can cause both to throttle. Consider disconnecting unused integrations.

Authentication issues

What it is: Amazon OAuth tokens (used to authenticate RepriceLab's API calls) expire periodically and must be refreshed. Authentication errors occur when the token refresh fails.

Symptoms: Store status shows "Disconnected" or "Auth Error" on the Multichannel page. All products on that store stop repricing. Repricing Activity shows authentication errors.

Resolution: Navigate to the Multichannel page and click Reconnect next to the affected store. This re-initiates the OAuth flow. Sign in to Seller Central again and click Allow. The connection should be restored within one repricing cycle.

Sync delays

What it is: SP-API calls to retrieve product catalog data or competitor prices can experience delays on Amazon's side, especially during high-traffic periods (e.g., peak shopping events like Prime Day).

Symptoms: Competitor prices seem stale. Buy Box data on the dashboard appears old. New products added to Amazon do not appear in RepriceLab within the expected timeframe.

What to do: Sync delays are usually temporary and resolve on their own. If delays persist for more than 2 hours, check Amazon's SP-API health dashboard for any platform-wide incidents. RepriceLab will automatically resume normal operation once the API is stable.

Price rejection errors

What it is: Amazon's pricing validation layer rejects certain price updates before they are applied to the listing. This is separate from throttling — the request reaches Amazon, but Amazon refuses the price value.

Common reasons for price rejections:

  • Price is below Amazon's minimum threshold for that product
  • Price exceeds Amazon's maximum allowed price (price gouging protection)
  • Price is more than 50% higher than the product's reference price
  • The listing is in a "Price Alert" state in Seller Central

Resolution: Check the Repricing Activity log for the specific error code. Adjust your minimum or maximum price for the affected products. If the listing has a Price Alert in Seller Central, resolve it there first before RepriceLab can update it.

Inventory and catalog errors

ASIN not found: Occurs when an ASIN is no longer active in Amazon's catalog (product discontinued, delisted, or not available in that marketplace). RepriceLab will skip these products and mark them as inactive.

SKU mismatch: If a SKU in RepriceLab does not match your current Seller Central SKU (e.g., after a catalog restructure), price updates will fail. Re-sync your catalog from the Multichannel page to refresh SKU data.

When to contact support

Contact RepriceLab support if:

  • Your store has been showing as Disconnected for more than 24 hours despite reconnecting
  • More than 50% of your products have SP-API errors consistently across multiple cycles
  • You see the same authentication error repeatedly after reconnecting

Include your store ID and a screenshot of the Repricing Activity error log when contacting support — this helps diagnose the issue faster.