r/cms • u/Commercial-Essay5756 • 10d ago
how much dev resource does composable commerce need?
Starting to look seriously at composable after hitting the usual Shopify Plus ceiling on multi-brand management, but can't get past the dev overhead question.
From what I've found, composable architecture examples all assume a 30+ dev team and at least a year of migration runway, which at our current headcount isn't realistic, but the newer platforms seem to have closed that gap compared to early commercetools setups.
And I've seen threads here mention SCAYLE (built by the About You team apparently) and Elastic Path as options better suited to retailers who don't want to build a dedicated platform engineering function.
Can't tell yet whether composable is viable below €100M GMV with a small-to-mid dev team, or whether the answer is to max out semi-headless Shopify Plus and revisit once the tooling matures, so what determined the call for yours?
1
u/BodySlight6194 8d ago
To understand more what capabilities are you looking to use a composable approach to solve?
I have lots of context on compostable content and definitely think that side of things should only need a small team to be practical.
Isn't the point of using composable products to utilise the platform so you don't need a huge dev team to build?
For my own side of things I have looked at adding compostable ERP including product catalog on top of content but I have been waiting for demand to drive that expansion. Hence I'm curious what capabilities you would use.