Portfolio Sync Fabric across a boutique hotel group
Two to twelve properties on SiteMinder Multi-Property, one master rate grid, per-property overrides that survive republishing, and an audit log the head office actually reads.
The Portfolio Sync Fabric module on the Hotelminder shortlist is aimed squarely at boutique groups running two to twelve properties on SiteMinder Multi-Property — a shape we see everywhere in Northern Italy, southern France, and the low countries. It is not aimed at chains of forty properties (they need a heavier tool) and it is not aimed at single hotels (they do not need any of this). Somewhere in between sits the sweet spot: enough properties that managing rates one by one is painful, few enough that a well-designed master template plus disciplined overrides is enough.
The master rate grid — one canonical view
Start by defining a single master rate grid that captures your group's shared logic: the base tariff logic (fixed floor plus seasonal multiplier), day-of-week multipliers (Fri/Sat premium, Sun/Mon discount, midweek flat), seasonal calendars (three seasons is a good default for European boutique groups — low, shoulder, peak — with the transitions calendared per property region), restrictions (minimum length of stay by season, closed-to-arrival on peak weekends), and cancellation policies. The Fabric holds this master grid in one place; nothing else should be edited by more than one person.
Per-property overrides — the boring but crucial part
Every property in the group can and should carry a small set of overrides that reflect its physical reality. The Vienna villa's 3-night restriction on New Year's Eve. The Milan flagship's 14-day cancellation policy that the corporate segment demands. The Amsterdam canal house's Sunday-arrival-only rule during Tulip season because check-in staff coverage is thinner. These overrides survive republishing — the master grid does not overwrite them unless you explicitly tell it to. That single guarantee is the reason boutique groups adopt the Fabric; every previous tool most of them tried would silently trample the overrides on Monday morning.
The audit log — who changed what, when, and why
Every push, every override, every revert appears in the audit log. Each entry carries the actor's Hotelminder user ID, the timestamp, the diff (what changed from what to what), and an optional free-text reason field. That last field is voluntary but we ask you to enforce it as a group discipline — the ninety seconds someone spends writing "shifted Vienna NYE to 3 nights after last year's overbook" pays back on every future audit conversation and on the day someone new inherits the portfolio.
The revert — how to undo a bad Monday
Any push can be reverted to any prior version, including the pre-Sync-Fabric baseline we snapshot at onboarding. Revert is one click in the dashboard, propagates in under two minutes, and re-writes the audit log with a revert-to-version marker. The pre-Fabric baseline is important: it means that on the day you want to test whether the Fabric is still saving you time, you can flip everything back to the manual state for a week and compare. Nothing lost.
Roll-out sequence for a five-property group
Week 1 — connect all five properties to Hotelminder with individually scoped SiteMinder API keys (see the key hygiene guide). Week 2 — advisor sits with the group's revenue lead and drafts the master rate grid in a shared editor, then imports it into the Fabric as a draft, not a live push. Week 3 — publish the draft to a single test property (usually the smallest, quietest one) and watch a full seven-day rate cycle. Week 4 — publish to the remaining four properties, keep the pre-Fabric baseline pinned as the fallback. From week 5 onward, weekly master pushes become the norm and the head office reads the audit log at the Monday revenue meeting.
What Portfolio Sync Fabric does not do
It does not do revenue management — it publishes what you tell it to publish. Pair it with Rate Reasoner for a suggested master grid you can edit, or with Distribution Intelligence Layer for the pickup-versus-forecast data that informs the next week's push. It does not replace SiteMinder Multi-Property — each property keeps its own SiteMinder login, its own guest reports, and its own accounting. The Fabric sits above and orchestrates.