How Foodera works
A simple guide to the system: the full operating cycle, then the steps for each type of user.
The operating cycle
From a customer order on a delivery app to the final revenue split — every step is documented in the system.
- 1 Customer orders Partner Kitchen Orders from HungerStation, Jahez, Keeta, Talabat and walk-ins arrive in one unified screen.
- 2 Request to CK Partner Kitchen The partner merges orders into a production order or sends a supply request.
- 3 Quality review Quality Manager Every request is reviewed and approved before it enters production.
- 4 Production Central Kitchen The CK produces approved orders and records a batch ID for each item.
- 5 Shipment Central Kitchen The shipment is registered as ready, then dispatched with its exit time.
- 6 Receipt (GRN) Partner Kitchen The partner counts and confirms what was received; stock is updated and the cycle closes.
- 7 Settlement & revenue Accountant / Founder Shipped vs received vs sold are reconciled and daily revenue is split automatically.
Creator path to a new brand
- 1Create an account
- 2Accept the conditions
- 3Present your concept
- 4Answer the scorecard
- 5Submit the recipe
- 6Contract & royalties
Who does what
Rules the system applies automatically
When a mandatory ingredient reaches zero at an outlet and no CK order is open for it, the brand is switched off on the delivery apps automatically, and switched back on once an order is placed or stock arrives.
Partners must acknowledge manuals periodically; a brand is activated at an outlet only after its training is completed.
The Central Kitchen only sees orders approved by the Quality Manager.
Every day, gross sales are split into (A) Creator royalty, (B) Restaurant operational fee, (C) Foodera platform fee and (D) CK ingredients cost.
85–100 points: strategic approval · 70–84: conditional approval · below 70: rejected. COGS is calculated from the recipe (target ≤ 30%).