OpenCart is still a practical open-source storefront: catalog, cart, and a large module marketplace, without a WordPress editorial layer. English-speaking teams meet it as a legacy shop to keep alive, a budget catalog, or a migration source toward Shopify or WooCommerce. I both build and replatform OpenCart, depending on whether the catalog and modules are still cheaper to extend than to replace.

Keep OpenCart when the catalog is conventional, the team already knows the admin, and you do not want a SaaS tax. Leave it when checkout UX, hosting, and security patches have become a second job, or when you need a modern headless storefront. I will not bolt a half-broken payment module onto an unmaintained 2.x install and call it production.

Work typically includes category and product structure, options, checkout, payment and shipping modules, multi-store where it is already in use, and a hardening pass (PHP version, file permissions, admin path, backups). For migrations I export products, customers, and orders, then put a redirect map in front of old URLs so organic listings do not die.

If the real pain is warehouse accuracy, pair this with ERP and inventory sync. If the pain is Google Shopping, see merchant feeds. Custom storefronts that only use OpenCart as a back office are closer to headless.

A contained OpenCart launch or rescue often lands in 4–9 weeks. A full replatform to Shopify or WooCommerce is a separate project on store migration, with its own freeze window.