Dynamic pricing for peak periods

Peak pricing can protect capacity and contribution, but it should not be used to disguise operational failure or surprise customers. Start with non-price controls, define a transparent rule and test the effect on demand, fairness and service quality.

Confirm the problem first

Is the constraint kitchen capacity, driver availability, long-distance demand, low-value baskets or a promotion running at the wrong time? A higher price cannot create grill space, trained staff or safe roads. It may simply move complaints to checkout.

Use a control hierarchy

1. Improve preparation, menu availability and order routing.
2. Limit slots or reduce delivery zones.
3. Pause promotions and low-contribution items.
4. Adjust minimum order or free-delivery threshold.
5. Consider a transparent peak fee or price change only if still justified.

Choose a rule customers can understand

Make the price transparent

Customers should see a realistic and attainable total, including mandatory fees, before committing. Do not advertise one price and reveal a compulsory peak, service or packaging charge at the final step. Explain the time, zone or condition clearly and keep optional tips genuinely optional.

Protect fairness and trust

Avoid opaque person-specific prices based on inferred vulnerability, device type or past willingness to pay. Use simple operational variables and document the rationale. Provide a clear support route for boundary errors or accessibility needs.

Test operationally

• Verify every channel and marketplace rule.
• Test daylight-saving and time-zone changes.
• Check refunds, promotions, loyalty and tax treatment.
• Provide a manual pause and rollback.
• Measure basket, conversion, contribution, complaints and capacity.
• Stop if service quality or customer trust deteriorates.

Practical next step

Choose one recurring peak and compare three options: zone reduction, promotion suppression and a transparent fee. Pilot the least intrusive control first and keep a written decision record.

Define governance and audit

Record who can change the rule, which data triggers it, how often it updates and how the customer total is calculated. Staff should be able to explain the price without inventing a reason. Preserve the effective rule for later complaints, refunds and finance review.

Use shadow testing

Before changing live prices, calculate what the rule would have charged during several representative weeks. Compare demand, capacity and contribution under normal, event, weather and failure conditions. Check edge cases such as a customer beginning an order before the peak window and paying after it starts.

Provide an off switch

Automatically generated pricing needs a manual pause for wrong data, reputational risk or operational change. Define who can use it and how channels are restored consistently. Review complaints and vulnerable-customer impacts, not only revenue.

Related guides

• Business Planning and Finance — the main guide for the wider topic.
• Pricing and Margin Management — the broader guide that frames this implementation.
• Service charge models — a closely related operational control to review alongside this page.
• Pricing delivery to cover true costs — a closely related operational control to review alongside this page.

Sources and date checked

Guidance checked: 24 July 2026. Recheck official guidance, local requirements and supplier documentation before changing a live operation.

• CMA: price transparency guidance
• CMA: unfair commercial practices