Documentation

Start with merchant onboarding. Go technical only when you need to.

The docs are split into two layers so commercial visitors can understand setup, permissions, review flow, and data handling before they ever need API or implementation details.

Merchant getting started Developer docs

Merchant setup summary

Setup is designed to be a short guided flow: connect Shopify, let the catalog load, review the first audit, and then decide whether your team needs ongoing automation.

Exact install permissions should always be reviewed in Shopify during the install flow. ACP needs access to catalog data required for audits and feed workflows, and deeper publish workflows may require broader permissions than the first read-only review step.

AI provider keys are not required to start the audit. They become relevant when the merchant chooses deeper optimization workflows that depend on model generation.

Merchant onboarding

Install flow

Connect Shopify, let ACP read the catalog, and start with the first audit before deciding what should be automated.

Read-only audit first

The public onboarding path is designed to show issues, score, and product priorities before any live catalog changes are reviewed.

Review and approval

Teams can inspect recommendations and decide how approval and publish workflows should be handled.

Ongoing automation

Paid plans are for stores that need recurring detection, cleanup, and stronger operating controls as products change.

Technical layer

Developer endpoints and route handlers

Integration notes for Shopify, AI providers, Stripe, and store data flows

Implementation details for optimization, approval, and publish workflows

The technical layer is kept separate so non-technical buyers are not forced to parse endpoints and model configuration before they understand the onboarding story.