Ecommerce

What are the options when WooCommerce can't handle your catalogue?

The short answer

There are three realistic options: keep extending WooCommerce, move to a packaged platform, or build a storefront around the catalogue itself. Whichever you choose, moving the indexed URLs, supplier data and pricing logic is most of the work, and it decides whether the move is safe.

Updated September 26, 2026

Keep extending WooCommerce

Workable while the catalogue is modest and pricing is simple. It gets hard when the store's real logic lives in bespoke theme code: on our own flooring store, pricing lived in thousands of lines bolted onto the storefront.

Move to a packaged platform

Often right when price is a number in a field and the catalogue is ordinary. It does not remove the migration work — the URLs, the data and any pricing rules still have to move.

Build around the catalogue

Worth it when price is a calculation, the catalogue is large, or suppliers disagree. We took this route for our own store: Catalogue Engine holds 118,651 catalogue rows with search that stays usable, resolves a room to boxes and a priced estimate, and rates freight before checkout.

What makes any option safe

The URL map. All 36,786 indexed URLs of the old store were mapped to live destinations before the DNS changed, so no ranked page became a 404. The method is in the guide to replatforming a large catalogue without losing rankings.

Asked next

Can we keep WooCommerce and replace only the catalogue?

Sometimes, and it is worth asking before a full move. Replacing one piece at a time — leaving the store running and moving one bounded part across — spreads the risk. Whether it works depends on where the pain actually is, which is what the free audit maps.

What should we have ready before planning a replatform?

The list of URLs the current store serves, your supplier feeds, and the rules someone applies to prices by hand. The URL inventory comes first, because it decides how much of the move is mechanical.