Step 1 – Check the logs first
Before anything else, go to Settings → View Logs and look at the most recent entries. Use Filter by Level and choose Error to see only failures. The log message usually tells you exactly what went wrong.
Most common causes and fixes
1. No proxy services enabled (most common)
Symptom: Imports by URL, Search, or Bestsellers fail or return empty results. Log shows “blocked” or “no data”.
Fix: Go to Settings → Configuration → Proxy. Enable and configure at least 2 proxy services. Free-tier accounts from ScrapingAnt and ScraperAPI are enough to start. Make sure both the Import Products and Update Products toggles are on for each enabled service, then click Save Settings.
2. Only 1 proxy service enabled
Symptom: Imports work sometimes but fail randomly. Update success rate is low.
Fix: Enable a second proxy service and set a different priority number so the plugin has a fallback. With 2+ services the plugin automatically retries with the next one if the first fails.
3. Proxy API key is wrong or expired
Symptom: You have proxy services enabled but imports still fail. Log shows an authentication error for the proxy.
Fix: Go to Settings → Configuration → Proxy. Click the Test button on each service card to check if the key is valid. If the test fails, log in to your proxy service dashboard, generate a new key, paste it in the plugin, and save.
4. Amazon API (Creators API) credentials missing or invalid
Symptom: The Import By PA-API 5 page shows Amazon API Setup Required. Or imports via API return an error about credentials.
Fix: Go to Settings → Amazon API Setting. Enter your Access Key, Secret Key, and Associate Tag from your Amazon Associates account under the Creators API section. Save. Make sure your Associates account has at least 3 qualifying sales in the last 30 days — Amazon requires this for API access.
5. Amazon Associates account not eligible for API
Symptom: API credentials look correct but API calls return “InvalidAssociateTag” or access denied errors.
Fix: Log in to your Amazon Associates account. Check that your account is active and has at least 3 qualifying sales (affiliate commissions) in the last 30 days. If not, use Import by URL, Import by Search, or Import Bestsellers (which use proxy services instead of the API) until your account becomes eligible.
6. Proxy credits exhausted
Symptom: Imports were working but suddenly stopped mid-month. The proxy service card shows high usage.
Fix: Check the API Usage bar on each proxy card under Settings → Configuration → Proxy. If one service is at 100%, its credits for the current period are used up. The plugin will fall back to the next service in the chain automatically — as long as you have at least 2 services enabled. If all services are exhausted, upgrade your plan or wait for the monthly reset.
7. Wrong Amazon marketplace / country
Symptom: Imports return products from the wrong country, wrong currency, or no results at all.
Fix: Go to Settings → Configuration and check the Amazon Country / Marketplace setting. Make sure it matches the Amazon site you want to import from (e.g. amazon.de for Germany, amazon.co.uk for UK). Your Creators API Associate Tag must also belong to the same marketplace.
8. Product URL format not recognised
Symptom: Import by URL fails with “invalid URL” or imports nothing even though the page exists on Amazon.
Fix: Make sure the URL contains /dp/ followed by the ASIN (10-character code). Shortened URLs, sponsored links, or search result URLs will not work. Copy the URL directly from the product page in your browser address bar.
9. Import starts but product never appears in WooCommerce
Symptom: The Import Console shows progress but no product is created in WooCommerce.
Fix: Check the logs for a “save failed” or “product already exists” entry. If the product already exists (same ASIN), it may have been imported before. Search WooCommerce products by the ASIN or title. If it is a new product, check that WooCommerce is active and that your user has product creation permissions.
Still stuck?
Export your logs via Settings → View Logs → Actions → Export Logs and include them when contacting support. The log file contains the exact error messages the plugin recorded.