The trigger

What Ignited Our Questions; What Triggered Something Could Be Done Better?

The idea did not begin with a machine.

It began with a problem we experienced ourselves. A problem that occured from our way of operation and type of food.

At a very busy event, waiting times stretched to as long as 70 minutes. Orders were prepared strictly according to a FIFO system: first in, first out. No exceptions.

When an order was ready, the number was called and the customer collected the food.

During one particularly busy service period, a customer complained that people who had ordered after her had already received their food. According to our system, that should have been impossible.

We checked the order sequence.

Her order had been prepared at the correct time.

The problem was that someone else had collected it.

The customer had not responded immediately when her number was called, and another person had taken the food. By the time the mistake became apparent, her order had moved as many as 25 positions behind the current production line.

That raised a simple but important question:

Why should one customer be able to take another customer’s food?

The honest answer was that our system allowed it.

The food had been placed at the collection point. A number was called. In the noise and pressure of a busy event, staff could not always confirm that the person taking the order was the person who had purchased it.

It was not necessarily theft in the deliberate sense. The person may have misheard the number, assumed the order was theirs or simply taken the wrong products.

But the result was the same.

One customer received food they had not ordered.

Another customer, who had already waited a long time, had to wait even longer.

It was our mistake because the process did not provide enough control.

From that moment, our rule became clear:

No number, no food.

But the incident also exposed a larger weakness in the traditional order-and-collection system.

Even when the kitchen prepares orders correctly, the final handover can still fail.

Numbers can be misheard.

Customers can miss the call.

Orders can be taken by the wrong person.

Food can remain uncollected.

Staff can spend valuable time repeating numbers, searching for customers and remaking lost orders.

The problem was not only cooking speed.

The problem was control over the complete transaction.

Who ordered?

Who paid?

Which food belongs to which customer?

When was it prepared?

Who collected it?

And how much time was lost when one of those steps failed?

That experience became one of the questions behind our self-serve food truck concept.

What if payment, access and collection could become one connected action?

What if the customer could select the product, pay for it and immediately receive access to that exact compartment?

No shouted number.

No unattended order.

No confusion at the collection counter.

No opportunity for another customer to take the wrong food.

The customer chooses.

The customer pays.

The correct compartment opens.

The customer collects.

That is not automation for the sake of technology.

It is a response to a real operational problem.

And it is one more example of why time control is not only about speed.

It is also about accuracy, ownership and certainty.