Catalogue Architecture
Part of Choosing an ecommerce platform for an Australian store
Matching platform requirements to a store's catalogue
Turn real products, variants and custom choices into catalogue requirements you can check in an ecommerce platform.
Match a platform to your catalogue by modelling the products that are hardest to sell correctly, then checking them in the proposed store setup. Product count alone tells little: a small range with stocked sizes, personalised choices or compatibility requirements can need more careful configuration than a larger range of simple items.
Make a representative product set
Choose a few real items before reading feature lists. Include a simple product, an item with stocked choices, one with a customer-supplied detail and one whose suitability depends on another product. For each, record the customer decision, the item staff must fulfil and the data they must maintain.
Product question / Requirement to record
- Is each choice a separate stocked item?
- SKU, stock quantity, image or delivery weight by size
- Does a choice customise one item?
- Engraving text or a gift message attached to the order
- Can choices be combined?
- Which combinations exist, and what appears when one is unavailable?
- Does the shopper need guidance?
- Compatibility, measurements or specifications needed before adding to basket
- What changes often?
- Supplier price, availability, product claim or seasonal assortment
Use the questions that fit your products. Keep customer-facing information separate from data used only by staff or fulfilment systems.
Distinguish a variant from a request
A stocked size or colour may need its own SKU and inventory. A typed engraving request may belong to the purchased item without creating a new stock record. Platform product models treat these choices differently.
BigCommerce documents variant options as selectable by shoppers. WooCommerce variable products can hold price and stock at variation level. Adobe Commerce configurable products use separate simple products for their variations.
Ask what the warehouse actually picks. Modelling every customer choice as a stock variant can create needless records; modelling a separate stocked item as text can obscure the quantity staff must control. The chosen structure should make the fulfilled item clear on the order.
Check limits where they affect the experience
Record the largest real combination set. Check how the intended platform, theme, app and import method handle it, and whether the proposed setup's option and variant handling covers the combinations your products require.
WooCommerce variable products provide controls for price, stock and image at variation level. Check how the proposed product page presents the combinations and handles unavailable choices.
Have a merchandiser change one variation's price, image and stock, then remove an unavailable combination. Inspect the product page, search result, basket and order record in the proposed configuration.
Follow the product through fulfilment
A correct product page is the first checkpoint. Ask what the order sends to fulfilment, whether accounting receives the right item, and whether a return identifies the same variation. For a custom request, check where the customer's wording appears and whether staff can act on it. Identify which system owns stock quantities if several systems can update them.
Record any requirement that needs an extension, custom field or changed import process, and assign its maintenance. Select a platform when the proposed catalogue setup presents a clear choice to the customer and an unambiguous item for staff to supply.
