Configure a Kitchen Product
Decide whether a catalogue product enters the kitchen/KDS flow and set the operational names used by POS and kitchen teams.
In this article
Kitchen routing is configured from the normal product form. For Harbor Demo Group at Harbor Soho, products such as Fish and chips or Beef pie can be opened from the Products catalogue and marked for kitchen production.
This setting does not enable KDS or send an order by itself. It stores the product metadata that TPV and KDS use later when the product is added to an operational ticket.
Before you start
- An organisation is selected, and for KDS verification a location such as Harbor Soho is selected.
- The operator has catalog:manage to create or update products. catalog:view is enough to open lists and product details but not to save.
- Product type and Tax category options exist for the same catalogue scope, because the UI requires both when saving a product.
- To verify the downstream KDS result, KDS is enabled for the location, the operator has KDS access, and the product has been added to an operational TPV ticket.
Instructions
- 1.
Open the product catalogue
From Harbor Demo Group, select Harbor Soho and open Catalogues > Products. This list is where the operator creates, opens, copies or edits the product before setting kitchen routing.
- 2.
Open or create the product
Open an existing product such as Fish and chips, or create a new product. A copied product starts as a new form and carries over the source product's kitchen configuration before the copy is saved.
- 3.
Enable kitchen routing
Turn on Requires kitchen when the product should enter the kitchen production flow and be eligible for KDS. Leave it off for products that should stay outside the kitchen board in normal new usage.
- 4.
Set the operational names
Use Kitchen name for the label the kitchen should see first on KDS. Use Short name for compact POS displays and as the KDS fallback when Kitchen name is blank. If both are blank, the normal product name is used.
- 5.
Complete the required product fields
Keep Name, Price, Product type and Tax category valid before saving. Product type options are limited to the exact catalogue scope, so a location product must use a location product type.
- 6.
Save the product
Use Create for a new product or Save for an existing product. Antylogic saves the kitchen fields as part of the full product payload, then returns to the list or previous screen after a successful save.
- 7.
Verify on KDS when needed
Add the configured product to a TPV ticket and move it into the kitchen flow. KDS shows relevant ticket items when Requires kitchen is active, or when an item is already sent, preparing or ready.
Validations and limits
- Saving requires catalog:manage; catalog:view can load product lists and detail screens but cannot save changes.
- The UI requires Name, Price, Product type and Tax category even when only the kitchen fields are being changed.
- Price must be parseable and greater than zero, and Name cannot be blank.
- A Product type from another scope is rejected.
- Kitchen name and Short name are optional; empty text is normalised to no value.
- No backend-specific length or format rule was confirmed for Kitchen name or Short name.
- Turning Requires kitchen off does not necessarily remove ticket items that are already sent, preparing or ready from KDS.
- KDS display name priority is Kitchen name, then Short name, then the product name.
Expected result
The product is saved with its kitchen-routing flag and operational names. Future TPV ticket items can carry that metadata into the kitchen workflow, while POS and KDS use the configured display-name priority.