Point of sale for restaurants and cafés

Your register doesn't need wifi.

Ajiliapp runs entirely on the device. Open the shift, take the table, split the check and get paid — signal or no signal. When the network returns, everything syncs on its own.

3
platforms: Android, Windows and the browser
0
network calls needed to take a payment
100%
of the register works with no signal
  • «the internet went down»
  • «the system is crawling»
  • «I can't close the register»
  • «the ticket never reached the kitchen»
  • «the check doesn't add up»
  • «it updated itself in the middle of the rush»

None of these stops service

Offline-first, not offline-sometimes

Cut the network. Keep charging.

Most POS systems are a web page with an error message where the connection used to be. Ajiliapp writes to the device first and tells the network later, if there is one. Try it right here: switch the connection off and keep selling.

Connection

Online

Flip the switch

When the signal returns the queue empties itself, and nothing is duplicated: every operation carries its own identifier, so a server that already saw it knows to ignore the second copy.

Table 4 · DiningOnline
Waiting to syncNothing pending

Modules

Everything between someone sitting down and someone paying.

Six pieces already running in a real café, every day. Not a roadmap — what is on the counter right now.

  • Floor

    Tables, sections and split checks

    • A map of the room by section: patio, dining room, bar
    • Move a whole table, or merge two that pushed together
    • Split the check by item, evenly, or by amount
    • Tip and discount are shared out proportionally
  • Tickets

    From the table to the kitchen, without shouting

    • Each item goes to its station: kitchen, bar, grill
    • Notes per dish — "no onion" arrives in writing
    • States: fired, cooking, ready
    • Reprint without deducting inventory twice
  • Inventory

    Deducts itself when the table closes

    • A recipe per product: one mojito takes rum, lime and mint
    • The deduction happens on payment, not when the order is taken
    • Low-stock alerts before you run out mid-service
    • Adjustments with a reason, so you know what broke and what was comped
  • Cash & shifts

    It balances, or says exactly by how much it does not

    • Open with a declared float
    • Blind count: you count without seeing what the system expects
    • Cash in and out, with a name attached
    • Close with the difference in plain sight, not buried
  • Menu

    Products, prices and taxes

    • Categories, variants and combos
    • Tax per product, not one global rate for everything
    • Discounts and coupons with a rule behind them
    • Cost and margin visible while you set the price
  • Reports

    What sold, not what you think sold

    • By product, by server, by hour of the day
    • Real margin, with the recipe cost inside it
    • Compare shifts and days against each other
    • Export for the accountant without asking anyone

The floor

A map of the room, not a list of numbers.

The server sees what they see when they look up. Tap a table to check its state.

  • Open
  • Seated
  • Wants the check
  • Split

Patio

Dining

Bar

Tap a table

Decisions

The parts nobody sees, and everybody feels at month end.

  • Money is calculated exactly

    Every price, tax and tip is handled in decimal, never in floating point. A total of 41.89 is 41.89 today and a thousand sales from now. Systems built on floats lose cents, and later nobody can find where.

  • The truth lives on your device

    The local database is not a cache — it is the source. That is why selling can never fail on a request that did not come back. The cloud, when it arrives, will be a copy, not the requirement.

  • The server's tablet stands on its own

    It takes orders and fires tickets while the register is busy taking a payment. There is no master device that, once it goes down, leaves everyone else staring at the ceiling.

  • It looks like your place

    The design system is themeable end to end: brand palettes, light and dark. Not a skin bolted on top — the colors live in one file and the whole POS obeys it.

  • It runs on what you already own

    Android for the tablet on the floor, Windows for the register at the counter, the browser for checking numbers from home. One app, not three products.

  • Your language and your currency

    Number, currency and date formats by region, and a translated interface. Not a late patch — it is in the foundation.

Not out yet

Get on the list and be among the first.

Ajiliapp is in development and gets tested every day in a real café. Leave us your email and we will write when it opens. No newsletter, no spam: one email when there is something to say.

What are you after?

We keep your email, what you are after, and the name of your place if you leave it. Nothing else.

What we get asked most

Read all the questions
  • Can I use it yet?

    Not yet. Ajiliapp is in development and runs every day in a real café, which is where it gets tested. Join the list and we will write the day it opens.

  • Which devices does it run on?

    Android for the tablet or phone on the floor, Windows for the register at the counter, and the browser for checking numbers from anywhere. Same application, not three separate products.

  • Does it really work offline, or just for a while?

    Really. The database lives on the device and is the source of truth, not a temporary cache. Selling, printing, opening and closing a shift never depend on the network. You could never connect the device and the POS would work the same.