Pricing plans

A pricing plan is a self-contained pricing world for a venue × event type × event-date range. Inside a plan, six layers stack to give you the price for any given event date. The whole plan can be enabled, disabled, duplicated and tweaked — letting you change next year's prices without touching this year's.

The six layers

Layers stack in this fixed order of precedence (top wins):

#	Layer	What it does
1	Manual date overrides	Locks a specific date to a fixed price. Short-circuits everything below — useful for VIP holds and one-off contracts.
2	Key dates	Bank holidays, NYE, Valentine's. Adds a percentage of the base on top of the multiplier stack.
3	Seasonal bands	Group months into peak / shoulder / low (or whatever you prefer). Multiplies the base.
4	Day of week	Saturday +15%, weekday −25% — the usual venue-week shape. Multiplies the running total.
5	Lead-time inflation	Couples booking 18 months ahead pay slightly less than couples booking 6 months ahead — this layer encodes that.
6	Base prices	Flat venue hire fee plus a per-guest catering minimum. The foundation everything else multiplies against.

The formula

final = base × season × day_of_week × lead_time + key_date_adjustment
        ↑ unless a manual override exists for the date

The plan editor shows this exact breakdown for any date you click on the live calendar preview. Operators don't have to guess what their rules will produce.

Plans are scoped — and that's how you A/B test

Each plan carries:

• Active date range — the event dates this plan applies to. Defaults to a calendar year (1 Jan – 31 Dec) but you can pick any window.
• Locations — empty list = applies to every venue. Pick specific ones to scope.
• Event types — empty list = applies to every event type. Pick "Wedding" to make it wedding-only.
• Priority — when two plans match the same event, the higher number wins.
• Status — Draft, Active, or Archived. Only Active plans are used at quote time.

Plans match on the event date, not the booking date. A wedding happening in June 2026 uses your 2026 plan regardless of when the couple enquired. Lead-time inflation is a modifier inside the plan that compares booking date to event date.

Duplicating for next year

The Plans index has a Duplicate action on every plan. The dialog defaults to:

• Name: shifts the year forward in the original name (e.g. "2025 weddings" → "2026 weddings")
• Shift dates: +1 year
• Adjust prices: +5%

The duplicate is a draft, scoped to the new year, with base prices and any manual overrides bumped by your chosen percentage. Multipliers (seasonal, day-of-week, lead-time) carry over unchanged because they're already proportional. From there, you fine-tune.

Calendar preview, always-on

The right side of the editor is a heatmapped calendar of every day in the plan year, shaded by computed venue-hire price. Click any day for the layer-by-layer breakdown:

Saturday 13 June 2026                      £6,120.08
Base venue hire   £4,000.00         £4,000.00
Seasonal band     Peak +30%         £5,200.00
Saturday          +15%              £5,980.00
Lead-time         0.8 yr × 3%/yr    £6,120.08
Catering minimum  80 × £75          £6,000.00

Every change you make to a layer updates the calendar in real time, so you can see exactly where prices move before you save.

Stacking plans with priority

Common pattern: an annual base plan plus a seasonal override.

• 2026 weddings — Jan 1 – Dec 31, priority 100, your normal pricing.
• Christmas 2026/27 — Nov 15 – Jan 5, priority 200, premium pricing for the party season.

Both are active. For a December event, both match — the Christmas plan's higher priority wins. For an October event, only the annual plan matches. No carving holes in plans, no precedence headaches.

Status & lifecycle

A plan moves through Draft → Active → Archived:

• Draft — hidden from quote evaluation. Use for plans you're still tuning.
• Active — used at quote time within its date range.
• Archived — preserved for the record, never matches new quotes. Quotes already issued under that plan are unaffected.

Toggle status from the index dropdown or the editor header — no need to delete a plan to take it offline.