Rebuilding NCR coupon stacking in WooCommerce or Magento

NCR Retail Online connected ecommerce storefronts with retail inventory and business management systems, helping merchants sell online while synchronising stock and operations. Its discontinuation created a second migration problem: retailers had to move catalogue, customer and order data while preserving the promotional rules customers expected. Coupon behaviour was easy to overlook until a migrated basket priced differently or a campaign attracted more discount traffic than planned.

Rebuilding NCR’s coupon stacking logic in WooCommerce or Magento starts with the discount decision process, not with copying coupon names. A robust rebuild separates eligibility, exclusivity, priority and calculation order, then proves each result against legacy baskets. For Australian merchants, that process must also account for AUD, GST-inclusive displays, state-based delivery zones and buy-now-pay-later payment flows.

Recover the legacy discount rules

Start with a coupon inventory rather than the old storefront. For each code, record whether it was entered or automatic, fixed-value or percentage, cart- or line-scoped, and restricted by products, categories, dates, minimum spend, customer group or shipping method. Include free-shipping effects and any maximum discount. Original thresholds matter because “$20 off” can apply to the cart, a line or the subtotal depending on where the rule was entered.

Next, reconstruct stacking relationships. Separate discounts may have been additive, mutually exclusive, restricted to one per group or selected by priority. A cart may also have applied the best available offer rather than every eligible code. Sample old baskets are essential: they reveal whether a fixed amount was deducted before or after a percentage, whether thresholds used pre- or post-discount spend, and how rounding was handled.

The NCR Retail Online pages can help identify the platform and the scope of data to gather, but they are not a substitute for historical configuration or transaction evidence. Pull exported coupons, products, prices, tax settings and representative orders from the merchant’s own records. If the original setup is unavailable, Counterpoint records and the retailer’s finance team become the best sources for reconstructing the intended calculations.

Design a platform-neutral rule model

Convert the coupon inventory into a structured rule that both platforms can understand. Each rule should include its identifier, discount type, value, scope, eligibility conditions, exclusions, start and end times, usage limits, stacking group, priority and calculation sequence. Keeping these fields independent from platform extensions makes later changes easier and prevents WooCommerce-specific settings from being mistaken for Magento requirements.

Map identifiers deliberately. A legacy SKU tied to Everyday 3 drinkware should become a WooCommerce product ID or Magento SKU, not a copied numeric label. Category rules need the same treatment. Store the old NCR reference alongside the new identifier so support staff can trace a rejected coupon back to its source rule.

In WooCommerce, model standard coupons with the native coupon object, then use a small plugin for legacy stacking policies, fixed-cart precedence and restricted discount groups. In Magento, express cart-level behaviour through cart price rules with coupon codes; catalogue price rules serve a different purpose and should not be treated as interchangeable. Before deploying either extension, confirm that it supports the target platform version, current PHP configuration and headless checkout integrations.

Implement deterministic stacking behaviour

Calculate every promotion on the server from the current cart. First test eligibility, including dates, customer groups, minimum spend, product restrictions and prior coupon usage. Then apply a documented order: percentage discounts, fixed line discounts, fixed cart discounts and shipping adjustments. This order must match the legacy result rather than a platform default, because changing it can alter both the discount and any GST calculation.

Work with the prices shoppers actually see. Australian stores commonly display prices inclusive of the 10% GST, so discounts should be calculated against the correct taxable base and rounded under the store’s established tax method. Record the gross discount, taxable discount and final payable amount separately. A code that was previously applied after tax must not become tax-exclusive simply because the new platform calculates carts differently.

Create a conflict matrix covering every combination that legacy coupons could encounter. Define whether a percentage coupon can accompany a fixed-value code, whether one code may be used per order, which code wins when several are eligible and whether a maximum discount caps the combined benefit. Enforce these rules through one calculation service or a tightly controlled plugin, and make repeated checkout requests idempotent so a retried payment cannot apply the same promotion twice.

Map products, customers and orders

Product eligibility often contains the most hidden assumptions. A legacy rule may have excluded sale items, particular manufacturers or an entire department. The dining and entertaining catalogue, for example, may have carried category-level or product-level coupon conditions that need explicit mappings. Generate a comparison report showing each legacy scope, its new counterpart and any products that could not be matched.

Preserve the relationship between coupons and customer groups. Migrate relevant customer identifiers, consent records and loyalty tiers, but do not assume that an old account number will remain unchanged. Where the transition is being managed through NCR Counterpoint partners, agree on who owns each rule and who authorises changes to discount limits. Retain the original code in the migration metadata even when the storefront displays a new campaign name.

Check for code collisions before importing. An existing WooCommerce or Magento coupon may already use the same text for a different offer. Decide whether to preserve the customer-facing code and change its internal rule, or create a new code with a dated retirement plan for the old one. Also confirm that cancelled orders, refunds and exchanges release or restore usage limits in the same way as the former system.

Test the migration against real baskets

Build a test corpus from historical NCR orders rather than relying only on successful promotional examples. Include single-code baskets, valid stacks, rejected combinations, threshold boundaries, sale items, shipping thresholds, expired offers and coupons previously used by the same customer. Add expected cart totals, discounts, tax, shipping charges and promotion messages for each case so differences can be measured automatically.

Compare outputs field by field across WooCommerce and Magento. A matching final total can still hide a difference in tax allocation, shipping treatment or discount attribution, so the comparison should also inspect the underlying totals. Test Australian delivery scenarios across postcodes serving Sydney, Melbourne, Brisbane and Perth, since state-based courier zones can affect free-shipping coupons even when the merchandise subtotal is unchanged.

Run the rebuilt rules in parallel with the old calculation where possible. Record every divergence, classify it as intentional or defective and assign a resolution before launch. If a campaign is promoted through a third-party destination such as the 99shoutbox site, verify the outbound link, displayed offer terms, code entry path and final basket total as part of the same test. The promotion must remain accurate after platform taxes, exclusions and stacking rules are applied.

Roll out safely across Australian stores

Begin with a limited release using internal test accounts and a small group of live orders. Monitor coupon application rates, rejection reasons, average discount depth, checkout abandonment and support contacts during the end-of-financial-year sales period. Customers may call a promotion a “voucher code” even when the legacy system labelled it a coupon, so staff need consistent explanations and access to the rule inventory. Buy-now-pay-later providers should also be included in checkout testing because the displayed discount must match the amount used to create the payment plan.

Review the results against the approved legacy examples, then enable the remaining traffic gradually with a reversible feature flag. Keep the old calculation and promotion data available during the initial observation period, and give Counterpoint partners a clear escalation path for discrepancies. Once the rollout is stable, archive unnecessary implementation notes but retain the coupon inventory, test corpus and mapping records for audit and future campaigns.

Export every legacy coupon into a shared inventory sheet today, with one owner assigned to each stacking relationship, exclusion and usage limit.