Recreating NCR Product Comparison in Magento with a Plugin

NCR Retail Online was built around the practical needs of retailers that wanted ecommerce selling, synchronised stock and connected business operations in one environment. Since the product has been discontinued, merchants moving from NCR Counterpoint need to preserve useful customer-facing tools rather than simply copy product records into a new shop. Learn more about 99shoutbox.com.

A product comparison feature is a good example. Shoppers expect to place several similar items side by side, review specifications and make a confident purchase decision. Magento can reproduce this experience with a suitable extension, carefully mapped catalogue data and a small amount of custom development. For Australian retailers, the result should also reflect GST-inclusive pricing, Australian shipping expectations and the way customers move between online research and physical stores. Learn more about Key Differences Between Ncr Retail Online And Magento For Inventory Management.html.

Map the Legacy Experience

Before selecting a Magento plugin, document how comparison worked in the former storefront. Record which products could be compared, how many items appeared at once, which attributes were visible and whether comparison was available from category pages, search results and product pages. A simple screen recording or annotated set of screenshots can prevent important details from being lost during migration.

The feature may have been more valuable than its interface suggested. A customer comparing two bar fridges might need capacity, dimensions, energy rating, door configuration and warranty information. Someone choosing point-of-sale hardware may care about connectivity, compatibility, included accessories and support terms. These fields must be identified separately from ordinary marketing copy.

The NCR Retail Online archive provides useful background on the platform’s original focus on ecommerce integration and retail operations. Migration teams can use that context to separate features that belong in Magento’s storefront from functions that should remain in Counterpoint, an ERP, a warehouse system or a third-party service.

Choose Magento Comparison Architecture

Magento Open Source and Adobe Commerce do not provide every comparison workflow a retailer may want out of the box, so an extension is usually the fastest starting point. A plugin should support configurable comparison attributes, responsive layouts, product variants and links back to each product page. It should also avoid adding excessive JavaScript or database queries that could slow category pages.

The extension should work with Magento’s attribute sets rather than relying on manually entered text. This allows a merchant to create reusable fields such as colour, material, screen size, operating system, dimensions or pack quantity. Admin users can then decide which attributes appear in comparison without asking a developer to edit template files every time the catalogue changes.

A plugin may still need a small custom module or theme adjustment. Common enhancements include changing the comparison limit, adding a “clear all” control, hiding empty attributes, displaying stock status and adapting the layout for touch screens. The objective is to extend the Magento storefront cleanly, rather than build a separate comparison application that becomes difficult to maintain.

When assessing a developer or extension provider, retailers can review Magento specialists for examples of ecommerce implementation experience. The important consideration is familiarity with Magento indexing, caching, theme compatibility and integrations, not simply whether a plugin includes a comparison button.

Build Product Data for Australian Shoppers

Comparison only works when catalogue data is consistent. Establish naming rules for attributes, units and values before importing products. Use centimetres and kilograms where appropriate, keep spelling consistent with Australian English and avoid mixing values such as “stainless steel”, “Stainless” and “SS” for the same characteristic.

Pricing requires particular attention. Australian customers generally expect displayed consumer prices to include GST, while trade customers may need ex-GST pricing, account pricing or quantity breaks. The comparison view should use the same tax configuration as the product page and should not show a misleading “from” price when configurable options have substantially different costs.

Local fulfilment details can make comparison more useful. A retailer serving Sydney, Melbourne and Brisbane may want to show stock by location, click-and-collect availability or an estimated dispatch window. Customers in regional Queensland, Western Australia or Tasmania can face different delivery times and charges, so a generic green “in stock” label may not provide enough information.

The product feed should also handle Australian postcodes, suburb names and state abbreviations correctly. If freight eligibility differs by location, that information should be explained near the comparison results rather than appearing only at checkout. The same principle applies to warranties, Australian electrical compliance, local support and delivery exclusions.

Test Performance Security and Merchandising

Begin testing with realistic catalogue sizes. A comparison extension that works with 500 products may behave differently on a store containing tens of thousands of SKUs, multiple websites and several customer groups. Test category pages, layered navigation, search results, configurable products and mobile devices while Magento indexes are running.

Check that comparison URLs do not create an uncontrolled number of crawlable pages. Canonical tags, robots directives and sensible internal linking can help search engines focus on product and category pages instead of indexing every possible combination. Product structured data should remain attached to the individual product page, where the complete offer, price and availability are maintained.

Security testing should cover access to comparison endpoints, form keys, customer sessions and third-party scripts. Keep Magento, the extension and the theme patched, and review vendor permissions in the admin panel. If the old platform handled customer accounts or order history, comparison work should remain separate from sensitive migration data.

Merchandising teams should test whether the feature supports real buying decisions. Compare products with missing attributes, multiple variants, sale prices and discontinued stock. An empty cell can either be hidden, labelled “not specified” or treated as a data-quality issue; leaving inconsistent blank space across the grid makes the storefront appear unreliable.

Rollout and Measure the New Experience

A staged release is safer than switching every catalogue category at once. Start with a well-structured range such as laptops, appliances, furniture or commercial equipment. Import the mapped attributes, enable comparison for that category and ask staff to use the feature on desktop and mobile before expanding it to the wider store.

The migration checklist should include redirects, customer account handling, order history, inventory synchronisation and payment configuration. Guidance on platform migration can help retailers assess the role of a Counterpoint partner, especially where Magento must exchange stock and order data with existing retail systems.

Track interactions after launch. Useful measures include comparison starts, products added to comparison, visits from comparison pages to product pages, add-to-cart rates and completed orders. Segment the results by device, category and location so a retailer can see whether shoppers in Melbourne behave differently from customers browsing from regional New South Wales.

A short comparison tool should be judged against business needs rather than visual similarity alone. Magento’s flexible catalogue model can support richer specifications, while a reliable integration keeps availability aligned with stores and warehouses. The following distinction helps define the migration scope:

A careful implementation therefore begins with the customer journey, translates the old comparison behaviour into structured Magento attributes, and validates every connection to stock, tax and fulfilment. For an Australian retailer, the practical standard is simple: the comparison screen must make products easier to choose while showing accurate GST-inclusive pricing, local availability and delivery information.