Completeness scoring. Atomic publishing. Template directives from headquarters.
The tools that ensure catalog quality and cross-location consistency. PIM-tier completeness scoring rates every catalog entry. A centralized media library governs all imagery. Bulk catalog tools handle import, export, field mapping, and duplicate detection. The F&B publishing pipeline stages menu changes as drafts and publishes them as atomic change sets with rollback. Template directives from headquarters propagate automatically to every business unit.
Completeness scoring. Media governance. Bulk operations.
Three surfaces for catalog quality. Completeness scores every catalog entry by its populated fields — surfacing gaps before they reach a customer-facing app. The media library is the centralized store for all catalog imagery, governed in one place. Catalog tools handle bulk import and export with field mapping and duplicate detection across the entire catalog spine.
Per-entry field scoring. Category-level coverage. Gap detection.
Every catalog entry is scored by the percentage of its schema fields that are populated. Scores are surfaced per item and aggregated per category. Incomplete entries are flagged before they propagate to selling surfaces. The scoring schema matches each category — a product’s completeness criteria differ from a stay’s, which differ from a service’s. The completeness surface shows which fields are missing and which items need attention.
Centralized media storage. Catalog-wide image governance.
One media library for the entire catalog. Images, videos, and graphics stored centrally and referenced by catalog items across all categories. Media governance in one place — no per-app image uploads, no duplicate assets across locations. When an image is updated in the library, every reference to it across the catalog reflects the change.
Import. Export. Field mapping. Duplicate detection.
Bulk catalog tools for large-scale catalog operations. Import with field mapping — map source columns to catalog schema fields. Export the full catalog or filtered subsets. Duplicate detection identifies potential duplicates across the catalog spine by configurable match criteria. Bulk editing applies changes across multiple catalog entries in one operation.
Menu drafts. Atomic change sets. Template directives from headquarters.
Two publishing models. The F&B publishing pipeline stages menu changes as drafts, groups them into change sets, and publishes them as one atomic update with price tracking and rollback. The template directive model turns Blueprint templates into headquarters mandates — a template published by headquarters pushes its configuration through to every business unit, automatically, with no per-location re-entry.
Headquarters publishes a template. Every business unit updates.
Templates from the Blueprint store connect to any data point in any Calisto Pro app. When used as a headquarters directive, a template becomes a propagating configuration. Headquarters authors or modifies a template — a catalog structure, a policy set, a checkout configuration, a brand standard. The template publishes to every purview in the group. Every business unit that references it receives the update automatically. No per-location manual re-entry. No version drift between locations. One template. Every location. Always current.
Staging. Diff review. Release authorization. Audit trail.
Publishing changes — catalog updates, policy modifications, template directives — pass through a governed pipeline. Changes are staged before they take effect. A diff surfaces exactly what changed, which purviews are affected, and which downstream surfaces will update. Release authorization gates the publish action — reviewers approve, reject, or request modification before the change goes live. The audit trail records every published change, every authorization decision, and every rollback.
Stage
Changes are staged before they take effect.
Diff
Exactly what changed, which purviews are affected, which surfaces update.
Authorize
Reviewers approve, reject, or request modification before the change goes live.
Publish
Approved changes go live. The audit trail records everything.