Getting Data Out of The Rug Merchant Without Losing Your Mind
I've spent more time than I care to admit working with The Rug Merchant's export pipeline. The tool itself is fine for basic queries, but the way it handles bulk data pulls is where most people run into trouble. I'll walk through what actually works in practice. The Rug Merchant is a data aggregation and visualization tool designed primarily for e-commerce sellers who need to track inventory patterns across multiple marketplaces. It pulls from platform APIs, normalizes the data, and surfaces it in dashboards. The core value is in its cross-platform comparison features, which most competitors don't handle cleanly. The catch is that it only supports a limited number of API integrations out of the box, and expanding beyond those requires either using their webhook system or writing custom connectors. Start by going to the dashboard and navigating to Settings > API Connections. You'll see a list of supported platforms. For each one, you need to authenticate directly through their official OAuth flow. I cannot stress this enough: never paste API keys into third-party fields. The Rug Merchant has a secure token storage system built in, but if you're manually entering raw keys, you've already bypassed their encryption layer. The proper flow takes about four minutes per platform and requires you to have admin-level access on the marketplace account.
Once authenticated, go to the Data Sources tab and click New Query. Here's where most people mess up. The default time window is 30 days, but if you're pulling historical data for the first time, the system will start indexing from the earliest available date your account permits. For sellers on major platforms, that can mean several years of records. The indexer is single-threaded, which means a full backfill for a high-volume store can take between 6 and 14 hours. I learned this the hard way when I set up my first query for a client with 40,000 transactions dating back three years. The dashboard showed a progress bar, but it was misleading. The actual work was queued server-side. I closed the tab, went home, and came back the next morning to find it complete. The workaround I use now is to set up queries during off-hours and check the notifications tab rather than watching a progress bar that doesn't reflect real-time status.
Common Pitfalls and What to Avoid
One issue that nobody talks about is field mapping drift. When a marketplace updates its API schema, The Rug Merchant may not immediately align its internal field mappings. I ran into this when Shopify pushed a change to their variant object structure, and about two weeks later, several of my product attributes were showing as null in reports. The data was still being collected correctly at the source, but the normalization layer had stale mappings. The fix was manual: go to Settings > Field Mappings, select the affected platform, and re-sync the schema. This took maybe ten minutes and resolved the issue across all existing queries. Another problem is rate limiting. The Rug Merchant respects API rate limits on your behalf, but if you're pulling from multiple platforms simultaneously, the system will stagger requests. During peak hours, this can slow things down significantly. My workaround is to configure query schedules through the Automation tab and set them to run between 2 AM and 5 AM. This keeps everything fresh in the morning without competing with other users for API bandwidth. The difference in completion time is usually between 45 minutes and 2 hours depending on your data volume.
Get the Full Details
Advanced Export Workflows
For anyone doing regular analysis, the CSV export feature is adequate but limited. The real power comes from using their API endpoint for custom pulls. The documentation is sparse, but the endpoint is straightforward: /api/v2/export with appropriate query parameters. I typically use Python with the requests library to schedule weekly exports and push them into BigQuery for deeper analysis. This avoids the 50,000-row limit that the CSV exporter enforces and gives you access to raw timestamp data that the dashboard abstracts away. Here's a practical example of a query I run weekly: A GET request to /api/v2/export with parameters for date range, platform filters, and metric selection. I pass an auth header with my API key and receive a JSON response containing paginated results. Each page returns up to 1,000 records. I loop through pages until the meta.next_cursor field is null, then transform the output into a schema that matches my analytics pipeline. This whole process runs in about three minutes for a typical week of data across five platforms.
When The Rug Merchant Falls Short
Be honest about its limitations. The tool struggles with negative transaction data and refund chaining. If your business model involves frequent returns that get restocked and resold, the revenue attribution will be inaccurate. The system tracks net revenue by default, but there's no toggle to show gross revenue before returns. I've worked around this by exporting the raw transaction log and running a secondary calculation in a spreadsheet that factors in return and resell cycles separately. It adds about 20 minutes to my weekly process, but the accuracy is worth it. Also, the mobile app is essentially a read-only dashboard with no meaningful functionality. Don't expect to manage queries or exports from your phone. The web interface works on tablets but the layout breaks below 1024 pixels. If you need mobile access, plan accordingly.
Cost Considerations
The free tier allows one platform connection and 10,000 records per month. That's useful for testing but insufficient for any real operation. The starter plan at $29/month adds three platforms and 50,000 records. The professional tier at $79/month unlocks unlimited platforms and records plus the full API access I described above. For anyone doing this seriously, the professional tier is the only one that makes sense. The starter tier will eat its record allowance in a single week if you have more than a handful of SKUs across multiple marketplaces.
