Configuring Counterpoint item cross-references for online search

NCR Retail Online connected online storefronts with retail inventory and business-management systems. Since the product has been discontinued, retailers moving to Magento or WooCommerce through NCR Counterpoint partners need a controlled way to carry product identity across both systems. Configuring Counterpoint’s Item Cross-Reference Field for Online Search creates that bridge between inventory records and the catalogue shoppers browse.

A shopper’s search can fail long before checkout. If Counterpoint stores TS-1042 while the web platform indexes TS1042, the product may exist but remain unreachable through the SKU search used by staff or warehouse teams. A cross-reference should therefore be a defined data relationship, not an improvised extra code or a substitute for sound catalogue data.

Australian retailers also need consistent pricing, local fulfilment and marketplace-ready product feeds. The platform retirement information explains the move away from the discontinued service, while the practical work lies in choosing identifiers, preparing matching records and testing the resulting customer experience.

Why item identity drives search

Counterpoint item records commonly contain several identifiers: a retailer’s stock-keeping unit, a barcode, a supplier code and values used for reporting. The cross-reference associates an inventory item with a code used elsewhere. It does not automatically merge separate inventory rows, nor does it replace the barcode printed on the shelf.

That distinction matters for apparel and homewares. A timber dining table in natural oak and black stained finishes might exist as separate sellable items with individual SKUs, prices and stock levels. Online, they may belong to one product family. The mapping should preserve that family relationship without losing the identity of each orderable variant.

The destination also matters. An ecommerce platform may match a customer’s SKU query against its own product identifier, a searchable custom field or a synchronised product attribute. The Counterpoint value must reach that field unchanged, including leading zeros and capitalisation, or staff searching during a busy Saturday in Melbourne may find nothing even when the article is in stock.

Designing the cross-reference mapping

Begin by naming the authoritative identifier for each sellable item. A retailer’s own SKU is often the best key because it remains stable through price changes, supplier updates and rebranding. Record whether the existing Counterpoint SKU will populate the ecommerce SKU field or whether the cross-reference will hold a separate external identifier. The partner’s connector documentation and a test export should confirm the destination before any bulk update.

Do not let one field carry incompatible meanings. If the cross-reference holds the online platform’s product ID, a barcode belongs in the barcode field; if it supports staff SKU lookup, use the exact SKU. Some implementations permit several references, while others expose only one. Test the supported behaviour rather than assuming another code can be added.

A clean mapping also requires a deliberate variant strategy. Decide whether the online parent receives the family code and each size or colour receives the item SKU, or whether every sellable row keeps its own catalogue identifier. The search index, order records, fulfilment labels and accounting exports must then follow the same pattern.

Preparing search-ready catalogue data

Before changing mappings, clean the records that will be published to the new store. The following checks reduce common causes of missing and duplicate search results:

• Assign one unique key to each sellable item, including every size, colour and pack configuration.
• Preserve leading zeros, punctuation and capitalisation exactly as they appear in the authoritative record.
• Separate genuinely different products that share a similar name, such as identical chairs sold in different finishes.
• Standardise customer-facing names with searchable material, colour and product terms used in Australia.
• Remove duplicate catalogue entries and confirm that images, barcodes and descriptions belong to the matching item.
• Test realistic searches using an exact SKU, a partial SKU and the words a customer would type.

Treat the first migrated batch as a controlled rehearsal rather than a production upload. Compare each Counterpoint record with its online counterpart, then verify search results, filters, product pages and basket entries. A small selection of simple items, variants and discontinued products will expose more mapping errors than a large batch processed without review.

Synchronising products and stock

A correct cross-reference does not itself keep inventory current. The ecommerce platform still needs scheduled product and price updates, stock-on-hand transfers and dependable error handling. Define how quickly stock changes must appear and whether an unavailable item should be hidden, shown as unavailable or offered from another location.

Physical checks provide a valuable safeguard during the transition. The barcode scanning guidance explains how scanning can help identify stock discrepancies while systems and processes are changing. A scan that matches the physical label but not the online SKU can expose an incorrect cross-reference before customers order the wrong item.

Search indexing introduces another possible delay. A corrected mapping may require the product feed to refresh and the platform to rebuild its index. Test an item that was previously unavailable, remove a temporary test product and confirm that zero-stock results behave as intended. Record how long each update takes so search expectations match the actual process.

Australian tax, market and security realities

For a retailer operating across Sydney, Melbourne and Brisbane, a shared catalogue must serve each store’s stock while respecting warehouse allocations and fulfilment rules. Counterpoint should remain the authoritative source for available quantities, while the ecommerce platform handles presentation and the customer’s order.

Prices displayed in Australian dollars must reflect the business’s 10% GST treatment consistently across the website, counter and exported records. GST affects pricing and tax reporting rather than the item identifier. Marketplace feeds for Australian retailers also need their own identifier rules, including the SKUs expected by operations teams and fulfilment partners.

Australian Post delivery options, including regional and remote-area surcharges, should appear before checkout. If stock comes through an offshore supplier, customs records can also affect the landed product record. Low-value imported goods valued at AUD1,000 or less generally attract 10% GST, while consignments above that threshold generally require an import declaration. Matching the supplier’s code to the correct local item prevents an imported record from surfacing under an unrelated online product.

Payment security needs attention during the same transition. Product and inventory data may move between platforms, but card details should remain with appropriately secured payment services. The PCI compliance guidance covers the reassessment required after an ecommerce platform changes, including the responsibilities that remain with the retailer.

Testing and governing the transition

Run search tests across the catalogue rather than relying on a handful of known items. Include exact SKU searches, customer-language searches, variant filters, products without stock and records with discontinued status. Check both Magento and WooCommerce against the same test set where a staged migration spans platforms, and retain the expected results for later comparison.

The migration also needs clear ownership and controlled access. Assign responsibility for Counterpoint values, connector settings, catalogue changes, index refreshes and exception handling. Keep an audit trail of manual edits, because a cross-reference corrected directly in one system can otherwise be overwritten by the next synchronisation.

For multi-site operational changes, a multi-line cost comparison illustrates why running costs deserve attention alongside projected savings. The same discipline applies to connector licences, staff training and manual stock corrections during the transition.

Select three representative products—a simple item, a multi-variant item and one affected by a store allocation—and record their Counterpoint identifier, expected search result and stock status in the launch checklist.