KMS Auto Bump Functionality

Background

Within the KMS there is currently a configuration option that allows tickets to be hidden from view after being active for X minutes.

Important distinction:

• The ticket is only hidden

• It is not automatically bumped

• It remains active within the system

• Manual bumping is still required to clear it

All tickets must currently be manually bumped by the kitchen team.

Client Use Case – Westmorland

In peak trading periods at motorway service locations:

• Trade volume becomes extremely high

• Operational focus shifts from KMS best practice to service speed

• Teams prioritise getting food out over screen hygiene

As a result:

• Tickets are completed physically

• But not always manually bumped on the KMS

• Tickets accumulate on the system

• Hidden tickets still exist in the background

This creates two challenges:

1. Operational visibility becomes cluttered

2. Increased system load and network traffic due to large volumes of un-bumped tickets being retained

Over time this can impact:

• Performance

• Responsiveness

• Overall KMS stability in high throughput environments

Problem Statement

The current "Hide after X minutes" setting does not solve:

• Ticket accumulation

• System load caused by un-bumped tickets

• The operational reality of high intensity service environments

Manual bump reliance does not scale well in high volume motorway or QSR style trading.

Requested Enhancement

Introduce an Auto Bump feature within KMS.

Core Requirement

Allow sites to configure:

Auto Bump after X minutes (configurable by site)

Behaviour:

• Ticket becomes active

• If not manually bumped within X minutes

• System automatically bumps the ticket

• Ticket is fully cleared from the active queue

This would be separate from the existing hide setting.

Configuration Scope

Minimum viable version:

• Auto Bump setting configurable at site level

• X minutes configurable value

Future enhancement – Version 2 (if required):

• Auto Bump configurable by sales area

If sales area granularity significantly delays delivery, site level configuration would still provide immediate operational value.

Operational Benefits

• Prevents ticket build up during peak trade

• Reduces screen clutter

• Improves KMS usability in high volume environments

• Aligns system behaviour with real world kitchen behaviour

• Reduces dependency on perfect staff compliance

• Potentially reduces unnecessary system load and network traffic

Commercial Impact

• Supports Westmorland peak trading environments

• Strengthens KMS offering for high volume estates

• Increases suitability for motorway services, travel hubs, QSR and stadium environments

• Reduces perceived performance issues caused by ticket accumulation

Suggested Priority

Medium to High

Driven by live enterprise client use case with scalability across similar environments.