How the apps work together
In Mihwar, one event in one app sets off the right response in the others — automatically, and on the record. This page lists what happens on its own, so your team knows what not to chase manually.
When something goes wrong, a follow-up opens itself
- A critical checklist step fails (e.g. “packaging integrity” marked fail) → a CAPA follow-up opens at that branch, titled after the step, linked back to the run.
- A HACCP / temperature check breaches its limit → a CAPA opens automatically. If the check is tied to a piece of equipment, a work order opens too — the breach and the broken asset are both on the record.
- A delivery arrives short, damaged, or substituted and the branch flags it at receive → the warehouse gets a discrepancy entry and a CAPA opens with the flagged lines attached. Serious receipt problems can also schedule a per-delivery quality inspection.
- A HIGH or CRITICAL work order is created — including by an anonymous QR scan-to-report — → a CAPA opens so the fix gets a root cause, not just a repair.
- The same asset breaks three times in 30 days → Mihwar clusters the repeats into one recurrence CAPA so the pattern gets investigated, not the symptom.
- A checklist run goes overdue → the escalation ladder you configured runs on its own: remind, reassign, open a CAPA, or skip-with-record.
Documents gate the work (read-and-sign has teeth)
- A checklist or quality step can cite an SOP → whoever performs the step must have read and signed the current version of that document first. Publish a new version and in-flight runs re-lock until people re-acknowledge.
- A shift can require a valid certificate (e.g. food-handler card, stored as a document) → Scheduling refuses to roster anyone whose certificate is missing or expired, and certificate-gated checklist steps refuse their completion.
- Closing a CAPA can require retraining → closing it books a training shift in Scheduling for the people involved — the loop ends with someone learning, on the schedule.
The kitchen feeds the forecast
- A closing-checklist “are we out of X?” tick → records a stockout signal against that item at that branch. The forecast treats it as demand you would have sold — so tomorrow's order draft already accounts for what ran out.
- Every fulfilled order and receipt → becomes training history for the demand model. The more your team uses the ordering flow, the sharper the suggestions.
Prep prints its own labels
- A prep checklist step tied to a recipe → ticking it prints the date/expiry/allergen label on the branch printer, shelf-life already worked out. Change a recipe's allergens and managers are alerted, with stale printed labels flagged for reprint.
Where to see it all
Every automatic action lands somewhere visible: the CAPA inbox for follow-ups, the work-orders board for repairs, the notification bell for the people involved, and the owner dashboard tiles for the rolled-up state. If an automatic record seems missing, check worker health under the relevant app's admin page — the background workers that carry some of these connections report their status there.