Bump bar

Bumping a ticket means marking it done and clearing it from the live kitchen queue. A bump bar is the row of physical buttons that does it; on a touchscreen it is the large control at the bottom of the ticket, which has to be reachable with a knuckle rather than a clean fingertip. Recall - bringing a ticket back - matters as much as bump, because tickets get cleared by accident several times a week.

In practice

Bumping a ticket means marking it done and removing it from the live queue. A bump bar is the physical buttons that do it; on a touchscreen it is the big obvious control at the bottom of the ticket, which has to be reachable with a knuckle.

Recall matters as much as bump. Tickets get cleared by accident several times a week, and a system without one-tap recall turns that into a phone call with a customer.

Both actions should be logged, because "how long did that order actually take" is answerable only if the moment it was marked ready is recorded.

Also called: bump, recall order.

Questions people ask about bump bar

Why does recall matter as much as bump?

Because tickets get cleared by accident several times a week in any busy kitchen. A system without one-tap recall turns that into a phone call with a customer, or a second cook of an order nobody can see any more. Recall is the difference between a mistake and an incident.

Should bump and recall be logged?

Yes, with timestamps. "How long did that order actually take" is only answerable if the moment it was marked ready was recorded, and a pattern of recalls on one station at one time of day is usually telling you something about the station rather than the staff.

Is a physical bump bar better than a touchscreen?

In a wet or greasy station, often yes: buttons work with gloves on and survive being wiped down. On a screen, the equivalent is a control big enough to hit with a knuckle without looking, which is a design decision rather than a hardware one.