Parameters (Store)

Access prerequisites

• Permission (module): approveStore
• License/Feature: MIDAS_MARKETPLACE enabled in the tenant license (Vault).
• Menu container: GENERAL → group Stores → Parameters (route /flexible-characteristics/parameters)

What it is / when to use

Parameters are the characteristics a product can have (size, colour, weight, etc.). The operator defines the catalogue of reusable characteristics and the type of each one (numeric with range, option list, or free text). These parameters are then associated with store categories, standardising product attributes.

Prerequisites

• Permission: approveStore (CPM static enum + dynamic module in the DB).
• License/Feature: MIDAS_MARKETPLACE enabled.

Step by step

1. Go to Stores → Parameters.
2. The list shows characteristics by name; filter with the search field.
3. Use Create to open the parameter dialog.
4. Set the name and type (along with the rules for that type); save.
5. On each item: View, Edit, Duplicate, or Delete.

Fields (parameter dialog)

Field	What it is	Required?	System/backend effect
Name	Name of the characteristic	Yes	Also copied to description on save.
Type (rules.type)	numeric, options, or free_text	Yes	Determines how the product fills in the attribute.
Numeric range (numeric.from / numeric.until)	Min./max. limits	Conditional	Required when type = numeric — from and until must be filled in. When saving as numeric, options are discarded.
Options (options[])	List of allowed values	Conditional	Required when type = options (≥ 1 option). Add/remove options via the field. When saving as options, the numeric range is discarded.

Actions and modals

• Create / Edit: opens DialogParameterFormComponent. Save is blocked if the name, range (numeric), or options (options) are missing.
• Duplicate: creates a copy with a numeric suffix in the name (id reset to zero) — useful for variations.
• Delete: confirmation via bottom-sheet.
• View: opens the parameter in read-only mode.

Business rules / considerations

Attention

• The type defines which rules are required: numeric requires a complete range (from/to); options requires at least one option.
• When the type is changed, the system discards incompatible rules (range ↔ options) at save time.

Related screens

• Categories
• Stores