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 NCR Brand and Manufacturer Fields After MigrationNCR Retail Online is being discontinued, and Australian retailers who depended on it are moving to Magento, WooCommerce or another platform through NCR Counterpoint partners. Migration conversations usually centre on customer records, payment integrations and the cutover weekend. Underneath all of that sits a product master built over years, where every SKU carries a brand, a manufacturer, a vendor code, a barcode and a price. That master links the point-of-sale terminal in a Sydney store, the warehouse system in Melbourne and the storefront a customer in Brisbane opens on a phone. Brand and manufacturer are the fields most likely to break. In the legacy setup they were maintained in parallel, so a brand called "Sunbake Foods" in one system could be "Sunbake" in another and "Sunbake Australia Pty Ltd" in a third. During a bulk import those variants become separate brands, faceted search fragments and support tickets from customers who cannot find the item they ordered last week. The fix is unglamorous and mostly procedural: audit what exists, decide what each field means, normalise values to Australian conventions, and document every decision. Why Brand and Manufacturer Fields Decay in TransitMigration tools map what they can match and quietly drop what they cannot. Descriptions survive because they are long free text. Short attributes such as Brand, Manufacturer and Vendor are matched through lookup lists, and every unmatched value lands in an exceptions report nobody opens until a customer complains. Collisions come next. Two brands differing only in capitalisation or one letter become indistinguishable once a platform generates brand URLs. Then comes overwriting: some scripts write the manufacturer into the vendor field, or replace a brand with the name of the distributor that supplied that season's stock. None of this is visible on launch day. The store looks healthy and product counts look right, while the damage surfaces weeks later in search relevance, marketplace rejections and the manual effort of correcting catalogue records. Treat the descriptive attributes as their own workstream, with an owner, an extract and a sign-off. Mapping the Legacy Product Master to the New PlatformMagento and WooCommerce handle these attributes very differently. Magento provides a brand concept with brand pages and layered navigation, plus a manufacturer attribute deprecated in the 2.3 series and now kept mainly as a path for custom attributes. WooCommerce ships no brand or manufacturer field at all; those values live as product attributes or taxonomy terms your theme must be built to display. The mapping below shows where each legacy attribute typically lands and what needs attention on the way in.
Because the platforms differ this much, settle the target shape of the catalogue before the first import. Decide which fields are customer-facing, such as brand, product name and short description, and which are operational, such as manufacturer, supplier, ABN and landed cost, then give each one source and one owner. Auditing the Source System Before ExportBegin with a read-only extract of the whole product master, taken while the legacy environment still exists. Ask your NCR Counterpoint partner for a full attribute dump rather than the CSV the old integration happened to pass across. Store the extract in an Australian-hosted location with restricted access, and record the date, the record count and a checksum so later decisions trace back to a known snapshot. Interrogate it. Count distinct brand and manufacturer values, list those used fewer than five times, pull every value containing Pty, Ltd or a year, and flag the ones that read like a department. In most Australian catalogues that shortlist is the real work, a few hundred values covering thousands of SKUs. A structured data migration checklist sets out the sequence and the sign-off points. Dry-import two hundred SKUs before touching production, chosen deliberately: the highest-volume line, a distributor-supplied house brand, a discontinued item with a long history, and a seasonal range that only appears in the December peak. Compare imported records to source side by side and fix the mapping while the feedback loop is cheap. Normalising Australian Identifiers and LabelsAustralian catalogues have their own conventions, and brand data is where they bite. Every supplier and manufacturer should carry an Australian Business Number, since GST credit claims on imported stock depend on it. Displayed prices include 10% GST, so the imported price field must be checked against the tax-inclusive figure rather than the ex-GST number the buying team thinks in. Imported goods sharpen the point. Consignments valued at AUD 1,000 or less are assessed GST and duty by Australian Customs at the border, often against a supplier that appears on paperwork as an overseas entity with a local ABN registered for GST. The legacy manufacturer field may hold a foreign company while the correct local importer belongs in your records, so decide which one is customer-facing and which stays operational. Regulatory labelling adds another constraint, with cosmetics and some therapeutic goods requiring an Australian Register of Therapeutic Goods listing and electrical products needing Australian certification, both tracked against the manufacturer rather than the brand. The habit of naming supplier fields differently from brand fields is widespread, as category listings on this mining systems directory illustrate, so issue a one-page attribute dictionary covering brand, manufacturer, supplier, supplier_code, gtin and country_of_origin to everyone who supplies data. Then normalise the values themselves: one case convention, no legal suffixes in the brand, no trailing punctuation, a controlled list of manufacturers, and a rule for how the brand sits beside the product name. Write those rules into the import mapping rather than a spreadsheet somebody remembers to apply. Keeping Suppliers and Marketplaces AlignedAustralian retail is unusually exposed to downstream readers of your product data. Feeds into Kmart, Big W and JB Hi-Fi, wholesale portals for Coles and Woolworths, and listings on eBay Australia and Catch all read the same brand and manufacturer fields, each with its own tolerance for duplication. Push two spellings of one brand and you get rejected feeds and duplicate listings in the same category. Suppliers will cooperate if the request is specific. Give each manufacturer a short document listing the exact values you will hold for their brand, the ABN to use, the GTIN range they own and the date the change goes live. Distributors adding house-brand lines need to be told they cannot overwrite the manufacturer attribute, and that enforcement belongs in import validation rather than in email. A single landing page for suppliers and trade customers saves argument. A custom bio page guide shows how one short profile can carry the new data rules, the ABN, the support contact and the migration dates without a full site rebuild. Keep it versioned and link it from the supplier portal, the purchase orders and the trade newsletter. Telling Staff, Suppliers and Customers What ChangedCatalogue changes rarely affect customers directly, which is why the failures get reported late. Before cutover, tell merchandising, buying and warehouse teams in Sydney and Melbourne exactly what changes in the product records and why. The pick line in Brisbane will be asked why a brand now shows a new name. Customers need a plain continuity message: same products, same stock, same support contacts, with renamed or consolidated brands named in a list rather than buried in a release note. The published platform migration announcement covers the formats that work, including the short in-store note and the pre-emptive email that reduces support contacts in the first week. After cutover, watch the catalogue rather than the sales dashboard. Search terms that stopped returning your top-selling brands, marketplace feed rejections and support contacts asking for a product under its old name are the early signals that a field did not survive. Feed those back into the dictionary so the next migration starts from a cleaner file. Putting the Field Audit on the CalendarA catalogue is not rebuilt during cutover; it is rebuilt from the decisions made in the fortnight beforehand: a frozen extract, a documented attribute dictionary, a shortlist of values to correct, and a rule that nothing overwrites a brand or manufacturer without an owner signing it off. So the next step is specific: book a two-hour session with your ERP lead, your ecommerce developer and the merchandising lead, and leave it with the first twenty values on the brand and manufacturer cleanup list written, dated and version-controlled. |
|||||||||||||||||||||||||||||||
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.