Recipes with versions
Nested recipes, expected yield and waste, allergens derived from the ingredients, and cost per unit.
An ELDA product / Production & café platform
Where your business rises.
One system for the bakery and the café it supplies: recipes, production and lot-tracked stock on one side — tables, kitchen, till and QR ordering on the other.


In most bakeries the till knows nothing about the oven, and the spreadsheet knows nothing about the till.
A patisserie is a small factory with a shop attached. Flour, butter and cream arrive in lots with expiry dates; recipes that change with the season turn them into dough, cream and cakes; and the result is sold by the slice at a table. Point-of-sale software sees only the last step. General ERP systems do not move at the pace of a bakery.
Mayentra follows the product the whole way. A recipe defines what a batch consumes, logging a batch takes stock out of the lots that expire first, and a sale in the café draws on what production put on the shelf. Cost, waste and margin come from what actually happened, not from estimates.
Maya is the Turkish word for the starter that makes dough rise — and for what something is made of.

Ingredients, expected yield and waste for every recipe version. Publishing a new version never rewrites past batches.

Pick the product, enter the quantity, save. Ingredients come out of the lots that expire first, and the finished goods get a lot of their own.

Every lot carries its expiry date. The list shows what has to be used or marked down first, with the value at risk.

Tables, tickets and split payments in the café. Closing a ticket takes the stock that production put on the shelf.
The web panel also runs on a phone, the café app is built for one, and guests order in their browser. Captions are translated; the app screens show the Turkish interface with sample data.
Open a screen to see it in full size.








Nested recipes, expected yield and waste, allergens derived from the ingredients, and cost per unit.
Batches consume ingredients first-expired-first-out and create traceable lots of finished goods.
Purchase orders, partial goods receipt, transfers between warehouses and stock counts.
Tables, tickets, split payments, cash shifts and an end-of-day report.
A kitchen display by station, ready notifications and service tasks for waiters.
Menu, basket, order tracking and waiter call in the guest's browser.
Refers to the current development build.
Each business's data is separated by PostgreSQL row-level security, not only by application code.
An endpoint without an explicit permission stays closed. Roles are assembled from 462 individual permissions.
Money and quantities use decimal arithmetic. Stock is kept in base units and converted only at the edges.
Writes carry an idempotency key, so a request repeated after a lost connection has a single effect.
Mayentra is in active development at ELDA. Production, stock, purchasing, the café app and QR ordering are in the current build and covered by automated tests. It has not been released yet: connections to payment terminals, fiscal devices and delivery platforms still have to be accepted with real providers before a pilot.
All screens come from the current development build and show sample data. The interface is shown in Turkish; English and German are available in the web panel.
Mayentra is preparing its first pilot. Businesses, integration partners and press are welcome to get in touch.
Contact ELDA