Run summary
Job c327fd01 used a public Amazon search URL as input, full_product mode, target_count 100 and reported 100 delivered records, 0 failed records and 500 Data Units spent.
The run started at 2026-06-10 07:16:14 UTC and finished at 2026-06-10 07:21:37 UTC. The full exports were offloaded to object storage; this page shows an illustrative row and the measured run metadata.
What this proves
The useful metric is delivered rows that can be inspected, exported and reused by an operator or API workflow, not request count alone.
The page is a historical production reference, not a promise that every current Amazon input has identical field coverage or latency. Buyers should run their own small input and compare the fields they need.
How to evaluate your own workflow
Send one Amazon search URL, category URL, product URL list or ASIN list and compare the delivered rows against the fields your team needs.
For agencies and data teams, the first pilot should measure delivered rows, failed rows, export shape, first-row latency and the time needed to turn the output into a client-ready report.
Production checklist
Start with one small input and compare the delivered fields with the report, catalog or pipeline you actually need.
Keep the job ID, source URL, mode and run date with downstream exports so operators and developers can audit the same result.