We have been analyzing the NCR Retail Online (NRO) business and our NCR Industry Solutions Board, an internal team that helps set strategy, has decided to set the NRO product to End of Life on March 31, 2018 . The CPOnline Product was also recently announced with an end of life date of September 30th, 2017 . The End of Life terms indicate that all current customers will need to be transitioned off their respective product and the servers turned off by 9/30/17 (CPO) & 3/31/18 (NRO) . Your NCR Counterpoint business partner has been notified of this decision in advance and has started taking steps to help you transition your eCommerce solution.

Next Steps

As of today, we are encouraging all customers to reach out to your current NCR Counterpoint Partner to begin the transition to a new eCommerce platform. Your partner will be your best resource in planning and transitioning to a new eCommerce solution.

NCR has worked with several partners to create options for your new eCommerce solution. Please refer to the below chart for information about these options. Your partner can provide you with further documentation about these solutions to assist you with the decision process. You can also view a list of FAQ’s about moving from NRO to one of the below options by clicking here .

We will be discussing this transition directly with the users that attend our Synergy User Conference at the end of June. We will be offering a presentation on eCommerce and we will have representatives at the exhibit booth to handle your questions. In the meantime, please reach out to your partner to help determine your next steps.

We appreciate your business and look forward to taking this next, innovative step together.

Recommended eCommerce Solutions

Solution Cost Platform Additional Notes
Commerce5
  • Upfront: Starts at $2500**
  • Monthly: Starts at $495.00 plus hosting
Magento Most tightly integrated with Counterpoint and offers the most advanced features
CP Magento
  • Upfront: Starts at $2,500**
  • Monthly: Starts at $200.00 including hosting
Magento Integrated with Counterpoint and offers features similar to NRO
CP Shop
  • Upfront: Starts at $999**
  • Monthly: Starts at $125.00 plus hosting
Woo Commerce Catalog, Inventory, and Orders are integrated with Counterpoint

Setting Up Price Match Logic in WooCommerce After NCR

NCR Retail Online was built to connect ecommerce sales with retail inventory, point-of-sale data and operational workflows. Since that product has been discontinued, Australian retailers moving to WooCommerce need to recreate important pricing behaviour rather than simply import products and customer records.

A price match guarantee is a good example. The policy may promise to meet a competitor’s advertised price, but the store still needs safeguards for stock status, delivery fees, GST, product variants, customer eligibility and approval history. A custom WooCommerce hook can provide that control without permanently overwriting the catalogue price.

Define the Australian Price Match Policy

Start by converting the written guarantee into explicit rules. Decide whether the competitor must be an Australian business, whether the item must be in stock, and whether the comparison includes shipping. A customer in Sydney may compare your price with a Melbourne retailer, but the delivered total to their postcode can differ substantially.

Clarify the treatment of GST, membership discounts, clearance products, marketplace listings and coupon codes. For example, you might match an identical product sold by an authorised Australian retailer, provided the competitor price is publicly available and the item is ready for immediate dispatch. Exclude international sites, auction listings and temporary loyalty offers unless your commercial policy says otherwise.

The final decision should be stored as an approval record rather than calculated from an unchecked form submission. Useful fields include the WooCommerce customer ID, product ID, competitor URL, submitted price, approved price, staff member, expiry time and reason for rejection.

Separate Catalogue Prices From Approved Matches

Do not alter the regular WooCommerce product price when one customer receives a match. The catalogue price supports reporting, promotions, tax calculations and future orders. A temporary adjustment should belong to the cart item or customer session.

A practical flow is to let a shopper submit a product ID and competitor amount through a secure form. Your server validates the request, sends it to a staff review queue, and stores an approved amount against the customer or cart. The cart calculation hook then reads that approval and applies it only to the matching line item.

Retailers migrating from NCR systems may also need a bridge between product, stock and order records. Guidance on API connections can help when Counterpoint remains the source of truth for inventory while WooCommerce handles the online transaction.

Add a Custom WooCommerce Hook

A dedicated filter gives the price-match feature a clear boundary. The following example uses a custom filter to return an approved unit price, then applies it during cart totals. In production, the approval lookup should use a database table or order-related service rather than an unstructured session value.

add_filter(
    'my_store_price_match_price',
    function ( $approved_price, $product_id, $customer_id ) {
        $match = my_get_active_price_match( $product_id, $customer_id );

        if ( ! $match || $match['expires_at'] < current_time( 'timestamp' ) ) {
            return $approved_price;
        }

        return max( 0, (float) $match['approved_price'] );
    },
    10,
    3
);

