¶ Units of measure and sale - selling in packages
Units of measure and sale in Hummerce let you sell one item in several units at once - piece, carton, meter or kilogram - each with its own conversion factor relative to the stock unit and its own price in the price list. This lets the store serve a retail customer buying a single piece and a business customer ordering whole bulk packages at the same time.
As of Hummerce 2.28 (full unit support - since version 2.26), updated 2026-09-29.
¶ Benefits and use cases
- Selling in bulk packages - a business customer buys a carton, a pallet or a dozen, while the warehouse keeps stock in one shared unit throughout.
- Several sales units for one item - the same item can be bought, e.g., by the piece and by the package, each with its own conversion factor and weight.
- Per-unit prices in the price list - each sales unit can have its own price, independent of the others.
- Unit table on the item page - the customer sees the conversion between units without calculating it by hand.
- One stock unit regardless of sales units - stock and reservations are always counted in one consistent unit, without errors when selling in different packages.
- The list of units the store can use is defined in the panel. The unit pc. is configured by default.
- The panel suggests a list of international standard codes used in logistics (e.g., piece, carton, pallet, meter, kilogram) - this makes it easier to pick consistent symbols and names without inventing your own from scratch.
- Every item has exactly one stock unit - it's the one used to keep stock and run the whole warehouse policy: quantity, reservations, availability.
- The stock unit is only visible once the store has more than one unit defined - an extra Units of measure tab then appears in the item editor.
- Besides the stock unit, an item can have any number of sales units, each with its own conversion factor relative to the stock unit (which can be a fraction) and its own weight.
- Since version 2.28 you can set several sales units for one item and assign them prices in the price list independently - the customer chooses which unit to buy in.
¶ Handling units on the item page and in the order
Showing units to the customer in the store (not just in the panel) requires implementation in that specific store. Options include:
- a conversion table between units on the item page,
- choosing the purchase unit when adding to the cart,
- showing the chosen unit in the cart and in the checkout process.
In price lists, every sales unit can have its own price defined, independently of the item's other units.
The warehouse always converts sold or received quantities to the stock unit and runs the whole warehouse policy in it - sales units are used only for presentation and purchase, not for keeping stock (Warehouse).
- Full unit of measure support - since version 2.26.
- Multiple sales units per item with separate price list prices - since version 2.28.
- Reading units through the AI assistant - as part of the MCP server, which has been available since version 2.34 (recommended 2.35.55 or newer).
- Choosing a sales unit in the cart and on the item page depends on the store template and requires separate front-end implementation.
- Per-unit prices require price lists that support the chosen sales unit.
- An item's stock unit is tied to its warehouse data - changing the stock unit doesn't automatically convert the quantity already recorded in the warehouse.
- Defining units and assigning an item's stock unit works after the update - this is panel work.
- Showing sales units to the customer in the store (front end) requires implementation - the front end doesn't show a unit choice or a conversion table without work on the template.
- Minimum estimated time:
- defining units and configuring the conversion factor for an item in the panel - from 1 h,
- choosing the purchase unit and a unit table on the item page in the front end (Bootstrap 5 and Bootstrap 4) - from 6 h.
- The time for a specific implementation depends on its scope - we quote it individually.
- What the time depends on:
- the number of sales units per item and the number of items to configure,
- the need for separate per-unit prices in the price list,
- the scope of template changes (unit table, unit choice in the cart, presentation in the order process),
- the store's version - an older version needs an update first (quoted separately).
- Changing an item's stock unit does not re-convert the quantity already recorded in the warehouse - this requires care and a possible stock correction.
- Choosing a sales unit and the conversion table on the item page don't work "on their own" once units are defined - this is separate implementation work in the template.
- The warehouse always keeps stock in the stock unit - sales units don't change how availability or reservations are counted.
- The price per unit of measure (e.g., price per kg or liter next to the item's price) is a separate platform mechanism, independent of the sales units described on this page, and requires separate implementation.
- We do not verify the unit configuration for legal compliance (e.g., the obligation to display the price per unit of measure for selected item categories).
- Automatic stock correction when an item's stock unit changes, instead of manual verification.
- Ready-made, panel-configurable presentation styles for the unit choice on the item page in the Bootstrap 5 template, without individual implementation per store.
Can one item be sold in several units at once?
Yes - an item has one stock unit (for keeping stock) and any number of sales units, each with its own conversion factor and price.
Can each sales unit have a different price?
Yes, since version 2.28 - per-unit prices are set independently in the price list.
Does the warehouse count stock separately for each sales unit?
No. The warehouse always converts quantities to the stock unit and runs the whole warehouse policy in it - sales units are used for presentation and purchase.
Does choosing a purchase unit work right after defining units?
Partially. Defining units and the conversion factor for an item works right away in the panel; showing the unit choice and conversion table to the customer in the store requires separate implementation in the template.
How long does implementing sales in bulk units take?
From 1 h for panel configuration, from 6 h to show the unit choice and conversion table in the store's front end - the exact scope is quoted individually.
Want to see how selling in bulk units could work in your store? Book a free demo (in Polish).
- Unit list: Assortment -> Units of measure - defining the units available in the store, with a suggestion of international standard codes.
- Item units: item editor -> Units of measure tab (visible once the store has more than one unit) - choosing the stock unit and managing sales units with a conversion factor and weight.
- Per-unit prices: the item's price list - a separate price for each sales unit (Price lists and individual prices).
¶ REST API and MCP
- REST API: reading and writing item units and their conversion factors (REST API).
- MCP (AI assistant - MCP server):
ec2_units_of_measure_list - the store's dictionary of units of measure: symbol, name, id, active/visible flags and optionally the number of price list entries expressed in that unit; the symbol is case-sensitive,ec2_unit_of_measure_create - adds a unit of measure to the store's dictionary (a typical implementation needs, e.g., pc, running meter, package, kg, m2, set, pair, m); the unit is informational - selling in a unit other than the item's base unit is a separate feature described above.
| Symbol |
Object |
Description |
| stock unit |
item |
The unit stock and the whole warehouse policy are kept in - one per item |
| sales units |
item |
The list of units the item can be bought in, with a conversion factor and weight relative to the stock unit |