Additional data in the basket line¶
Each basket item can contain an additional line of data.
You can enable this line in
Basket storage time¶
The time for which a basket is stored depends on whether the basket belongs to an anonymous user or a logged-in user.
A basket for a logged-in customer is stored forever.
A basket for an anonymous user is stored for 120 hours by default. You can configure a different value:
You can use the
ibexa:commerce:clear-baskets command to delete anonymous expired baskets:
It deletes all anonymous baskets from the database that are older than
A listener can check if the product is still available, or discontinued. You can disable this setting in configuration:
The listener checks if the current stock is greater than or equal to the quantity the customer wants to order. In this case the order is allowed.
The optional setting
discontinued_products_listener_consider_packaging_unit enables ignoring the packaging unit
in order to sell the remaining products, even if the remaining stock does not fit the packing unit rule
(for example, the packing unit is 10 pieces but 9 are left in stock).
The listener reduces the quantity in the order to the number of products that are in stock.
Product quantity validation¶
You can configure the minimum and maximum quantity that can be ordered per basket line:
If the quantity is more than the maximum or less than the minimum, it is set to either max or min.
A basket can be shared if a user logs in from a different browser (default), or it can be bound to the session.
If you do not want the basket to be shared between different sessions, change the following setting to
In the summary, there is a comment field that the user can fill in.
By default, the comment box does not have a limit, but you can set a limit in configuration:
The mapping of the request order should be modified to unlimit the number of characters
navigation_ez_location_root parameter is the entry root Location point for the whole navigation in the Back Office.
This value is usually set to
2, the Location of the content structure.
1 2 3 4
navigation_ez_depth parameter is responsible for the main navigation depth.
Content from the Back Office is fetched only up to this depth.
This does not include the product catalog, which has its own depth specified.
navigation_sort_order to set the order of sorting by priority.
To define which Content Types should be included in the navigation, set the
1 2 3 4
To fetch content from different Sections, provide the Section IDs in configuration.
If you want to fetch all Content Types, even those with priority 0, use the
By default this is set to
To use a different field as the navigation node label, change the
The parameter takes Field Type identifier for
and Solr field name for
The field has to exist in Solr indexed data.
You can define the name used for navigation in configuration. The
label_fields parameter contains a list of attribute names (Solr names) that are used as the name in the menu.
The first available attribute is used.
The standard attribute
name_s does not always contain the correct translation.
name_s is used in
label_fields, navigation may not be translated.
To resolve this, configure the ID of the attribute directly e.g.
Additional navigation node information¶
You can also add additional information about the navigation node with
The fields have to exist in Solr indexed data.
Displaying images instead of labels in navigation¶
You can use an additional field to display an image from the content model instead of the node label:
1 2 3 4
You need to adapt the template to render the image instead of the label, for example:
1 2 3 4 5 6 7 8 9
Last viewed products¶
You can set the limit of products displayed in the Last viewed product block in:
You can configure the Fields that are used as labels for breadcrumb nodes. The first match wins.