Skip to content
ATLASBIP Business Intelligence Partners
ATLASBIP Business Intelligence Partners

HoReCa · Restaurant POS & SaaS Live product

Foodost — Restaurant POS and management system: five apps on one API

Five apps, one restaurant, nothing typed twice

Foodost is the restaurant operating system we designed, built and run. An offline-first POS, a real-time kitchen display, a QR menu with an AI waiter, an admin panel and an operator console share one API. An order is taken once, then reaches the kitchen, the stock, the fiscal receipt and the P&L without anyone retyping it.

Discuss a similar project Walk through a service

Project facts

Project type
Our platform
Services
Platforms
Web · POS · Kitchen display · QR menu & kiosk
Languages
AZ · EN · RU

The challenge

Six tools on one counter, and none of them talk

A typical restaurant runs on a till from one vendor, a tablet for each delivery app, paper tickets on a spike, a separate fiscal register, stock in a spreadsheet and the owner’s WhatsApp. On a quiet Tuesday it holds. On a Friday at 20:40 it breaks.

  1. Delivery tablets

    Every order typed twice

    Wolt and Bolt Food each ring on their own tablet. Someone retypes every order into the till, and the kitchen hears about it last.

  2. Paper tickets

    The kitchen loses the thread

    Tickets fall off the rail, modifiers get misread, and nobody can see which table has waited longest.

  3. Cloud-only till

    No internet, no sales

    When the connection drops mid-rush, the till freezes. Orders go onto napkins and never quite make it back into the system.

  4. Spreadsheet stock

    Stock counted on Monday

    Ingredients leave the shelf with every plate, but the spreadsheet only finds out at the weekly count, long after the waste and the losses.

  5. Menu prices

    Margins are a guess

    A supplier raises the price of lamb and the menu stays the same. Nobody knows what a kebab really costs until the month’s books close.

  6. Owner’s phone

    Numbers arrive tomorrow

    Each branch sends its own photo of the Z report. Comparing them takes an evening, so it rarely happens.

Foodost replaces the pile with one flow

19:52 Offline-first POS

The internet drops. The till keeps selling.

Every order, payment and receipt is written to the device first and synced to the cloud after. When the connection goes, waiters keep taking orders and cashiers keep closing bills. When it returns, the queue empties itself: nothing retyped, no ticket lost.

  • Offline-first

    Orders, payments and receipts are created on the device and queued. The queue syncs by itself the moment the connection returns.

  • Tables and tabs

    A floor plan per zone shows free, occupied, bill-requested and reserved tables. Tables merge, move between waiters and keep open tabs.

  • Split and pay

    Bills split by guest, by amount or by item. Cash and card mix on one bill, and tips are tracked apart from revenue.

  • Voids under control

    A void or a comp needs a reason and a manager PIN, and every one lands in the audit log.

  • Sold out everywhere

    Mark a dish sold out once, and every till and the QR menu stop selling it at the same moment.

20:14 Kitchen display · Delivery

Every channel lands on one kitchen screen

Hall orders, QR orders, Wolt and Bolt Food arrive on the same kitchen display as soon as they are confirmed. Each dish goes to its station, a timer starts, and a ticket turns red before the guest starts looking at the clock.

All channels, one stream
  • Hall POS
  • QR menu & kiosk
  • Wolt
  • Bolt Food

Kitchen display

Menu, prices and sold-out dishes sync back to the delivery platforms.

  • Stations and courses

    Each dish goes to its station (grill, hot, cold or bar), and courses fire in order: starters, mains, desserts.

  • Modifiers you can read

    “No onion”, “well done” and “sauce on the side” are printed clearly on the ticket, not left to a waiter’s handwriting.

  • Timers and late alerts

    A timer starts when the order is confirmed. Tickets change colour as they age, and late ones stand out across the kitchen.

  • Ready and recall

    One tap marks a ticket ready and notifies the waiter. A mistaken tap is recalled just as fast.

  • Delivery in the same flow

    Wolt and Bolt Food orders are accepted and printed automatically and land between the hall tickets, with their own prep timers.

  • Several brands, one kitchen

    Each brand keeps its own menu and prices on the platforms, while stock and recipes stay shared, and margin is shown after platform commission.

20:31 QR menu · Kiosk · AI waiter

The guest orders. The AI waiter knows the menu.

A QR code on the table opens a photo menu in Azerbaijani, English or Russian, with no app to install. Guests ask the AI waiter what to eat, order, call a waiter, pay by card and tip from their own phone. The order goes to the kitchen display and the bill to the POS.

