How to automate daily product feeds from Counterpoint to your new store

When NCR announced that Retail Online was being discontinued, thousands of Australian retailers suddenly found themselves staring down a barrel of stock chaos. With shops from Perth to Cairns still ringing through Counterpoint, the question became less about whether to migrate and more about how to keep every barcode, variant, and price moving into the new ecommerce platform without manual spreadsheets eating up the arvo.

Daily product feeds sit at the heart of that migration. A feed is the steady stream of records that tells your online storefront what is on the shelf, how much it costs in AUD, and whether that limited-edition release will ship before the weekend rush. Get the feed right and your team can focus on seasonal campaigns for Boxing Day, EOFY, or back-to-school rather than chasing down which SKU is missing in Queensland. Get it wrong and customers see ghost stock, oversold items, or a flat-out broken store.

Automating this flow means choosing the right bridge between Counterpoint and the platform you have moved to. Before picking between Magento and WooCommerce, it helps to read up on NCR Online vs Magento so the daily feed does not hit unexpected walls. The rest of this piece walks through the practical side of that bridge, from scheduling and file formats to handling Australian-specific quirks like GST rounding and state-based freight rules.

Understanding daily product feeds and why they matter

A daily product feed is a scheduled export of every sellable item in your inventory system, formatted for another piece of software to read. In retail, feeds typically use CSV, XML, or JSON files listing product names, SKUs, prices, stock counts, categories, and images. The receiving platform imports that file on a timer, often once or twice a day, so the website always reflects what is actually sitting on the shop floor.

For Australian retailers juggling both bricks-and-mortar and online channels, the daily cycle matters because trading hours stretch across multiple time zones. A Brisbane store owner pushing a price update at 8 am AEST expects it to live on the Sydney and Melbourne sites within minutes, not hours. Without automation, that owner would be exporting CSVs by hand every morning before brekkie while serving the first customers.

The smarter approach is to let software handle the heavy lifting. A scheduled feed runs even when the manager is at the beach for Australia Day or dealing with a public holiday in their state. It captures changes from purchase orders, stocktakes, supplier returns, and markdowns, then delivers a clean, structured file the ecommerce engine can absorb without complaint. The result is fewer mismatches, happier customers, and a calmer inventory team.

Mapping your Counterpoint data to a new storefront

Before any feed can fire, the data inside Counterpoint needs to be mapped to the fields your new platform expects. This step is where many retailers burn time, because the default fields in a Magento or WooCommerce setup rarely line up with what Counterpoint has stored for years. Common mismatches include category structures, tax classes, attribute sets, and image URLs that point to a Windows share rather than a web-accessible folder.

Start by auditing the master list in Counterpoint and tagging which fields must travel with the product. In Australia, that almost always means GST-inclusive pricing, ACCC-compliant product descriptions, and accurate weight and dimension records so Australia Post and courier services can calculate freight correctly. A boutique in Adelaide selling homewares, for instance, needs the cubic weight exported too, otherwise regional customers in Darwin or Hobart end up with shockingly expensive shipping at checkout.

The next step is choosing field aliases. If Counterpoint stores the barcode as UPC and your new store expects EAN, build a small translation table. The same goes for supplier codes, season codes, and any custom flags you have used for in-store promotions. The cleaner this map is, the smoother the daily feed runs, and the less manual cleanup the team has to do when items first appear online.

Choosing the right automation method

Common automation paths:

• Direct API-to-API connector installed by your Counterpoint partner, usually a recurring licence with ongoing support.
• Middleware platforms such as a dedicated iPaaS solution that handles scheduling, transformation, and error logging.
• Custom scripts written in Python or PowerShell that pull from Counterpoint, transform the file, and push it to the new store via SFTP or REST endpoints.

A side-by-side view helps clarify the choice for an Australian retailer weighing cost against control.

For a Sydney-based apparel store running 8,000 SKUs across two locations, the API connector route tends to pay for itself within a quarter because staff no longer spend their mornings reconciling stock. A regional grocer in WA with only a few hundred lines, by contrast, may find a small script on a back-office server more than adequate.

Scheduling, time zones, and Australian retail quirks

Australia throws a few curveballs at feed scheduling that overseas guides rarely mention. The country spans three standard time zones and five during daylight saving transitions, so a 2 am export in Sydney lands at 3 am in Melbourne and 1 am in Brisbane. Many ecommerce platforms batch their import jobs at specific UTC offsets, and a poorly timed feed can clash with other maintenance work.

Another local wrinkle is the End of Financial Year rush on 30 June. Stock levels spike, clearance pricing runs wild, and feed jobs often double in volume as items move into and out of sale categories overnight. Building slack into the schedule, or running an extra feed window during late June, prevents the dreaded 503 error that crashes a feed mid-upload when the boss is trying to clear the warehouse before EOFY.

Public holidays also need handling. If your retail operation closes on ANZAC Day or the Melbourne Cup public holiday in Victoria, the feed should still run so the website stays accurate for online shoppers, but staff should not be expected to babysit it. A well-designed automation pipeline sends a summary email or Slack notification to the duty manager the moment an import fails, which is far better than discovering the problem three days later when the customer complaints roll in.

Keeping the feed healthy after launch

Going live is only the beginning. A daily feed will quietly degrade over time as Counterpoint fields are renamed, new product lines are added, and your ecommerce platform updates its schema. The trick is to keep watch without watching it manually.

Useful monitoring habits:

• Logging every feed run with start time, finish time, and row counts.
• Comparing yesterday's stock on hand to today's, then flagging any item that dropped by more than a set threshold.
• Tracking rejected rows so you can fix the source data rather than patching the file downstream.
• Reviewing image URLs quarterly because local file shares sometimes get reorganised during store refits.

Retailers in Australia also need to think about compliance and consumer law. The Australian Consumer Law sets clear rules about pricing display, lay-by terms, and refund statements, so the feed should never overwrite a legally required disclaimer just because a field looks similar. A simple checklist at the start of every quarter, comparing the live store against the latest ACCC fact sheets, keeps the storefront honest and the business out of trouble.

A reliable daily product feed turns the back office into something that runs itself, freeing the team to focus on seasonal campaigns, customer service, and the everyday realities of running a shop in a country as spread out as Australia. For retailers still mapping out the move away from the retired platform, the NCR Retail Online site still lists the partner directory that handles the heavy lifting on the integration side. The shop that wins the next holiday rush is the shop that gets the feed right first.