The catalogue is bigger than the platform was built for
Past roughly 50,000 SKUs, a store starts fighting the platform's own limits, not just the quality of the implementation on top of it.
eCommerce platform selection & replatforming
For retail, B2B and marketplace teams whose catalogue, checkout or operating model no longer fits platform defaults. We separate configuration, extension and replatforming before committing to a build.
SIGNS YOU'VE OUTGROWN YOUR PLATFORM
Past roughly 50,000 SKUs, a store starts fighting the platform's own limits, not just the quality of the implementation on top of it.
Customisation has piled up into a stack nobody fully trusts anymore, and every new promotion risks breaking the last one.
Adding an integration or a sales channel turns into archaeology before it turns into work.
Instead of planning for a spike, the team just hopes it doesn't happen during a launch.
OUR APPROACH
Most stores asking which platform to move to shouldn't move at all. We test first whether the real constraint can be removed with a targeted change — replatforming only wins when the evidence shows the platform itself, not the implementation, is the ceiling.
Complex catalogues (50,000+ SKUs), B2B pricing rules, deep customisation.
Overkill, and expensive to run, for a small team that needs low operational overhead.Fast, managed, strong app ecosystem; scales cleanly onto Plus.
Poor fit when core workflows need extensive platform workarounds to function.API-led storefront with less platform lock-in than an app-heavy model.
Smaller extension ecosystem for very specific workflow needs.Merchant-controlled catalogue for content-led stores; strong in EU markets.
Weaker fit once enterprise governance or complex orchestration dominates.WHAT WE CAN OWN
We give you a criteria-led platform recommendation, then define the journeys and checkout built on it.
Vendor procurement and licensing stay with you; brand strategy and content production run as a separate track.Rules, pricing models and extension boundaries are defined up front, with ERP, PIM, OMS and payment integrations connected through clear contracts.
Day-to-day merchandising and replacing an existing source system stay separate, explicitly scoped work.Cutover, rollback and a rehearsed migration come first, followed by an upgrade, extension and technical-debt roadmap so the decision keeps paying off.
Cleaning up messy source data needs an owner on your side.HOW WE WORK
Business rules, journeys and platform evidence.
We map capabilities, constraints and ownership.
Decision criteria and a risk map.
Criteria, vendor facts and integration needs.
We compare realistic platform and migration paths.
A documented recommendation and boundary.
Approved scope, environments and source access.
We build, integrate and test vertical journeys.
Working increments and release evidence.
Production data and agreed priorities.
We review behaviour, upgrades and backlog trade-offs.
A sequenced improvement roadmap.
FREQUENTLY ASKED
Not if redirects, structured data and content parity are planned before cutover — that is the plan, not an afterthought.
No. Most stores asking should not replatform yet. We first test whether targeted changes remove the limiting constraint with less risk.
Lift-and-shift preserves what already works and moves faster. A rebuild earns its cost only when the data model or architecture is itself the constraint — we decide this before scoping, not after.
Migration includes an explicit compatibility review — what carries over, what gets rebuilt and what gets replaced — before any code moves.
Tell us where the platform pushes back — we'll tell you if that's a configuration problem or a real ceiling.
Get a platform fit review →Don't have a store yet? See eCommerce store development →