Skip to content

Overview

This page documents general notes for the Kitchen Prep Tool Service in Orbital.Web.

Base Routes

  • Login route: /scan/login
  • Authenticated base route: /scan

Feature Routes

  • /scan/product-scan
  • /scan/waste-log
  • /scan/master-products
  • /scan/tu-inventory
  • /scan/prep-inventory
  • /scan/prep-needed-today
  • /scan/tu-purchasing-sheet
  • /scan/users
  • /scan/cross-location-dashboard

General Notes

  • Access to some pages is role-based (for example scanner, non-admin, and admin behavior).
  • Some pages are context-dependent by kitchen code (for example USQ visibility behavior in sidebar filtering).
  • Feature documentation in this section should stay aligned with route definitions in Orbital.Web/src/pages/kitchen-prep-tool/routes.tsx.

Kitchen Codes Source of Truth

Kitchen codes used by the Kitchen Prep Tool Service are sourced from a MongoDB table and should be treated as the source of truth for kitchen onboarding and kitchen-level feature behavior.

When onboarding a new kitchen, update the MongoDB kitchen-code table first before expecting the new kitchen to appear and behave correctly in Kitchen Prep Tool workflows.

New Kitchen Onboarding Note

  • Step 1: Add or update the kitchen record in the MongoDB kitchen-code table.
  • Step 2: Validate the kitchen code and related metadata are correct.
  • Step 3: Confirm the new kitchen appears correctly in Kitchen Prep Tool context-dependent pages.