Inventory reports to run before finalizing migration

Migrating an ecommerce operation is more than moving product records from one platform to another. The new store must inherit reliable stock quantities, accurate product details, usable order history, and the business rules that keep online and physical sales aligned. A report-driven review gives retailers evidence that the data is ready before the final export and cutover.

This is especially important for businesses moving away from NCR Retail Online after its discontinuation. A transition to WooCommerce, Magento, or another supported platform can preserve continuity, but only if the source data is examined carefully. Reports reveal duplicate products, inactive SKUs, unexplained quantity differences, and other issues that may remain hidden in a routine data export.

The strongest migration process creates a baseline in the existing system, compares it with the transformed data, and repeats the checks after import. Inventory reporting should cover more than current stock: it should also explain how products sell, how items move between locations, and where financial or operational risks may appear.

Establish a complete inventory baseline

Start by exporting a current inventory valuation report. This should show every active and inactive item, SKU, description, quantity on hand, unit cost, retail price, extended cost, and inventory location. Save the report in a durable format such as CSV or PDF, then record the date and time it was generated.

The valuation report provides the main control total for migration. Add the extended inventory cost and count the number of products and variants. These figures can later be compared with the transformed source file and the imported catalog. If the totals differ, the team has a specific discrepancy to investigate rather than relying on visual inspection.

Run the report after posting all pending receipts, transfers, adjustments, returns, and sales transactions. A baseline generated while transactions are still waiting to be finalized will give the migration team inaccurate quantities and could create avoidable reconciliation work.

Clean the product and SKU master

A product master report should identify every sellable item and its relationships. Include SKU, barcode, product name, brand, category, variant attributes, supplier, tax class, price, cost, weight, dimensions, and status. For products with variants, confirm that each size, color, or configuration has a unique child SKU.

Pay close attention to duplicate identifiers. Two products with the same barcode, two records sharing a SKU, or variants with inconsistent naming can cause an import to fail or merge unrelated inventory. Search for blank SKUs, missing barcodes, unusually long descriptions, invalid characters, and products assigned to obsolete categories.

The migration guidance for WooCommerce can help frame decisions about which catalog fields and historical records should move. Even when a partner handles the technical import, the retailer remains responsible for confirming that the product hierarchy reflects real merchandising needs.

Measure stock accuracy and movement

An inventory movement report shows why the current quantity exists. Run it for a meaningful period, such as the previous twelve months, and include sales, receiving, returns, transfers, adjustments, write-offs, and manual corrections. This report is useful for finding items whose stock levels look plausible but are supported by an unreliable transaction history.

Compare movement totals with physical counts and accounting records where possible. Large unexplained adjustments may indicate damaged goods, receiving mistakes, unrecorded transfers, or staff procedures that need attention before the new system goes live. Migration can transfer the quantity, but it cannot repair an inaccurate process by itself.

A low-stock or reorder report should be saved at the same time. Capture reorder points, preferred suppliers, minimum order quantities, lead times, and replenishment status. These values may not map directly into the destination platform, so documenting them separately protects purchasing operations during the transition.

Compare the reports that control risk

Several reports should be reviewed together rather than treated as isolated exports. The inventory valuation total should agree with the quantity and cost information in the product master. The movement report should explain material changes in the valuation. The low-stock report should identify products whose replenishment settings are present and meaningful.

Use the following comparison to determine which checks deserve priority during migration preparation:

Export reports using identical date ranges and location filters whenever possible. A comparison becomes misleading when one file includes all stores and another covers only the ecommerce warehouse. Keep a record of every filter, grouping, and exclusion so that another person can reproduce the results.

Review demand, returns, and reserved stock

A sales-by-SKU report supports decisions about migration sequencing and testing. Identify fast-moving products, seasonal lines, products with no sales, and items that sell only through a physical store or a particular online channel. These segments help the team choose representative products for import validation instead of testing only a handful of convenient examples.

Review sales history separately from current availability. A product may show strong demand but have zero stock because it is discontinued, backordered, or awaiting a purchase order. Flag these distinctions before importing inventory statuses, since a simple in-stock or out-of-stock value may not represent the intended customer experience.

Returns, exchanges, damaged items, and negative inventory deserve their own report. Reconcile open returns and pending refunds with the order system, then decide whether they should migrate as transactions, be closed in the old platform, or be documented for manual handling. Carrying unresolved exceptions into a new system can distort stock counts and customer service records.

Reserved, committed, or allocated inventory must also be identified. Stock held for open orders, layaways, bundles, transfers, or wholesale customers may not appear as freely available quantity. Confirm how the destination platform calculates available-to-sell stock and map the old status to the new rule before opening the store.

Validate locations, channels, and security

Multi-location retailers should run a location-level stock report showing quantity on hand, available quantity, committed stock, and transfer activity for every store or warehouse. Check location names and codes against the destination platform, including spelling, time zones, tax settings, and fulfillment permissions.

Run channel-specific reports if the business sells through a website, marketplace, point-of-sale system, or wholesale portal. The same SKU may have channel-specific pricing, quantities, or publication rules. Comparing channel totals can uncover overselling risks caused by delayed synchronization or duplicate product listings.

Access control should be reviewed alongside reporting. Identify who can view cost, edit quantities, approve adjustments, and export customer or order data. The main NCR Retail Online resource provides context about the platform’s retail and ecommerce capabilities, while the migration team should document which users and permissions must be recreated in the replacement system.

Convert findings into migration controls

After reviewing the reports, create a discrepancy log with the SKU, location, issue type, source value, expected value, owner, and resolution date. Group issues into data cleanup, business-rule mapping, transaction reconciliation, and post-import verification. This makes unresolved work visible and prevents a vague “data review” task from delaying the cutover.

Use a short, report-based control list before approving the final migration:

• Reconcile product count, SKU count, and inventory valuation totals.
• Resolve duplicate, blank, inactive, and incorrectly mapped SKUs.
• Confirm available, committed, damaged, and in-transit quantities by location.
• Preserve reorder points, supplier details, pricing rules, and variant relationships.
• Export open orders, returns, adjustments, and exception records for agreed handling.
• Repeat the same reports after import and compare totals using identical filters.

Schedule a final data freeze with clear ownership. Record the last transaction time in the old platform, complete the final export, and prevent untracked edits until the new store is validated. After import, test stock deductions, returns, transfers, product updates, and order synchronization with realistic scenarios; the user acceptance testing practices offer a useful framework for making those checks consistent.

The migration should be approved only when the destination reports can explain the same inventory position as the source reports, with documented exceptions for anything intentionally changed. Run the baseline exports, reconcile the numbers, and use the results to authorize a controlled cutover with confidence.