Antylogic
DemoApp login

399 operational guides

Docs sections
DocsProduct catalogues
Device

Assign product taxonomy

Assign Product type, Tax category, Allergens and Specifications from the product form, then save the change through the standard product update flow.

In this article

Use this guide when a Harbor Soho product such as Fish and chips, Beef pie or Sticky toffee pudding needs its catalogue taxonomy reviewed before it is used operationally.

Taxonomy is edited in the normal product form. Product type and Tax category are required by the app form, while Allergens and Specifications are selected as chips and saved as complete replacement lists.

Before you start

  • You are signed in with an active organisation context for Harbor Demo Group.
  • Harbor Soho or another active location is selected when editing a location catalogue product.
  • You have `catalog:view` to open the product and `catalog:manage` to save changes in the product's owning scope.
  • The product already exists and is editable in its organisation or location scope.
  • The Product types, Tax categories, Allergens and Specifications catalogues are available for selection.

Instructions

  1. 1.

    Open the product

    Open the Products catalogue for Harbor Soho and select the product that needs taxonomy review. Organisation-owned products can be edited from the organisation catalogue instead.

  2. 2.

    Keep required fields valid

    Check that the base product fields remain valid before changing taxonomy. The same update saves Name, Price and taxonomy, so Save stays unavailable while required product data is missing or invalid.

  3. 3.

    Choose the Product type

    Select the Product type that classifies the item, such as starters, mains, desserts or drinks. The selector only shows product types from the exact catalogue scope of the form.

  4. 4.

    Choose the Tax category

    Select the Tax category already configured for the catalogue. The product form does not create tax categories inline.

  5. 5.

    Review Allergens and Specifications

    Scroll to the in-app sections labelled Alérgenos and Especificaciones, then select the chips that apply. Submitted allergen and specification lists replace the existing relationships.

  6. 6.

    Save and confirm

    Select Save once the form is changed and valid. The app updates the product in its owning scope, refreshes the product detail and list, and shows the selected taxonomy values after reload.

Validations and limits

  • With `catalog:view` only, the detail can open but the form is read-only.
  • Saving requires `catalog:manage` in the product's organisation or location scope.
  • Location-owned products must be saved through the location product update route, while organisation-owned products must be saved through the organisation update route.
  • System-scope catalogue items cannot be edited from this flow.
  • The frontend requires Product type and Tax category, although the backend model can allow null values outside this form validation.
  • Allergens and Specifications use replacement semantics. Submitting none removes existing relationships for that group.
  • The backend validates `product_type_id` scope when supplied. Equivalent same-scope backend validation was not verified for `tax_category_id`, `allergen_ids` or `specification_ids` beyond UI filtering and database foreign keys.

Expected result

The product is updated with the selected Product type and Tax category, and its Allergens and Specifications relationships are replaced by the submitted chip selections.

Related articles