Dynamic price bands: multi-site pricing without the spreadsheet

What does the capability do?

It lets a multi-site operator run genuinely local pricing without turning every price change into a spreadsheet project, and without maintaining a parallel structure of pricing groups.

• Bands are dynamic, not configured. There is no group entity to create, name, or keep in sync. A band is simply the set of sites currently sharing the same fees. Set a price at a site and it forms a new band or joins an existing one, automatically. The pricing is the structure.
• Change a band or a site, equally naturally. A band-wide update moves every matching site together; pricing one site individually moves just that site into its own band. Both are first-class operations, so local exceptions and estate-wide rises use the same, obvious mechanism.
• A row per site, fees together. Each package prices each site with its registration fee, recurring fee, and freeze fee as one row. The freeze fee is priced with the same care as the headline fee, not forgotten in a policy document.
• A default that closes the gaps. A default pricing row covers any site without an explicit price, so opening a new location never leaves a package unpriced or accidentally free.
• Safe bulk updates. A band-wide edit matches sites on their current fee triple: only rows whose three fees equal the band’s current fees are updated, each with its own audit event, and the operation reports exactly how many sites changed. Sites on a different tariff cannot be caught by mistake.
• Scheduled rises included. Future-dated changes work at the same per-site or per-band granularity through scheduled price changes, so a rise lands on the right date without manual work.

Why dynamic beats configured groups

Pricing groups sound tidy until they meet reality: a site needs a local exception, so someone creates a new group, moves the site, and now two structures (the groups and the actual prices) must be kept honest against each other forever. Deriving bands from the prices themselves removes the second structure entirely. If a site’s fees were adjusted out of band yesterday, today’s band update passes over it, which is exactly what the operator would want and exactly what a per-site spreadsheet forgets. The classic multi-site accident, a change meant for one group applied to the whole estate, has nothing to latch onto.

Why it matters

Local pricing is commercial reality for multi-site and franchise operators; the question is only whether the software carries the complexity or the staff do. Dynamic bands, per-site rows with a default, audited bulk updates, and scheduled changes mean the price list in the system is the price list, provably, at every site. That trustworthiness is what the Membership accelerator is built around.