For restaurants, bars, kitchens and shops

Everything your shop does. One place.

A storefront your customers order from. One queue for every order, however it arrived. Stock that counts itself down before it embarrasses you, and takings you can actually read at the end of the day.

Nothing to install. Your customers need no app and no account.

Takes the place of the order notebookthe WhatsApp cataloguethe stock list on the wallthe calculator at closing

Here to order, not to sell?

Every shop on Ekime is open to anybody. Browse them, or search everything they sell in one list.

You are already running all of this. Just not in one place.

Orders come from five places

A call, a WhatsApp message, somebody at the counter, a customer at table six, a rider waiting. They live in different places and none of them add up at the end of the night.

You find out the fish is finished when somebody orders it

Nothing counts down while you are busy. The menu keeps selling what the kitchen ran out of an hour ago, and somebody has to go back to the customer.

Money came in. What did you make?

Takings are one number. What sold, what it cost in delivery, which discount went out, what the service charge added — that is a different number, and it usually waits for a quiet evening that never comes.

Your shop, your link

A shop that looks like yours, not like a form

Your logo, your colours, your photographs. Dishes lead with the picture, the way people actually choose food. A dish with no photograph yet gets a plate of its own rather than a grey box — so a menu looks finished on the first day, not the fiftieth.

  • One link for Instagram, WhatsApp, a card or a QR code
  • Search and categories, so sixty dishes are not one long scroll
  • Dine in, pickup or delivery — you choose what you offer
  • Delivery areas with their own fee, estimate and minimum
  • Customers follow the order afterwards and rate it when it is done
The counter

Every order in one queue, whatever door it came through

The link, the counter, table six, a delivery — all of it arrives in the same list, marked with where it came from. Move an order through confirmed, preparing, ready and done, and everybody looking at the screen sees the same thing.

A diner who scanned the code on their table does not have to say where they are sitting: the order already knows, and it is dine-in whatever else was chosen. Somebody sitting at table nine is not collecting.

Stock

The menu stops selling what the kitchen ran out of

Stock comes down as part of taking the order, not afterwards — so two customers cannot both buy the last one. Cancel or refund an order and the goods go back on the shelf. At zero the item closes itself, and before that the overview tells you what is running low while there is still time to do something about it.

Money you can read

Takings, a revenue chart and what each day actually brought in — separated from what was merely ordered. The wallet sits behind a transaction PIN.

The people who work for you

Invite a cook by email or hand them a code to type once. Give them a role. Take it back the day they leave, without changing a password.

A record of who did what

Every change is written down with the person who made it — by the plumbing, not by each screen remembering to. No screen can forget.

Everything in it

The whole thing, listed plainly

Not a teaser. This is what is in the product today.

Menu

Categories, items, prices and pictures. Options with real rules — a required size, up to three toppings — enforced on the shop and again on the server.

Orders

One queue for every order whatever door it came through, moved through confirmed, preparing, ready and done.

Stock

Counted down inside the same transaction that takes the order, given back when one is cancelled or refunded, and closed at zero.

Storefront

Your own link, your colours, your logo. Photo-led menu, delivery areas, minimums and prep time.

Tables & QR

Print a code for each table. A diner scans it and the order lands on that table as dine-in.

Delivery areas

Name the parts of town you deliver to, each with its own fee, estimate and minimum basket.

Customers

Built from the phone number on the order, so a returning customer is the same customer, with their history in one place.

Discounts

Codes with their own rules. Applied when the shop confirms the order, never taken on trust from the browser.

Reviews

Food, service and room, rated separately after an order is done. The average shows on your shop.

Wallet

What you actually took, behind a transaction PIN, with a running record of every movement.

Team

Invite by email or a code somebody types once. Give them a role, take it back when they leave.

Receipts

Printable, for the customer and for the kitchen.

Activity log

Every change recorded with who made it — written by the plumbing, so no screen can forget to log.

Reservations

Bookings kept alongside the orders rather than in a separate book.

Online payment

A shopper can pay from the order's own page, settled by the gateway's callback and credited exactly once.

Your own clock

Every shop keeps its own timezone, so "today" means today where the shop is.

How it works

Open by this afternoon

  1. Create your shop

    Your name, where you are and what kind of business it is. A couple of minutes, and nothing to install.

  2. Put your menu in

    Categories, dishes, prices, pictures and the options that go with them. A setup guide walks the first run and ticks itself off.

  3. Share your link

    One link for Instagram, WhatsApp, a card or a QR code on the table. Orders start arriving at the counter.

Questions

Including the two where the honest answer is “not yet”.

No. Your shop is a web page. They open the link, choose what they want and order — no app, no account, no password. They follow the order afterwards with the order number and the phone they gave you.

Put your shop online this afternoon

Create it, put your menu in, share the link. Nothing to install, and your customers need no app and no account.