Keeping B2B Pricing Tiers Intact After NCR Retail Online

Moving away from NCR Retail Online is more than a change of storefront software. For a business selling to retailers, trade customers, schools, hospitality groups or resellers, the real risk sits underneath the catalogue: customer-specific prices, volume breaks, contract rates and approval rules can be lost during the move.

The product has been discontinued, so many Australian merchants are transitioning to platforms such as Magento or WooCommerce with help from NCR Counterpoint partners. That transition can preserve commercial logic, but only when pricing data is treated as a core business asset rather than a minor catalogue field.

The goal is to keep each buyer seeing the right price at the right time. A wholesale customer in Melbourne may have a different rate from a small trade account in Newcastle, while a national customer may require a negotiated price list, GST-compliant invoices and delivery charges that vary by postcode.

A successful migration therefore needs a pricing map, a clean customer record and a controlled testing process. It should also account for Australian conventions, including Australian dollars, GST-inclusive or ex-GST display choices, ABNs and the seasonal pressure around end of financial year.

Identify Every Pricing Rule Before Migration

Start by documenting how prices are currently calculated in NCR Retail Online and any connected NCR Counterpoint system. Capture standard retail prices, wholesale price books, customer group discounts, quantity breaks, promotional overrides, contract pricing and manually negotiated rates. A spreadsheet can work well at this stage, provided each rule has an owner and a clear description.

Do not rely on labels such as “Trade” or “Wholesale” without checking what they actually do. One group might receive 15 per cent off the standard price, while another may have fixed prices for selected products. Some customers could be assigned to a price level through their account record, while others may receive a discount code or sales-representative adjustment.

Review old catalogue references as part of this audit, including the legacy product pages, but use live system exports as the source of truth. The aim is to separate useful commercial data from outdated pages, discontinued products and pricing rules that have not been used for years.

Build A Pricing Crosswalk

Before importing anything into Magento, WooCommerce or another replacement, create a crosswalk between the old pricing structure and the new platform’s fields. For each tier, record its name, eligibility conditions, currency, tax treatment, product scope, minimum order quantity and start or end date. This prevents a vague “wholesale customer” label from carrying too much responsibility.

A useful crosswalk might map an NCR price level to a customer group, role, shared catalogue or pricing extension. It should also identify exceptions. For example, a buyer may receive a contract price for fasteners but the standard trade rate for safety equipment. If the new system cannot represent that distinction natively, decide whether to use a plug-in, a custom rule or a controlled manual process.

Pay special attention to product identifiers. Supplier SKUs, internal SKUs and barcodes may not match, especially where products have been renamed or bundled. A wrong SKU match can apply the correct discount to the wrong item, creating a pricing error that may remain hidden until a customer places a large order.

Protect Customer Eligibility

Customer groups should be migrated with the same care as price lists. Export account numbers, business names, contact details, assigned tier, payment terms, sales representative and any approval status. In Australia, the ABN is often a practical matching field for business accounts, but it should be validated rather than blindly copied because trusts, branches and trading names can complicate records.

Keep retail shoppers separate from business buyers. A public coupon or guest checkout discount should never accidentally stack with a protected wholesale rate. Likewise, a buyer who has several contacts should normally share one business pricing profile, while individual users retain their own login, permissions and order history.

Check how the replacement platform handles tax display. Australian customers may expect prices to be shown inclusive of 10 per cent GST, while internal trade negotiations may be conducted ex GST. Configure display, invoices and exports consistently, and test that a customer’s GST status does not alter the agreed product price unless that behaviour is explicitly required.

Transfer Data With Controlled Mappings

The migration itself should be staged rather than treated as a single upload. Export a representative sample containing retail customers, several B2B tiers, products with quantity discounts and accounts with negotiated rates. Load that sample into a test environment, then compare the displayed prices against approved examples before transferring the full catalogue.

Migration utilities can reduce repetitive work, particularly when moving customer records, products and order history between systems. Guidance on migration plugins can help shape the technical approach, but a plug-in should not be trusted to interpret unusual pricing logic without review. Automated transfer handles volume; business owners still need to validate meaning.

Preserve the original customer and product identifiers in a reference field where possible. This makes it easier to trace a disputed invoice back to the old record and gives support staff a reliable way to investigate duplicate accounts, missing variants or an incorrectly assigned price book.

Test The Buying Experience

Pricing tests should cover the whole buying journey, not just a back-office export. Log in as a retail customer, a standard trade customer, a high-volume account and a customer with a negotiated contract. Add products individually and in quantities that cross each discount threshold. Confirm the cart, checkout, tax calculation, invoice and order confirmation all show the expected result.

Test stacking behaviour carefully. A 10 per cent trade discount, a seasonal promotion and a free-shipping offer may be intended to combine, or they may be mutually exclusive. Configure those rules deliberately and document the result. Test out-of-stock products, substitutes, bundled items and variable products as well, because pricing extensions often behave differently across product types.

Run location-based checks relevant to Australia. Use an account in Sydney, one in Melbourne and one in a regional area such as Ballarat or Toowoomba to verify that freight rules do not alter the product tier unexpectedly. Confirm that the displayed currency is AUD and that invoice dates, GST amounts and shipping charges remain correct across the store and the accounting workflow.

Put Governance Around Future Changes

A migration can preserve today’s tiers and still fail later if staff change prices without controls. Establish an approval process for new price books, customer-group changes, discount codes and contract overrides. Record who approved each change, when it begins, which products it covers and when it should expire.

Set alerts for unusual outcomes, such as a sudden increase in orders at the lowest price, a customer account moving between tiers or a product selling below its intended margin. Review pricing reports after launch and compare ecommerce orders with sales-team quotes and Counterpoint records. During the first few weeks, daily checks are sensible; after the system stabilises, a weekly or monthly review may be enough.

Make the rules understandable to customer service and account managers. A short internal guide should explain which group receives each rate, how to request a pricing change and what evidence is needed for a business account. This matters when a customer calls from Perth before the warehouse opens in the east, or when a sales representative needs to resolve an urgent quote during the EOFY rush.

Keep a read-only copy of the old exports, mapping documents and test results. Do not leave the discontinued platform as the only place where pricing history can be found, but retain enough evidence to resolve disputes and demonstrate how a current rate was established.

The strongest transition treats B2B pricing as a controlled ruleset: documented before export, mapped to the new platform, tested with realistic accounts and monitored after launch. That approach protects negotiated margins while giving customers a consistent experience across online orders, sales-assisted purchases and invoices.

Begin with one approved export containing every active customer tier and a sample of products, then have the finance and sales owners sign off the crosswalk before any full migration is run.