Upload fails immediately or parser reports unsupported format.
Where to Check in PassiveWP
WordPress Admin -> PassiveWP -> Amazon Earnings -> Overview
Step-by-Step Fix Walkthrough
Fix Step 1: Re-download the report directly from Amazon as CSV.
Where to click WordPress Admin→PassiveWP→Amazon Earnings→Overview
What to do Open Amazon Earnings→Uploads, upload one CSV, wait for processing completion, then verify rows in Reports/Overview.
How to verify Imported/report totals should align with the selected date window from your source file.
Fix Step 2: Confirm the report type is supported.
Where to click WordPress Admin→PassiveWP→Amazon Earnings→Overview
What to do In Amazon Earnings, set date range first, then review cards/tables and open deeper views for anomalies.
How to verify Imported/report totals should align with the selected date window from your source file.
Fix Step 3: Open CSV quickly to verify rows/columns look complete.
Where to click WordPress Admin→PassiveWP→Amazon Earnings→Overview
What to do Open Amazon Earnings→Uploads, upload one CSV, wait for processing completion, then verify rows in Reports/Overview.
How to verify Imported/report totals should align with the selected date window from your source file.
Fix Step 4: Retry import with a fresh file.
Where to click WordPress Admin→PassiveWP→Amazon Earnings→Overview
What to do Open Amazon Earnings→Uploads, upload one CSV, wait for processing completion, then verify rows in Reports/Overview.
How to verify Imported/report totals should align with the selected date window from your source file.
Most Common Causes
- File is not CSV or has incompatible structure.
- Report type not supported by importer.
- File corruption or partial download.
How to Prevent It Next Time
- Standardize report download process.
- Name files clearly with date range and report type.
- Store original source exports for auditing.
When to Contact Support
- You completed every fix step and still get the same error.
- The issue impacts revenue-critical pages or high-volume campaigns.
- You can share timestamps, affected link/product IDs, and screenshots of the exact error state.
