Platform Selection
Part of Ecommerce catalogue architecture
Checking catalogue limits during platform selection
Use real product and category scenarios to check variant, bundle and filtering limits in the exact ecommerce setup proposed.
Compare each shortlisted platform against the same awkward products, using the exact plan and storefront setup proposed. A published ceiling is a screening figure; the decision also depends on whether staff can maintain the product, shoppers can select it clearly and the correct item reaches the order.
Treat a numeric cap, a plan or version prerequisite, a channel restriction and a product-model requirement as different constraints. A mechanism such as generated variations or child products is not, by itself, a numerical catalogue ceiling.
Make a comparable worksheet
Choose a simple item, the product with the most stocked combinations, a personalised item, a bundle and the largest category. Record current requirements and a plausible future range separately, then apply the same tests to every candidate.
| Measure | Record for each candidate |
|---|---|
| Product options and combinations | Documented numerical ceiling, required count and combinations that must not be sold |
| Storefront selection | What the intended theme, apps and channels display; any plan or channel restriction |
| Stock and order identity | The SKU and quantity passed to fulfilment |
| Bundles and requests | Required app, extension or custom work, prerequisites and separate limits |
| Discovery | Filtering behaviour and any page or channel restriction in the largest category |
| Maintenance | Import route, edit effort, error handling and owner |
Mark each requirement as demonstrated in the proposed setup, documented but unshown, or unresolved. Enter a numerical ceiling only when it is verified for the proposed setup; otherwise mark it unresolved rather than inferring one from a product mechanism.
Demonstration: BigCommerce’s Catalog Overview example creates a physical coffee mug priced at 10.00, with weight 4 and categories 23 and 21. It shows two selectable Mug Color variants, Blue with SKU-BLU and Gray with SKU-GRAY; record two variant records and those SKUs for the test, not a platform-wide ceiling.
Check the limits that apply to each setup
Shopify. Keep variants, bundles and filters as separate worksheet checks. Name the checks as Adding variants, Shopify Bundles, and Adding filters with Shopify Search & Discovery; for the proposed plan, theme, apps and channels, record the verified constraint or mark it unresolved, then demonstrate each required product and collection.
WooCommerce. Variable Products lets you generate all possible variations from attribute values or add variations manually; each variation can have its own price and stock settings. Demonstration: set up a test product with Medium and Large as its only attribute values, generate the variations, and compare the resulting two combinations with the combinations the store intends to sell.
Product Bundles is a separate extension: it can limit available variations and set a minimum and maximum quantity for each bundled product, or for the combined quantity of bundled items. Its stated prerequisites are WooCommerce 8.2+, PHP 7.4+ and WordPress 6.2+; check those against the proposed setup and test the required bundle there.
BigCommerce. Catalog Overview says complex products with shopper-selectable variant options use a variants array, with an SKU and option values assigned to each variant. Contextual Filters configures Product Filtering: the API supports the default channel, ID 1, and category pages, not Brand or Search Results pages; Product Filtering requires a Pro or Enterprise plan, and the API requires an access token with the information & settings modify scope.
For the filtering demonstration, use the largest category on the proposed channel and plan, then compare its displayed filters with the required worksheet criteria. The Contextual Filters API can retrieve active filters at /v3/settings/search/filters and available filters at /v3/settings/search/filters/available; Enterprise accounts can use custom fields as product filters.
Adobe Commerce. A configurable product displays one product with dropdown choices, while each variation is a separate simple product with its own SKU and inventory. Its variation attributes must be global, use Dropdown, Visual Swatch or Text Swatch input, and have values; demonstrate the intended product by checking that the child products cover the required choices and track their stock individually.
Platform Limits for Complex Product Handling
- WooCommerce - Variable Products
- Unlimited variations (subject to server limits)
- WooCommerce - Product Bundles
- Limited by extension; requires WooCommerce 8.2+, PHP 7.4+, WordPress 6.2+
- BigCommerce - Contextual Filters
- Available on Pro/Enterprise only; limited to default channel, category pages
- Adobe Commerce - Configurable Products
- No hard limit; dependent on system performance and global attribute setup
Use one acceptance scenario per constraint
Give every candidate the same difficult item and category data. Have the supplier create a stocked combination, exclude an impossible one, import a change, capture a customer request and place an order with a bundle.
Browse the largest category and inspect a product page on a phone. Record what the customer sees, what reaches fulfilment and what staff must change later.
A limit matters when the proposed configuration cannot represent, display or maintain a required product acceptably. Keep unresolved dependencies and their owners in the decision record.
