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 |
How To Move NCR Purchase Order Approval History To A New ERPNCR Retail Online was built to connect ecommerce activity with retail inventory and business management workflows. With the product discontinued, retailers moving to Magento, WooCommerce, or another ERP-connected platform need to preserve more than products, customers, and stock balances. Purchase order approval history can explain who authorised spending, when a commitment was made, and whether a supplier invoice matched the approved request. That history is often stored across NCR Counterpoint records, exported reports, email notifications, and user permissions. A successful transfer therefore requires a controlled archive and a carefully designed ERP synchronisation process, rather than a simple CSV upload. The aim is to keep historical evidence accessible while creating clean approval workflows in the replacement system. Australian retailers also need to account for GST, supplier records, privacy obligations, and the practical demands of stores operating across Sydney, Melbourne, Brisbane, Perth, and regional areas. Staff may approve orders from a phone between customer service tasks, while head-office teams work in different time zones and rely on click-and-collect, seasonal promotions, and fast replenishment. Define What Approval History Must Be PreservedStart by documenting the complete purchase order lifecycle in NCR Counterpoint and any connected NCR Retail Online tools. Typical fields include the purchase order number, supplier, store or warehouse, order date, requested delivery date, line items, quantities, unit costs, GST treatment, approval status, approver, approval timestamp, rejection reason, comments, and later amendments. Include cancelled, rejected, partially received, and closed orders because removing unusual cases can weaken the audit trail. Separate transactional history from current master data. A supplier’s present address, payment terms, or ABN may be migrated to the new ERP, while the historical purchase order should retain the values that applied at the time of approval. This distinction matters when a vendor changes ownership, a store moves location, or a buyer’s role is reassigned. Create a data dictionary before exporting anything. Map terms such as “pending,” “approved,” “void,” and “received” to the target ERP’s status codes. Record whether timestamps are stored in local time or UTC, and preserve the original time zone where possible. For Australian operations, identify whether an approval was made during AEST, AEDT, AWST, or another local setting so an audit does not appear to show an impossible sequence. Export The Source Records Without Losing ContextUse a read-only export from the legacy environment wherever possible, then save the original files in an access-controlled location. Export both structured data and supporting documents, including approval comments, attached quotes, supplier correspondence, and revised purchase orders. If the platform offers an audit log, capture it separately rather than assuming its information is included in the purchase order export. A practical export may contain one header file, one line-item file, an approval-events file, and a document index. Link these tables with stable identifiers rather than supplier names or descriptions. A purchase order number can be reused across branches or systems, so a compound key such as company code, store code, financial year, and order number may be safer. Check the export against operational totals. Compare the number of orders by month, supplier, location, approval status, and financial year. Investigate gaps around major promotions, end-of-financial-year buying, and stocktake periods. Australian retailers often experience sharp demand changes around Christmas, Boxing Day, Easter, and local events, making seasonal anomalies especially important to explain. Map Approvals To The New ERP WorkflowThe target ERP may use approval routes based on dollar value, department, location, supplier category, or employee role. Build a mapping table that connects each legacy approver to a current user account, while retaining the original name and role in a historical field. Do not substitute a current manager for a former approver in a way that suggests the new person authorised the old transaction. Historical records should usually be imported as closed or read-only transactions. Reopening an old order in the new ERP can trigger duplicate notifications, reserve stock unexpectedly, or create a second commitment with the supplier. If the replacement platform cannot store a native approval timeline, use a linked audit document or an immutable custom record containing the original event sequence. Treat status conversion as a business decision. “Approved” does not always mean “received,” and “partially received” should not be converted to “complete” simply because the purchase order is old. Preserve each event with its date, user, and source-system reference. Where the target system supports comments, add a migration note identifying the source export and transformation rule. For format validation, think of the conversion like separating two signal types rather than blending them together. A useful technical comparison is this guide to polarisation differences: the source and target formats must be understood before data is transformed, or important meaning can be distorted even when every row appears to transfer successfully. Protect Compliance And Commercial EvidencePurchase order approvals can contain names, email addresses, phone numbers, buying patterns, and supplier pricing. Apply the Australian Privacy Act 1988 and the organisation’s privacy policy when deciding who can access the archive. Limit administrator privileges, encrypt files during transfer, and keep a record of who performed the migration and who approved the final reconciliation. The Australian Consumer Law does not prescribe a particular purchase order archive, but accurate records can support disputes about delivery, pricing, warranties, and representations. Tax and accounting records may also need to be retained for the period required by the ATO; many business records must be kept for at least five years, although the correct period depends on the record and circumstances. Confirm the retention schedule with the retailer’s accountant or legal adviser. Keep the source export untouched and store checksums for the files used in migration. If an external implementation partner handles the data, verify its identity, security controls, subcontractors, and deletion process. A vendor registry can be one reference point during due diligence, but it should supplement, not replace, contract checks and direct verification. Reconcile Inventory, Invoices, And Supplier BalancesApproval history becomes useful when it can be connected to what happened afterwards. Match purchase orders with goods receipts, supplier invoices, credit notes, returns, and payment records. Flag orders approved but never sent, sent but never received, and received without a matching approved order. These exceptions can reveal old workflow weaknesses before they are reproduced in the new ERP. Pay attention to GST-inclusive and GST-exclusive amounts. The target system should preserve the original tax basis and currency, while current configuration should follow the retailer’s accounting setup. Compare line extensions, freight, discounts, rounding, and tax totals rather than checking only the grand total. A one-cent rounding difference may be harmless, but a repeated mismatch can indicate a flawed mapping rule. Include adjacent retail liabilities in the wider cutover review. For example, gift cards and stored-value products may sit outside purchase orders but still affect reconciliation and customer obligations; the retailer’s gift card information should be reviewed as part of the broader migration inventory. This prevents a narrow procurement transfer from overlooking connected ecommerce balances. Run a sample-based reconciliation after loading the new ERP. Select high-value orders, rejected orders, amended orders, and orders from each major store or warehouse. Then run aggregate tests across the full dataset. Have procurement, finance, store operations, and IT sign off separately because each team sees different failure points. Manage Cutover With A Controlled ArchiveChoose a cutover time that limits purchasing activity, but do not assume every Australian store can stop simultaneously. A retailer with locations in Perth and the eastern states may need a staggered freeze that accounts for local operating hours and warehouse dispatch deadlines. Communicate the final-entry deadline clearly, then capture any late approvals in a controlled exception log. Before switching users to the new ERP, complete a trial migration in a non-production environment. Test login permissions, approval notifications, supplier matching, report filters, attachments, and search by original NCR purchase order number. Confirm that an auditor can follow a transaction from request through approval, receipt, invoice, and payment without relying on an administrator’s private knowledge. NCR Counterpoint partners can help coordinate data extraction, workflow redesign, and operational continuity; guidance on migration support options is particularly relevant when stores must keep trading during the changeover. Document the partner’s responsibilities, escalation contacts, validation duties, and access expiry date before work begins. Recommended Transfer ControlsUse these controls to make the approval-history migration defensible and repeatable:
A migration should leave staff with a practical way to locate old approvals without granting broad access to sensitive commercial data. Keep the legacy reference number searchable in the new ERP, establish a simple procedure for requesting archived documents, and schedule a post-cutover review after the first full purchasing cycle. The safest immediate step is to create a representative export covering one busy month, one quiet month, and several exceptional orders, then have procurement and finance approve the field mapping before any production data is transformed. |
|||
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.