The order is entered once
and then runs itself
Guest QR menu, kitchen display, POS and stock — in one system. An item chosen at the table routes itself to the right station, lands on the bill and writes off the products.
Payments go to your account · 0% commission on orders
- Table
- 7 · window area
- Items
- 4 · two stations
- Total
- 38,40 €
- Beans
- −36 g
- Milk
- −0,45 l
- Syrup
- −20 ml
written off by recipe, no manual entry
order entry — by the guest or the waiter. Kitchen, POS and stock all read it from there.
commission on orders. The guest pays to your merchant account; the platform never touches the money.
instead of an app: the guest opens the menu with a phone camera and orders themselves.
Four contours
Guest, kitchen, POS and stock all work on one order
Not four programs to reconcile at close, but one order that passes through all of them.
The menu in the guest's phone
A QR on the table opens the venue's menu, no app to install. The guest picks size, add-ons and a note, sees allergens and ingredients, pays by card or on-site.
- Two modes — a QR on every table, or one QR at the counter for coffee to go.
- The server sets the price , not the browser: the order total can't be tampered with.
- Items are snapshotted at order time — editing the menu never rewrites bills already placed.
Bean of the week · 180 ml
Gluten, nuts, milk
The kitchen gets items by station
The order is split into tickets and routed to where it's made: hot line, cold line, bar, desserts. The screen updates in real time, and open tickets never age off it.
- Serving courses — cold and hot go out in the right order, not all at once.
- Recipe on screen — ingredients, grams and steps, so a dish doesn't depend on who's on shift.
- Every action is logged — who took it, who served it, when. Nothing to argue about.
The POS doesn't ask you to re-enter the order
The same order opens at the till with the total already counted. Cash, card on the terminal, tap-to-pay or a manual mark — the payment method doesn't change anything else.
- The bill splits by amount or by specific items — the remainder recalculates itself.
- Tips, refunds, change and a cash shift with reconciliation — all in the same screen.
- No double charges : a repeated request never creates a second payment.
Terminal online tap the card
A sold dish writes off the products itself
A dish has a recipe, and the recipe has grams. Sell a 350 ml cappuccino and exactly the beans and milk of that variant's recipe leave stock — not the base one's.
- The stock ledger is immutable — entries can't be edited or deleted, only added.
- Food cost and margin per dish, using a weighted-average purchase price.
- The stop-list turns on by itself when an ingredient runs out. Manual overrides automatic.
What else is inside
Six things that usually live in separate files
Rooms, tables & QR
A floor plan, each table with its own code. Or one code at the counter for coffee to go.
Shift schedule
A monthly planner: select several staff and paint days for all of them at once. Plus an hourly timeline.
Roles & permissions
Waiter, bartender, cook, cashier, manager. Financial reports are seen only by those who should.
Invoice import
Excel, CSV or a photo of the invoice. The system parses the lines, you confirm — the receipt hits stock exactly once.
Inventory counts
Full, partial or by zone. A gap between the count and the balance becomes an adjustment, not an argument.
Reports & export
Sales over a period, a breakdown by payment method, tips, refunds, cash-shift reports, CSV export.
Before & after
What changes in a shift
| Process | Usually | With BeShare |
|---|---|---|
| Taking the order | A notepad, then re-entry at the till | Guest or waiter enters it once |
| Sending to the kitchen | By voice or a printout for everyone at once | A ticket goes to its own station |
| Splitting the bill | Counted on paper | By amount or by item, the remainder itself |
| Product balances | A spreadsheet filled in from memory | Write-off by recipe at the moment of sale |
| Cost of goods | Counted once a month, if there's time | Food cost per dish visible at once |
| Stop-list | Found out after the guest already ordered | An item dims in the menu at zero balance |
| Money | Reconciling terminal and till at end of day | Payment tied to the order, the report is ready |
Money
The payment goes past us
The venue connects its own acquiring account. The guest's money reaches you directly; BeShare never sits in the payment chain.
No percentage of turnover — not on dine-in, not on coffee to go. The platform has a fixed subscription.
The total is computed on the server, payment is confirmed by the provider's webhook, and every action is written to history.
Launch
A pilot instead of a big rollout
We put the base contour on one location, watch it on a real shift and refine it to your processes. Without stopping the venue's work.
Setup
We load the menu and prices, print QR codes, add staff and roles.
Shift
Guests, waiters and the kitchen work in the system on a live flow.
Feedback
We gather what got in the way: for the floor, the kitchen, the till and the owner.
Refinement
We adjust to your processes and decide whether to go further — stock, purchasing, a second location.
What the venue provides
A menu with prices, recipes if you have them, an understanding of the current till, a few staff to test, and honest feedback.
What BeShare does
Sets up the system, loads the menu, prepares QR codes, onboards staff, runs the pilot and refines the product.
Questions
Briefly about money and rollout
How much does BeShare take per order?
Zero. The venue connects its own acquiring account and the guest's money goes straight to it — the platform never sits in the payment chain and takes no cut of turnover. BeShare earns from the subscription.
Do we need to replace the till and terminal?
Not necessarily. The POS layer is made vendor-independent: a cloud terminal, tap-to-pay, a cabled connection or a manual payment mark all look the same to the system. You can start with the hardware you already have.
Will the guest have to install an app?
No. The QR opens a normal page in the browser: menu, cart, payment and order status. No sign-up needed — the order lives at its own link.
We have no recipes. Won't stock work?
The menu, kitchen and POS work without them — stock is a separate step. You can add recipes gradually, starting with your best-sellers: write-off turns on exactly for the dishes that already have a recipe.
What about staff mistakes — are they visible?
Every action on an order and every stock movement is written as its own entry: who, what and when. The stock ledger is also immutable — an entry can't be edited or deleted, only a correction added. So a discrepancy can always be traced, not guessed.
How long does the pilot take?
Setup takes a few days: load the menu, print QR codes, add staff. Then the pilot runs on live shifts — exactly as long as it takes for the floor, kitchen and till to accumulate feedback. After that you decide whether to expand the contour.
Start with one shift
We'll load the menu, print QR codes and start the POS and kitchen at your location. Then you decide by the result.
0% commission on orders · Payments to your account · Disconnect any time
For photo studios — dedicated page →For podcast studios — dedicated page →All industries on BeShare for business →
Numbers, names and balances are for demonstration.