How to Transfer NCR’s Shopping Cart Rules (Buy X Get Y) to a Plugin

NCR Retail Online connected ecommerce stores with NCR Counterpoint inventory and business management systems, letting prices, stock and orders flow through one retail operation. The product has been discontinued, so retailers moving to Magento or WooCommerce through NCR Counterpoint partners must rebuild significant selling logic. A Buy X Get Y offer cannot be transferred safely by copying its name.

The detail that matters is the customer result. “Buy two, get one free” might cover the cheapest eligible item, a nominated product or every match after a threshold. Other rules can exclude sale products, gift cards, staff accounts or coupon stacking. Each variation needs an explicit definition covering eligibility, calculation order, taxes, refunds and stock before it becomes plugin logic.

WooCommerce provides a practical target through WordPress hooks, custom code and order metadata. Magento can produce the same outcomes through a module or supported cart rules, although its extension model differs. NCR Counterpoint partners can assist with either route, but the retailer still owns the promotion decisions, test data and acceptance criteria.

Australian conditions should shape the specification. Prices are normally displayed in Australian dollars with GST included, and fulfilment can vary between a Sydney warehouse, a Melbourne collection point and a Brisbane online store. Australian Consumer Law requires offer terms to be clear, while GST on low-value imported goods can affect landed costs under Australia’s customs regime. These factors belong in test cases.

Translate legacy behaviour into a rule inventory

Start with an inventory of every active promotion, its owner, dates, source system and customer-facing terms. Include one worked basket with exact products and totals. The comparison below converts common legacy behaviour into a migration decision rather than assuming every “free” offer means a free product.

Also capture coupons, sale-price exclusions, customer groups, maximum uses, loyalty points and shipping thresholds. Keep the NCR rule ID, plain-English terms and an approved calculation example beside the target logic. This audit trail prevents a developer from interpreting “free” as “100% off” when a shipping or quantity condition applies.

Identify where each rule lives

Do not assume the entire promotion resides in NCR Retail Online. A campaign may combine a storefront rule, coupon record, category constraint and price override maintained through Counterpoint. Ask staff to demonstrate the live offer in a test cart, then trace every input that changes the result. This reveals what must move, what can remain and what should be retired.

NCR’s API-first migration guide describes the wider move away from a tightly coupled platform. For rule transfers, an API-first design separates catalogue and inventory data from calculation logic and clarifies which endpoint owns price, stock, order status and eligibility. A plugin can consume stable inputs without editing Counterpoint records directly.

Create a mapping from NCR item number, product variant, barcode, category, regular price and tax code to the destination catalogue ID. Label each field as master, calculated or migrated configuration. For inventory-sensitive rewards, document whether stock is reserved only after payment or promised while available, and record who can change the field after launch.

Design the plugin around deterministic rules

A reliable plugin separates eligibility, reward selection and discount allocation. It first gathers cart lines matching quantity, category, price, customer and date conditions. It then selects the reward under a defined rule, such as the lowest-priced eligible line, and allocates the value so tax, refunds and totals stay consistent.

Calculation order must be deliberate. Decide whether coupons change the price used to find the cheapest item, whether thresholds are checked before or after discounts, and whether an automatic reward stacks with another offer. Prevent negative line totals, define the rounding point and save the rule ID with inputs in order metadata so support staff can explain a discount.

Documentation helps developers reproduce behaviour. A screen-recorded timelapse of the legacy cart journey can show how quantity, eligibility and totals change before checkout. Use the recordings with written examples to create automated-test fixtures, producing a specification based on observed outcomes rather than assumptions about the old engine.

Connect products, stock and pricing

Catalogue migration is the first dependency. Resolve duplicate variants, renamed categories and products eligible under NCR but absent from the new store. Reconcile stock rules, including whether a free reward comes from the same store, fulfilment centre or online warehouse. This matters when a Sydney customer can collect locally but a Melbourne order is shipped nationally.

Pricing needs equal care because Australian checkout totals normally include GST on taxable goods. Use the platform’s line subtotal and tax treatment instead of calculating a second gross amount. Compare pre-discount subtotal, taxable discount, GST, shipping and final AUD total with approved examples. Refunds should return the allocated discount with the relevant product, not an untraceable store credit.

In WooCommerce, use a custom plugin or focused extension so pricing remains independent of the active theme. In Magento, implement matching behaviour in a module and use rule priorities where the native engine supports them. Neither should become the product database: read catalogue and stock from the commerce platform, then write only the promotion decision and supporting metadata.

Test against realistic Australian scenarios

Turn the inventory into a test matrix containing normal purchases, threshold boundaries, mixed categories, sale items, cancelled orders, partial refunds and out-of-stock rewards. Run each basket in a sanitised staging environment and compare every line, discount and total with the signed-off NCR example. Add mobile purchases, multiple Australian postcodes and collection from different city locations.

Test promotional claims as well as arithmetic. Under the Australian Consumer Law, an offer described as “free” should not conceal material conditions such as a minimum spend or shipping charge. Show qualifying products, quantities and limits before checkout. Where rewards alter GST or costs associated with low-value imports, present the final payable amount transparently.

Include security and performance. Run the calculation against peak event traffic and two customers competing for the last reward. Use idempotent order hooks so retries cannot apply a discount twice, keep card data out of custom logs and confirm that fees and metadata do not break recurring payments, tax reporting, refunds or PCI DSS controls.

Migrate, communicate and monitor

Roll out in stages, beginning with low-risk promotions. Compare calculated discounts and order outcomes across old and new channels, then expand by category and customer group. Keep a feature flag that can disable the new rule logic without disabling checkout. Publish an ownership schedule for changes after NCR Retail Online is no longer available.

Customer communication should begin before cutover. The customer notification planning resource explains how to cover channel changes, order references, refunds and support contacts. Contact customers who have consented to ecommerce updates, respect their channel preferences and avoid promising repricing for existing orders unless the business has decided otherwise.

After launch, monitor rule applications, average reward value, rejected eligibility cases, support contacts and stock discrepancies between Counterpoint and ecommerce. Review unexpected outcomes with merchandising, finance and store operations. The immediate next step is to appoint a rule owner and complete a one-page inventory of every active Buy X Get Y offer, including one approved basket example that the first plugin test must reproduce.