Setting Up Tiered Pricing in WooCommerce After NCR

For decades, NCR Retail Online handled complex price ladders for Australian retailers — customer-specific brackets, trade-tier breakpoints, and GST-aware calculations that synced across the till. When NCR announced the product was being discontinued, store owners in Sydney, Melbourne, and regional centres were told to move their storefronts to platforms like WooCommerce through NCR Counterpoint partners. The mechanics of migration are straightforward at the surface, but rebuilding the old price rules so that wholesale buyers in Brisbane or Adelaide still see familiar figures requires deliberate work.

Tiered pricing in WooCommerce is achievable through configuration rather than a one-click switch. The moment a store wants a hospitality supplier in Perth to see sixty-day-account terms or a trade buyer in Geelong to receive a flat percentage off past a set cart value, custom logic is needed. Getting this right early saves customer-service headaches once the new site goes live.

Reading the old NCR pricing structure before rebuilding it

Before any plugin is installed, the existing NCR price file should be pulled into a spreadsheet and audited. Most Australian retailers using the old system had three or four price tiers — a "RRP" public tier, a "Trade" tier for registered resellers, a "VIP" tier for large-volume accounts, and sometimes a separate "Staff" tier with restricted access. Each tier carried its own minimum order thresholds, and most stores applied GST on top of the discount price rather than embedding it, which differs from how some New Zealand-based NCR deployments worked.

The audit matters because not every NCR pricing layer translates directly to WooCommerce. Some stores used percentage modifiers rather than fixed prices, others used quantity breaks at the SKU level, and a small number used time-windowed promotions that aged out. A clear inventory of which behaviours must carry over — and which can be simplified — keeps the rebuild from stretching into a six-month project. Stores concerned about preserving historical transactions often export the full order history before the platform is retired; the practical answer to where sales records end up is usually a one-time CSV plus a clear retention policy through the new system.

Picking the right pricing extension for Australian stores

WooCommerce itself does not have built-in tiered pricing, so a plugin is essential. The Australian market has settled on a handful of reliable options, and the choice usually comes down to whether the old NCR rules were customer-based, quantity-based, or a mix of both. Wholesale Suite and the Dynamic Pricing extension by WooCommerce.com each handle different models well, with the right pick depending on the legacy configuration.

For stores that previously used NCR's customer-group price lists, the role-based approach offered by Wholesale Suite mirrors the old system most faithfully. A buyer tagged as "Trade Queensland" can be assigned a price level that follows them through online orders and pickups alike. The plugin integrates cleanly with WooCommerce Subscriptions, useful for stores selling ongoing consumables to cafés and restaurants in cities like Adelaide. Quantity-based discounts call for a different tool — the Dynamic Pricing module handles "buy five, save ten percent" style rules and stacks percentage tiers on top of fixed breakpoint savings, with each old NCR rule needing a one-to-one map into the new extension.

Rebuilding customer-specific price lists from legacy data

Once the plugin is chosen, the customer master file from NCR becomes the foundation. Exporting customers in CSV — usually available through the NCR Counterpoint integration — gives a clean source of names, tier assignments, and historical purchase volumes. Each customer maps to a WooCommerce role, and each role maps to a price tier.

Trade customers in Australia expect tax invoices with separate GST line items, so discounted prices must be entered GST-exclusive. A common mistake during migration is importing the NCR "sell price" as though it were GST-inclusive, which double-dips the ten percent tax once WooCommerce Tax settings kick in. Running a sample order as a test trade customer confirms whether the figures reconcile against the old printouts. Payment gateways add another wrinkle: eWAY, Afterpay, and Zip Pay each behave slightly differently with role-based discounts, and some need a minimum cart value before deferred payment appears. Trade-account terms are usually replicated with the Deposits for WooCommerce plugin, with the balance invoice issued once the goods ship.

Handling GST and Australian compliance considerations

GST is the line item most often misconfigured during migration. NCR's old pricing engine generally applied tax after discounts, which matches Australian Taxation Office guidance. WooCommerce can be set the same way, but it must be confirmed within the Tax tab of every product — plugin-level discount settings will not override a product left in the older "inclusive" mode.

B2B trade customers providing an ABN can have the Australian Business Number captured at checkout through a plugin like Australian Postcode and ABN Validation, which then hides the GST line item from the cart. This matches the experience buyers in Brisbane, Perth, and the NSW Central Coast were accustomed to under NCR, and removes friction when a tax exemption is granted or revoked mid-account. Australia Post shipping zones also differ from WooCommerce's default country-level logic, so the pricing setup should be tested with regional postcodes such as 4670 in Bundaberg or 7250 in Launceston to confirm freight costs still apply correctly when a discount triggers free-shipping thresholds.

Testing the configuration before going live

Testing is where most migrations go wrong. A staged WooCommerce environment with a copy of the production database lets a store owner order as every customer tier and confirm that the cart total matches the expected NCR figure within rounding tolerance. Many Australian retailers forget that NCR stored prices to four decimal places, while WooCommerce works to two — a small difference that can accumulate across large invoices and trigger disputes with trade customers.

A useful test rig is a spreadsheet listing the top fifty SKUs, the four pricing tiers, and the expected totals. Run each combination through the test store and tick off the matches. Any row that fails usually points to a missing customer role assignment, an old price still sitting in the meta table, or a caching plugin serving a stale product page to logged-in users.

Rolling out and supporting customers through the change

Once the tests pass, the rollout benefits from a short soft-launch window where the most engaged customers — typically large account holders in Sydney or Melbourne — are given early access. Their feedback tends to surface edge cases that internal testing misses, particularly around mixed-cart orders containing both retail and trade items.

Support documentation should sit on a help page explaining, in plain English, where the new tiered prices live and how trade buyers can request a role re-assignment if it carries across incorrectly. Afterpay and Zip Pay customers expect a frictionless checkout, so any extra login or verification step needs to be clearly signposted.

Practical recommendations for the migration

• Rebuild pricing rules from an audited NCR export rather than memory, so trade customers stay in sync with the old platform
• Configure discounts as GST-exclusive and confirm tax settings per product for accurate Australian tax invoices
• Use role-based plugins for customer-group ladders and Dynamic Pricing for quantity breaks, then map each old rule one-to-one
• Validate freight calculations against regional postcodes such as 4670 and 7250, not only capital-city addresses
• Run a soft launch with top account holders across NSW, Victoria, and Queensland before full cut-over

A reasonable budget for the rebuild depends on the depth of the old NCR setup, but the migration cost is rarely as high as feared once the audit is done well. The real expense hides in the testing phase, where every tier needs validation against the legacy printout.

After a few weeks of live trading, the new WooCommerce store should feel familiar enough that long-time trade buyers in regional Western Australia or Tasmania barely notice the change. A successful rebuild shows up as a quiet inbox — no angry emails about wrong prices, no GST reconciliation queries, no frantic calls from resellers asking why their discount disappeared. When the pricing engine hums along without intervention, the migration has done its job and the merchant can spend less time holding the platform together and more time looking after the customers it was built to serve.