CatalogWise questions, answered before checkout.

CatalogWise is an AI commerce readiness platform for Shopify catalog teams. It audits public and connected catalog signals so merchants can understand how machine-readable their product data, structured data, feeds, FAQs, attributes and trust signals are before investing in deeper diagnostics or implementation.

AI Commerce Readiness describes how well a catalog exposes clear product facts for machine interpretation. It covers structured data, product attributes, feed consistency, semantic depth, policy signals, FAQ coverage and crawler accessibility. It does not mean guaranteed visibility in any third-party AI system.

CatalogWise is built for Shopify brands, ecommerce managers, DTC teams, SEO teams, feed managers, catalog managers and agencies that need a technical view of product data quality and machine-readable commerce signals.

CatalogWise is designed around Shopify catalog workflows first. The public scan can inspect many public storefront signals, while optional Shopify Deep Access can unlock approved read-only catalog diagnostics for Shopify workspaces.

No. CatalogWise is an independent product for Shopify catalog readiness. It does not claim endorsement, certification or platform partnership unless a separate written authorization exists.

CatalogWise improves readiness and signal quality. It does not guarantee rankings, sales, placement or recommendation by third-party AI, search or commerce systems.

CatalogWise improves readiness and signal quality. It does not guarantee rankings, sales, placement or recommendation by third-party AI, search or commerce systems.

Traditional SEO tools often focus on keywords, technical crawl issues and SERP performance. CatalogWise focuses on whether catalog data is explicit enough for machine-readable product evaluation, including schema, feeds, attributes, trust signals and FAQs.

Feed tools help create or distribute feeds. CatalogWise audits readiness across the storefront, structured data, public pages, feed signals and catalog semantics so teams can prioritize what to fix before or alongside feed work.

A general Shopify audit may cover UX, conversion, speed and apps. CatalogWise concentrates on AI commerce readiness: product data, machine-readable signals, connected catalog diagnostics, report delivery and ongoing monitoring.

The public preview checks public storefront signals such as robots.txt, sitemap.xml, product URL discovery, page titles, meta descriptions, canonical URLs, OpenGraph, Twitter tags, JSON-LD schema, FAQ signals, policy links and content depth.

An account lets CatalogWise preserve scan results, enforce fair quota, protect the premium PDF paywall and prepare a deeper diagnostic path if you upgrade. It also reduces scanner abuse.

The limit protects scanner infrastructure and keeps the public preview commercially useful without replacing paid diagnostics. Paid plans unlock deeper scans, PDF export and monitoring without the free waiting period.

CatalogWise can detect visible storefront signals: public URLs, metadata, structured data, FAQ indicators, policy links, public schema, selected product pages and crawler accessibility signals.

It cannot reliably detect private feeds, Admin API product fields, metafields, hidden variants, private inventory, app-only data, customer data, full review verification or product data blocked from crawlers.

The preview reviews a limited set of public product URLs from the sitemap and storefront markup. Paid or optional Deep Access diagnostics are designed for broader SKU-level analysis.

The scan performs visible checks step by step: robots, sitemap, product discovery, page extraction, structured data parsing, trust signal mapping and readiness scoring. The delay helps make the result feel traceable rather than instant and opaque.

CatalogWise reports the crawler accessibility limitation and marks unavailable fields as unknown. Deeper diagnostics may still be possible after account setup and optional Shopify Deep Access.

You should only scan a store you own, manage, represent or have a reasonable authorization basis to audit. Unauthorized scanning may violate the Acceptable Use Policy.

Unknown means CatalogWise did not have enough evidence from public signals. The system should not invent missing products, feed fields, metafields or private catalog data.

Optional Shopify Deep Access can unlock SKU-level diagnostics, product fields, variants, metafields, collection consistency, feed readiness evidence and richer report data, depending on granted permissions and plan entitlements.

Deep Access is needed only for approved diagnostics that inspect non-public catalog data. Public scans do not need Shopify Admin access.

