Migrating Discount Rules and Coupons from NCR Retail Online

When NCR Retail Online was discontinued, retailers had to move their online operations to another ecommerce platform, commonly Magento or WooCommerce through NCR Counterpoint partners. Discount rules and coupon codes deserve special attention during that transition because they often contain hidden conditions, date limits, customer groups, product exclusions and checkout behaviours that are not transferred automatically.

A successful migration preserves the commercial intent of each promotion rather than simply copying its visible code. Australian retailers may need to account for GST-inclusive pricing, Australian dollar rounding, state-based delivery charges, EOFY promotions and different trading patterns between Sydney, Melbourne, Brisbane and regional areas. A structured export and testing process reduces the risk of customers receiving an unintended discount or finding that a valid voucher fails at checkout.

Audit Existing Promotions Before Exporting

Begin by creating a complete inventory of active, scheduled and expired promotions in NCR Retail Online. Include automatic discounts, manually entered coupon codes, buy-one-get-one offers, quantity breaks, customer-specific pricing and free-shipping campaigns. Expired rules may still be useful as historical records, but they should be clearly separated from promotions that need to operate on the replacement store.

Record the business purpose and exact conditions for every rule. A useful migration sheet includes the promotion name, code, discount type, amount, eligible products, excluded products, minimum order value, customer segment, usage limit, start date, end date and whether the discount can be combined with another offer. Also note whether the rule affects the entire cart, selected categories, individual SKUs, shipping or payment methods.

Pay particular attention to catalogue changes. A product may have had one SKU in the former store and a different SKU in Magento or WooCommerce. Bundles, variations and discontinued products can cause a rule to target the wrong items after import. Match promotions against the new catalogue identifiers rather than relying only on product names.

Australian retailers should also check whether prices were displayed and stored with GST included. A “10% off orders over $100” rule can produce unexpected results if the threshold is evaluated against an ex-GST subtotal in one system and a GST-inclusive subtotal in another. Document the intended customer-facing result in Australian dollars before rebuilding the promotion.

Rebuild Rules According To Their Commercial Logic

Magento and WooCommerce use different models for promotional pricing. Magento generally separates catalogue price rules, cart price rules and coupon conditions, with detailed controls for customer groups, websites, product attributes and rule priority. WooCommerce relies on core coupon settings and may need an extension for advanced conditions, role-based discounts, quantity breaks or automatic promotions.

Translate each NCR Retail Online rule into its functional equivalent instead of attempting a direct field-by-field conversion. For example, a product-level markdown should usually become a catalogue rule, while a code requiring a minimum spend belongs in cart or coupon settings. A free-shipping offer may need its own shipping-zone configuration as well as a coupon condition.

Some rules will need clarification before they can be recreated. “Spend $150 and receive $20 off” might mean merchandise subtotal, subtotal after other discounts, or the final amount before shipping and tax. “Buy two, get one free” may apply to identical products, selected variants or any three items in a category. These distinctions should be written down and approved internally before the new configuration is published.

The successful switch to WooCommerce illustrates why operational details matter alongside platform selection. Coupon logic must fit fulfilment, inventory and customer-service processes, especially when a promotion is used online but stock is also managed through a retail or Counterpoint environment.

Compare Platform Behaviour Before Choosing A Build

A migration decision should consider how each platform handles promotion depth, administration and integration. The right choice depends on the complexity of the retailer’s pricing model, the skills of the implementation team and the required connection to point-of-sale and inventory systems.

Magento can be appropriate for a retailer with multiple storefronts, sophisticated customer groups or frequent conditional campaigns. It also provides more granular rule priorities, which helps when several discounts could apply to the same cart. The trade-off is greater configuration and testing effort.

WooCommerce may be more practical for a smaller Australian retailer running a focused catalogue and a manageable set of voucher campaigns. Its core coupon features cover fixed-cart, fixed-product and percentage discounts, but advanced combinations may depend on extensions. Each extension introduces another update, compatibility and security consideration.

Platform behaviour should be tested with real examples rather than judged from feature lists. A promotion that looks equivalent in the admin interface may calculate differently when products have sale prices, when tax is included, or when a customer applies two codes. This is particularly important around Boxing Day and Click Frenzy, when a checkout error can affect a high volume of orders in a short period.

Test Coupons Across Checkout And Fulfilment

Build a staging test matrix covering ordinary, boundary and invalid scenarios. Test the minimum spend exactly, one cent below it and one cent above it. Check excluded products, sale items, mixed carts, guest customers, logged-in wholesale customers, multiple quantities and expired codes. Confirm that the discount appears correctly in the cart, checkout, order confirmation, invoice and refund workflow.

Coupon security also needs review. Codes should not be guessable, reusable beyond their intended limit or valid on an incorrect storefront. Set usage limits per coupon and per customer where appropriate. Confirm that a code cannot be applied after its end date because of time-zone differences between the platform server, the retailer’s Australian business location and the customer’s device.

Shipping and tax tests should reflect local trading conditions. A retailer sending parcels from Melbourne to Perth may use different shipping zones and thresholds from one shipping within metropolitan Sydney. Test free delivery against residential and regional postcodes, click-and-collect orders, split shipments and shipping fees added by a fulfilment connector. Verify that GST is calculated on the discounted taxable amount according to the configured tax settings.

If the former operation relied on scheduled or batch-based processing, the migration should include an operational test rather than only a checkout test. The guide on batch order processing is relevant when orders, discounts or fulfilment updates are handled in groups. A promotion may appear correct at checkout yet fail when orders are imported into inventory, accounting or warehouse workflows.

Protect Coupon Data And Customer Trust

Coupon migration involves more than copying codes. Export files can contain customer identifiers, usage history and internal campaign notes, so access should be restricted and temporary files should be stored securely. Do not transfer unnecessary personal data into the new platform merely because it appears beside a coupon record.

Retain a read-only archive of the original rules, including screenshots or exported reports where possible. This supports customer-service investigations when someone says a voucher was valid under the former store. It also gives the finance team evidence for reconciling promotional costs, refunds and credit notes after launch.

Review discount abuse controls before opening the new store. Limit one-use codes, prevent unauthorised stacking and monitor unusually high redemption rates. A public campaign promoted through an Australian email list may spread quickly beyond its intended audience, while a staff or VIP code should be limited to the relevant customer group.

For retailers serving communities around Tweed Heads, local trading patterns can be different from those of a purely metropolitan store, particularly when customers shop across the Queensland–New South Wales border. The Tweed Heads casino case study provides a useful reminder that location, customer behaviour and operational context should inform ecommerce planning rather than being treated as generic settings.

Launch With A Controlled Promotion Schedule

Do not activate every historical coupon on launch day. Start with the promotions required for current trading, then add seasonal and legacy campaigns after their conditions have been checked. This prevents an old code from interacting with a new launch offer or a newly imported product range.

Assign an owner to each campaign and record the approved rule in a shared register. The register should show who approved the offer, when it begins and ends, which channels may advertise it, and how its performance will be measured. Include online, in-store and marketplace usage if the same offer is promoted across multiple channels.

Before launch, place test orders using a staff account, a guest account and a customer group account. Confirm inventory deductions, tax, fulfilment status, refund calculations and reporting. After launch, monitor the first orders manually and compare the order totals with the expected results from the staging test matrix.

The immediate next step is to export every active NCR Retail Online promotion into a rule register, classify each one as catalogue, cart, coupon, shipping or customer-specific, and test the highest-value campaign in a staging store before recreating the remainder.