Exporting And Recreating NCR Retail Online Coupon Codes

NCR Retail Online was built to connect ecommerce selling with retail inventory, customer records and business operations. Its coupon tools were useful for managing promotions across an online shop, yet the platform’s discontinuation means retailers must preserve promotion data before moving to a replacement system.

A coupon migration is more involved than copying a list of discount codes. Each offer may include a percentage or dollar value, minimum spend, product restrictions, customer eligibility, usage limits, expiry dates and rules about combining promotions. Those details need to be captured clearly so the recreated offer behaves the same way in Magento, WooCommerce or another platform supported by an NCR Counterpoint partner.

Australian retailers also need to account for local trading patterns. Boxing Day sales, end-of-financial-year promotions, Click Frenzy campaigns and postcode-based delivery offers can create large groups of codes with different validity windows. A careful export and rebuild process protects reporting accuracy while preventing expired or unrestricted discounts from being accidentally released.

Confirm The Migration Scope

Start by listing every coupon family that may still be active or relevant. Include public promotion codes, unique customer codes, staff or wholesale discounts, abandoned-cart offers and codes printed on receipts or included in email campaigns. Do not rely solely on the ecommerce dashboard; check marketing calendars, saved spreadsheets and point-of-sale procedures as well.

Separate historical codes from live offers. Historical data may be needed for order reporting, refunds or customer service, while active codes must be rebuilt before the new storefront launches. A promotion used for a Sydney warehouse clearance may have very different conditions from a nationwide online code, so record the intended sales channel and audience.

NCR’s main site provides useful background on the platform’s transition and retail software ecosystem; review the NCR Retail Online information alongside records held by your implementation partner. If the old administration area is unavailable, ask the partner whether an archived database, scheduled export or support-assisted data extract exists.

Capture Every Rule Before Exporting

Create a working register with one row per coupon code or coupon campaign. Useful fields include the code itself, campaign name, discount type, discount amount, currency, start date, end date, minimum order value, eligible products, excluded products, customer group, redemption limit and current status.

Record whether the discount applies before or after shipping and tax. This distinction matters in Australia, where GST-inclusive shelf pricing and delivery charges can produce unexpected totals if the new platform calculates the offer differently. Also note whether a code can be combined with loyalty points, free shipping or another promotion.

Screenshots are worth keeping when a rule cannot be exported as structured data. Save the promotion summary, condition settings and usage report with a consistent filename, such as EOFY-2024-15OFF-rule-details.png. Screenshots do not replace a data file, but they provide evidence when a destination platform cannot represent a legacy condition exactly.

For product-based offers, preserve the identifiers used by the destination catalogue rather than copying only product names. SKU, variant ID and category mappings are safer than descriptions, especially when products have been renamed or when a retailer sells across Melbourne, Brisbane and regional delivery zones.

Export The Source Data Safely

If NCR Retail Online still permits administration access, look for a promotion, discount or coupon export in CSV format. Export codes with their conditions and usage records where possible. Run separate extracts for active, scheduled and expired offers so that the migration team can distinguish what should be recreated from what should remain archival.

If there is no native export, use a partner-approved database extract or reporting method. Avoid scraping a live customer-facing site: it may miss disabled codes, conceal usage limits and expose only the visible part of a promotion. Never place customer email addresses, password data or payment information into a coupon worksheet unless the migration process specifically requires it.

Use a controlled file with restricted access. Store the original export as read-only, make a working copy for cleaning, and keep a change log showing who edited each row. Coupon codes themselves are commercially sensitive; a leaked code can turn a limited offer into an uncontrolled discount, particularly during a high-volume period such as the Boxing Day rush.

Clean the file without changing the original. Remove duplicate rows, flag blank codes, standardise dates to a documented format and check that every amount is in Australian dollars where applicable. Preserve leading zeroes and unusual characters in codes, because spreadsheet software can alter them during import.

Map Coupons To The New Platform

Before importing anything, map each NCR rule to the vocabulary of the replacement platform. Magento may use cart price rules, catalog price rules and coupon conditions, while WooCommerce may rely on built-in coupon settings plus extensions for advanced restrictions. A partner should confirm which features are native and which require an extension.

Create a mapping sheet with columns for the source field, destination field, transformation and test result. For example, an NCR minimum order value may map directly to a cart subtotal condition, while a rule based on a retail customer group may need a new customer role or segment. If a legacy feature has no equivalent, document the approved workaround rather than silently dropping it.

Email promotions need special attention. A rebuilt code is ineffective if old campaigns continue pointing to an expired checkout or if automated messages contain outdated restrictions. The guidance on email marketing after migration can help connect coupon planning with mailing lists, automated journeys and tracking links.

Consider URL structure and analytics at the same time. Keep campaign names consistent, add a source or medium parameter to promotional links and decide whether old codes should remain valid for a short overlap period. An overlap can protect customers during transition, but it must have a fixed end date and a clear owner.

Rebuild Codes In Controlled Batches

Do not import every promotion directly into production. Begin with a small batch containing different rule types: a percentage discount, a fixed amount, a free-shipping offer, a product-specific code and a customer-restricted code. This exposes mapping problems before hundreds of offers become difficult to audit.

Recreate public campaign codes first when they have the greatest sales impact. Then handle unique or customer-specific codes, taking care to preserve one-use limits. If the destination platform generates codes differently, import the existing values only if it supports them safely; otherwise, create a documented replacement range and connect old and new codes in the migration register.

Use a naming convention for internal campaign labels even when the customer-facing code stays unchanged. A label such as EOFY_2025_ONLINE_AUD helps staff identify the campaign without opening each rule. For a retailer serving customers in Perth and Adelaide from separate fulfilment locations, include channel or region information where the discount genuinely differs.

Product data should be checked before rule activation. Confirm that every referenced SKU is published, purchasable and assigned to the correct category. A giftware retailer could use its crystal serving range as a sample catalogue set; the crystal product example illustrates why product names alone are insufficient when variants and collections are involved.

Test, Reconcile And Retire Legacy Codes

Test each recreated offer in a staging environment using a matrix of valid and invalid scenarios. Check the code at the minimum spend, just below the minimum, with an excluded item, with a sale item, after the expiry time and alongside another discount. Test guest checkout and logged-in checkout separately if customer eligibility is part of the rule.

Verify Australian-specific behaviour as well. Confirm that prices display in AUD, GST is calculated as expected, delivery discounts apply only to intended services and postcode restrictions work for metropolitan and regional addresses. Include a sample order from a Melbourne suburb and a regional New South Wales postcode if delivery logic is part of the offer.

Reconcile the new system against the source register. Count active codes, compare discount values, review expiry dates and check that every exception has an owner’s approval. Keep a status column such as “recreated”, “tested”, “replaced” or “archive only”. This provides a defensible record for customer service and finance teams when an order is queried later.

After launch, disable legacy redemption only when the replacement checkout has passed its final test and communications have been updated. Monitor coupon use, rejected-code messages, average order value and unexpected margin changes during the first promotional cycle. The immediate next step is to create the controlled coupon register and populate it from the last verified NCR Retail Online export.