The initial connected scan is prepared around read_products. Future capabilities may add scopes only when the product genuinely needs them and the merchant authorizes them.

The readiness architecture is read-first. Shopify Deep Access is intended for diagnostics only and does not perform product, order, inventory, customer or theme writes.

Yes. Optional Deep Access should be revocable by the merchant through Shopify and CatalogWise account workflows once production credentials are configured.

CatalogWise is designed for catalog readiness and should not need customer data for product diagnostics. Users should not submit unnecessary personal or sensitive data into scans or chat.

Metafield analysis requires Deep Access because public pages do not expose every metafield. Paid workspaces can use this data only when approved access is available.

Variant analysis uses connected or clearly visible public data. The public scan may infer visible variant signals, while Deep Access can inspect richer variant fields when approved.

Public scans can detect collection links and context when visible. Deep Access can support a stronger collection consistency review when approved.

Headless stores can be scanned when public pages expose crawlable product URLs and signals. Deep Access may be more important for headless setups where public markup is sparse.

CatalogWise can use AI to structure extracted evidence into summaries, issues, recommendations, unknowns and confidence levels. It should only use provided scan signals and should not invent unavailable data.

CatalogWise is OpenAI API-ready through server-side environment variables. If OPENAI_API_KEY is missing, deterministic local scoring keeps the product working without presenting fallback output as live AI analysis.

It should not. The prompt and schema instruct the system to mark unavailable information as unknown and to separate public scan evidence from connected-scan requirements.

A structured audit turns extracted signals into a predictable JSON output with scores, issues, recommendations, product findings, unknowns, confidence and legal caveats. This keeps reporting and dashboards consistent.

Confidence scoring indicates how much evidence supported a finding. Public scans often have medium or low confidence for fields that require Admin API, feed or SKU-level access.

Yes. AI can misread incomplete evidence or produce recommendations that need technical validation. CatalogWise treats recommendations as diagnostic guidance, not automatic implementation instructions.

Yes. Merchants should review recommendations before changing schema, product content, feeds, FAQs, policy pages or app configuration.

CatalogWise focuses on readiness diagnostics. Content generation may be supported later, but recommendations should be reviewed by catalog and brand teams before publication.

CatalogWise can identify FAQ coverage gaps and prepare mapping guidance. Any generated FAQ should be reviewed for accuracy, policy fit and product truthfulness.

Yes. It identifies missing attributes, thin descriptions, weak entity coverage and FAQ gaps that reduce machine-readable product clarity.

The PDF includes executive summary, score cards, public signal inventory, product evidence table, structured data findings, feed readiness findings, FAQ and trust findings, issue severity matrix, roadmap, paid unlocks and disclaimer.

The PDF is a core deliverable designed for internal teams and agencies. It packages findings, priorities and next steps into a shareable asset beyond the free web preview.

The public preview shows a web preview. PDF download is a paid entitlement so CatalogWise can keep the public preview useful without giving away the full product.

Email delivery is provider-ready through Resend or Postmark when configured and is a paid entitlement for report workflows.

Yes. Agency workflows are designed for client-ready audit delivery, multi-store context and future white-label reporting.

White-label report support belongs to Agency workflows. Free and standard reports remain CatalogWise-branded.

The roadmap prioritizes schema, product data, feed, FAQ, trust signal, collection and internal linking fixes by severity, plan level and expected readiness impact.

Free reports are tied to public scan quota. Paid monitoring and connected plans are designed for recurring report updates according to plan limits.

Paid reports are intended to be shared internally with ecommerce, SEO, product, feed and leadership teams.

Recommendation export is a paid workflow. Agency and higher-tier plans can support more client-ready exports.

Free includes account-based public scan access, limited results and the locked report preview. It excludes full PDF, email delivery, Deep Access diagnostics and full AI guide context.

Starter is for merchants who need more report value from public diagnostics, including paid report access without the full connected catalog workflow.

