Recreating NCR Bulk Import Templates in WooCommerce

When NCR Retail Online was discontinued, retailers had to move their catalogue, stock processes and online selling workflows to another platform. WooCommerce is a practical destination for many small and mid-sized Australian businesses, particularly those already using WordPress or working with an NCR Counterpoint partner.

The difficult part is rarely uploading a spreadsheet once. The real task is recreating a dependable product import and export system: matching old fields to WooCommerce fields, preserving variants, updating stock without overwriting prices, and making future catalogue changes repeatable.

A well-designed template gives staff a common language for products, categories, tax settings, images and inventory. It also reduces the risk of duplicate products or incorrect pricing when a business is managing a physical shop in Brisbane, Melbourne or regional New South Wales alongside its online store.

Map The Old Catalogue Before Importing

Start by exporting the NCR data into a working copy rather than editing the original file. Keep the original column names visible, then create a second sheet that maps each legacy field to a WooCommerce field. A useful mapping might connect ItemNo to SKU, Description to Name, RetailPrice to Regular price, and QtyOnHand to Stock.

Do not assume that similarly named fields behave identically. An NCR category may contain a department hierarchy that must be split into WooCommerce parent and child categories. A single legacy “price” field may also hide sale pricing, member pricing or tax-inclusive values. For retailers selling products such as clothing, footwear or gifts for him, clear category and attribute rules are essential for navigation and filtering.

Australian businesses should decide early whether prices in the source file include GST. Most consumer-facing prices in Australia are displayed as GST-inclusive, while some wholesale or trade systems store ex-GST values. The WooCommerce tax configuration, catalogue prices and import file must use the same assumption, or every product can be displayed incorrectly.

Build A WooCommerce-Compatible CSV

WooCommerce’s built-in importer accepts CSV files with recognised headings, including SKU, Name, Published, Regular price, Sale price, Categories, Images, Stock, and Stock status. The exact column set depends on whether the file contains simple products, variable products, subscriptions or other extensions.

Create one master template with stable headings and a separate staging file for transformations. Use UTF-8 encoding, a comma delimiter unless your workflow requires another format, and one product per row for simple products. Avoid merged cells, coloured formatting and formulas that have not been converted to values. Product descriptions can contain HTML, but that HTML should be tested for broken tags and unsafe pasted content.

When a product has variations, the structure changes. The parent row should identify the variable product, while child rows use a unique SKU and refer to the parent through a Parent value or matching product identifier. Attribute columns such as Attribute 1 name and Attribute 1 value(s) need consistent spelling. “Black”, “black” and “Blk” should not become separate options.

Images deserve particular attention because image paths in an NCR export may point to a local folder that WooCommerce cannot reach. Replace those paths with publicly accessible image URLs or upload the files to WordPress first. A workflow that helps teams convert and edit spreadsheet content can be useful, provided staff inspect the result rather than relying on automatic formatting.

Preserve Stock, Pricing And Product Relationships

The safest import process separates catalogue content from live stock updates. A full product migration can include names, descriptions, categories, attributes and images. Later stock files should contain only the fields needed for inventory, such as SKU, stock quantity and stock status. Importing a complete catalogue every morning can unintentionally replace descriptions, prices or images.

SKUs must be unique and stable. Do not use a product name as an identifier because names change and may contain punctuation. If the existing NCR item number is reliable, retain it as the WooCommerce SKU. If multiple stores share a product, agree on whether stock is imported as one combined quantity or managed by a multi-location extension.

Use decimal and date formats consistently. Australian spreadsheets can be affected by regional settings, especially when files move between Microsoft Excel, Google Sheets and export tools. Check that prices such as 19.95 have not become text, that leading zeroes in SKUs have survived, and that commas inside descriptions have not shifted values into new columns.

Before importing thousands of records, run a small test with products covering the main cases: a simple item, a product with an image, a variable product, an out-of-stock product and a GST-sensitive price. Review the shop page, product page, cart and administration screen before expanding the batch.

Recreate Category And Attribute Logic

NCR department structures often need more than a direct category rename. WooCommerce separates categories, tags and global attributes, and each has a different purpose. Categories should describe where a product belongs, tags can support secondary discovery, and attributes should power filters or variations such as size, colour, material and brand.

A mapping sheet can contain columns for Old category, New category, Parent category, Slug and Notes. This prevents small spelling differences from creating duplicate branches. For a larger catalogue, an automation mapping guide can help plan category transformations before they are applied to production data.

Keep the taxonomy understandable for Australian shoppers. A hardware store may need categories that reflect local buying habits, while a fashion retailer serving customers in Sydney and Perth may need filters for size, colour and fabric. Avoid building a structure around internal NCR department codes if customers will never see or search for those terms.

Check SEO slugs and redirects after the import. If old product or category URLs were indexed, changing them without redirects can create broken links. Product descriptions should also use Australian spelling and relevant local measurements, such as centimetres, kilograms and Australian clothing sizes where appropriate.

Make Imports Safe For Australian Operations

Schedule catalogue updates outside busy trading periods. A Melbourne retailer may process click-and-collect orders while staff are serving customers in-store, and a temporary stock mismatch can create an avoidable oversell. Keep a timestamped copy of every input file and record who approved each import.

Hosting quality matters when importing large files or downloading images. A WooCommerce installation with limited PHP memory, short execution limits or slow storage can stop partway through a batch. A managed environment such as reliable WooCommerce hosting may provide a stronger base, though the server still needs to be configured for the catalogue size and import method.

Australian compliance should be part of the data design. Product and checkout information must be handled in line with the Privacy Act 1988, while refund and replacement policies should reflect Australian Consumer Law. Do not place unnecessary customer details in product spreadsheets, and limit administrator access to files containing supplier or operational information.

Checks Before And After Each Import

Use these checks before pressing the import button:

• Confirm UTF-8 encoding, column headings and delimiter settings.
• Check unique SKUs, GST treatment and decimal prices.
• Test image URLs and variation parent-child relationships.
• Save a dated backup of the database and source CSV.

Then inspect the store after processing:

• Search for imported products by SKU and product name.
• Open category pages, filters, product images and variation selectors.
• Compare a sample of stock and prices with the retail system.
• Review import logs for skipped, duplicated or failed rows.

Connect The Template To Daily Store Work

A template becomes valuable when it supports repeatable routines rather than a one-off migration. Decide which file is authoritative for each field. The retail system may control stock, WooCommerce may control descriptions and images, and a separate pricing workflow may control promotions. Without ownership rules, the next import can overwrite carefully edited information.

Use a staging site for structural changes and a production export for routine updates. Staff should know whether an empty cell means “leave unchanged” or “delete this value”; those meanings are not interchangeable. When possible, use separate files for creating products, updating stock and changing prices.

The checkout process also needs testing after the catalogue is in place. Product data can look correct while shipping, payment, tax and click-and-collect settings remain broken. The guidance on rebuilding the checkout flow is relevant when moving the customer journey from NCR Retail Online into WooCommerce.

Keep a short change log with the file name, import date, operator, number of rows and any errors. This makes it easier to identify whether a problem came from the source export, a spreadsheet transformation, the importer or a plugin. It also gives an NCR Counterpoint partner or developer enough information to diagnose an issue quickly.

The central lesson is to treat the WooCommerce CSV as a controlled data model, not just a spreadsheet. Preserve stable SKUs, map categories deliberately, separate stock from catalogue updates, test GST-inclusive pricing and verify every import on a small sample first. A careful template can reproduce the useful discipline of NCR’s bulk product workflows while giving an Australian retailer a maintainable WooCommerce operation.