¶ Hummerce roadmap - direction of platform development

The Hummerce roadmap shows the direction of the platform's development: where new features come from, who decides the order they're implemented in, and where to check what's already shipped. New features reach the store through successive versions, released regularly as part of the Hummerce developer program.

Last updated: 2026-09-29.

¶ Benefits and use cases

Predictable platform development - Hummerce develops in a regular rhythm of successive versions, not only on individual customer request.
Influence over the direction of development - customers in the developer program submit ideas and vote on tasks from the proposal list.
A transparent change history - every released version is described and linked to a page with the full feature description.

¶ How it works

¶ Where new features come from

The order new features are implemented in is set by the Hummerce developer program - customers submit ideas and vote on tasks from the proposal list, and selected tasks reach the next versions of the platform. The full mechanism is described on the Hummerce developer program page.

¶ What and when we publish

We announce concrete plans for the next version publicly only once they're confirmed - we don't publish earlier developer-program findings (proposals still being voted on, tasks in progress). Released features go on the What's new in Hummerce versions page, with a link to each feature's description.

¶ Implementation

Following the roadmap doesn't require implementation - it's information about the platform's direction of development, not a store feature. Released features reach the store through a regular update, described in the Hummerce developer program.

¶ Limitations

We don't publish plans before their official announcement, or internal developer-program details (voting results, budget, tasks in progress).
The order in which tasks are delivered depends on developer-program participants' votes and the development team's current capacity - it isn't guaranteed in advance.
We do not verify submitted feature ideas for legal compliance.

¶ Frequently asked questions

Can customers influence which features Hummerce builds?
Yes - by submitting ideas and voting in the developer program. This is described on the Hummerce developer program page.

Where can you check which features appeared in recent versions?
On the What's new in Hummerce versions page and at hummerce.com/roadmapa/.

Are plans for the next version published in advance?
No. We announce concrete plans publicly only once confirmed, not at the proposal or voting stage.

How long does implementing a roadmap feature take for a specific customer?
Most features reach the store through a regular update, with no separate implementation - described in the Hummerce developer program. If extra configuration is needed, we agree on the time individually.

Does every submitted idea reach the nearest version?
No. The order depends on developer-program participants' votes and the development team's current capacity.

Hummerce developer program - how to submit ideas and vote on tasks.
What's new in Hummerce versions - the full history of recently released features.
On hummerce.com: Roadmap (in Polish), How we implement (in Polish).

Want to submit a feature idea or ask about the direction of Hummerce's development? Contact the Hummerce team (in Polish).