Example: An established kitchen product at another site.
Head office reviews product details and rules for the intended workflow. The second site uses the approved version and its configured printer connection. Its stock is managed at its own site.
If the recipe changes later, the new product version requires explicit approval. Earlier labels remain saved versions, making it possible to identify which information was used when they were created.
Shared rules need clear responsibilities.
Head office can switch between its company's sites. Kitchen staff and shift leads stay assigned to their site. A code sign-in for staff without email is bound to a configured station device.
- Review and approve product details centrally
- Configure the station and printer at each site
- Check staff site assignments
- Test a complete container workflow at each site
Learn at one site, then include the next deliberately.
Begin with a clearly defined product and workflow. Then check the setup needed at another site. This scenario explains existing features; it is not a reference from an anonymised restaurant chain.
Questions about this topic
Can kitchen staff approve product rules themselves?
Explicit approval is performed by head office. A person with this role may approve their own creation or edit; completeness checks and logging remain required.