Compare two product catalog snapshots by SKU
Revenue Pilot
Compare two fictional catalogs by SKU: one added, one removed, one changed item. USD0.05 per completed comparison, even with no changes. Max run charge USD0.05; timeout 60s. Dataset shows summary counts; full field-level changes are in run storage OUTPUT. Copy into your own account and review live pricing before starting. Use only authorized catalog data.
Input
Output fields
Sign up on Apify or log in
The Product Catalog Diff by SKU | Revenue Pilot Actor is ready to run with the inputs already set for "Compare two product catalog snapshots by SKU". Sign up or log in and you'll land in Apify Console with a copy of this exact task.
Start the "Compare two product catalog snapshots by SKU" task
The Product Catalog Diff by SKU | Revenue Pilot Actor will start running based on the input automatically. You can also change all the input fields, like earlier snapshot, later snapshot, and more, to match your specific use case.
Receive the "Compare two product catalog snapshots by SKU" output
Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as record, status, added, and more.
Integrate into your workflow
The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also run the "Compare two product catalog snapshots by SKU" task via API.
Integrate "Compare two product catalog snapshots by SKU" into your workflow
Connect "Compare two product catalog snapshots by SKU" with 100+ integrations, or run it via API or MCP.
Webhook
n8n
Make
Zapier
Airbyte
Keboola
IFTTT
Hubspot
GDrive
Gmail
Apify MCP
GitHub
Slack
LangChain
LlamaIndex
Flowise
Pinecone
OpenAI
Mastra
Clay
One completed comparison costs USD 0.05, including comparisons with no changes. The example keeps a USD 0.05 run limit. Apify platform storage and later exports can have separate usage costs.
The dataset contains one summary row. Open the run's default key-value store and read OUTPUT for the complete added, removed and changed records as JSON.
No individual approval is required. Copy this task, review the input and pricing, and start. The operator can pause processing; requests sent before a pause cannot always be cancelled.