Using Counterpoint’s Sales History to Forecast Online Demand After Migration

Moving from NCR Retail Online to Magento, WooCommerce or another ecommerce platform changes the way online orders are captured, but it does not erase the value of your existing retail data. Counterpoint sales history can provide a practical demand baseline when product records, customer behaviour and inventory processes are being rebuilt.

The useful goal is not to copy every historical figure into a new dashboard. It is to turn reliable transaction data into stock forecasts, replenishment rules and online merchandising decisions that suit Australian shopping patterns, delivery distances and seasonal events.

Why sales history matters after migration

A new ecommerce platform often begins with limited online data. Early reports may show page views, abandoned carts and orders, but they cannot yet reveal a dependable purchasing cycle. Counterpoint can fill that gap with years of store transactions, including sales volume, product variations, discounts and timing.

This history is especially valuable for retailers whose websites previously worked alongside physical stores. A customer may have bought an item at a Brisbane shop, reserved it online in Melbourne or collected it from a local branch. Combining those channels produces a clearer picture of total demand than treating the migrated website as a completely new business.

Historical data should still be treated as evidence rather than certainty. Product ranges, prices, suppliers and delivery promises may have changed since the original sale. Forecasting works best when old patterns are tested against current stock availability and recent online behaviour.

Build a clean Counterpoint baseline

Begin by exporting sales at a useful level of detail. Product code, variant, date, quantity, selling price, discount, location and channel are usually more useful than a single monthly revenue total. Include returns and cancelled transactions where possible, so the baseline reflects units actually sold.

Clean the catalogue before calculating demand. Match discontinued SKUs to their current replacements, standardise sizes and colours, and separate bundles from individual products. A blue shirt in several sizes should not be treated as one interchangeable item if the warehouse holds each size separately.

Flag periods that could distort the baseline. A supplier shortage, store closure, one-off corporate order or major clearance event can make a product appear more or less popular than it normally is. Keeping these notes beside the dataset allows the forecasting model to discount unusual results rather than blindly repeating them.

Turn history into demand signals

A simple starting point is average weekly unit sales, calculated over a representative period. Add a recent-weighted average when customer preferences have shifted, giving newer transactions greater influence than older ones. This is useful after a migration because the range and shopping experience may have changed.

Use separate signals for steady sellers, seasonal products and intermittent products. A basic average may work for phone accessories, while winter clothing needs a calendar adjustment and specialist equipment may sell only a few times each quarter. The forecast should describe the product’s sales rhythm, not force every SKU into the same formula.

Lead time also matters. If a supplier takes three weeks to deliver and the product sells eight units per week, the reorder point must cover expected sales during those three weeks, plus a safety buffer. That buffer can be higher for imported stock heading to Perth or regional Queensland, where freight delays can have a greater impact.

Adapt forecasts to Australian trading patterns

Australian retail calendars have their own demand spikes. Boxing Day promotions, end-of-financial-year sales and the weeks before Christmas can produce sharp changes in order volume. A forecast trained on ordinary weeks may understate demand for gifts, outdoor goods and electronics during these periods.

Weather and geography also affect purchasing. A cold snap in Melbourne may lift demand for heaters and winter clothing while northern Queensland remains in a different seasonal pattern. Retailers serving Sydney, Adelaide and Darwin from the same catalogue may need regional forecasts rather than one national average.

Include GST in pricing and margin analysis, while keeping unit demand separate from tax calculations. Customers generally see prices in Australian dollars and expect clear delivery estimates. Compare historical performance by state, store and fulfilment region when deciding whether a product should be stocked nationally, offered online only or assigned to selected locations.

Connect forecasts with fulfilment decisions

A demand estimate becomes useful when it changes what the business does. Set reorder thresholds, preferred supplier quantities and fulfilment rules from the forecast, then review those settings as new orders arrive. The objective is to keep popular products available without filling storage space with slow-moving stock.

Dropshipping can cover long-tail products that are expensive to hold locally, but it needs accurate availability and delivery information. Retailers planning this model can review dropshipping workflows as part of their migration process, particularly when Counterpoint records show occasional demand rather than consistent weekly sales.

Online availability should reflect real stock wherever possible. A product shown as available for immediate dispatch when it is sitting in a shop awaiting transfer can create cancellations and poor reviews. Decide whether store stock is eligible for ship-from-store, click and collect or local reservation, and make those choices visible in the new platform’s inventory rules.

Use category-specific forecasting controls

Different product groups need different assumptions. Replenishable goods can use recent unit velocity, while fashion needs size-level analysis and end-of-season markdown planning. High-value goods may require a lower safety stock but tighter supplier coordination because each excess unit ties up significant capital.

Automotive retail provides a useful example. Demand can depend on vehicle compatibility, service intervals and local fleet patterns, so a generic product forecast may be misleading. Historical category information and specialist context, such as the material in this automotive retail guide, can help teams distinguish genuine demand from sales generated by a particular fitment or workshop relationship.

Set minimum data thresholds before automating decisions. A product with only two historical sales should not receive the same replenishment treatment as an item sold every week for three years. Use manual review, supplier lead times and comparable products until the item has enough current evidence.

Measure forecast quality after launch

Forecasting should continue after the migration goes live. Compare predicted units with actual sales by SKU, category, location and week. Track bias as well as accuracy: a forecast that is consistently too low creates stockouts, while one that is always too high produces aged inventory and unnecessary markdowns.

Review the effect of promotions separately from ordinary demand. A discount may increase units without proving that customers will pay the standard price later. Record campaign dates and promotion depth in the reporting layer so future forecasts can recognise promotional uplift without treating it as permanent demand.

Useful operational checks include:

• Stockout rate for high-priority products
• Forecast error by category and sales channel
• Supplier lead-time variation
• Return and cancellation rates after launch

Teams can also review these signals every week:

• Products gaining demand through online search
• Stores with excess stock suitable for fulfilment
• Items affected by seasonal or regional events
• Orders delayed by inventory mismatches

A practical review cycle might run weekly for fast-moving products and monthly for slower categories. Keep a record of forecast changes, including the reason for each adjustment. This creates accountability and helps staff distinguish a genuine market shift from a temporary reporting anomaly.

The strongest migration process treats Counterpoint history as a foundation, not a finished answer. Import clean records, connect them to current catalogue and inventory data, then allow actual online performance to refine the model. For Australian retailers, the working rule is straightforward: forecast units by product and region, adjust for local seasons and supply lead times, and review the result against real stock every trading week.