Recreating NCR Product Attributes in WooCommerce

When an NCR Retail Online catalogue moves to WooCommerce, the visible products are usually the easy part. Names, prices, descriptions and images can be imported with a spreadsheet, but the less obvious product attributes often carry the information customers use to compare, filter and purchase. Material, dimensions, colour, brand, pack size and compatibility details all need a clear destination in the new store.

NCR data may also contain several kinds of fields mixed together. Some values describe a product, some control inventory, and others support retail operations such as department reporting or point-of-sale behaviour. Treating every column as a WooCommerce attribute can create a cluttered catalogue, while ignoring useful fields can make products harder to find.

A careful migration preserves the commercial meaning of the old data while adapting it to WooCommerce’s structure. For Australian retailers, this includes details such as metric measurements, Australian dollars, GST-inclusive display prices, postcode-based delivery and local terminology. The goal is a clean product information model that works for shoppers and staff after the NCR system has been retired.

Audit The NCR Product Data

Begin by exporting a representative sample from NCR rather than attempting to transform the entire catalogue immediately. Include products from different departments, products with variations, discontinued lines, bundled items and products with unusually long descriptions. A sample exposes inconsistent values before they become hundreds of import errors.

Create a field inventory with the original column name, its purpose, data type, example value and proposed WooCommerce destination. Separate descriptive data from operational data. “Colour” and “Fabric” are customer-facing attributes, while supplier code, reorder level and internal department number may belong in custom fields, inventory metadata or another business system.

Look for variations in spelling and format. “Stainless steel”, “Stainless-Steel” and “SS” may refer to the same material, while Australian catalogues can contain centimetres in one record and millimetres in another. Normalise these values before import. A controlled vocabulary gives filters consistent results and prevents shoppers from seeing several versions of the same option.

Map Attributes To WooCommerce

WooCommerce global attributes are generally the right choice for information used across many products. Create reusable attributes such as Brand, Colour, Size, Material, Style and Capacity under the product attribute settings. Global attributes support consistent filtering and can be used to build variation options where the product model requires them.

Use product-level custom fields for information that is unique, technical or unlikely to be shared across the catalogue. For example, a furniture retailer may use global attributes for Finish and Assembly Required, but store a detailed “Care instructions” value as product metadata. Avoid creating a separate global attribute for every NCR column, especially internal notes that customers will never search.

Variation attributes need extra care. If an NCR product has colour and size combinations with different stock levels or prices, each combination should become a WooCommerce variation. A general “Colour” field attached to a simple product will not provide separate inventory control. Establish whether the source system represents a real sellable variant or merely a descriptive label before building the product structure.

For retailers moving away from NCR, an API-first migration guide can help frame decisions about which catalogue and stock records should remain authoritative. This matters when WooCommerce will exchange data with a POS, warehouse platform or marketplace rather than operate as an isolated store.

Prepare Values For The Import

Build a transformation sheet between the NCR export and the WooCommerce import file. The sheet should define the target attribute name, accepted values, conversion rule and handling for blanks. For example, “Capacity” might convert “1L”, “1000 ml” and “1 litre” into a consistent customer-facing format, while the underlying numeric value can remain available for filtering.

Keep customer-facing text natural for Australia. Use “colour” rather than “color”, centimetres and kilograms rather than imperial measurements, and prices displayed in AUD with GST treatment that matches the retailer’s tax settings. Product dimensions should state whether they are assembled, packaged or shipping dimensions. These distinctions prevent confusion when shoppers compare furniture, appliances or homewares.

Do not silently discard information that has no immediate WooCommerce equivalent. Preserve the original NCR field in a staging file or migration archive, then decide whether it belongs in a custom field, a product note or an external system. This is especially useful for historic stock codes, supplier references and warranty data that may be needed by customer service later.

A product information management system can be useful where several sales channels need the same enriched catalogue. Guidance on choosing a PIM tool is relevant when product descriptions, specifications and media will be maintained outside WooCommerce. The important principle is to nominate one source of truth rather than allowing conflicting edits in multiple systems.

Import Attributes And Catalogue Content

Create the global attributes and their terms before importing products. This gives the import process stable destinations and makes it easier to identify rejected values. For a large catalogue, use a migration plugin or a scripted process that can match existing terms, create missing terms and produce an error log. Manual entry is suitable for a small range, but it becomes unreliable when thousands of records are involved.

Use stable identifiers such as SKU to match updates. Product names are poor keys because they change, may contain punctuation differences and are not always unique. Keep SKUs consistent with the POS and inventory platform wherever possible. If the NCR export contains leading zeroes, preserve them as text so a code such as 004812 does not become 4812.

Import in stages: categories and brands first, global attributes next, simple products after that, and variations once parent products are available. Images, stock quantities and pricing can follow in separate passes. This approach makes failures easier to isolate and reduces the risk of a partial import leaving products with incorrect stock or missing variation relationships.

For an Australian shop, test local purchasing details alongside attribute data. Check that GST is calculated or displayed correctly, delivery addresses accept states and territories, suburb and postcode combinations behave sensibly, and shipping methods reflect services such as Australia Post or a regional courier. If the store offers Click and Collect, confirm that store location and availability data are not accidentally imported as customer-facing product attributes.

Validate Search Filters And Storefront Behaviour

A successful import is more than a row count. Open products in the storefront and confirm that attributes appear in the intended sections, filters return the correct products, and variation selections update price, stock and images. Test both desktop and mobile layouts because long specification labels can make mobile product pages difficult to scan.

Check edge cases deliberately. Review products with missing attributes, multiple values, accented characters, apostrophes, slashes and unusually large dimensions. Confirm that “Black” does not become separate from “black”, and that a blank value is not displayed as “N/A” unless that wording is genuinely useful. Search for common Australian terms and spelling, including “colour”, “jumper” and “mobile phone”, where relevant to the range.

Measure the effect on merchandising and analytics. Attribute filters should help shoppers narrow a catalogue rather than produce empty combinations. Product feeds for Google, marketplaces and email systems may require specific labels, so validate those exports after the WooCommerce import. Keep a before-and-after sample of URLs, SKUs, prices and stock records to detect accidental changes during later synchronisation.

For home and entertaining products, attribute accuracy can directly affect purchase confidence. A shopper comparing dining furniture needs reliable dimensions, finish, seating capacity and care information; a useful example of this category structure appears in dining and entertaining. Clear specifications reduce avoidable returns and help staff answer questions without reopening the old NCR records.

Practical Migration Recommendations

• Define global attributes only for values customers will browse, compare or use as variations.
• Preserve NCR identifiers and keep an untouched export as a migration archive.
• Standardise spelling, units, colour names and capacity values before loading products.
• Import a small pilot catalogue and test filters, variations, tax display and delivery settings.
• Schedule a review after launch to remove unused terms and correct recurring data issues.

The strongest WooCommerce migration treats product attributes as structured retail data rather than decorative text. A clear mapping, controlled vocabulary and staged import can retain the useful knowledge held in NCR while giving the new store better filtering, clearer specifications and more dependable stock relationships.

For Australian retailers, the practical finish is a catalogue that speaks plainly, displays measurements and GST correctly, and behaves consistently from product search through checkout. Keep the source data documented, assign ownership for future edits, and review attribute performance as the range changes.