View Product Detail
Open an existing catalogue product and review the full product detail form: sales name and price, kitchen/KDS settings, tax category, product type, image, colour, allergens and specifications.
In this article
Use this guide when a location manager or menu administrator needs to check a product record before deciding whether a separate edit action is required. In the GB demo, Harbor Soho products such as Fish and chips, Beef pie and Cheddar and leek soup are suitable examples.
The detail view is read-first. Users with view permission can inspect the record; write controls only belong to update or delete flows when the product is editable in the current scope.
Before you start
- An organisation is selected; for location catalogue detail, a location such as Harbor Soho is also selected.
- The product exists and is readable from the current scope: organisation, location or inherited organisation catalogue.
- The user has `catalog:view` or `catalog:manage` for the relevant scope.
- Product types, tax categories, allergens and specifications are available so the form can display readable selector labels.
Instructions
- 1.
Open Products
From the Harbor Soho location catalogue, open the Products tab. This is the normal entry point for checking an existing menu item.
- 2.
Choose The Product
Find the product in the table and open its row or row action. A route with a product id enters detail mode; the same form without an id starts product creation and is outside this action.
- 3.
Review Sales Fields
Check the product name, price, product type, tax category, description, colour and image. These fields explain how the item appears in catalogue, TPV and reporting surfaces.
- 4.
Review Kitchen Fields
Check whether Requires kitchen is enabled, then review Kitchen name and Short name. Requires kitchen controls whether the product participates in the kitchen/KDS flow.
- 5.
Review Dietary Tags
Check Allergens and Specifications. The form resolves these from auxiliary catalogues so the operator sees readable tags rather than raw ids.
- 6.
Confirm Editability
If the product is editable in the current scope, the same surface can show Save and Delete controls for other actions. If the user only has view permission or the product belongs to a non-editable scope, the fields are read-only and Save is not shown.
Validations and limits
- The UI requires a selected organisation; location detail also requires a selected location.
- The detail query is enabled only when there is a product id, a valid scope context and `catalog:view` or `catalog:manage`.
- The backend detail endpoint is protected by `PermCatalogView`.
- Products outside the current organisation or location scope are treated as not found.
- `catalog:view` allows opening the detail but does not grant editing; `catalog:manage` is required for write actions in the product's editable scope.
- Opening the detail does not create, update or delete product data.
Expected result
The operator can review the product record, confirm the sales, kitchen, tax and dietary data, and understand whether a separate edit action is available or needed.