BeeBee

BeeBee cashes up faster.

Every evening BeeBee reconciles till, online shop and delivery platforms. With Pharen it takes 5 minutes instead of 60 and saves about €1,400 a month.

A BeeBee sushi platter
Client
BeeBee
Industry
Restaurants
Location
Ilmenau, Thuringia
Services
  • Process design
  • workflow automation
  • data reconciliation

The BeeBee restaurant in Ilmenau receives about 3,700 orders a month, at the till, in its online shop and through delivery platforms. At the end of each day, a workflow in Pharen Hub brings the day's data from all 3 sources together. It maps the values to the same fields, totals orders, revenue and cancellations, and checks delivery platform payouts and cancellation reasons against fixed rules.

The reconciliation used to take about 60 minutes every evening, and with the month end close almost 40 hours a month. Today it takes about 5 minutes in the evening, and on most days 0 to 3 exceptions remain. That saves about 35 hours a month, worth about €950 at €27.40 labour cost per hour in hospitality. On top come about €430 a month from delivery platform payouts whose gaps now show up the same evening. Together that is about €1,400 a month. Resolving the issues stays with BeeBee.

With Pharen, BeeBee has:

  • brought about 3,700 orders a month from till, online shop and delivery platforms together in one daily overview
  • cut the check at the end of the day from about 60 to about 5 minutes and the month end close from about 8 hours to 1
  • saved about 35 hours of working time a month, worth about €950
  • made gaps in delivery platform payouts visible the same evening, about €430 a month
  • resolved missing cancellation reasons the same evening, while the shift still remembers
  • limited open items to the exceptions, 0 to 3 on most days

Starting point

At 8 pm, delivery hours end at BeeBee in Ilmenau, 7 days a week. After that, there used to be about 60 more minutes that no guest ever sees: the end of day close.

About 3,700 orders come in each month, about 120 on a normal day: at the till, in the online shop and through delivery platforms. Every order was recorded, but in 3 systems that knew nothing about each other. Only when someone laid orders, revenue, cancellations and payouts side by side was the day complete.

3 systems, 3 formats

The till supplies the sales on site and the day’s cancellations. The online shop lists direct orders with the payment method. Each delivery platform keeps its own order lists and pays out later, minus commission and often bundled for several days. The values did not arrive in the same format or under the same labels.

Before: about 60 minutes after closing

Someone from the team opened all 3 views, copied the daily totals into a spreadsheet and checked whether order count, revenue and payout matched. Cancellations needed a reason. If one was missing, the search went back to the shift, often not until the next day, when nobody remembered exactly.

If a delivery platform payout was lower than the orders behind it, someone had to find out whether a fee, a delayed payment or a mistake was the cause. After a busy day there was often no time left for that. At the end of the month, someone then laid the delivery platform payouts against the orders once more, about 8 hours of work, and small differences still slipped through.

About 60 minutes on about 30 evenings is 30 hours a month. With the month end close it came to almost 40, as much as 1 full working week. The Federal Statistical Office puts labour costs in hospitality for 2025 at €27.40 per hour worked. So the reconciliation cost BeeBee a good €1,000 a month, for copying figures and doing the sums again.

Implementation

What we built in Pharen Hub

We set up the end of day close as one workflow. It takes the day’s data from the till, the online shop and the delivery platforms, maps it to the same fields and writes orders, revenue and cancellations per source into one shared overview.

Then the workflow checks fixed rules. Does a delivery platform’s payout match its orders? Fees the platform lists do not count as a discrepancy. Does every cancellation have a reason? If something stays unresolved, it appears as an open item with source and amount. A day without discrepancies is closed without the team adding up every total again by hand.

BeeBee’s end of day close as a workflow in Pharen Hub. After closing, it pulls data from the till, online shop and delivery platforms, maps their fields to one shared schema, separates the delivery platform fees, adds up the values per source and saves the totals. Check rules log mismatched payouts and cancellations without a reason as open items, otherwise the day is closed.
The workflow, rebuilt with sample data in Pharen Hub. Only when a check rule fires does an open item appear in the daily overview.

How the end of day close runs today

  1. After closing, the daily totals from the till, online shop and delivery platforms go into the workflow.
  2. The workflow maps the different fields to one shared schema.
  3. Orders, revenue and cancellations are added up per source and saved as the daily total.
  4. Delivery platform payouts and cancellation reasons run through the fixed check rules.
  5. Without a discrepancy, the day gets the status “Closed”. With a discrepancy, only the affected item stays open.
  6. The team checks the receipt or the shift note, adds the reason and closes the item. For an uneventful day a glance at the overview is enough, with 2 open items it takes about 5 minutes.

The workflow does not change any payout and books nothing in the accounts. It prepares the reconciliation and shows where a decision is needed. Resolving the issues stays with BeeBee.

Result

One day, 2 open items

The daily overview below shows 7 sample days with anonymised figures. On 26 September there were 75 till orders with €2,520.00 in revenue, 30 online shop orders with €945.00 and 19 delivery platform orders with €655.00. Together that is 124 orders and €4,120.00.

3 orders were cancelled. That left 2 items for the team: one delivery platform payout was €43.10 below the order total, and 2 till cancellations had no reason. For the €43.10 the team looks at the delivery platform’s statement, and for the cancellations it asks the shift that was on the till that evening. Everything else was already reconciled.

BeeBee’s daily overview in Pharen Hub with 7 sample days from 20 to 26 September, each with orders, revenue, cancellations, open items, status and note
The daily overview with sample data. On 26 September it shows 124 orders, €4,120 in revenue, 3 cancellations and 2 open items to check, while the days before are all closed or resolved.

About 35 hours less reconciliation a month

Today the evening check takes about 5 minutes instead of 60. The month end close needs about 1 hour instead of 8, because the days are already checked. Almost 40 hours a month have become about 3.5, so about 35 hours less. At €27.40 labour cost per hour in hospitality, that is about €950 a month.

Gaps in delivery platform payouts show up the same evening

A gap like the €43.10 on the sample day now shows up the same evening, while it can still be documented and disputed with the delivery platform. At about 10 such gaps a month, that is about €430 that used to get lost in the monthly statement.

Together with the saved working time, that makes about €1,400 a month.

What has changed

The end of day close no longer starts with 3 views and an empty spreadsheet. The team opens the daily overview and sees right away whether anything needs resolving. It resolves missing cancellation reasons the same evening, while the shift still remembers. For the month end close, the days are already checked.

BeeBee now cashes up faster. And clocks off sooner. 🍣

Published on , updated on .

More case studies

What's on
your horizon?