Standards belong in the workflow.
Recipes, quality checks, tasks, temperature limits and follow-up should be part of everyday operations, clearly available when the work happens.
About Shamel
Why we built Shamel.
Restaurant operations often live across paper, messages, spreadsheets and team memory. We built Shamel to turn operating standards into a system teams can follow, measure and improve.
The problem we saw
The work happens. The picture gets scattered.
These tools have their place. But when operating details are spread between them, putting together the daily picture becomes another job for the team and management.
- Paper checklist
- WhatsApp message
- Verbal follow-up
- Spreadsheet
- Team memory
- What actually happened?
- Which branch followed the standard?
- Where did the problem start?
- Was it resolved?
Why Shamel
Three ideas guide what we build.
A problem needs a next step.
A rejected batch, missed task or temperature issue needs an owner, a due date and a corrective action, so an observation becomes something the team can follow through on.
Data should help management decide.
Operational data is useful when it reveals patterns: where issues repeat and what needs to improve. Reports should make those patterns visible and help teams act.
Built from restaurant operations
Shamel started with experience on the ground.
Mustafa Muhisen founded Shamel after years of working in food and beverage operations. The idea came from seeing the same problems repeatedly:
- Standards exist, but are hard to follow consistently.
- Information is spread across multiple places.
- Management often discovers issues late.
- Operational data is hard to turn into useful decisions.
That experience shaped the focus: bring standards, information and follow-up closer to the people applying them every day.
What we are building
Connected operations. A shared view of quality.
A connected operating and quality system for multi-branch restaurants, linking the standards management sets with what central kitchens prepare and branches put into practice.
Management
Standards & visibility
Central kitchen
Preparation, production & quality
Branches
Daily execution & follow-up
- Recipes & standards → Batches & quality
- Labels & expiry → Checklists & temperature
- Work Hub & reports → Follow-up & improvement
A deliberate focus
Every system has a role. This is ours.
Shamel focuses on operations, quality, consistency and follow-up. We are not trying to replace every system a restaurant relies on.
Shamel is not a POS, accounting system, full inventory platform or HR and payroll system.
Built around the team
Designed for the way teams operate here.
From central kitchens to branches, Shamel supports multi-branch structures, Arabic and English, and both reading directions. Plan pages also support Jordanian dinars, US dollars and Saudi riyals to make the options clear for the team.
Explore the plansWhere we are going
Standards that are easier to apply. Improvement that continues.
Our direction is straightforward: make restaurant operating standards easier to apply, measure and improve in every branch, with a clearer view of the work teams do.
See Shamel in everyday operations.
Follow the daily workflow, then explore the tools behind it.