Wheelhouse vs ShipHero
Side-by-side trajectory, velocity, and editorial themes.
Wheelhouse is making its whole revenue-management stack promptable
Wheelhouse is opening its revenue-management platform to programmatic and AI-driven use. It shipped an MCP server exposing 58 tools at claimed 1:1 parity with the UI, backed by a new set of RM API endpoints (history, sync, segments, teams) — and is running an API hackathon to seed usage. In parallel it keeps deepening pricing intelligence: neighborhood occupancy benchmarking, AI-detected local events on the calendar, and more precise historical anchoring for price floors.
Two reinforcing bets: an API-first surface that lets operators (and their AI assistants) drive pricing from code instead of clicks, and richer market-relative signal so those decisions are better informed. The MCP move is the directional one — it turns Wheelhouse from an app you log into a set of levers an agent can pull. The pricing-intelligence releases (neighborhood metrics, event detection, anchoring sources) suggest the differentiation is shifting toward data quality and market context.
Expect the RM API and MCP surface to keep expanding toward full write parity and more operators building automation on top; the pricing-intelligence cadence points to more neighborhood and demand-signal metrics next.
ShipHero grinds out warehouse-workflow refinements, sanding friction off packing, putaway, and reporting
ShipHero is in steady incremental mode, shipping a stream of targeted warehouse-operations refinements. The recent window clusters around three areas: Hospital (problem) location management with new filters, bulk cleanup, and mobile issue detail; packing and scanning workflow changes; and more filtering/reporting in the 3PL Portal and Shipments Report. Each release is a small, concrete quality-of-life fix aimed at warehouse and 3PL operators.
The direction is operational polish rather than new capability: reduce clicks, add filters where operators hit friction, and give 3PL teams more control over holds, containers, and locations. The Aug 3 packing-scan behavior change shows a willingness to simplify entrenched workflows based on customer feedback, even at the cost of an opt-out.
Expect the same cadence of workflow and reporting refinements across packing, putaway, and the 3PL Portal, driven by operator feedback, with no directional pivot signaled in these entries.
See more alternatives to Wheelhouse →
See more alternatives to ShipHero →