Core concepts
The vocabulary you'll meet across the API, storefront, and MCP.
A quick glossary of the domain objects you'll work with.
| Term | Meaning |
|---|
| Organization | A tenant. Owns billing, plan, users, and one store. |
| Store | The shop or content site. Has a slug, domains, theme, settings. |
| User | A member of an organization, with roles/permissions. |
API key (crmk_…) | Org-scoped credential for server-to-server + MCP access. |
| Term | Meaning |
|---|
| Product | A catalog entity: simple, configurable (variants), or bundle. |
| Attribute | An EAV field (e.g. color, material) — specs and facets. |
| Attribute set | A named group of attributes defining a product's shape. |
| Category | A tree node for catalog organization. |
| Collection | A curated/automatic group of products for merchandising. |
| Term | Meaning |
|---|
| Theme | The set of Liquid templates, sections, assets + settings that render a store. |
| Section | A customizer-editable block with a {% schema %} of settings. |
| Template | A page's section layout (index, product, collection, page, …). |
| Customizer | The visual editor that edits theme settings + sections on a draft. |
| Content type | A custom, EAV-backed record type (e.g. houses, dishes) for non-product listings. |
commerce_enabled | Store flag; when false the cart/checkout routes 404 → a content site. |
| Term | Meaning |
|---|
| Quote / Order | The cart becomes a quote, then an order on checkout. |
| Customer | A storefront shopper; can belong to tiers, accrue loyalty. |
| Sales rule / Catalog rule | Cart-level discounts vs catalog price adjustments. |
| Plan / Entitlement | The subscription tier + the quotas/limits it grants. |
| Term | Meaning |
|---|
| MCP server | Exposes the API as agent tools + ships skills (playbooks). |
| Skill | A reusable playbook (e.g. shop-builder) served over MCP. |
Continue to Getting started → Accounts & organizations.
