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 NCR customer fields to a modern registration form

NCR Retail Online connected ecommerce storefronts with retail inventory, order management and business systems. With the product discontinued, many Australian retailers are moving customer account data to replacement platforms such as Magento or WooCommerce, often with assistance from NCR Counterpoint partners. The registration form is a small part of that change, but it can determine whether customer records remain useful after migration.

Custom account fields may contain information beyond a name and email address: loyalty identifiers, store preferences, trade details, delivery instructions or consent records. Some fields will still be needed in the new store, while others should be removed, renamed or moved into a separate customer profile system.

A careful migration protects data quality and customer experience at the same time. Shoppers in Sydney, Melbourne or Brisbane should be able to register quickly, select accurate Australian address details and use familiar options such as click and collect. Retailers also need a defensible process for privacy, security and consent.

Identify every field before changing the form

Start by creating a complete inventory of the existing NCR customer account fields. Record the field label, internal key, data type, whether it is mandatory, where it appears, and which operational process uses it. A field called “Member number” may feed loyalty pricing, while “Preferred store” could control local fulfilment or promotional messages.

Export a representative sample of customer records and compare it with the live registration, account-edit and checkout experiences. This often reveals hidden dependencies, including fields populated by imports or used in marketing integrations. Check customer service screens, order exports and reports before deciding that an apparently unused field can be deleted.

Separate personal information from operational metadata. Date of birth, mobile number and marketing preferences need a clear business purpose and appropriate handling. Internal flags, staff notes and system identifiers should generally not be exposed as editable registration fields. Preserving every column simply because it exists can create unnecessary privacy and maintenance risks.

Build a practical field mapping

Create a mapping document with one row for each source field. Useful columns include the NCR field name, destination field, transformation rule, permitted values, migration treatment and validation owner. Each source field should be classified as migrate, transform, archive or discard, with a reason recorded for the decision.

Some changes are straightforward. “First name” may map directly to the new platform, while a single “Full name” value may need to be split only when the data is reliable. A free-text “State” field should be converted into Australian state and territory codes, such as NSW, VIC, QLD, WA, SA, TAS, ACT and NT. Postcodes should remain four-digit strings so leading zeroes are not lost.

Consider whether a custom value belongs in the registration form at all. A preferred store may be better represented by a location selector, and a loyalty number may need verification against the loyalty service rather than simple text entry. For homewares or furniture retailers, delivery access details can be important, but they may belong in an address or fulfilment workflow instead of permanent account registration. Retail categories such as home retail category can also influence which profile data is genuinely useful.

Design the new registration experience

Keep initial registration focused on information required to create and service an account. Name, email address, password or passwordless authentication, mobile number and an appropriate communication preference may be sufficient. Ask for optional information later through the account area, loyalty enrolment or a post-purchase interaction.

Australian customers expect address forms that recognise suburbs, states and postcodes without forcing them through unfamiliar international layouts. Support Australian mobile formats while storing numbers consistently, and make it clear whether prices and future communications include GST considerations. If a retailer operates stores in Adelaide, Perth or regional Queensland, include a searchable store selector rather than asking customers to type a location manually.

Avoid copying old labels into a new interface without checking their meaning. “Customer type” might need plain-language choices such as personal, business or trade. “Preferred contact” should distinguish service communications from marketing consent. Required fields should be limited, visibly marked and explained where their purpose is not obvious. A shorter form generally produces cleaner data because shoppers are less likely to enter placeholders.

Protect privacy and account security

Customer-field migration should align with the Australian Privacy Act and the Australian Privacy Principles. Tell customers why information is collected, how it will be used and whether it is required to provide the requested service. Marketing consent should be separate from acceptance of account terms, with records showing the wording, timestamp and source of each consent.

Review retention rules before importing historic values. Old promotional preferences may be stale, and an inactive account should not automatically receive marketing messages simply because a legacy field contains “yes”. Give customers a clear way to update their details, unsubscribe and request access or correction where applicable.

Security controls need attention during export, transfer and import. Use encrypted files or a secure transfer service, restrict administrator access and delete temporary extracts after reconciliation. Passwords must never be migrated as readable values; customers should receive a secure reset or account activation process. For wider monitoring and incident planning, review these ransomware early warnings alongside the migration runbook.

Test the migration across real customer journeys

Test with anonymised records that reflect actual Australian data conditions: multi-part surnames, shared household emails, rural addresses, four-digit postcodes, +61 mobile numbers and customers who shop across several stores. Include accounts with blank optional fields, duplicate emails, invalid legacy values and unusually long text.

Run the new form through desktop and mobile devices, especially because many customers browse and buy on phones. Test account creation, email verification, password reset, profile editing, consent changes, loyalty recognition and guest checkout. Confirm that a customer can select click and collect in Melbourne or Brisbane without the registration data producing an incorrect delivery or store result.

Reconcile totals and samples after import. Compare the number of migrated accounts, populated fields, duplicates, rejected rows and transformed values. Ask customer service staff to review the new account view and verify that they can find the information needed for refunds, order queries and store support. A staged release or pilot store can expose issues before the full customer base is moved.

Keep the process controlled after launch

A migration is easier to maintain when the new registration schema has a named owner. Document each field’s purpose, source, permitted values, privacy basis and downstream consumers. Keep the mapping file, test results, consent approach and rollback procedure in a controlled location rather than relying on individual spreadsheets.

Replacement platforms have different extension models and security responsibilities. Magento implementations may use customer attributes and custom modules, while WooCommerce commonly relies on user metadata and carefully selected plugins. Confirm how each platform handles validation, exports, API access, backups and staff permissions before recreating a custom field.

NCR’s product discontinuation also makes it important to verify which security assurances still apply to connected services and archived data. This review of NCR security certifications can support discussions with technology partners, although each retailer should validate its own current hosting, payment and integration controls.

Migration decisions worth recording

  • List every legacy field and identify its business owner before exporting customer data.
  • Map Australian addresses, state codes, postcodes and mobile numbers with explicit validation rules.
  • Separate account essentials, loyalty information, fulfilment details and marketing preferences.
  • Preserve consent history where it is reliable, and re-collect permission when the old record is unclear.
  • Use secure transfer methods, temporary access controls and a documented deletion process.
  • Test duplicates, blank values, unusual addresses, mobile screens and account recovery before launch.
  • Reconcile imported totals and keep a rollback plan for the first production release.

A clean registration form should be the result of deliberate data decisions rather than a visual copy of the NCR experience. Once the mapping and privacy rules are settled, the implementation team can build a simpler account journey while retaining the customer information that genuinely supports service, fulfilment and loyalty.

The next practical step is to export a field inventory from the current NCR environment and have the ecommerce, customer service and privacy owners classify every field as migrate, transform, archive or discard.

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.