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

Migrating NCR Vendor-Managed Inventory to a Multi-Vendor Marketplace

NCR Retail Online helped retailers connect ecommerce selling with stock control, retail operations and business management. Its discontinuation changes the task from maintaining an existing online channel to preserving the data relationships that made the operation dependable. Vendor-managed inventory, or VMI, deserves particular care because stock availability may be controlled by suppliers rather than by the retailer itself.

A multi-vendor marketplace plugin introduces a different model. Instead of one retailer publishing products from a central catalogue, several vendors may own products, update quantities, fulfil orders and receive settlements through the same storefront. The migration therefore involves more than importing SKUs. It requires a clear translation between NCR records, supplier responsibilities and marketplace workflows.

Australian retailers also need to account for GST-inclusive pricing, Australian Business Numbers, local delivery zones and consumer-law obligations. A supplier in Melbourne may replenish a store in Geelong quickly, while a vendor shipping from Perth to regional Queensland needs a different delivery promise. Those practical details must be reflected in the new data model rather than handled manually after launch.

The safest approach is to treat the project as a controlled data conversion. First identify what each NCR field meant operationally, then map it to the marketplace plugin, validate ownership and replenishment rules, and test orders across ordinary, split-shipment and out-of-stock scenarios.

What The Existing VMI Records Really Contain

NCR exports may contain familiar fields such as SKU, description, price, quantity and supplier code, but VMI information often sits in less obvious places. Reorder thresholds, preferred vendors, purchase order references, warehouse locations, delivery calendars and consignment indicators can be hidden in custom fields or operational notes. A simple product export may therefore omit the information that determines who is responsible for keeping stock available.

Start by separating product identity from inventory responsibility. Product identity includes the SKU, barcode, brand, dimensions, variants, images and tax category. Responsibility includes the vendor, stock owner, replenishment method, agreed lead time, minimum order quantity and the person or system allowed to change availability.

Retailers moving away from NCR should document these relationships before choosing import settings. A useful reference is this guide to replicating NCR capabilities, particularly when the old platform supported automated operations that the new marketplace extension does not provide by default.

Build A Field-Level Migration Map

A field map should show the source column, its business meaning, its destination field and the transformation required. For example, an NCR supplier code may need to become a marketplace vendor ID, while a stock quantity may need to be split between physical stock, available stock and stock reserved for open orders. Record whether each value is imported once or synchronised continuously.

Create separate mappings for products, vendors, locations, stock movements, purchase orders, customer orders and financial records. Do not assume that a matching field name means matching behaviour. “Supplier” could describe the manufacturer, the wholesaler, the party that owns consignment stock or the party that fulfils the customer order.

This distinction matters in an Australian marketplace where one vendor may ship from Sydney, another from Adelaide and a third from a regional warehouse. The storefront needs reliable fulfilment and delivery estimates, while the back office needs accurate settlement and GST reporting. Assign a named owner to every ambiguous field and keep a decision log for changes made during testing.

Choose A Marketplace Structure That Fits

Magento and WooCommerce can both support marketplace extensions, but the choice should follow the operating model rather than the preferred software brand. Consider how vendors will access their dashboards, whether they can edit products, how stock feeds arrive, how commissions are calculated and whether the platform supports multiple fulfilment locations.

A plugin may provide vendor registration, product management, order splitting and commission records, yet still require custom integration for VMI. An implementation partner such as KPN Interactive can help connect the marketplace layer with inventory, accounting and supplier systems, especially where the retailer needs automated stock updates rather than spreadsheet uploads.

Define the source of truth before development begins. If a vendor’s ERP owns available stock, the marketplace should consume that value and prevent manual edits. If the retailer owns the count for consignment goods, vendor dashboards should display restricted information while the central system controls availability. Two systems must never be allowed to overwrite each other without a conflict rule.

Clean And Standardise The Catalogue

