Shopify
Shopify's October drop lets Sidekick test store changes on AI shoppers and has POS know buyers.
A side-by-side editorial comparison of Hi.Events and Wheelhouse — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Hi.Events | Wheelhouse |
|---|---|---|
| Sector | E-comm | E-comm |
| Velocity score | 6.3 | 5.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | event-ticketing, open-core, self-hosted, box-office | revenue-management, dynamic-pricing, short-term-rentals, api-first |
| Last editorial update | 3d ago | 2mo ago |
| Website | Visit → | — |
Hi.Events 2.0 rc.3 adds paid Enterprise features: reserved seating and a box office.
Hi.Events v2.0.0-rc.3 adds reserved seating with a visual seat-map designer and a browser-based box office with Stripe Terminal card readers, both marked Enterprise and requiring a licence in production. It also adds a per-product purchases view, refunds on manual orders and grouped ticket emails. On 1.x, v1.11.3 refuses to run while the example JWT_SECRET that earlier versions shipped is still configured, since anyone could forge sessions with it, and v1.11.2 rebuilt on patched PHP.
After a summer of shipping data outward, Wheelhouse turns back to the pricing engine.
Two releases on 27 August move differently from the API, webhook and MCP work that filled July and August. One retunes the More conservative curves for Last Minute Discount and Far Future Premium — the far-future premium now starts building around 180 days out rather than 365, climbing toward roughly 25% — while moving listings already on that setting to a Custom rule matching the old curve, so live pricing did not change underneath anyone. The other puts aggregate Occupancy, Asking Rate, ADR and Pickup rows at the top of the Portfolio Calendar, following whatever filter or segment is applied.
Hi.Events v2.0.0-rc.3 adds reserved seating with a visual seat-map designer and a browser-based box office with Stripe Terminal card readers, both marked Enterprise and requiring a licence in production. It also adds a per-product purchases view, refunds on manual orders and grouped ticket emails. On 1.x, v1.11.3 refuses to run while the example JWT_SECRET that earlier versions shipped is still configured, since anyone could forge sessions with it, and v1.11.2 rebuilt on patched PHP.
The 2.0 cycle has gone from structural changes (recurring occurrences, embedded checkout, an API) to venue-grade features, and now to an open-core split between free self-hosting and licensed Enterprise features. The 1.x line is in security-only mode, with users pushed toward 2.0.
Expect a 2.0.0 final soon after rc.3, with the Enterprise licence terms spelled out, and 1.x limited to security fixes.
Two releases on 27 August move differently from the API, webhook and MCP work that filled July and August. One retunes the More conservative curves for Last Minute Discount and Far Future Premium — the far-future premium now starts building around 180 days out rather than 365, climbing toward roughly 25% — while moving listings already on that setting to a Custom rule matching the old curve, so live pricing did not change underneath anyone. The other puts aggregate Occupancy, Asking Rate, ADR and Pickup rows at the top of the Portfolio Calendar, following whatever filter or segment is applied.
The outward push has not stopped, but the centre of gravity is returning to the product's own surfaces and the model behind them. Both releases take something that already existed — segment-aware aggregation, the conservative pricing curves — and place it where a revenue manager is already working, at the top of the calendar or inside a default setting. Migrating existing listings onto a Custom rule rather than changing their prices suggests these defaults are now treated as something customers depend on rather than something to iterate freely.
The calendar rows are described as step one of tying pricing strategy to how each day is performing, so further per-date controls or actions taken directly on the calendar are the most likely next move.
Other E-comm products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Hi.Events or Wheelhouse.
Shopify's October drop lets Sidekick test store changes on AI shoppers and has POS know buyers.
Foxy follows its legacy API lockdown with a FedEx rate-type option.
Virto Commerce opens two-factor sign-in to extensions after its Admin UI refresh.
Antavo's feed is loyalty-industry commentary; the product rarely appears in it.
Cody rebuilds its Products module and pipes in-store sales and stock into Google Ads.
Cart Abandonment Recovery Pro 1.3.0 adds an activity log and an email capture popup.
See all Hi.Events alternatives → · See all Wheelhouse alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Hi.Events is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Hi.Events is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other E-comm products to evaluate alongside.
Top Hi.Events alternatives in E-comm are ranked by recent ship velocity. Browse the "Hi.Events alternatives" section above for the current picks, or visit /alternatives/hi-events for the full list with editorial commentary on each.
Top Wheelhouse alternatives in E-comm are ranked by recent ship velocity. Browse the "Wheelhouse alternatives" section above for the current picks, or visit /alternatives/wheelhouse for the full list with editorial commentary on each.