One catalog for all business types. Schema-driven. Define once — every app reads.
A single unified catalog spine. Each concept domain has its own schema — its own field structure, its own data model. The catalog adapts to any business type through the purview's concept type. Define a catalog item here. Every downstream app reads the same record. One definition. No re-entry anywhere in the platform. Pre-configured templates from the Blueprint store connect to any data point in any Calisto Pro app — full customization, plus templates to accelerate setup.
Eleven concept domains. Each with its own schema. One universal spine.
The catalog is not a flat product list. It is a structured spine — each domain carrying its own field structure. A product has variants, compliance rules, and shipping configuration. A service has providers, scheduling rules, and intake forms. A stay has room types, rate plans, and cancellation policies. The schema shapes the catalog item. The concept type determines which domains the purview uses. The spine is universal — what it holds is configured per business.
Eleven concept domains. Each with its own schema. One universal spine.
The catalog is not a flat product list. It is a structured spine — each concept domain carries its own field structure. A product has variants, compliance rules, and shipping configuration. A service has providers, scheduling rules, and intake forms. A stay has room types, rate plans, and cancellation policies. The schema shapes the catalog item. The concept type determines which domains the purview uses. The spine is universal — what it holds is configured per business.
Market. Dine. Time-Slots. Projects. Experiences. Stays. Events. Real Estate. Rentals. Artists. Active.
Each domain is a complete definition surface for that type of catalog item. Every domain carries its own subgroups of configuration — from the item definition to the supporting libraries, policies, and rules.
Every item defined by its schema. Every downstream app reads the same record.
A catalog item is a structured record defined by its category's schema. The schema determines which fields appear, which are required, which are conditional on sub-type. The item editor renders the schema — identity fields, media, configuration blocks, policy attachments, and cross-references to reusable libraries. One definition point. Every app that needs the item reads it from the catalog. No re-authoring.
Currency at the purview level. Language at the catalog level.
Currency is set per purview. Every app, every price display, every checkout reads the purview’s currency. Catalog items carry multi-language content fields per entry.
Define once. Reference across the catalog.
Provider profiles, waiver templates, modifier groups, territory zones, commission structures, inspection checklists, departure templates, seating layouts, space setups, crew roles, and more. Each domain includes reusable definition libraries — authored once, referenced by catalog items across the domain. A waiver template is written once and attached to any item that requires it. A provider profile is defined once and assigned across services. Libraries prevent re-entry and ensure consistency.
Define once. Reference across the catalog.
Each domain includes reusable definition libraries — authored once, referenced by catalog items across the domain. A waiver template is written once and attached to any item that requires it. A provider profile is defined once and assigned across services. Libraries prevent re-entry and ensure consistency.