Edit Product

In this article

Before you start

• The operator is signed in with Harbor Demo Group selected.
• For a location product, Harbor Soho or another location is selected.
• The product already exists and is visible in the current organisation or location catalogue.
• The operator has `catalog:manage` for the scope that owns the product. View-only operators can open the detail but cannot save.
• Product types and tax categories already exist, because the current form requires both before saving.
• File upload is available if the product image needs to be changed.

Instructions

1. 1.

   Open Products

   Open the location catalogue management area and select the Products tab. In the GB demo, use Harbor Soho and locate an existing product such as Fish and chips, Beef pie or Sticky toffee pudding.

2. 2.

   Open the Product

   Select the product row or its row action to open the existing product detail. The form loads the current values before the operator changes price, classification, kitchen settings or attributes.

3. 3.

   Update Required Fields

   Review the product name, price, product type and tax category. For example, update Fish and chips from GBP 16.20 to a new menu price while keeping the correct product type and tax category selected.

4. 4.

   Update Kitchen Details

   Set whether the product requires kitchen preparation, then adjust the kitchen name and short name when the operation uses different names for POS or kitchen display workflows.

5. 5.

   Update Content

   Edit the description, display colour and image if required. When a new image is selected, it is uploaded before the product record itself is saved.

6. 6.

   Update Attributes

   Select the allergens and specifications that apply to the product, so dietary and operational metadata stay aligned with the product record.

7. 7.

   Save Changes

   Press Save once the form has changes and all required fields are valid. The system updates the product, refreshes product data, shows a success message and returns to the Products tab.

Validations and limits

• Opening the detail requires catalogue access; saving requires `catalog:manage` on the owning organisation or location scope.
• A product must have an existing id. Opening the product form without an id is the creation flow, not the update flow.
• Name must contain text after spaces are trimmed.
• Price must be a valid decimal amount. The UI constrains the field from 0 to 9999, and the update service rejects zero or negative prices.
• Product type and tax category must be selected before the current form can be saved.
• Product type options are limited to the exact catalogue scope of the product.
• Invalid colour values are normalised to an empty product colour.
• If image upload fails, the failed image is not applied to the product update.
• Saving replaces the previous allergen and specification links with the selected lists.
• The update is a full form save, not a partial patch. Direct API clients must send the fields and lists they want to keep.
• If the product is tied to historical service catalogue usage, Antylogic may freeze catalogue snapshots before applying the change.

Expected result

The product is updated in the correct organisation or location scope, with commercial details, tax classification, kitchen settings, image and attributes ready for future catalogue, TPV and KDS workflows.