From scan to review

  1. Scan

    The QR code on the table opens the menu in the browser, with photos, descriptions and prices.

  2. Ask

    The AI waiter answers from the restaurant’s own menu: dishes, ingredients, allergen and dietary tags.

  3. Order

    Modifiers, portions and notes go straight to the kitchen display, or to a waiter for approval first.

  4. Call

    “Call waiter” reaches the staff at once, so nobody has to wave across the room.

  5. Pay and tip

    The guest splits the bill, pays by card at the table and leaves a tip for the waiter or the team.

  6. Review

    Ratings and reviews arrive after the meal, and a bad one alerts the manager.

  • Photo menu
  • AZ · EN · RU
  • Allergen and dietary tags
  • Kiosk mode
  • Live prices and sold-out
  • Card payment at the table

21:05 Recipes · Food cost · Stock

Every plate sold takes its grams off the shelf

Each dish has a technical card down to the gram, with yield and cooking loss. When the dish sells, every ingredient leaves stock by that card. When a supplier’s price changes at goods receipt, the cost of every dish that uses it is recalculated, and so is its margin.

  • Technical cards

    Grams, yield and cooking loss per dish. Semi-finished items have recipes of their own, expanded down to raw ingredients at every sale.

  • Automatic deduction

    Every sale deducts its ingredients from the branch stock in real time, including delivery and QR orders.

  • Purchasing

    Low-stock alerts turn into purchase lists grouped by supplier, and goods receipt updates stock and cost prices.

  • Counts and variance

    Stock is counted on a phone. Expected against counted shows the gap that waste, over-portioning or mistakes leave behind.

  • Waste and expiry

    A waste log records what was thrown out and why, and first-expiry-first-out rotation keeps the oldest stock moving.

  • Live food cost

    Food cost per dish and per period moves with every sale and every goods receipt, not at month end.

23:48 Fiscal receipts · Shifts · Staff

At closing the drawer, the receipts and the payroll agree

Every sale produces an E-Kassa fiscal receipt. At close the system already knows what should be in the drawer: the cashier counts, any variance is flagged, the Z report is taken, tips are split, and the hours the team clocked flow into payroll.

  • E-Kassa fiscal receipts

    Receipts are issued through the E-Kassa integration straight from the POS, with the fiscal printer and the end-of-day Z report in the same flow.

  • Shifts and cash drops

    Shifts open and close with a count, and cash drops during service are recorded as they happen.

  • Cash reconciliation

    Expected against counted cash, card sales against the terminal. Every difference raises a signal instead of hiding in a notebook.

  • Clock-in and schedules

    Staff clock in on the till or on their phone, and managers build the week’s schedule with drag and drop.

  • Payroll and tips

    Worked hours feed payroll. Tips go directly to the waiter or into a pool split by the rule the restaurant chooses.

  • Suspicious operations

    Unusual operations raise a signal for the owner, with the audit trail of who did what behind them.

09:00 Chains · Central menu · P&L

Every branch on one screen before the first coffee

Menu, prices and recipes are managed centrally and pushed to every branch, with different prices per branch or zone where needed. The owner compares branches side by side: sales, average check, food cost, labour and voids. The P&L builds itself from sales, purchases, payroll and expenses.

  • Central menu and prices

    One change to the menu, a price or a recipe reaches every branch, and prices can differ by branch or zone.

  • Branch comparison

    Sales, average check, food cost, labour and voids side by side, with a signal when one branch falls behind the rest.

  • Consolidated P&L

    Chain-wide profit and loss from sales, purchases, payroll and expenses, with drill-down into any branch.

  • Central warehouse

    A central kitchen prepares semi-finished goods, branches order internally, and every transfer is traceable.

  • Franchise and royalties

    Franchise branches run on the same menu and standards, and their sales feed royalty tracking.

  • Roles per level

    The owner sees the chain, a branch manager sees their branch, and a cashier sees the till.

Engineering

Five apps on one API, built for a Friday rush

Foodost is a multi-tenant cloud platform we designed, built and run. Five web apps share one API and one data model, so an order, a price or a recipe exists in exactly one place. The POS writes locally and syncs, the POS and kitchen talk in real time, and every restaurant works in its own isolated tenant.

  • Cashiers · waiters

    POS

    Offline-first till with tables, tabs, split bills, PIN sign-in and fiscal receipts.

  • Cooks · expo

    Kitchen display

    Real-time tickets by station, course timers, ready and recall.

  • Guests

    QR menu & kiosk

    Photo menu, AI waiter, orders, waiter calls, card payments, tips and reviews.

