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 |
|
Magento | Most tightly integrated with Counterpoint and offers the most advanced features | ||||||||||||||||||||||||
| CP Magento |
|
Magento | Integrated with Counterpoint and offers features similar to NRO | ||||||||||||||||||||||||
| CP Shop |
|
Woo Commerce | Catalog, Inventory, and Orders are integrated with Counterpoint | ||||||||||||||||||||||||
Preserving subscriber consent during an NCR migrationA successful list move should deliver more than accurate names and email addresses. For a newsletter, the subscriber profile is also evidence of how a person was contacted, what they agreed to receive, when permission was captured, and whether they later withdrew it. That evidence is the opt-in history. The operational backdrop makes this especially important. NCR Retail Online has been discontinued, and NCR has directed customers toward alternatives such as Magento and WooCommerce through NCR Counterpoint partners. A transition may therefore involve a new ecommerce platform, a different email service, a revised customer database and separate operational systems all at once. Australian marketing emails are governed principally by the Spam Act 2003, which generally requires consent before commercial electronic messages are sent. The Privacy Act 1988 and Australian Privacy Principles may also apply, along with relevant state or territory privacy laws. A migration should preserve the evidence needed to demonstrate lawful, transparent and appropriately scoped communication. The safest approach treats subscriber data as a linked record rather than a flat CSV file. Identity, consent, acquisition source, permissions, unsubscribe events and migration evidence should travel together, with clear rules governing how each field is used after the move. Why consent records deserve equal weightAn email address tells a retailer where to deliver a message. Consent evidence tells the retailer whether that delivery is permitted. Many legacy databases retain only an active or inactive flag, which may be enough to exclude someone from a campaign but not enough to reconstruct why the person was included. Keeping that distinction prevents a dormant subscriber file from becoming an implied permission list. Consent can be express or inferred, and the record must match the method used. A checkbox response, verified signup request or recorded customer instruction each provide different evidence. Opens, clicks and previous purchases are behavioural signals, not substitutes for marketing consent, while a purchased or transferred mailing list does not automatically carry adequate permission. Historic campaign routes can also reveal what subscribers saw when they agreed to receive communications. Auditing old links against the legacy NCR gift pages, saved emails and archived forms may clarify the original offer. These artefacts provide context, but a page alone cannot prove that a particular person opted in. Reconstruct the original sign-up journeyStart with the exact source data. For each subscriber, locate the email address, legacy customer ID, consent status, consent timestamp, signup source, form or campaign version, communication categories, unsubscribe history and any evidence that the action was completed. Preserve the original values and time zone before normalising them for the destination platform. Where a signup form no longer exists, reconstruct its context from campaign records and saved website assets. The NCR for-her gift guide, for example, may identify the subject and promotion connected with a historic signup. It still needs to be tied to a dated subscriber action and the wording of the permission that was presented. Scope matters as much as timing. A subscriber may have agreed to receive weekly gift updates without accepting general product news, or may have permitted email but not SMS. Those distinctions should become explicit permissions in the new platform. A record that says only “subscribed” should be classified as unverified rather than expanded into broader communication rights. Design a field-level handoverKeep an immutable copy of the source export so the migration can be reproduced and audited. Then create a normalised destination record that links the contact, consent evidence and suppression status without replacing the originals. Store the migration date, operator, source file identifier and validation result alongside the imported data. Each legacy field should have a defined destination, transformation and verification rule rather than relying on a column-name match during import.
The legal owner of the subscriber data must also remain clear after the transition. If the same retailer continues sending the newsletter under a new platform, a structured transfer may be sufficient. If a partner or successor entity becomes the sender, the purposes, disclosures and permission scope require separate review. The field mapping should show which organisation controls each record and who can access the underlying evidence. Move the audience without weakening safeguardsRun the import as a controlled rehearsal before loading production data. Use a representative sample, reject invalid addresses, reconcile record counts and compare duplicate rates with the legacy system. A repeatable import identifier prevents an interrupted retry from creating duplicate subscriptions or repeated consent entries. Document every system that can read, export or delete subscriber information, including ecommerce, point-of-sale, customer support, email and operational tools. A business may also use the SatPointer operations platform for operational tracking. That does not make it a marketing system, but it illustrates why the data-flow map should name every location holding customer information and restrict access according to purpose. Suppression lists need particular attention. Unsubscribe events should override campaign selections, preference tags and imported active-status flags. Legacy signup forms must stop using outdated consent language, while transactional messages should remain distinct from promotional newsletters. After migration, send internal test campaigns through Magento, WooCommerce and the chosen email service, then reconcile delivery, suppression and consent logs before contacting subscribers. Make consent history durable for the next platformFuture sign-ups should create structured evidence from the outset. Record the timestamp and time zone, source URL, form version, permission granted, consent method and responsible entity. A preference centre should make categories easy to change, explain the purpose of each subscription and keep a history of amendments. Double opt-in can add assurance for higher-risk lists, although it should complement rather than replace good recordkeeping. Australian shoppers commonly encounter promotions through crowded mobile inboxes while using click-and-collect, buy-now-pay-later services and marketplace events such as Click Frenz. Campaigns should be relevant enough to stand apart from that activity. Sydney and Melbourne share daylight-saving changes, while Brisbane remains on Australian Eastern Standard Time, so audience scheduling and historic timestamps benefit from recipient-level time-zone handling. Prices, taxes and transactional notices should also reflect familiar Australian expectations, including Australian dollars and GST-inclusive pricing. Treat the migration as a transfer of accountability, not a cosmetic change of platform. An address list can be replaced in an afternoon; the permission trail, suppression history and accountable owner may take much longer to rebuild. The durable asset is not simply the subscriber count, but the verifiable consent history that supports every future communication. |
|||||||||||||||||||||||||||
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.