Growth is the recommended plan for Deep Access diagnostics, premium PDF reports, full AI guidance, SKU-level priorities and monitoring foundations.

Scale is for larger catalogs that need deeper monitoring, more scan volume, richer workflows and operational reporting.

Agency is for multi-client workflows, white-label-ready reporting, multi-store dashboards, client-ready exports and agency onboarding.

Start with Free if you need a baseline. Choose Growth when you need Deep Access diagnostics, full AI guidance and premium reporting. Choose Agency when you serve multiple clients.

Subscriptions are designed to be cancellable for future billing periods through secure billing workflows when checkout is configured.

Yes. Annual billing can be enabled through configured secure checkout prices when the billing environment supports it.

Yes. The refund policy explains subscriptions, consumed reports, implementation work and applicable legal caveats.

No. CatalogWise is designed for online scanning, online checkout, online report unlocks and async implementation intake.

Yes. Agencies can use CatalogWise to run readiness audits, prepare client-ready reports and create recurring AI commerce readiness services.

The Agency architecture includes multi-store workspace and agency_stores data modeling for client portfolios.

Agency plans are designed for client-ready PDF audits and export workflows.

White-label reporting is planned inside Agency workflows and should be used only within valid client permissions.

Yes. Monitoring, report refreshes and roadmap tracking can support recurring catalog readiness retainers.

Agencies request access online, then configure clients, stores and reports when approved or subscribed.

Client invitation is a natural agency workspace workflow and is represented in the data model for future implementation.

The dashboard architecture supports multi-store views, report previews, recommendation queues and agency panels.

They can run public scans when reasonably authorized. SKU-level diagnostics require optional merchant-approved Deep Access.

Yes. Agencies can route clients into online implementation for audits, roadmap work and 30-day monitoring.

CatalogWise legal pages are prepared for an EU-based B2B SaaS operator with international customers.

CatalogWise collects account data, email, store URL, scan results, report events, chat messages, billing status, cookies and review submissions when used.

CatalogWise should never ask merchants to paste private Shopify passwords. Optional Deep Access uses secure server-side credential handling when enabled and approved.

Yes. Necessary cookies support product operation. Optional analytics, marketing and AI session personalization require consent.

Eligible users can request deletion through the privacy contact. Some records may be retained where required for security, accounting or legal reasons.

Yes. A secure checkout provider is the prepared billing path for subscriptions and one-time implementation payments. CatalogWise does not need to store full card data.

No. AI outputs are diagnostic and informational. Users should validate recommendations before making changes.

CatalogWise is not designed to sell customer data to advertisers. Marketing cookies, if ever used, require consent.

Yes, limited personal data such as account email, chat messages, billing identifiers and consent records may be processed to provide the service.

Contact privacy@catalogwise.com or the privacy contact configured in the production legal settings.

Check that the store is public, accessible and not blocking crawlers. If it still fails, create an account, retry later or contact support with the store URL.

Some stores use non-standard sitemap locations, block crawlers or expose product URLs through client-rendered navigation. Optional Deep Access may provide better coverage when approved.

Product URLs may be blocked, omitted from sitemap, rendered client-side or hidden behind app logic. CatalogWise marks the limitation rather than inventing products.

The checked public pages may be missing Product, Offer, Breadcrumb or Organization schema, or the schema may not expose enough fields for product comparison.

The premium PDF is a paid deliverable. public previews show a web preview while paid plans unlock downloadable and email-ready reports.

Checkout requires secure payment provider credentials and price environment variables. If checkout needs setup, CatalogWise fails gracefully and asks you to contact support.

The agent may be disabled by admin settings, limited by plan, unavailable because API credentials are missing or temporarily blocked by guardrails.

Free accounts are limited to one public scan every three days. Upgrade to run deeper diagnostics, export PDFs and monitor readiness without waiting.

In production, update the store record from the dashboard settings. In the preview flow, run a new scan with the corrected public domain when quota allows.

Use support@catalogwise.com or the support contact configured in production settings.