Add-ons in Hummerce let you offer the customer related products to buy alongside the main item's product page - e.g. accessories, consumables or complementary parts of a set. An add-on isn't mandatory (though it can be configured that way) and is usually priced more attractively than when bought separately.
Last updated: 2026-09-29.
¶ Benefits and use cases
- Upselling on the product page - the customer sees a suggestion to buy a related item without leaving the main product's page.
- Grouping add-ons - add-ons can be grouped by topic (e.g. accessories separate from consumables).
- Flexible pricing - an add-on's price can be added to the main item's price, or shown and billed as a separate cart line.
- Savings information - the store can show the customer the combined catalog price of the set and the savings amount for buying together.
- Add-on visibility in the cart and order - an add-on added as a separate cart line also reaches the order and integrations (warehouse, ERP) as a separate line.
Add-ons are a way of using the general configurable product mechanism: in the main item's Configurable set tab, you add an item-type component and assign to it the items available to buy as an add-on. The same component mechanism also powers sets, made-to-order products and personalization - described in more detail in Product configurators.
¶ Selecting and adding an add-on as a customer
- From each add-on group, the customer can usually choose only one.
- Choosing an add-on either adds its price to the main item or adds it as a separate cart line - depending on the component's configuration.
- The store can limit the number of add-ons shown without extra customer interaction (e.g. showing a few suggestions with the option to expand the rest).
- The main item can be a standalone item or an article with variants.
- For the add-on component, you set, among other things: whether choosing an add-on is mandatory or optional, whether the add-on's price is added to the main item's price, and whether the add-on should be shown in the cart as a separate line.
- An item becomes visible as an add-on once its configuration has a dedicated price for selling it as an add-on filled in.
The mechanism is based on the configurable product - the current behavior of item components and their front-end appearance depend on the version of product configurators.
- Add-ons require a configured configurable product (an item-type component in the Configurable set tab).
- How the add-ons section looks on the product page depends on the store template (Bootstrap 5 template or Bootstrap 4).
- An item offered as an add-on must have a dedicated price for selling it as an add-on filled in.
- Add-ons require implementation - configuring the component on the main item's card and adjusting its presentation in the template.
- Minimum estimated time:
- configuring the add-on component for one main item - from 2 h,
- adjusting the appearance of the add-ons section in the template - quoted individually once the scope is set.
- What the time depends on: the number of main items with add-ons, the number of groups and add-ons per group, how the price is calculated (added or a separate line), the scope of visual changes in the template.
- An add-on is an item configured as a configurable product component - by itself it's no different from a regular item, and it requires a dedicated price for selling it as an add-on.
- The appearance and presentation of add-ons (e.g. the number of suggestions shown, group layout) depends on the component's configuration and on the specific store's template.
- We do not review the add-on configuration for legal compliance (e.g. how the combined price and savings are presented to the customer).
- Ready-made, panel-configurable presentation styles for add-ons in the Bootstrap 5 template, without extra implementation per store.
Is an add-on a separate item in the catalog?
Yes - it's a regular item, additionally configured as a component in the main item's configurable set, with a dedicated price for selling it as an add-on.
Does the customer have to choose an add-on to buy the main item?
No, unless the add-on component is configured as mandatory.
Is the add-on's price calculated separately or together with the main item?
It depends on the component's configuration - the add-on's price can be added to the main item's price or billed as a separate cart line.
Is the add-on visible separately in the order and in the ERP integration?
Yes, if the component is configured so the add-on goes into the cart as a separate line.
How long does implementing add-ons for an item take?
From 2 h to configure the component for one main item. Adjusting the template's appearance is quoted once the scope is set.
Want to see how add-ons could work in your store? Contact the Hummerce team (in Polish).
- Configuring add-ons: the Configurable set tab in the main item's editor - adding an item-type component, setting its parameters (whether selection is mandatory, whether the price is added, cart visibility) and assigning items as add-ons.
- Item price as an add-on: the dedicated add-on-sale price field in the item's price configuration.
¶ REST API and MCP
- MCP (AI assistant - MCP server): tools from the combinations/configurable-set group -
ec2_combinations_get_slots, ec2_combinations_create_slot, ec2_combinations_get_slot_items, ec2_combinations_add_slot_items - reading and configuring the add-on component as a slot of the configurable product.