Managing Gift Card Balances After an NCR Retail Online Migration

When NCR Retail Online was discontinued, merchants had to move their ecommerce operations to another platform, often Magento or WooCommerce through an NCR Counterpoint partner. Product catalogs, customer records, orders, and payment settings may have transferred successfully, while gift card balances require more deliberate handling.

A gift card is both a customer benefit and a financial liability. The balance must remain accurate, redemption must work across the intended sales channels, and the business needs a reliable audit trail. A migration that preserves product data but loses stored-value records can quickly create disputes, write-offs, and customer frustration.

Handling gift card balances after migrating from NCR Retail Online therefore calls for a controlled process rather than a simple import. The safest approach combines historical data preservation, platform configuration, reconciliation, testing, customer communication, and clear ownership between the retailer and its implementation partner.

Confirm Liability And Card Scope

Start by identifying every gift card type that existed in the old environment. The inventory may include physical cards, digital certificates, promotional cards, employee cards, store credits, and cards issued through a point-of-sale system rather than the online store. Each category can have different expiration, refund, and redemption rules.

Review the original platform documentation and transition notices available through the NCR Retail Online site. Then compare those records with the current Counterpoint database, accounting reports, and payment processor exports. The goal is to establish which system was authoritative for issuance, activation, redemptions, reloads, refunds, and remaining balances.

Also determine where each card can be redeemed. Some merchants allow online and in-store use, while others support only one channel. Record those limits before choosing a migration method, because a platform extension that handles online codes may not synchronize correctly with the store register.

Preserve A Complete Source Record

Before decommissioning access to the former store, export a read-only archive of all gift card information. Useful fields include the card number or token, current balance, original value, issue date, last activity date, expiration status, transaction history, customer association, and activation state. Never store unmasked card numbers in ordinary spreadsheets unless the security process explicitly permits it.

Retain supporting reports for sales, redemptions, voids, refunds, and manual adjustments. These records help resolve cases where the balance in the old ecommerce system differs from the balance shown by the POS or general ledger. They also provide evidence if a customer disputes a balance months after the platform change.

Catalog structure can affect customer service after migration. For example, a retailer specializing in food and beverage may review its merchandising categories through food and wine while checking whether gift cards were sold as ordinary products, service items, or a separate stored-value instrument. The classification should be documented before product data is re-created.

Select The Right Migration Treatment

There are three common approaches: migrate balances into a native gift card feature, create equivalent codes in a compatible extension, or keep the old system as a reference while issuing replacement cards. The best choice depends on the target platform, the POS connection, the number of active cards, and whether customers need a unified online and in-store balance.

A native or integrated solution is usually preferable when it supports secure tokens, partial redemption, refunds, balance checks, and synchronization with Counterpoint. A standalone spreadsheet may help with reconciliation, but it is not a suitable long-term redemption system. Manual lookups create delays and increase the possibility of duplicate use.

Replacement cards may be appropriate when the legacy data is incomplete or the new platform cannot accept the original numbering format. In that case, map every old card to a new identifier, preserve the original balance, and mark the conversion in a secure cross-reference file. Do not simply issue replacement value without invalidating or controlling the original card.

Rebuild Gift Card Rules In The New Store

Configure the new ecommerce platform before importing live balances. Define whether customers can check a balance, apply a card to an order, combine multiple cards, use a card with a discount, or receive a refund back to the original stored-value account. These decisions should match the retailer’s published terms and the capabilities of the connected POS.

Check how the platform handles taxes, shipping, split payments, cancelled orders, partial captures, and order returns. A gift card might be authorized for one amount and captured for another, especially when inventory is fulfilled in stages. The integration must release unused authorization and restore value when an order is cancelled or refunded.

Use realistic catalog and checkout scenarios during configuration. A merchant selling beverages, for example, may use a beer category as one test area while validating age-restricted products, shipping rules, discounts, and gift card application. The category itself is not the stored-value system, but testing within representative shopping journeys can reveal conflicts between promotions, fulfillment, and payment logic.

Reconcile And Test Before Launch

Create a migration control total before importing anything. Add the balances of all active cards in the source report, then compare that figure with the total loaded into the new system. Reconcile by card as well as in aggregate; matching totals can conceal two cards with swapped or duplicated balances.

Run tests for full redemption, partial redemption, insufficient balance, zero balance, expired status, refunds, cancelled orders, and combined payment. Test both authenticated and guest checkout if the store supports both. At the register, verify that a card redeemed online shows the correct remaining balance in Counterpoint, and repeat the process in the opposite direction.

Keep a small group of staff or trusted customers in the pilot. Ask them to check balances, complete purchases, and review receipts on different devices. Capture transaction IDs and screenshots for every exception so the implementation partner can correct the configuration before public launch.

Establish Customer And Staff Controls

Customers need clear instructions about whether their existing card number, PIN, or email address will continue to work. If the migration changes the redemption process, explain how to access the new balance checker and what information support staff may request. Avoid asking customers to email full card numbers or PINs.

Store associates should have a short escalation procedure. It should cover mismatched balances, unreadable cards, duplicate records, expired certificates, failed online redemptions, and requests for refunds. Staff must know when they may perform an adjustment and when approval from a manager or finance team is required.

Use these operational recommendations during rollout:

• Assign one owner for gift card reconciliation and one backup owner.
• Lock manual balance adjustments behind role-based permissions.
• Keep daily reports of issued, redeemed, refunded, and adjusted value.
• Review exceptions against the archived source record before changing a balance.
• Reconcile the first several weeks of activity more frequently than normal.

Security deserves the same attention as accounting. Use tokenized or masked card data where possible, restrict exports, enable administrator multi-factor authentication, and set retention rules for migration files. A gift card balance can be spent like cash, so access to the data should be treated as access to a payment instrument.

Put The New Process Into Practice

After launch, monitor gift card transactions as a separate workstream rather than assuming they will follow ordinary order behavior. Compare daily issued and redeemed totals with the new platform, POS, and accounting records. Investigate unusual spikes, repeated failed attempts, negative balances, and large manual adjustments promptly.

Keep the legacy archive available for the period required by the retailer’s accounting, legal, and customer-service policies. It should be secured and read-only, with access logged. Once the retention period ends, dispose of sensitive exports according to the company’s data-destruction procedure.

A successful transition gives customers continuity while giving the retailer stronger control over stored value. Finalize the balance reconciliation, complete live-channel testing, train support staff, and publish the updated redemption policy before directing customers to the new store. Taking those steps turns a platform change into a controlled migration rather than a source of unresolved gift card liability.