Point of sale
POS for multiple carts and service points, including several sites at one event.
Case study / Magic Bean Coffee
Magic Bean Coffee can have several carts and service points at one event. We built our own platform to suit that setup, with POS, online ordering, kitchen displays and loyalty designed together.
Explore the case study ↓The business context
Magic Bean Coffee is part of em.bee Group. Because we run it ourselves, we know how orders, preparation and customer service work on a busy day.
An event can involve several carts and sites working at once. We needed software that suited that operation and was straightforward for customers and staff.
The challenge
The off-the-shelf solutions we considered were targeted at single-site operators. They weren’t the right fit for an operation where multiple carts and multiple sites may be working at the same event.
The standard loyalty options were also awkward to fit into service. They added steps for customers and staff, so using a separate loyalty or CRM add-on wasn’t giving us the experience we wanted.
Why we chose bespoke
We needed to support multiple carts and sites at one event, with loyalty built into the service process. The single-site products and separate loyalty options we considered weren’t a good fit.
Building our own meant we could design POS, online ordering, kitchen displays and loyalty together, using the way we actually work as the starting point.
That gives customers a smoother experience and makes service more efficient. It also lets us change the software when the operation changes.
The solution approach
Four parts of the same operation.
POS for multiple carts and service points, including several sites at one event.
Online ordering designed alongside the service process that receives and prepares the orders.
Order information presented for the people preparing it.
Loyalty built into the platform so it works with ordering and service, without the friction we found in separate add-ons.
Designed as one experience
Built for carts and service points operating across an event.
What we learned
For us, the reason to build was the fit. We needed to work across an event and make loyalty part of a good service experience.
Those requirements gave us a reason to go bespoke. Understanding them came before choosing the technology.
Next case study: AI-assisted receipt & invoice processingTalk to us
Tell us how you run service, what you use now and where it falls short.
Discuss your project