You can configure PIM per Repository.
ibexa.repositories.<repository_name>.product_catalog configuration key, indicate the catalog engine to use:
1 2 3 4 5 6 7 8 9
default engine is available out of the box, and configured under
1 2 3 4 5 6 7
local type is the built-in type of catalog based on the Repository.
options.product_type_group_identifier you can define the identifier of the Content Type Group used for storing products.
root_location_remote_id indicates the remote ID of the Location where products are stored.
To set up different VAT rates for different regions (countries), you can use the following configuration under the
ibexa.repositories.<repository_name>.product_catalog.regions configuration key, for example:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
VAT rates configuration accepts additional flags under the
It is an extension point that you can build upon to add custom functionalities.
You can use it, for example, to pass additional information to the UI or define region-specific exclusions when calculating the tax values.
For each VAT category value, setting a value to "null" (~) is equal to making the following setting:
1 2 3 4
Code generation strategy¶
Product codes for variants are generated automatically based on the selected strategy.
The following strategies are available:
incremental(default) - variant code consists of base product code plus index, for example:
random- variant code consists of base product code plus random string of characters, for example:
You can choose the strategy with the following configuration:
1 2 3 4 5 6 7 8
You can also create your own custom code generation strategy.
You can configure which catalog filters are applied by default with the following configuration:
1 2 3 4 5 6 7 8
The order of filters in this configuration reflects the order in which they are displayed in the Back Office.