- Merchant creates and publishes products
- Customers add products to carts
- Checkout is created from the cart
- Customers pay on the Colossal Checkout page
- An order is created
Surfaces
Each of these primitives is exposed across multiple surfaces:- Events are typed operations that any automation step invokes directly. Use them in App Action steps when you wire deterministic operations from event or step data.
- Actions are typed operations that any automation step invokes directly. Use them in App Action steps when you wire deterministic operations from event or step data.
- Tools are LLM-callable functions. Use them when you want an LLM to pick what to call. Most write tools wrap the matching action (so they route through your approval policy). Read tools return shapes tuned for the LLM, sometimes richer than the matching action. For example,
get_customer_detailsincludesorder_countwhile theget_customeraction does not. - Storefront API is the public GraphQL surface. Use it from your storefront, an MCP server, or any external client that needs read or write access.
Projects
A project is your commerce environment. Each project has its own products, prices, customers, integrations, automations, and team members. Projects support multiple roles. Owners manage team settings and invites, builders can work in the chat and builder surfaces, and members are the default role for non-admin collaborators. Projects usually have a storefront, but that’s just one of multiple commerce surfaces that will be available. We are working on adding support for agentic protocols, allowing AI agents to discover and purchase products on behalf of users.Custom domains
When creating a project using chat, Colossal automatically deploys a storefront for it on a free subdomain. But for production storefronts, we recommend adding your own domain. You can do this either in the chat or by clicking Edit custom domain in the menu when clicking the Publish button in preview.