Catalog

Organizations that are Shopify merchants early in agentic commerce

• These organizations should first enable and configure Shopify’s agentic storefront settings and improve product attribute completeness to validate whether Shopify Catalog exposure addresses immediate needs.

Organizations whose primary issue is internal product data governance

• Consider a PIM first (e.g., Plytix, Akeneo, Salsify). A PIM can act as the source of truth that then feeds downstream AI surfaces.

Organizations that need broad marketplace/feed management beyond agentic channels

• Feedonomics or mature feed platforms may be more appropriate when optimizing dozens of channels with strict templates and SLAs.

Organizations requiring security/compliance evidence prior to contracting

• Catalog does not publish SOC 2 or ISO certification evidence in accessible sources; regulated buyers may face procurement delays or inability to onboard.

Organizations requiring deterministic accuracy guarantees

• Any enrichment or AI expansion approach introduces the possibility of incorrect attributes unless workflows are tightly governed and audited.

Current limitations acknowledged by the vendor

• Public pages indicate an early-access and sales-led rollout approach.

Roadmap signals

• No detailed public roadmap was found in accessible sources.

Scale limitations

• No published throughput limits, rate limits, or SLA targets were found in accessible sources.

Security or compliance gaps

• Security certifications and audit reports are not publicly documented.

API limitations or integration constraints

• API key access appears to be gated by vendor contact.
• Bulk operations are referenced in documentation (for example: fetch up to 50 products in one request), but comprehensive limits and pricing are not public.

unique selling points suggested by the vendor (require validation)

• The vendor frames the product as a parallel storefront model designed for agent consumption while retaining the human-facing storefront.
• The vendor positions the product as enabling distribution of structured product data across multiple agentic shopping surfaces and protocols.
• The vendor highlights metrics intended to represent AI referrals and surfacing/completeness dashboards.

Independent validation

• Independent validation is limited. Press coverage summarizes funding and mission, but there are no published product performance benchmarks or third-party case studies accessible.

Where competitors have advantages

• Shopify: native integration and control over checkout and merchant admin.
• Feedonomics: mature channel operations and managed services.
• PIMs: workflow governance, internal collaboration, and structured product content management.

Availability of credible third-party reviews

• Gartner Peer Insights: no Catalog (getcatalog.ai) profile or reviews were found via accessible search results; Gartner pages can be difficult to access automatically.
• TrustRadius: no Catalog vendor page or reviews were found in accessible sources.
• G2: no G2 page or reviews were found for Catalog (getcatalog.ai). Search results surfaced similarly named products that are not attributable to getcatalog.ai.

Community and discussion signals (contextual, not verified reviews)

• Reddit contains discussions about agentic storefronts, unified catalog problems, and the general issue of AI shopping requiring structured, accurate catalog data. These threads are not directly about Catalog but provide market context:
  • Merchants discussing Shopify agentic storefronts and confusion about what it means.
  • Posts emphasizing structured variant/attribute data as the primary determinant of AI shopping readiness.

Vendor-published proof points (treated as vendor claims unless independently verified)

• The Catalog homepage displays example analytics dashboards (for example: AI referrals and readiness scoring). Methodology, customer identities, and independent verification are not provided in the accessible page snapshots.

Inferred reasons for adoption

• Likely reasons inferred from product positioning and broader market context:
  • Desire to be referenced by AI systems across multiple surfaces without building internal data pipelines.
  • A managed enrichment workflow beyond standard Merchant Center feeds or basic product schema.

Churn and reasons for leaving

• No direct churn testimonials were found in accessible sources.

Direct quotes

• Due to lack of accessible third-party user reviews specifically for getcatalog.ai, this report does not provide user quotes about product quality or support. Community quotes included in other sections focus on the broader agentic-commerce catalog readiness problem rather than Catalog itself.

Company sizes

• Likely best fits (inference):
  • Mid-market ecommerce brands: approximately 10–500 employees with meaningful SKU breadth and active growth channels.
  • Larger enterprises may engage but will require demonstrated security and compliance posture that is not publicly documented.

Industries and verticals where adoption is strongest

• Consumer goods categories where attribute richness affects recommendations (home goods, apparel, beauty, electronics accessories) and where AI shopping assistance is more frequently used.

Roles and personas

• Decision makers
  • VP/Head of Ecommerce, Growth Marketing leaders, Digital Merchandising leaders.
  • For developer-facing APIs: Head of Product or Engineering for shopping assistants, marketplace tools, or comparison engines.
