Short answer
If the store already sells and the team runs WordPress, stretch WooCommerce with custom engineering. If price comes from a measurement or the store must share truth with operations, build custom ecommerce or put the store on top of the operations system.
WooCommerce is not "old"
If you already have a catalog, payment methods, and a team loading products there, throwing it away for fashion is expensive. In the curtains case, years of custom plugins (installments, QR, quoting) lived on WooCommerce because the store was already live.
When WooCommerce is enough
- The product has a price or rule that fits a plugin.
- Local checkout (installments, QR, Mercado Pago) is the bottleneck, not the business model.
- The team already operates the WordPress admin.
When it stops fitting
- Price comes from a measurement, a recipe, or a production flow.
- Store and operations must share stock, statuses, and customers.
- Every campaign needs a developer so checkout does not break.
Then custom ecommerce stops being a whim. The useful question is not "which stack is trendier?". It is "where does the order's truth live?".
FAQ
Do we have to migrate?
No. Sometimes the lower cost is a well-built plugin and a solid local checkout.
How much does custom ecommerce cost?
It depends on catalog and gateways. It often looks like a system phase or a large focused tool. We lock it in writing after diagnosis.