¶ Hummerce developer program - submitting ideas

The Hummerce developer program lets customers submit ideas for new platform features and vote on tasks from the proposal list (the roadmap). Selected tasks reach the next versions of Hummerce and - in most cases - every participating store through a regular update, with no separate implementation per customer.

Last updated: 2026-09-29.

¶ Benefits and use cases

Influence over platform development - customers submit feature ideas and vote on tasks from the proposal list.
Features reach every participant - most completed tasks are available to all program participants through a regular update, with no extra implementation in each store.
Access to updates for every module installed in the store, as new platform versions ship.
Development cost shared among participants - instead of funding an entire feature alone, a customer votes on a task delivered jointly for many stores.

¶ How it works

¶ Submitting ideas

Customers submit proposals for new features, which go onto the Hummerce proposal list (roadmap).

¶ Voting and selecting tasks

Program participants vote on tasks from the proposal list. The order in which tasks are delivered depends on the number of votes and the development team's current capacity - voting results and the task list for the year are announced to program participants.

¶ Delivery

Selected tasks reach the next versions of the platform. Most features are available through a regular update; if a task needs extra configuration in a specific store, that's noted on the task. Program participants get an update at least twice a year, and more often when new functionality ships.

¶ Implementation

Joining the developer program doesn't require separate technical implementation - how long updating a store to a new version takes depends on the scope of changes and how customized the store is. Tasks that need extra configuration or changes in an individual customer's implementation are planned and quoted separately.

¶ Limitations

The order in which tasks are delivered depends on participants' votes and the development team's current capacity - not every submission reaches the nearest version.
Tasks that need changes to an individual customer's implementation aren't available through a plain update - they require separate implementation work, planned and quoted separately.
Updating stores with individual changes (interface, data migrations) takes more work than updating a standard store.
We do not verify submitted feature proposals for legal compliance (e.g. GDPR, store terms of service, licenses of the solutions used).

¶ Frequently asked questions

Can customers submit ideas for new Hummerce features?
Yes. Proposals go onto the proposal list (roadmap), which developer program participants vote on.

Does a feature chosen by vote reach only one store?
No. Most completed tasks are available to every program participant through a regular update to the new version.

How often does a store get updates through the program?
We ship new platform versions regularly - a summary of the latest releases is on the What's new in Hummerce versions page.

How long does updating a standard store to a new version take?
It depends on the scope of changes and how customized the store is - we agree on it when planning the update. More complex cases, e.g. interface changes or large data migrations, may need extra time.

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

Want to submit a feature idea or join the developer program? Contact the Hummerce team (in Polish).