• End users
  • Merchandising and operations teams managing product data quality.
  • Developers integrating extraction and search APIs.

Pain points and challenges the product addresses

• Products not appearing in AI shopping answers.
• Poor or inconsistent product representation (incorrect variants, missing materials/compatibility, thin descriptions).
• Difficulty keeping structured product objects synchronized with live price and availability.

Qualification criteria: what makes a suitable fit

• The organization has sufficient catalog complexity that manual enrichment is costly.
• The organization can operationalize a review and approval workflow for enrichment changes.
• The organization can measure incremental impact (AI referrals, assisted conversions) and has baseline analytics.

Deal disqualifiers: what makes a poor fit

• Requiring published SOC 2 or ISO 27001 evidence prior to vendor onboarding.
• Needing fully transparent self-serve pricing.
• Very small SKU counts where AI readiness can be addressed via native platform settings and basic schema/merchant center hygiene.

What the product does (core value proposition in objective terms)

• Catalog describes its offering as product data infrastructure for agentic commerce with two distinct go-to-market surfaces:
  • Merchant-facing: a managed layer that ingests a brand’s product catalog, enriches and structures it into machine-readable product objects, and distributes that structured data to AI shopping surfaces so brands can be referenced by name.
  • Developer-facing: APIs and documentation for extracting and enriching product data from URLs and for running agentic/semantic search across commerce sources.
• The vendor's central claim is that modern AI shopping agents rely on structured data rather than traditional web pages; Catalog aims to normalize and publish machine-readable product data across multiple agentic shopping surfaces.

Target market and market positioning

• Merchants and brands (particularly those on mainstream ecommerce platforms) that seek improved discoverability and more accurate representation in AI shopping surfaces (examples referenced by Catalog include ChatGPT, Gemini, Perplexity, Claude, Amazon Rufus, and Walmart Sparky).
• Developers and agent builders who prefer a structured product data layer (extraction, enrichment, search) instead of maintaining scrapers and brittle integrations.
• Market positioning is described as an infrastructure or protocol layer rather than classic SEO tooling or a basic feed-management application.

Company background (founding year, HQ, key leadership)

• Catalog identifies itself as Prosona, Inc dba Catalog and states a San Francisco presence.
• Founders (vendor-stated): Hamish Gunasekara (Co-Founder/CEO) and Dylan Farrell (Co-Founder/CTO).
• LinkedIn lists company headquarters in San Francisco, CA and a self-reported company size of 2–10 employees (LinkedIn ranges can be imprecise).

Funding and growth: investment rounds, acquisitions, estimated customer count/revenue if public

• Catalog announced a $3M pre-seed round led by Acrew Capital with participation from WndrCo and Hustle Fund (vendor announcement).
• Public sources reviewed did not provide verified customer count, ARR, or retention metrics.
• No acquisitions were found in accessible sources.

Pricing model with specific tiers and costs where available

• Merchant product materials indicate that pricing is not publicly listed and depends on catalog size and update frequency; pricing inquiries require contacting the vendor.
• API access is provided via API keys obtained by contacting the team; no self-serve pay-as-you-go pricing was found in public documentation.

Total cost of ownership considerations (implementation, training, hidden costs)

• Sales-led onboarding is likely to increase procurement overhead (security review, legal review, DPA, vendor risk assessment).
• Potential variable costs for merchants:
  • Ongoing enrichment and sync frequency (vendor ties cost to update frequency).
  • Internal time to review and approve enrichment changes (the vendor notes that enrichments are reviewable prior to publication, which can add operational time).
  • Data quality work on the merchant side (variants, GTINs, policies, structured attributes) to maximize AI surfacing outcomes.
• Potential variable costs for developers:
  • Usage-based costs (not published) for extraction, enrichment, search, and bulk operations.
  • Compliance and security review for using third-party enrichment and crawling/extraction services.

Key competitors in the space (list 4–6 direct alternatives)

• Shopify’s built-in agentic storefronts and catalog access / MCP tooling (for Shopify merchants).
• Feedonomics (feed management and optimization; sales-led pricing).
• PIM suites with syndication/enrichment workflows (examples): Salsify, Akeneo, Plytix.
• Product discovery/search platforms (less directly comparable for data distribution to agents): Bloomreach, Algolia (not deeply researched in sources for this report).