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

Moving Loyalty Data From NCR Retail Online to New Tools

When NCR Retail Online was discontinued, merchants had to rethink more than storefront design, product catalogs, and checkout workflows. Customer loyalty programs are often among the most valuable assets in an ecommerce operation because they connect purchase history, customer identity, rewards, and retention campaigns. Moving those assets carefully is essential when transitioning to Magento, WooCommerce, or another platform supported by NCR Counterpoint partners. Learn more about Drinkware.html.

A loyalty migration is not simply a matter of exporting a spreadsheet and importing it somewhere else. Points balances, membership tiers, referral credits, coupon rules, consent records, and redemption history all need to remain accurate. A small data error can weaken customer trust, create financial exposure, or cause support problems immediately after launch.

The strongest approach combines data cleansing, platform mapping, customer communication, and a controlled launch. Retailers should treat the project as a business continuity exercise, preserving the customer experience while adapting the loyalty system to a third-party ecommerce and marketing stack.

Define The Loyalty Program Inventory

Begin by documenting every loyalty feature currently in use. This includes account registration, points earned per dollar, bonus events, birthday rewards, referral incentives, VIP levels, store credits, promotional coupons, and expiration policies. Record which rules are managed by the online store, the point-of-sale system, email software, or manual staff processes.

The inventory should also identify data fields connected to each member. Common fields include customer ID, email address, phone number, account status, points earned, points redeemed, pending points, adjusted points, tier level, reward history, and marketing consent. Separating active balances from historical transactions is important because the new platform may calculate the current balance differently from the legacy system.

Review edge cases before selecting a replacement tool. Look for duplicate accounts, household memberships, guest purchases, negative balances, expired points, refunded orders, and customers with multiple email addresses. A clean source file makes testing easier and reduces the risk of importing inaccurate rewards.

Choose A Compatible Replacement

Third-party loyalty tools differ in their integrations, pricing models, automation features, and data structures. Some are designed primarily for online stores, while others connect ecommerce with point-of-sale systems, customer relationship management platforms, email marketing, and mobile applications. The right choice depends on whether the retailer needs a digital-only program or a unified omnichannel experience.

Magento and WooCommerce can support a wide range of loyalty extensions and external services, but compatibility should be evaluated beyond the storefront. Confirm whether the tool can receive order events, handle refunds, exclude certain products, support multiple currencies, and synchronize customer changes in both directions. Retailers using NCR Counterpoint or another retail management system should verify how sales made in physical stores will contribute to the same member account.

Hosting and security also affect loyalty performance. A platform migration is a useful time to review infrastructure, backups, access controls, and payment-related responsibilities. The guidance in this hosting options guide can help frame that assessment, especially when customer accounts and reward data will be processed across several connected services.

Map And Validate Customer Data

Create a field-mapping document before any production import. Each legacy field should have a defined destination, transformation rule, or retirement decision. For example, an old membership number may become an external customer reference, while a tier code may need to be converted into a new platform’s named segment.

Points require special attention because systems may store them as integers, monetary values, or ledger transactions. Establish a single conversion rule and document how fractional points, pending points, expired points, and manually adjusted balances will be handled. If the new tool cannot reproduce the former calculation method, decide whether to preserve the balance exactly or provide an equivalent customer credit.

Run several test imports using anonymized or copied data. Compare record counts, balances, tier assignments, opt-in status, and account matching results. Test customers with no activity as well as customers with extensive purchase and redemption histories. A successful import should produce an exception report that identifies records needing manual review rather than silently discarding them.

Migration Area Existing Data To Review Validation Method Common Risk
Customer identity Email, phone, account ID, duplicate profiles Match records and review collisions One person receives multiple accounts
Points balance Earned, redeemed, pending, expired points Recalculate sample accounts Incorrect rewards liability
Membership tiers Tier name, thresholds, renewal dates Test boundary cases Customers move into the wrong tier
Reward catalog Coupons, credits, expiration dates Redeem test rewards Invalid or unusable offers
Consent records Email, SMS, privacy preferences Compare opt-in totals Unwanted communications
Purchase history Orders, refunds, qualifying products Check event synchronization Points earned on excluded transactions

