ONIX Catalog Audit
Pricing
from $0.50 / completed report
ONIX Catalog Audit
Check UTF-8 product-feed CSV files for common missing fields, invalid prices and identifiers. Export row-level findings as JSON and CSV. No store access or live-page checks; up to 20,000 rows per file.
Pricing
from $0.50 / completed report
Rating
0.0
(0)
Developer
Yurii Lobas
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Check common product-feed fields for missing values, invalid prices, availability and identifier issues. This is not a complete platform-policy certification and does not fetch product pages.
Input
Supply CSV text using the input schema or INPUT.example.json. UTF-8 CSV, TSV and semicolon delimiters are supported. Maximum 5 MiB, 20,000 data rows and 100 columns per file. XLSX and XML are not supported. Diff requires a unique key in both files; the sample uses sku. Mapper requires an explicit target-to-source mapping. No store credentials are needed.
Results
The default dataset holds individual findings, changes or mapped records. OUTPUT holds the complete JSON result; REPORT holds UTF-8 CSV. An empty audit dataset can mean no findings: check OUTPUT for counts. Results never automatically update a store.
Data handling
Unlike the browser demo, cloud runs send supplied data to Apify storage. Use data you are authorized to process. Do not include customer personal data or credentials. The Actor does not fetch URLs in your CSV.
Contact: info@onyxautomationapp.com
Pricing
One completed report costs USD 0.50, regardless of product or finding count. Apify also applies an Actor Start event of USD 0.00005 per GB (minimum one). Run with 128-1024 MB and a maximum-charge limit of at least USD 0.51. Platform usage during a customer run is included; later storage access may incur Apify fees.
A report with validation findings is still a completed report. The report event is requested only after CSV, dataset rows and the complete JSON have been saved. Invalid input or failed writes do not trigger the custom report event; the platform start event may still apply. No automatic retries or resumed runs are supported: contact support for a failed or uncertain charge before running again. A fresh run creates a separate report and may incur another charge. Own-account tests are not customer revenue.
