ShipHero vs Spryker
Side-by-side trajectory, velocity, and editorial themes.
ShipHero's rebuilt Wholesale flow is the center of gravity — mobile redesigns, LPN pallet picks, tighter API governance.
ShipHero's April release cadence is almost entirely Wholesale-focused, layering features and polish onto the new Wholesale flow that replaced the legacy system on April 1. Mobile gets standardized redesigns (Cycle Count, Wholesale Dashboard); the workflow gains LPN pallet/carton picks, default-settings governance, and inline API label voiding. On the platform side, unhealthy webhooks get auto-disabled — a real reliability tightening for integration partners.
ShipHero is consolidating around a unified, mobile-first Wholesale experience for 3PLs running high-volume operations. The post-cutover work mostly closes capability gaps the legacy flow had (LPN handling, settings), suggesting confidence in the rebuild and budget freed for adjacent investment. Replenishment got a V2 UI alongside, hinting at a broader app-wide redesign cycle.
Expect similar treatment for Returns and Receiving — both still on older mobile patterns. The webhook-disable policy is a precedent that more API governance (rate limits, scope controls) will follow.
Spryker's changelog feed is currently capturing documentation pages rather than discrete releases.
The recent feed is dominated by feature-overview and integration-guide pages — Customer Account Management, Merchant users, Marketplace Merchant Portal, IAM, MFA, PunchOut Gateway — rather than dated release announcements. What's being surfaced reflects Spryker's B2B and marketplace footprint: Back Office for operators, Merchant Portal for sellers, MFA and IAM for the security layer, PunchOut for procurement integration. None of these entries describe a fresh capability — they describe what already exists.
Without dated release content, trajectory has to be read from what Spryker is documenting rather than what it's shipping. The doc emphasis on Marketplace, PunchOut, and MFA suggests B2B procurement and merchant onboarding remain the center of gravity. For any move to look directional, this feed would need to start surfacing changelogs rather than evergreen reference pages.
Until the source switches from doc-page captures to release-note entries, classifications will stay trivial regardless of what Spryker actually ships. Once the changelog surface clears up, expect commentary to focus on Marketplace operator features and the PunchOut integration matrix.
See more alternatives to ShipHero →
See more alternatives to Spryker →