Preserve Customer Trust During The Change

Customers should receive clear, timely communication about the loyalty transition. Explain whether their points, tier status, rewards, and account login will remain available. If customers must create new passwords or accept updated terms, provide simple instructions and avoid language that suggests their benefits have disappeared.

A short transition window can protect the program from conflicting changes. Consider freezing manual balance adjustments shortly before the final export, then record any transactions made during the freeze for later reconciliation. If a full freeze is impractical, capture a final delta file and apply it after the primary import has been verified.

Seasonal promotions deserve additional planning. Holiday campaigns, gift incentives, and limited-time bonuses can generate unusually high account activity, so they should be tested before launch. A merchandising area such as Christmas gifts may be useful for illustrating how reward exclusions, bonus points, and promotional messaging should work during a high-volume period.

Test Integrations And Daily Operations

A loyalty program depends on more than the customer account page. Test the complete customer journey from registration and purchase through fulfillment, return, refund, reward issuance, and redemption. Confirm that points are awarded at the intended event, whether that is order placement, payment capture, or shipment.

Check integrations with the point-of-sale system, email provider, analytics platform, customer service tools, and tax or fraud services. A customer who buys a product in a store may expect the purchase to appear online, while a returned ecommerce order should remove or reverse the associated points. These events need reliable identifiers and clear retry procedures when an integration fails.

Staff training is equally important. Store associates and support agents should know how to locate a migrated member, explain a balance, issue an approved adjustment, and escalate discrepancies. Create a concise operational runbook covering refunds, duplicate profiles, locked accounts, reward expiration, and privacy requests.

Protect Loyalty Data And Compliance

Loyalty records combine identity information with behavioral and transactional data, making access control essential. Limit administrative permissions according to job responsibilities, require multifactor authentication where available, and maintain logs for balance changes and reward issuance. Service accounts used for integrations should have only the permissions they need.

Review data retention and consent requirements before transferring records to a new provider. Marketing consent should not be inferred merely because a customer had an account or earned points. Preserve the original consent status, document the migration basis, and provide accessible ways for customers to update preferences or request data removal.

Security review should include the vendor’s breach response process, encryption practices, backup policy, subcontractors, and data residency where relevant. Loyalty promotions can also create financial risk, so monitor unusual redemptions, sudden balance changes, and repeated coupon use after launch.

Launch In Stages And Measure Results

A phased rollout can expose problems while the old process is still available for reference. Start with internal accounts or a small customer segment, then expand after confirming balances, communications, and redemption behavior. Keep a read-only export of the legacy program so staff can investigate historical questions without continuing to operate two active systems indefinitely.

Establish launch metrics that reveal both technical and commercial performance. Track migration success rate, duplicate-account rate, support contacts, reward redemption, points liability, email delivery, repeat purchase rate, and checkout conversion. Compare these results with a pre-migration period rather than judging the new tool by a single busy day.

Use the first several weeks to reconcile daily transaction totals and investigate exceptions. Schedule a formal review after the first promotional cycle, when customers have had enough time to earn and redeem rewards. This review should produce practical adjustments to program rules, customer messaging, staff procedures, and integration monitoring.

Practical Steps For A Controlled Transition

  • Create a complete export of customer, points, tier, reward, consent, and transaction data.
  • Select a loyalty provider with dependable ecommerce, point-of-sale, and marketing integrations.
  • Build field mappings and test balances with duplicate, inactive, refunded, and high-value accounts.
  • Communicate login, rewards, privacy, and expiration changes before the new program opens.
  • Monitor imports, redemptions, support cases, and suspicious activity throughout the first launch period.

A careful migration can turn the end of NCR Retail Online into an opportunity to modernize retention marketing and unify online and in-store experiences. Begin by auditing the current program, then involve your ecommerce developer, retail system partner, loyalty vendor, and customer support team in a shared migration plan. With tested data, transparent communication, and staged deployment, customers can keep the value they have earned while the business gains a more flexible foundation for future growth.

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.