All your orders in one pot.
Bigos connects the till, the kitchen and delivery platforms. An order from Uber Eats, Glovo, Wolt, Bolt Food or Pyszne.pl lands straight on a bill in the POS and on a ticket in the kitchen. No stack of tablets on the counter, no retyping.
Running every day at Pizzeria Bube in Wrocław, Poland.
Today every platform means another tablet.
Retyping
Staff copy each order from the platform tablet into the till. At peak time that costs minutes per order and mistakes in the extras.
Menus drift apart
A price changed in the till stays old on Glovo. The burrata is sold out, and Wolt keeps selling it.
No full picture
Revenue from platforms, dine-in and takeaway sits in five dashboards. Food cost and margin are guesswork.
One way in for every sales channel.
The hub receives orders from the platforms and from the restaurant's own website, converts them into one format and passes them to the till. Status goes back to the platform automatically.
What happens to an order
Receive
The platform sends the order to the hub. The hub checks the signature and the order number, so the same order never comes in twice.
Accept
The till accepts automatically with the venue's preparation time, or shows the order for a member of staff to confirm.
Kitchen
The ticket prints in the kitchen and at the bar. The bill appears in the till with the platform name and pickup time.
Status
“Ready” and “Picked up” from the till go back to the platform, so the courier and the customer see the real state.
Menu
Prices, photos and availability are set once in the back office. Marking an item unavailable in the till hides it on every platform.
Integration status
Orders from the restaurant's own website are live in production. Platform integrations are being built now, and we are applying for access to the platforms' APIs for restaurants.
Until the integrations are live, platform orders are entered in the till as a delivery / takeaway bill with the platform name and external order number.
Built for waiting staff, not for accountants.
Big buttons, size prices right on the tile, an alarm when food is late. Every screen comes from the working app; the data shown is sample data. The app itself is in Polish.
Floor plan
Tables in the venue's real layout. Colour tells you everything: open bill, not sent to the kitchen, food late, someone else editing.
Open bills
Open bills as cards: who, since when, last change. 15 minutes after a kitchen ticket the card starts blinking until someone taps “Served”.
Ordering
Categories, tiles with photos and size prices, half-and-half, extras, guests at the table, one-tap discounts.
Waiter's phone
The same bill on a phone. Bills live on the till in the venue, so everything keeps working without internet.
Back office
Menu, settings and versions in the browser. Reports by hour, product, waiter, discount and bill type, with CSV export.
Everything the floor and the kitchen need.
Fiscal printer
Receipts on Elzab printers over the local network: line discounts, split payments, change. A receipt queue that never prints twice.
Kitchen and bar tickets
ESC/POS printers. Only new items go on the ticket, removed ones print as CANCELLED. Serving order: first, next, last.
Many devices, one bill
The till and the phones see the same bills. A bill open on one device is locked for the others.
Works offline
Bills and the fiscal queue live on the tablet in the venue. When the internet is back, data syncs to the server by itself.
Split the bill
By guest or by item and portion. Each part is its own receipt, and the total always adds up.
Bookings
Website and phone bookings in one list. An hour before arrival the till asks staff to pick a table on the map.
Food cost and stock
Recipes, the cost of every size and extra, invoices from KSeF (the Polish e-invoice system), stock counts. Margin in the reports.
Back office
Menu, VAT rates, printers and devices from the browser. Every publish is a new version you can roll back to.
Bigos was built in a pizzeria, not in an office.
The first venue is Pizzeria Bube in Wrocław: an 18-table dining room, takeaway, catering and delivery. Every feature comes from something we were missing in our previous system.
An integration that doesn't lose orders.
The hub is a server-side service the platform connects to. The restaurant installs nothing extra: the order reaches the till it already uses.
Platform webhooks and APIs
We receive orders by webhook or poll them from the API, acknowledge them and keep the status up to date.
No duplicates
Every order is keyed by source + external ID. A repeated call returns the same result.
Queue and retries
If the venue is briefly offline, the order waits in a queue and is delivered when the till is back.
Security
HTTPS only, HMAC signatures, per-venue credentials stored on the server, never on devices.
Data in the EU
Server in the European Union. Customer data limited to what the order needs and deleted after the retention period (GDPR).
Full log
Every message to and from the platform is stored with a timestamp, so any dispute can be traced.
// POST /v1/orders · X-Bigos-Signature: sha256=…
{
"source": "glovo",
"externalId": "GL-4821-7730",
"venue": "bube-wroclaw",
"type": "delivery",
"pickupAt": "2026-11-21T19:40:00+01:00",
"items": [
{
"sku": "PIZ-MARG-33",
"name": "Margherita 33 cm",
"qty": 2,
"unitPrice": 4400,
"modifiers": [
{ "sku": "ADD-MOZZ", "qty": 1, "price": 600 }
]
}
],
"total": 9400,
"currency": "PLN",
"status": "accepted" // → in_kitchen → ready → picked_up
}Let's talk.
Running a restaurant, or representing a delivery platform and want to discuss an integration? Write to us.