add_action( 'woocommerce_before_calculate_totals', function ( $cart ) {
    if ( is_admin() && ! defined( 'DOING_AJAX' ) ) {
        return;
    }

    $customer_id = get_current_user_id();

    foreach ( $cart->get_cart() as $cart_item ) {
        $product    = $cart_item['data'];
        $product_id = $product->get_id();
        $price      = apply_filters(
            'my_store_price_match_price',
            (float) $product->get_price(),
            $product_id,
            $customer_id
        );

        if ( $price < $product->get_price() ) {
            $product->set_price( $price );
        }
    }
}, 20 );

The my_get_active_price_match() function should return only an approved, unexpired record. It should also check the product variation ID where relevant, because a 500 ml version and a 1 litre version must not share a price approval accidentally.

Validate Requests Before Approval

A front-end price match form is only a request, not proof. Use a WordPress nonce, sanitise the competitor URL, validate the numeric amount and require a logged-in customer if your policy needs account-level tracking. Never trust a hidden field containing the product price or customer ID.

The review process should compare like with like. Check brand, model, colour, size, warranty, included accessories and availability. For Australian operations, include delivery to the customer’s postcode when freight makes the competitor’s advertised amount misleading. A lower shelf price in Brisbane may not be a lower delivered price to Perth.

Use a short approval lifetime, such as 24 or 48 hours, and recheck stock before payment. If the competitor page disappears, changes price or becomes unavailable, the approval should be marked invalid rather than silently continuing at checkout.

Recreate Operational Automation

A matched price should trigger the same operational events as a normal WooCommerce order. Inventory must be reduced through the correct system, tax must be calculated consistently, and the order should clearly show the original price, approved price and reason for the adjustment.

When stock is managed in Counterpoint or another retail platform, decide whether the price-match approval is sent back through an API, recorded only in WooCommerce, or synchronised through a partner integration. This prevents staff in a Canberra store from seeing a different availability position from the online team in Melbourne.

Automated emails can notify a supervisor when a request needs review, alert the customer when it is accepted, and expire pending requests after a defined period. Workflows previously handled by the discontinued platform can be recreated with scheduled actions, webhooks or an integration service; examples of automated workflows provide a useful migration reference.

Control Staff Access And Customer Data

Only authorised team members should approve or amend a price match. Create a capability such as manage_price_matches, then assign it to approved managers rather than giving every shop-floor user full administrator access. This is especially important for businesses operating across Sydney, Adelaide and regional stores.

Keep an audit trail for every decision. Record who approved the request, what evidence was checked, which amount was accepted and whether the approval was later revoked. Do not store unnecessary payment details or retain competitor screenshots indefinitely if they contain personal information.

A role-based model is also helpful when moving away from NCR Retail Online. Advice on role-based access can be adapted to WooCommerce by mapping duties to WordPress capabilities and restricting access to customer and pricing data.

Test The Cart And Checkout Behaviour

Test the feature with simple and difficult cases. The cart must preserve the approved price when quantities change, but it should not allow a shopper to duplicate an approval across unrelated products. Variable products, bundles, subscriptions and backorders each need a deliberate decision.

Use a staging site with Australian tax settings, AUD currency and realistic delivery zones. Check that the displayed amount, GST component, order email, invoice and accounting export all agree. If the shop accepts Afterpay or other payment methods, verify that the adjusted total reaches the gateway correctly.

A short testing checklist helps the team cover the important paths:

  • Approved match on a simple product
  • Rejected request with an invalid competitor
  • Expired approval at checkout
  • Variation with a separate approved price

Visual review matters as well as code review. Check the request form on a mobile device, since many shoppers compare prices while visiting a physical shop, and use visual testing examples when reviewing layout consistency across screen sizes.

Launch With A Controlled Migration

Before enabling the feature, import only active price-match records that have a clear owner and expiry date. Old NCR data may contain historical adjustments that should remain available for reporting but must not continue discounting current carts.

Run a pilot with a small group of staff and a limited product category. Compare WooCommerce orders with the retail system, confirm stock deductions, and review approval logs after each test order. Train staff to explain the policy consistently, including whether delivery fees, GST and loyalty discounts are included.

Once the pilot is stable, enable the hook during a quiet trading period and monitor failed calculations, rejected requests and unusual margin changes for the first week. The immediate next step is to create the my_get_active_price_match() lookup and test it on one variable product in a WooCommerce staging environment.

After you have completed your move to a new eCommerce platform, don’t forget to submit the Store Closure Request form to close your NRO site and cancel your billing subscription.