How to Structure Your New Product Hierarchy Without NCR Categories

Moving away from NCR Retail Online is more than a platform change. It is an opportunity to rebuild the way products are grouped, named, filtered, and presented to shoppers. A clear hierarchy helps customers find the right item quickly, gives staff cleaner stock information, and makes reporting more dependable across online and physical stores.

The old category structure may have reflected the limitations of a previous system rather than the way your business operates today. As retailers transition to platforms such as Magento or WooCommerce, they can replace inherited categories with a flexible product taxonomy based on customer intent, merchandise relationships, stock control, and Australian trading conditions. The NCR Retail Online platform history is useful context, but your new catalogue should be designed for the future rather than copied from the past.

Start With Customer Language

Begin by recording how shoppers actually search for products. A hardware retailer might organise stock around “power tools”, “hand tools”, and “outdoor equipment”, while customers may search for drills, cordless saws, garden hoses, or pressure washers. Both views matter, but the hierarchy should give priority to the terms that help a buyer make a decision.

Review website searches, sales staff notes, customer service conversations, and product names used in stores. Australian buying habits can vary by location: a customer in suburban Melbourne may expect click-and-collect information, while someone ordering from regional Queensland may care more about freight size, delivery timing, and stock held nearby. These needs should influence filters and product information, even when the main category remains the same.

Create a simple vocabulary list before building categories. Include the common product name, accepted synonyms, spelling variations, technical terms, and words used by suppliers. “Fridge” and “refrigerator”, or “sunnies” and “sunglasses”, may need to lead to the same product group without creating duplicate branches in the catalogue.

Separate Products From Attributes

A category should describe what an item is, not every detail about how it differs from another item. A clothing store could place all women’s jackets in a category, then use attributes for size, colour, material, fit, waterproof rating, and season. Creating a separate category for every colour or size would produce a deep, difficult menu and make stock administration unnecessarily complicated.

Use product types and attributes to handle variation. A parent product might be “linen shirt”, with child or variant records for white, navy, and sage in different sizes. For retailers selling footwear, “men’s running shoes” can sit within the hierarchy while brand, width, size, support level, and colour operate as filters. This approach supports better search results and avoids forcing one SKU into several unrelated category paths.

Keep commercial groupings separate from descriptive data. “On sale”, “new arrivals”, “staff picks”, and “EOFY specials” are merchandising collections, not permanent product categories. They should be managed through campaigns, tags, rules, or landing pages so that a product can move between promotions without damaging its place in the core catalogue.

Design Levels That Scale

Most retailers can start with three useful layers: department, product family, and product type. For example, “Home and Living” could contain “Kitchen”, which could contain “Cookware”. A cookware product may then be described as a frying pan, saucepan, or Dutch oven through its product type and attributes.

Add a fourth level only when it provides a genuine browsing benefit. A hierarchy that goes from “Sports” to “Cricket” to “Equipment” to “Bats” to “English willow bats” may be appropriate for a specialist business, but it is excessive for a general department store. Too many levels bury products, especially on mobile screens, where Australian shoppers often compare items while travelling or standing in a shop aisle.

Set rules for where a product belongs when it serves several purposes. A camping lantern could appear primarily under camping equipment, with secondary links from lighting or emergency supplies. Decide whether your platform supports a primary category plus secondary associations, and use those relationships consistently. Do not create duplicate product records simply because an item is relevant to multiple departments.

Map Data Before Migration

Build a product hierarchy document before importing catalogue data. For each existing category, record its proposed replacement, the treatment of discontinued products, the attributes required, the responsible team, and any redirect needed from an old URL. This mapping exercise reveals duplicate names, abandoned categories, inconsistent spelling, and products that were previously placed wherever there was room.

Separate catalogue clean-up from platform configuration. First decide which products should exist and how they should be described. Then configure the category tree, product types, attributes, filters, search rules, and navigation in Magento, WooCommerce, or the selected replacement system. Partners familiar with NCR Counterpoint can help preserve stock and operational links, but they should work from an approved taxonomy rather than make business decisions during the import.

Pay close attention to Australian requirements and logistics. Prices should support Australian dollars and GST display rules, while shipping attributes may need to distinguish metro delivery from remote areas such as the Northern Territory or regional Western Australia. Bulky goods, dangerous goods, click-and-collect eligibility, and store-level availability should be represented as structured data where possible, rather than buried in product descriptions.

If existing subscriptions, licences, or account arrangements affect the changeover, review the available transition guidance before setting a migration timetable. A clean hierarchy will not prevent problems caused by missing product identifiers, incomplete stock feeds, or a rushed domain and redirect plan.

Govern Search And Merchandising

A hierarchy stays useful only when someone owns it. Give responsibility to a catalogue manager, ecommerce lead, or small cross-functional group that can approve new categories and resolve naming disputes. Define when a new category may be created, which attributes are mandatory, how brands are written, and how seasonal ranges are archived.

Use search analytics to identify gaps rather than automatically adding a category for every search term. If shoppers frequently search for “wide fit work boots”, the right response may be a filter for fit and use case, a curated landing page, improved product data, or a synonym rule. A new category is justified when the group has enough products, a clear buying purpose, and a stable place in the range.

Test the structure with real tasks. Ask a store team member to find a product, a customer to compare two variants, and a fulfilment worker to confirm the correct stock item. Test on a phone as well as a desktop, and include shoppers from different parts of Australia. A customer in Sydney may browse by brand, while a rural customer may start with availability and delivery constraints.

Monitor zero-result searches, abandoned category pages, filter usage, conversion rates, and internal search refinements after launch. Review the taxonomy after major range changes, but avoid constant rearrangement. Stable URLs, familiar navigation, and consistent product naming build confidence over time.

A strong replacement hierarchy is shallow enough to browse, detailed enough to filter, and disciplined enough to support inventory and reporting. It should reflect the language customers use, while structured attributes carry the technical details that make products distinct.

The key point to remember is simple: do not recreate NCR categories for the sake of continuity. Build a customer-led product taxonomy with clear levels, reliable attributes, deliberate migration rules, and ongoing ownership.