Rets
Rets builds a digital menu for restaurants, cafes and canteens: you enter a dish once, its name and description are stored in Uzbek, English and Russian, and the guest reads it on their phone in whichever language they picked. When a price moves there is nothing to reprint — you edit one field and the menu is current the same moment.
Rets is an online menu platform for restaurants, cafes and canteens. The owner signs in with a Google account, picks a short name — a “username” — and within a few minutes has a live menu that works on a phone. The menu sits at a permanent address: rets.mezes.uz followed by your name.
The core problem it solves is how expensive and slow updating a menu is. On paper, one changed price or one new dish means retyping, redesigning and reprinting the whole thing. That is why prices so often get corrected by hand and an outdated menu stays on the table for months. In Rets it is a few clicks: open the dish, type the price, save — and the guest sees the new price a minute later.
The second part, and the strongest one, is the three languages. Every dish keeps a separate name and a separate description in Uzbek, English and Russian. Whichever language the guest opens the menu in, that is the language the description comes in too. For a restaurant that gets tourists this is not merely convenient — it is the shortest way to stop explaining orders across the table.
There is nothing in the guest’s way: no sign-up, no login, no app to install. The link opens, you move through the categories, and every dish shows its photo, description and price. The address of the menu never changes, so you only have to put it on the QR code on the table or in a social profile once — after that you keep updating what is inside it.
As the restaurant grows, two more things come in handy: inviting a collaborator so your manager can keep the menu up to date with you, and opening the menu on your own domain, without Rets branding. The second one is not just a promise — joxon.mezes.uz is a live example running exactly that way.
Redesigning and reprinting a whole paper menu because one price moved costs money and time. The result is a menu that lags behind reality: the guest reads one price and gets another one on the bill. Online, the edit happens in one place and shows up everywhere at once, because there is only one copy of it.
Printing a menu in two or three languages means several times the paper and several times the work on every update. So usually one language survives and the rest lands on the waiter. In Rets the language is part of the menu: one dish is written in three languages and the guest picks the one they need.
The menu usually lives on the owner’s phone or in a designer’s folder. At the end of a shift you wait for whoever is able to add the new dish. In Rets the owner invites a manager by email and that person edits the menu on their own — while the settings and the domain stay with the owner.
To send someone your menu you need a link, not a picture. Rets gives every restaurant a permanent address, and later you can connect your own domain and open the menu entirely under your own name — with no platform name and no link back to it left on the page.
Nothing is needed on the guest’s side — no account, no app. The link opens and the menu is right there. Below are the screens they go through, in order.
On the platform’s home page the restaurants appear as cards. Each card carries the restaurant’s name, its logo and a “View menu” button. If you already have a link to one particular restaurant you never need this page — the link opens the menu directly.
A wide cover image sits at the top, with the restaurant’s logo and its short name, written with an @, over it. This page is the restaurant’s main face online: the guest gets the same layout whether they open it on a phone or on a computer.
Under the cover there is a row of categories, each with the number of dishes in it alongside. The “All” tab shows the whole menu; tap another one and only that section stays. Dishes that were never assigned to a category do not vanish — they collect automatically in a group called “Others”.
Every dish gets its own card: the photo on top, then the name, a short description and the price. The number is written with a space between the thousands and the currency word after it — for example, “65 000 sum”. The currency is set separately for each restaurant.
The language switch sits in the top corner of the page. Once a language is chosen, it is not only the buttons and headings that change: the names and descriptions of the dishes move to that language too. The choice is remembered in your browser, so next time the menu opens in it straight away.
If the menu has not been filled in yet, the guest gets a clear line rather than a blank screen: “Menu is not added yet”. Because the address is permanent you can put it on a QR code on the table or in a profile description — after that only the contents of the menu change, never the address.
This is what sets Rets apart. Language here is not a button on top of the page — it is built into the content itself: one dish is named three times in the database.
In the dish form, both the name field and the description field carry uz / en / ru tabs. You switch tabs and type the English and the Russian version of that field. The price, the photo and the category are single values — they do not depend on the language.
When a category is created its name is entered in the same three languages. One language is enough to save it — you can fill the rest in later, when there is time for it.
If a dish has no English name, the menu does not show an empty cell: the system falls back to one of the languages that do exist. The order is fixed — first the language the guest chose, then Uzbek, then English, then Russian. So a half-filled menu still works; in some places the guest simply reads the name in another language.
The guest picks the language themselves and that choice is stored in their browser, so there is nothing to pick again on the next visit. The address of the menu does not change with the language — send one link to three different guests and each of them reads it in the language they are used to.
The table below shows how the main labels in the menu look in all three languages. It is not a translation sample — these are the exact words that swap when the guest changes the language.
| Where in the menu | UZUzbek | ENEnglish | RURussian |
|---|---|---|---|
| Heading of the restaurant list | Restoranlar | Restaurants | Рестораны |
| The menu section | Menyu | Menu | Меню |
| The all-dishes tab | Barchasi | All | Все |
| Group for dishes without a category | Boshqalar | Others | Прочее |
| Button on the restaurant card | Menyuni ko’rish | View menu | Смотреть меню |
| When the menu is empty | Menyu hali qo’shilmagan | Menu is not added yet | Меню пока не добавлено |
| Currency next to the price | so’m | sum | сум |
| The full price as shown | 65 000 so’m | 65 000 sum | 65 000 сум |
The names and descriptions of the dishes swap in exactly the same way — the difference is that you write those, not the system. That is why the most useful habit while filling the menu in is to type the English and the Russian version straight away: coming back to finish them off is the part that gets forgotten.
The menu is filled in from a separate control panel. It is kept apart from the page the guest sees, which means there is no need to take the menu down while you edit it.
Google is the only way in. There is no password to invent, no confirmation email to wait for, and the whole business of resetting a password never comes up. Once you are in, the session lasts a long time — you are not signing in again every day.
The first step is the restaurant’s name and a “username”. The short name is 3 to 30 characters long and uses only lowercase Latin letters and digits. The address of the menu is built from it, so it is worth picking something close to the restaurant’s name and easy to type.
A menu starts with categories — salads, hot dishes, drinks and so on. Categories are edited in place in the list: click the name, change it, save. There is no separate page to open.
Every dish takes a name, a description, a price, a category and a photo. The name and the description go in three languages. The price is typed as a plain number and the system formats it: write “65000” and the menu shows “65 000 sum”.
Dish photos, the restaurant logo and the cover image are all uploaded here. An uploaded image is compressed and resized automatically so the menu opens quickly — a large photo straight from your phone needs no preparation. When an image is replaced, the old one is not kept.
Settings hold the logo, the cover, the currency and the short name. The currency is chosen separately for each restaurant and applies to every price in the menu alike.
Four figures greet you the moment you sign in: the number of dishes, the number of categories, the number of collaborators and the number of dishes without a photo. The last one is the most useful — it shows at a glance which part of the menu is still unfinished.
The owner does not have to fill the menu in every time. They can invite a collaborator and hand the day-to-day work over to a manager.
A collaborator’s rights are deliberately narrow: they fill the menu in, but they cannot change the restaurant itself. That is what makes giving a manager access safe — they will not break a domain setting by accident.
There are two roles: owner and collaborator. Here is the difference.
| Action | Owner | Collaborator |
|---|---|---|
| Adding and editing dishes | Yes | Yes |
| Adding and editing categories | Yes | Yes |
| Uploading and replacing images | Yes | Yes |
| Changing the logo, cover and currency | Yes | No |
| Changing the short name | Yes | No |
| Inviting a collaborator | Yes | No |
| Connecting a custom domain | Yes | No |
| Deleting the restaurant | Yes | No |
If the restaurant has a domain of its own, the menu can open there. This is not a second website to build — it is the same menu, at a different address and without the platform’s name. The control panel is in Uzbek, so the statuses below are quoted exactly as they appear in it.
| Status | What it means |
|---|---|
| tekshirilmoqda… | The domain has been accepted and is in the queue. This state does not usually last long — it may simply be waiting for the DNS change to spread. |
| DNS tekshiruvi o’tmadi | The domain does not point at Rets yet, or the A record was entered incorrectly. The fix happens on the domain settings side, after which you ask for another check. |
| SSL sertifikat olinmadi | The domain was found, but the certificate for the secure connection could not be obtained. This is usually temporary — trying again is enough. |
| Ulangan ✓ | Everything is ready: the menu opens on your domain over a secure connection. There is nothing else to do. |
When something fails, the process does not stall halfway — the system rolls back and leaves you a retry button. In other words, typing the domain in wrong will not take your menu down.
There is no need to imagine it — there is a live example. joxon.mezes.uz is not a separate project or a separate site: it is the own domain of one of the restaurants on Rets, which makes it this exact feature in working order.
A menu opened on your own domain carries neither the Rets name nor a link back to it. The guest sees only the restaurant’s logo, its cover and its menu — the page feels like the restaurant’s own site.
Connecting your own domain does not create a new menu and does not copy the old one. It is a second address for a single menu: add a dish and it appears in both, edit a price and it changes in both.
On your own domain the language switch, the category tabs and the dish cards work exactly as before. And you keep editing the menu from the same control panel — no second account, no second password, no second place to work in.
The easiest way to compare is to open one restaurant’s menu at both addresses: inside the platform and on its own domain. The dishes are the same and the layout is the same; the difference is in the browser’s address bar and in the branding on the page.
The sign-in page has a “Sign in with Google” button. There is no password to invent and no registration to go through — the Google account you already have is enough.
You type the restaurant’s name and a “username”: 3 to 30 characters, lowercase Latin letters and digits only. The permanent address of the menu is built from that name.
Split the menu into sections — salads, hot dishes, desserts, drinks. The category name goes in three languages as well, and one of them filled in is enough to save it.
Each dish gets a name, a description, a price, a category and a photo. Switch between the uz / en / ru tabs in the name and description fields and write all three versions straight away — coming back to finish them off is the part that gets forgotten.
In settings you upload the restaurant’s logo and the wide cover image at the top of the menu, and choose the currency. After that the menu looks finished.
Open the menu on a phone and click through the language switch three times. If some dish has no English or Russian name it will show up in another language — those visible spots are the ones you fill in.
In the collaborators section you enter their email address. Once they accept the invitation they edit the menu and the categories on their own, while the settings stay with you.
You point your domain’s A record at the address Rets gives you and type the domain name into the settings. Once it passes the check, the menu opens on your domain, without the platform’s branding.
There is no password login at all. That is convenient, but it means deciding in advance whose Google account opens the restaurant’s account — it will be tied to that person.
The three languages belong to the menu, not to the panel itself: the buttons and the section names are Uzbek. If the person filling the menu in does not read Uzbek, that has to be taken into account beforehand.
The address of the menu is built from the “username”. You can change it in the settings, but the QR codes and links handed out with the old address go stale — which is why the name is worth choosing carefully from the start.
The system does not translate a dish name automatically — you write all three versions. Where a language is missing, the text from another one is shown, so the menu keeps working, but a tourist may end up reading an Uzbek name.
Assigning a dish to a category is not compulsory, but anything unassigned lands in the general group at the end of the menu. For a tidy menu it is better to give every dish a category.
So that the cards look alike, images are placed into a frame of the same proportions. A very tall or very stretched photo may have its edges cut off, so it helps to centre the dish when you take the picture.
Rets does not sell domains and cannot change their DNS settings itself. Pointing the A record is done wherever you bought the domain; from there on the system takes the check and the certificate over.
A collaborator works with the menu and the categories, and nothing else. The logo, the currency, the short name, the domain and deleting the restaurant all stay with the owner. This is deliberate: the daily work is shared, the responsibility is not.
A Google account and a few minutes. You sign in to the control panel with Google, type the restaurant’s name and its short name — and the address of the menu is ready. What is left is adding the categories and entering the dishes. There is no designer, no developer and no separate website to order.
Yes, and that is the main point of it. Both the name and the description of every dish are stored separately in Uzbek, English and Russian: you switch between the uz / en / ru tabs in the form and type each one. Category names work the same way. The guest picks the language when they open the menu, and the whole menu — headings, categories, dish names and descriptions — moves to it.
The menu still works and no gaps show up. In place of the missing language the system takes one of the versions that do exist: first the language the guest chose, then Uzbek, then English, then Russian. So you can fill the menu in step by step — in the unfinished spots a tourist will simply read the Uzbek name.
No. The menu is an open link — no sign-up, no login, no app to install and no phone number to leave. Anyone who opens the link sees the whole menu. Signing up is only for the people who edit it: the owner of the restaurant and the collaborators they invite.
Yes. You point your domain’s A record at the address Rets gives you, then type the domain name into the settings. The system checks the domain and obtains the certificate for a secure connection itself; once the status is active, the menu opens on your domain without the platform’s branding. This is not a second menu — it is a second address for the same one. A working example: joxon.mezes.uz.
Yes. In the collaborators section you enter their email address, an invitation goes out, and once they accept it they start working on the menu. A collaborator adds and edits dishes and categories and uploads photos. But they cannot touch the logo, the currency, the short name or the domain settings, and they cannot delete the restaurant — all of that stays with the owner.
No, it does not. Dishes with no category are collected automatically in the “Others” group and stay visible in the menu. That is handy as a stopgap: you add the dish quickly and decide on its category later.
You enter the price as a plain number and the system takes care of how it looks: write “65000” and the menu shows “65 000 sum”. The currency word follows the language of the menu — “65 000 so’m” in Uzbek, “65 000 сум” in Russian. The currency itself is set separately for each restaurant.
No. The address of the menu stays the same; only what is inside it changes. You edit a price or add a new dish — the QR code on the table and the links you handed out stay exactly as they were, and the guest opens the updated menu next time round. The address only changes if you change the short name or the domain yourself.
Start the way a guest would: open the platform, look through a restaurant’s menu and press the language switch to see how one menu opens in three languages. Then sign in to the control panel with Google and add your own restaurant — with the categories and a few dishes in place, the menu is already usable.