Catalogue cleansing is often the largest part of the work. Remove duplicate SKUs, close discontinued products, standardise units of measure and resolve products that were entered under different names by different suppliers. Confirm that barcodes are valid and unique, especially where products have Australian and imported packaging variants.

Use consistent attributes for size, colour, pack count, material and compatibility. A catalogue item such as a dinner plate may appear in several sizes and finishes, so each sellable variation needs its own SKU and stock value. Images and descriptions should be checked as carefully as transactional data; a useful merchandising example is the everyday dishes range, where product structure and variation clarity influence customer choice.

Apply Australian tax rules during cleansing. Prices displayed to consumers are commonly GST-inclusive, while supplier costs and settlement reports may require separate tax components. Keep the GST code, taxable status and displayed price logic distinct so that marketplace commissions and vendor payouts do not quietly produce incorrect calculations.

Translate VMI Into Vendor Workflows

VMI is a business agreement, not simply a stock field. The migration must express who monitors demand, who initiates replenishment, who owns goods until sale, and who carries the risk of shrinkage or obsolete stock. Those rules should appear in vendor permissions, alerts, purchase workflows and reporting.

For each vendor, define the inventory feed frequency, accepted file or API format, stock reservation behaviour and response to rejected updates. A vendor might send a quantity of 40 each morning, while the marketplace reserves three units for paid orders and exposes 37 for sale. Another vendor may provide an availability status rather than a precise quantity, requiring different logic.

Include exceptions such as backorders, partial fulfilment and vendor holidays. A supplier taking a break over the Christmas-New Year period may need a temporary lead-time adjustment rather than a product shutdown. The system should also distinguish “out of stock”, “awaiting supplier confirmation” and “available for preorder”, because each status creates a different customer promise.

Recreate Automation And Controls

Automated synchronisation should cover more than quantity. Product updates, price changes, vendor status, purchase orders, shipping events, refunds and cancellations all need defined triggers. Use queues and retry handling so a brief supplier system outage does not create permanent stock errors.

Set thresholds for suspicious changes. A feed that changes a product from 80 units to zero may be correct, but it may also indicate a malformed file. Require review for unusually large movements, duplicate identifiers or a sudden price change. Keep an audit trail showing the original value, the updated value, the time of the change and the system that submitted it.

Security deserves equal attention. Vendor accounts should use strong authentication, restricted permissions and separate access to customer information. Marketplace administrators should be able to revoke a vendor’s access without deleting historical orders. Payment details should remain with the approved payment provider, while settlement records retain enough detail for reconciliation and dispute handling.

Test Orders Across Australian Scenarios

Testing should begin with representative data rather than a tiny sample of perfect products. Include single-vendor orders, mixed-vendor baskets, split shipments, substituted stock, GST-free items where relevant, refunds, failed payments and cancelled fulfilment. Test postcode-based delivery rules for metropolitan Sydney, Melbourne and Brisbane as well as regional destinations.

Check how the platform handles Australian addresses, suburb names and state abbreviations. Delivery calculations should account for services such as Australia Post, StarTrack or a vendor’s own courier arrangement without promising the same timeframe everywhere. Confirm that order confirmations, invoices and refund records show prices and taxes clearly in Australian dollars.

Run a reconciliation between NCR’s final stock and order records and the new marketplace totals. Compare product counts, available quantities, open orders, vendor balances and customer credits. Perform a small controlled launch with selected vendors, monitor stock and fulfilment for several trading days, then freeze the legacy system before the full cutover.

The migration is complete only when operational ownership is visible in daily work. A vendor should know which orders require action, the retailer should know which stock is trustworthy, and customers should receive accurate availability and delivery information. Preserve the original NCR export in read-only storage, retain the mapping decisions, and schedule post-launch checks for inventory variance, failed feeds and settlement differences.

Begin with a dated export of NCR products, vendors, stock movements and open orders, then create the field-level mapping that identifies the owner and destination of every VMI value.

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.