One API One data model · real-time events · offline sync

  • Owners · managers

    Admin panel

    Menu, recipes, stock, purchasing, staff, finance, branches, CRM and reports.

  • Our team

    Operator console

    Where we run the platform: onboarding restaurants, subscriptions, feature access, support and alerts.

Principles

  • Offline-first sync

    The POS keeps a local store and an outbox, and queued changes replay in order when the connection is back.

  • Real time

    Orders, ready taps and sold-out marks travel over live connections between the POS, the kitchen and the QR menu.

  • Multi-tenant SaaS

    Every restaurant or chain works in its own isolated tenant, with its branches, devices and users inside it.

  • Roles and PINs

    Owner, branch admin, manager, cashier, waiter, kitchen and courier roles, and cashiers sign in with a PIN.

  • Audit trail

    Voids, comps and other sensitive operations are logged with who, when and why.

  • Three languages

    Every app works in Azerbaijani, English and Russian, and the QR menu follows the guest’s language.

  • Open API and webhooks

    Partner systems read and write through a REST API and receive events through webhooks.

  • Model-agnostic AI

    The AI waiter runs on a pluggable language-model layer, so the model can change without touching the menu.

Integrations

  • E-Kassa Fiscal receipts and Z reports
  • Wolt Orders, menu and status sync
  • Bolt Food Orders, menu and status sync
  • Payriff Online card payments
  • Card terminals Payment reconciliation
  • Printers Receipt, fiscal and kitchen printers
  • Scales and scanners Weighed goods and barcodes
  • Excel / CSV Import and export
  • E-mail and SMS Confirmations and campaigns
  • REST API Webhooks for partner systems

Also in the admin panel

  • Reservations and banquets
  • CRM and loyalty
  • Gift cards
  • Promotions and campaigns
  • Reviews
  • Delivery zones and couriers
  • Expenses
  • Franchise and royalties
  • Audit log
  • Reports with drill-down

Our role

What Atlas BIP did

  1. Product and service design

    We mapped a restaurant’s service minute by minute (hall, kitchen, delivery, stock and closing) and designed five apps around it.

  2. Offline-first engineering

    We built the POS to write locally and sync, and the kitchen display and QR menu to update in real time.

  3. Costing, stock and finance

    We modelled tech cards, multi-level recipes, purchasing, shifts, payroll and P&L as one data model.

  4. Integrations and hardware

    We connected E-Kassa, Wolt, Bolt Food, Payriff, printers, scales and scanners, and opened a REST API with webhooks.

  5. The AI waiter

    We built the AI waiter into the QR menu and kiosk on a model-agnostic language-model layer.

  6. Running the SaaS

    We run Foodost as our own product: onboarding, subscriptions, support and releases through the operator console.

Stack

Web apps for any till, screen or phone

Apps
  • TypeScript
  • React
  • Vite
Real time and offline
  • WebSockets
  • IndexedDB
Platform
  • REST API
  • Webhooks
  • Multi-tenant SaaS
AI
  • LLM

Questions and answers

What restaurant owners ask about Foodost

Does the POS really keep working without the internet?

Yes. Orders, payments and receipts are created on the device and queued. When the connection returns, the queue syncs to the cloud on its own, and the kitchen display, stock and reports catch up without anyone retyping.

Does Foodost work with E-Kassa, Wolt and Bolt Food?

Yes. Fiscal receipts are issued through the E-Kassa integration, and Wolt and Bolt Food orders are accepted into the same flow as hall and QR orders, with the menu, prices and sold-out dishes synced back to the platforms.

What exactly does the AI waiter do?

It lives inside the QR menu and the kiosk. It answers guests’ questions from the restaurant’s own menu (dishes, ingredients, allergen and dietary tags) in Azerbaijani, English or Russian, and helps them choose what to order.

Can one system run a chain of restaurants?

Yes. Menu, prices and recipes are managed centrally with per-branch pricing, stock moves through a central warehouse and transfers, and the owner sees branch comparison and a consolidated P&L.

Can Atlas BIP build a system like this for our business?

Yes. Foodost is our own product, and the same team designs and builds offline-first apps, real-time operations screens and ERP back offices for other industries. Tell us how your operation runs, and we reply within 24 hours with questions and a plan.

Next project

All projects
Trade & distribution · ERP Techizat A phone-first trading ERP and partner portal for a building-materials supplier.

Your project

Your system is next

Tell us how orders, money and documents move through your company today. We reply within 24 hours with questions and a concrete plan.

Discuss a similar project Message us on WhatsApp

Restaurant, branch, supplier and staff names, dishes and figures on screens are sample data.

Back to the start