FAQ
Frequently asked questions
Operational and commercial questions teams ask before rollout.
What does Catalog QA scan?
Catalog QA scans product, media, metadata, category, pricing, stock, variant, and feed-readiness fields via Magento APIs and reports actionable issues.
How quickly can we get value after connecting Magento?
Most teams see first KPI and insight cards within minutes after initial sync completes. Time depends on store size and API responsiveness.
Do you pull all Magento data on every page view?
No. Dashboard pages read local synced tables. Magento APIs are used by background sync jobs, not by every dashboard request.
Can we see profit, not only revenue?
Yes. Upload COGS by CSV and the profit module estimates gross profit, margin %, and discount impact on margin.
What payment issues can be detected?
Examples include paid-not-invoiced, invoiced-not-paid, amount mismatches, and refund inconsistencies based on synced Magento documents.
Do alerts spam users every few minutes?
No. Alerting supports cooldown windows to deduplicate repeated triggers for the same type/store/time window.
Is multi-store supported?
Yes. Plan tiers define store limits and higher plans include stronger multi-store operational rollups.
How does lead/contact data work?
Contact submissions are validated server-side, protected by honeypot and rate limiting, and stored in DB for follow-up.
Still evaluating?
Open the interactive demo, review Catalog QA docs, or request a tailored walkthrough.