Topics: onboarding, demo, audit, setup, contact, API access
Questions answered
- How do I get started with Catalog?
- What do I need for setup?
Book a demo or request an audit
Evidence basis: public_source · Section citation
Use the existing demo scheduling link to speak with Catalog, or request a product-data audit through the main website. The audit form asks for contact details and the brand website; the team follows up by email.
Sources: Catalog website · Request a product-data audit
What to bring
Evidence basis: public_source · Section citation
Bring your brand website, commerce platform, examples of difficult product questions, and the sources available to answer them. Identify the channels and measurements that matter to your team.
Sources: Catalog website · Request a product-data audit
Agree on access, review, and launch
Evidence basis: public_source · Section citation
Confirm the source connection, workspace setup, products to include, review process, and domain configuration with Catalog. Establish how you will check published content and what evidence will count as success.
Launch time depends on access, source quality, catalog size, review, and DNS. This reference does not promise a fixed turnaround. Pricing and commercial terms must be confirmed with the team; no purchasable plan is offered here.
Sources: Catalog website · Request a product-data audit
Choose the engagement path
Evidence basis: editorial_guidance · Section citation
For a merchant deployment, begin with the product-data problem and the source platform. For a developer integration, begin with the input type and required API output. For an evaluation, begin with a representative product sample and the question the pilot needs to answer. These can be related projects, but none automatically includes the others.
The documented API access contact is founders@getcatalog.ai. The demo and audit links remain on their original services. Reading a contact address or preparing a request is different from sending it. An agent should obtain the user's agreement before sharing contact details, product data, credentials, or other information with a service.
brand
- path
- Brand implementation
- prepare
- Store URL, commerce platform, product scope, difficult product questions and source access
- confirm
- Connection method, review, publishing scope, domain work and ongoing responsibilities
api
- path
- Developer API
- prepare
- Input URLs/vendor/query, needed fields, endpoint version and intended workload
- confirm
- API account, billing, processing options, result schema and error handling
evaluation
- path
- Audit or pilot
- prepare
- Representative products, baseline evidence, target outcome and measurement window
- confirm
- Deliverables, sample limits, success criteria and interpretation boundaries
Sources: Catalog website · Request a product-data audit · Public API authentication reference
Onboarding completion states
Evidence basis: implementation_review · Section citation
The Shopify implementation includes installation confirmation, workspace provisioning, webhook setup, initial synchronization and storefront domain work. These are separate checks. A successful OAuth connection does not mean every product has been processed, and an enabled product does not prove its public page is correct.
Before reporting a merchant launch complete, verify the intended product scope, actual public representations, correct consumer-site links and the necessary DNS/TLS state. Confirm which ongoing measurements are connected and which remain unavailable. Setup time depends on permissions, source quality, review and domain configuration; use a scoped estimate from the team.
Sources: Catalog website · Request a product-data audit
Related documents
Contact destinations
Book a demo ↗ Request an audit ↗
API access: founders@getcatalog.ai