Skip to main content

Feature Request: Shared Stock / Capacity Management for Custom Item Field Values

1 hour 39 minutes ago #100000786 by thomas.eilers@gfse.org
-- Browser(s) name and version -- : Firefox 160.0

Hello HikaShop Team,

I would like to suggest an enhancement to HikaShop Custom Item Fields: the ability to manage stock or capacity individually for each selectable field value, with the option to share this capacity across individual products, multiple products or entire product categories.

We currently use HikaShop together with HikaMarket and HikaSerial, so compatibility with these extensions would also be important.
This functionality would be particularly useful for events, workshops, seminars, training courses and other activities with limited availability.

1. Background and Use Case
Imagine an event that offers several workshops or activities, each with a limited number of available places.
The event itself is offered through different products representing registration types, such as:
  • Members
  • Non-members
  • Students
  • Other registration categories
Although these are separate products, all customers must share the same available capacity for each workshop or activity.
Currently, this can be achieved by creating additional option products and variants with stock management.
However, this approach requires maintaining numerous additional products and variants, even when the selected activity does not affect the product price.
It also creates additional order-product rows, making order processing and exports more complicated.

2. Proposed Feature
Introduce optional stock or capacity management for individual values of Custom Item Fields.
This functionality should be available at least for the following field types:
  • Radio buttons
  • Dropdown / Select lists
  • Checkboxes (multiple selections)
Each selectable value should optionally have its own maximum capacity and remaining availability.
For example:
Custom Field: Workshop SelectionMaximum CapacityAvailable Places
Workshop A128
Workshop B153
Workshop C100
Workshop D2017
When an option reaches its capacity limit, it should automatically become unavailable for selection.
Fields without capacity restrictions should continue working exactly as they do today.

3. Assignment to Products and Categories
The feature should support both individual products and product categories.
Ideally, the following configuration options would be available:

Individual product
The capacity applies only to a particular product.

Multiple selected products
Several products share the same capacity for each Custom Field value.

Product category
All relevant products within a selected category share the same capacity.

Categories and subcategories
Custom Fields can be assigned to categories, optionally including their subcategories. Capacity pools should also be configurable separately for individual subcategories.
For example:
A category named "Annual Workshop 2027" contains several registration products:
  • Member registration
  • Non-member registration
  • Student registration
All three products should share the same capacity for Workshop A, Workshop B, etc.
If a customer books Workshop A through the member registration product, the available capacity for Workshop A must also decrease for customers booking through the other registration products.
However, a separate category such as "Annual Workshop 2028" should have independent capacities, even if the same Custom Field is reused.

It is therefore important to distinguish between where a Custom Field is displayed and which products or categories share its capacity.

4. Automatic Stock / Capacity Management
The system should automatically manage capacity according to order quantities and order statuses.
Important requirements include:
  • Automatically reduce available capacity when a booking becomes binding.
  • Restore capacity when an order is cancelled or refunded, according to configurable order-status rules.
  • Support partial cancellations and quantity changes.
  • Prevent overbooking when multiple customers place orders simultaneously.
  • Perform server-side availability checks.
  • Use atomic stock updates or another reliable locking mechanism to prevent race conditions.
  • Optionally reserve capacity for pending orders, with configurable expiration or release rules.
  • Prevent duplicate stock reductions or releases when an order status is processed more than once.
Ideally, these mechanisms could reuse HikaShop's existing stock-management logic.

5. Frontend Behaviour
The available capacity should optionally be displayed next to each selection.
For example:
  • Workshop A – 8 places available
  • Workshop B – 3 places available
  • Workshop C – Fully booked
  • Workshop D – 17 places available
Fully booked options should be disabled or clearly marked as unavailable.
If an option becomes fully booked while a customer is completing an order, HikaShop should reject that selection and display an appropriate message.
This should also work correctly with checkbox fields where multiple values can be selected.

6. Optional Quantity Selection
It could also be useful to support quantities for individual selected values.
For example, a customer might select two places for a particular workshop.
In that case, the system should deduct two places from the corresponding shared capacity.
However, quantity selection should be optional. In many scenarios, selecting a value simply represents one booked place.

7. No Price Adjustment Required
The primary purpose of this feature is stock and capacity management, not price calculation.
In many cases, the selection of a workshop, tutorial or activity does not change the price of the main product.
Therefore, capacity management should work independently of any pricing functionality.
No additional products or price adjustments should be required simply to manage limited availability.
Existing pricing, tax calculation and invoice generation should remain unaffected.

8. Order Data and Exports
Selected Custom Item Field values should continue to be stored with the corresponding order items.
They should remain available for:
  • Order details
  • Order confirmation emails
  • Invoices, where configured
  • CSV and Excel exports
  • Other integrations using Custom Item Field data
By eliminating the need for additional option products purely for stock management, order data and exports could become significantly simpler.

9. Compatibility with HikaMarket and HikaSerial
Since we use HikaShop, HikaMarket and HikaSerial together, it would be important for this functionality to integrate properly with these extensions.
In particular:
HikaMarket
  • Shared capacity should remain consistent when products are managed by vendors.
  • Vendor orders and their corresponding main orders must not cause duplicate capacity deductions or releases.
  • Vendor-specific permissions and ownership should be respected when managing shared capacity.
HikaSerial
  • The new capacity-management functionality should coexist with existing HikaSerial workflows.
  • Where relevant, integrations involving serials, tickets or other generated records should not interfere with capacity accounting.
The exact integration requirements could be discussed during implementation.

10. Expected Benefits
This feature would:
  • Reduce the need for hidden option products and variants.
  • Simplify product and event configuration.
  • Allow different products to share limited capacities.
  • Support category-based capacity management.
  • Prevent simultaneous overbooking.
  • Automatically release places after cancellations.
  • Simplify order processing and exports.
  • Preserve existing product prices and tax calculations.
  • Provide a flexible solution for many different booking and registration scenarios.

Summary
The proposed functionality is:
Optional stock/capacity management per Custom Item Field value, with configurable shared capacity across individual products, selected products or product categories, including automatic stock adjustments, cancellation handling and protection against simultaneous overbooking.
Ideally, this should build upon HikaShop's existing stock-management mechanisms wherever possible and remain compatible with HikaMarket and HikaSerial.
I believe this would be a valuable enhancement for many HikaShop users, particularly those managing workshops, training sessions, seminars, appointment slots, event registrations or other activities with limited availability.

Thank you for considering this feature request.
Best regards
Thomas

Please Log in or Create an account to join the conversation.

Time to create page: 0.049 seconds
Powered by Kunena Forum