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

Transferring NCR’s Custom Invoice Numbering Sequence to a New System

NCR Retail Online connected ecommerce stores with NCR inventory and business management systems, but the product has since been discontinued. Merchants moving through NCR Counterpoint partners to Magento or WooCommerce must carry over more than products and customer records: invoice numbering must preserve history, prevent duplicates and keep new documents aligned with finance, fulfilment and support workflows.

A custom sequence might combine a prefix, branch code, year and padded counter, such as INV-2026-000184. Treat that format as a controlled business rule, not a cosmetic field. In Australia, it sits alongside AUD, 10% GST, ABN details and ATO record-keeping guidance, which generally calls for five years of retention. Preserving a number is useful, but it does not by itself make an invoice a valid GST tax invoice.

Audit the Existing Sequence

Start by establishing which identifier is authoritative at source. An NCR order number, customer invoice, POS receipt, dispatch docket and payment-gateway reference may use different counters. Record where each is created, whether it can change and which system holds the audit history. Trace a test order from capture to settlement so the invoice number is not confused with an order ID or remittance reference.

Document every formula, including prefixes, padding, store codes, date segments, annual resets, manual overrides and separate ranges for legal entities or channels. Check old exports, voids and credit notes rather than one live screen. Decide which historic numbers must stay identical, whether gaps are permitted, whether the new platform continues the final sequence and how year-end resets or new branches work.

Build the Migration Specification

Create a field-level map from NCR to the destination. Capture invoice number, date, order reference, customer, legal entity, store, line descriptions, AUD amounts, GST treatment, discounts, shipping, paid total, payment status and void status. Keep legacy IDs in a dedicated field so support staff can retrieve the original record even if the platform assigns a different internal identifier.

Turn the rules into examples that developers and finance staff can both test. Include the first and last valid number, rollover behaviour, deleted drafts, treatment of tax codes and authority to override. Specify whether the date segment follows Australia’s 1 July to 30 June financial year, and record the time zone for boundary cases.

Merchants can ask a specialist such as QloudPress to review the specification through migration planning help, while internal owners retain sign-off. This can help where NCR data must be reconciled against a WooCommerce or Magento installation rather than handled by a general ecommerce export.

Move and Validate Historical Invoices

Export historical invoices with stable identifiers, retain the untouched source and import the original invoice numbers intact. Clean the data before loading it: flag duplicates, blank customer names, invalid postcodes, unsupported tax codes, orphan lines and totals that do not recalculate. Do not silently repair an amount; quarantine the record, document the discrepancy and obtain approval for a linked adjustment.

Before importing, confirm the destination can store and reprint the original document number. If its standard invoice model cannot, use a supported mapping, extension or accounting-system identifier. Never replace a historic invoice number with an autogenerated order ID, because finance records, customers and tax documentation may already reference it.

For Australian GST compliance, check that migrated tax invoices include the supplier’s name and ABN, recipient name and address, invoice date, supply description, GST amount and total. Sales of $1,000 or more generally require a full tax invoice, while lower-value sales may qualify for a simplified invoice. For merchants adopting WooCommerce, archived WooCommerce payment guidance explains how gateway references fit around the new order flow; use it as background, not a substitute for the current gateway’s documentation.

Configure Safe Number Generation

Configure the destination to generate each number atomically. A database sequence, transactional counter or equivalent is safer than COUNT or MAX plus one, because concurrent checkouts can claim the same number. Apply a database uniqueness constraint, and make retries idempotent so repeated requests cannot allocate another invoice.

Keep the invoice identifier separate from the order identifier and customer-visible payment reference. Prefixes or dates aid readability, but the counter and legal-entity range are the control. Use disjoint ranges for stores or subsidiaries, log every assignment and apply explicit time zones with an unambiguous Australian date format such as DD/MM/YYYY.

Check that no WooCommerce invoicing extension, Magento store scope or accounting connector silently resets or overrides the counter. Where the destination offers only platform-generated identifiers, use a supported invoice-number extension or linked accounting system rather than editing issued documents after the fact.

Limit manual changes. A used number should remain immutable; corrections should use a credit note, replacement invoice or approved adjustment linked to the original. Give sequence administration to a small finance or IT group, restrict wider access and retain an audit log of viewing, exporting, reserving and voiding numbers.

Test the Numbering Workflow

Build a test set from clean, messy and high-risk records. Cover duplicate imports, concurrent order creation, abandoned checkouts, refunds, manual entry, offline POS activity and the 30 June to 1 July rollover. Verify that each valid transaction receives one number, retries do not create another document and NCR references remain searchable.

Run a parallel period in staging using Australian transactions, including AUD 10% GST, GST-free lines, discounts, shipping and round-dollar totals. Reconcile counts and values by store, legal entity and invoice date rather than comparing one grand total. Test accountant exports too, because a correct on-screen invoice can still carry a truncated identifier or wrong tax breakdown.

Rehearse the final cutover, including a failed import, restored snapshot and rollback point. Record expected results for each step and name the person authorised to make the go-live decision. Testing only the happy path leaves the costliest duplication risks unresolved.

Cut Over and Keep Control

At cutover, pause invoice-producing channels, take a final NCR backup and record the last allocated number. Move the remaining delta, complete the migration and reconcile it against sales, GST and payment records before reopening checkout. For a Melbourne business, an “arvo” cutover sounds casual, but the runbook needs an exact AEST or AEDT timestamp and must account for Sydney staff, public holidays and daylight-saving changes.

Customer service staff should learn how to find both the legacy NCR number and the new platform reference through archived unified order lookup training. Give them a short guide explaining which number belongs on a quote, invoice, receipt or credit note, plus an escalation route for mismatches. Keep temporary NCR archive access until finance and support confirm historical lookups are complete.

Monitor allocations, imports, voids, credit notes and support searches after launch, then archive the mapping, test evidence and signed reconciliation. A successful cutover leaves one unique, traceable invoice number per transaction, preserves every historic reference and gives the business a documented sequence it can maintain without NCR Retail Online.

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.