Skip to main content

Brand and model

A Brand and a Brand model (BrandModel) are classification levels under the category in the catalogue tree. The brand has a list and a record; the model is managed through its record page under the brand.

Brand pages: /Entities/CAT/Brand and /Entities/CAT/Brand/{id}
Model page: /Entities/CAT/BrandModel/{id}

Side menu visibility

Brand / BrandModel items may not appear as separate side menu entries under Product Catalogue; use the direct paths or links from records when you have permission.

Brand​

What this screen does​

  • Manages brands with both names and descriptions
  • Optionally links ProductCategoryId
  • Is selected in the product's cascading classification after the category

Fields​

FieldRequiredUse
name / nameArOptional in the current interface validationName in English and Arabic
description / descriptionArOptionalDescriptions
ProductCategoryIdOptionalProduct category

Brand model (BrandModel)​

What this screen does​

  • Shows / edits a model at /Entities/CAT/BrandModel/{id}
  • Is linked to the brand through brandId in the payload
  • Is selected on the product after the brand is chosen

Fields​

FieldRequiredUse
name / nameArOptional in the current interface validationName in English and Arabic
description / descriptionArOptionalDescriptions
brandIdFrom the brand context / defaultsParent brand
No brand picker in the details template

The model's SaveDetails interface does not show a separate Brand picker in the template; the link comes from the record context / defaults.

How to use the screens​

  1. Create a brand and link it to a category when needed
  2. Create or open a model under the brand through the BrandModel path
  3. On the product, choose MarketUnit → Category → Brand → BrandModel in that order

Best Practices​

Keep a single chain for each product line

A brand without a category, or a model without a brand, breaks the clarity of the tree even if the record is saved.

Interface validation is lenient

The Brand / BrandModel fields are optional in the current yup validation; adopt an internal data policy that requires both names and the classification link.