How Shamel works · Multi-branch restaurant operations

How Shamel works. From standards to decisions.

Connect the recipe to production, production to quality checks, and branches to follow-up. See how daily work becomes one clear operational flow in Shamel.

Set up operations

Start with the way your team is organized.

Define the company, brands, central kitchen and branches. Invite the team and set each person's role and access before daily work begins.

• Company → brand → central kitchen and branches.
• Team invitations, roles and permissions matched to responsibility.
• Configure the operational modules your company uses.

Clear locations and responsibilities for the work ahead.

Define the standard

Define it once. Put it to work everywhere.

Document ingredients, units, preparation instructions, shelf life and QC questions in the recipe. Set temperature limits for each asset so the team has a clear reference when recording and checking.

• Preparation steps and SOPs guide the team.
• Units, quantities and shelf life belong to the recipe.
• Quality requirements and asset temperature limits guide real checks.

An approved recipe and standards for production and inspection.

Produce the batch

Turn an approved recipe into a traceable batch.

Choose the recipe and production quantity. Shamel calculates ingredient quantities and generates the batch number, retaining production and expiry dates and relevant recipe data.

• The recipe and quantity define the production batch.
• An automatic number follows the batch through operations.
• A clear status shows what has been produced and needs inspection.

A recorded batch ready for its quality workflow.

Check and approve

Quality belongs inside the workflow.

Inspection questions come from recipe standards. The batch progresses through sequential approvals using existing permissions. If it fails, the rejection reason stays in its record.

• Production and receiving checks follow the configured workflow.
• Pass or fail with a recorded outcome.
• Approvals follow the team's assigned roles.

A quality decision that determines the batch's next step.

Label and send

Keep the information with the batch.

Generate a label from the recorded batch data, then select the destination within the transfer workflow. The batch identity and dates travel with it to the next location.

• The label carries the batch number, production and expiry dates.
• Arabic or English printing follows your settings.
• Branch receiving follows the existing quality checks.

An identified batch, ready for the branch to receive.

Receive and track

A new location. The same batch identity.

The branch handles receiving, quality and expiry follow-up. When another branch needs part of the quantity, that portion is reserved until receiving is accepted or rejected.

• Example: 12 units, transfer 6, then 6 at each branch after acceptance.
• On rejection, the reserved units return and the source has 12 available.
• The batch number and dates stay intact. A transfer is not new production.

Clear quantities and receiving status, with time-to-expiry in view.

Run the branch

One working day. Connected follow-up.

The team completes opening and recurring checklists, records fridge, freezer and vehicle temperatures, then reviews out-of-range readings and batches approaching expiry.

• Task completion updates checklist progress and the activity record.
• Each asset has appropriate temperature limits and a reading history.
• Expiry follow-up highlights batches needing action while there is time.

A documented routine with visible exceptions to follow up.

Resolve the exception

Give every issue an owner and an action.

A rejected batch, an out-of-range temperature or a task needing follow-up: the team records a Work Hub ticket, assigns an owner, sets a due date and follows corrective action through to closure.

• Create manually, or from violations when automatic creation is enabled.
• Ownership, a due date and visible work stages.
• Corrective action and follow-up history stay with the ticket.

A documented resolution management can review.

Review and improve

Turn daily operations into informed decisions.

Management reviews dashboards and reports by branch and period. Completion rates, violations and quality outcomes help direct attention to the work that needs it.

• Where do issues repeat, and which branch needs follow-up?
• Where are temperature readings outside the accepted range?
• Which operations are delayed, and how are outcomes changing?

A review that informs the next standard and operational cycle.

Connected steps. One view of operations.

1. Standardize
2. Produce
3. Check
4. Send
5. Operate
6. Resolve
7. Improve

See Shamel working inside your operation.

Start with your company structure. Bring the workflow to your team and branches.