Cron jobs for automated inventory reports in your new system

Inventory reporting used to be a quiet background task when NCR Retail Online was running your store. With that platform now discontinued, many Australian retailers have moved across to Magento or WooCommerce through NCR Counterpoint partners, and the responsibility for scheduling recurring stock jobs sits squarely with you. Cron jobs, the small scheduled commands that tell a server when to run a script, become the engine behind your daily, weekly and monthly inventory reports.

The good news is that cron is straightforward once you understand the moving parts. A well-written cron job can pull stock counts from your point-of-sale system, format them into a spreadsheet or email, and deliver the file before your Sydney or Melbourne store opens its doors. What follows is a practical walkthrough of how to set that up, what to schedule, and how to keep the reports aligned with local obligations such as GST, BAS and Australian Consumer Law record-keeping.

Understanding cron jobs in a post-migration retail stack

A cron job is essentially a line of text in a configuration file that tells the operating system to run a specific command at a specific time. On Linux servers, which most Magento and WooCommerce hosting plans run on, this file is called crontab. Each entry contains a schedule expressed as five fields (minute, hour, day of month, month, day of week) followed by the command to execute.

For retail inventory work, the command usually points to a PHP, Python or shell script that queries your database or API, calculates stock-on-hand figures, and writes the result somewhere useful. The script can be as simple as a curl call to your own endpoint, or as elaborate as a multi-warehouse reconciliation routine. The cron daemon then fires that script on the schedule you set, without anyone needing to click a button.

Many retailers worry they will lose the polished reporting they once enjoyed after moving off NCR Retail Online. A reliable cron setup can replicate and even improve on the original behaviour, and revisiting replicating NCR Retail Online features helps decide which reports are worth automating first.

Comparing platform options for cron-based inventory automation

Before writing a single line of script, it helps to know how your new platform handles scheduled tasks. Magento and WooCommerce each ship with their own cron implementations, and the hosting choice matters as well.

If you are running a single boutique store in Brisbane or Adelaide, WooCommerce with a managed host will keep things tidy. Larger chains with several storefronts across NSW and Victoria typically get more from Magento's native scheduler, especially when integrated with NCR Counterpoint for inventory sync. A practical step-by-step Magento migration guide is worth reading if you are still weighing up which direction to take.

Preparing your hosting environment in Australia

Pick a hosting provider with data centres in or near Australia to keep latency low for your admin panel and API calls. Local providers such as Servers Australia and VentraIP, along with international players that maintain Sydney points-of-presence like AWS, Google Cloud and Azure, all meet this bar. Whatever you choose, confirm that cron access is enabled on your plan, since some shared WooCommerce hosts restrict it.

Set your server timezone to Australia/Sydney or Australia/Melbourne rather than UTC. This makes schedule lines easier to read and matches the trading day your team actually lives by. If you operate primarily in Perth, you may prefer Australia/Perth, but most multi-state retailers standardise on AEST/AEDT because Queensland, NSW, the ACT, Victoria and Tasmania line up with it for most of the year. SSH access should be locked down with key-based authentication and IP restrictions before you start adding jobs to the system.

Writing a cron script that pulls real-time stock data

Start by identifying the data source. If your new ecommerce platform is fed by NCR Counterpoint, the script will likely query the Counterpoint API or its underlying SQL database for current stock levels per SKU and per location. For Magento, the script can use the built-in inventory API; for WooCommerce, the wc-stock function and a custom endpoint both work well.

A typical PHP script would open a database connection, join products with stock items, format the result as CSV, and email it to a distribution list or upload it to S3. Keep the script idempotent so running it twice does not duplicate rows, and log everything to a file such as /var/log/inventory-report.log. That log will save you hours when something goes wrong at 2am on a Sunday before the Boxing Day rush.

Schedule the script with a crontab entry that reflects your reporting cadence. A common starting point is:

15 6 * * * /usr/bin/php /var/www/html/reports/daily-stock.php

That line runs the report at 6:15am every day, late enough that overnight Counterpoint syncs have settled but early enough that store managers in Hobart or Darwin see it with their morning coffee.

Scheduling reports around local time zones and trading peaks

Australian retail has its own rhythm, and your cron schedule should respect it. EOFY stocktakes on 30 June, the Black Friday and Cyber Monday weekend in late November, and the post-Christmas Boxing Day sales all generate spikes in stock movement. A pre-dawn inventory snapshot on each of those days gives you a clean baseline before customers start shopping.

For GST-registered businesses, a monthly report aligned with your BAS lodgement cycle is also useful. Most Australian retailers lodge BAS quarterly, so a cron that runs on the first business day of each new quarter and produces a stock-on-hand summary makes reconciliation far easier. Pair this with a weekly low-stock alert that runs every Monday at 7am AEST, giving category managers time to reorder before the weekend trade in Perth or Brisbane picks up.

Remember daylight saving. AEDT runs from early October to early April, while Queensland, Western Australia and the Northern Territory stay on AEST, ACST and AWST respectively. With your server set to Australia/Sydney, prefer wall-clock times like 6:15am rather than UTC offsets so a single schedule behaves sensibly year-round.

Meeting GST, BAS and ATO compliance through automation

Stock reports are not just operational tools. Under Australian Consumer Law and ATO record-keeping rules, you need to keep auditable inventory records for at least five years. A cron job that drops a dated CSV into a write-once bucket such as Amazon S3 Glacier or a local NAS with snapshots gives you that audit trail automatically.

If you sell taxable goods, the report should also include the GST component per line, so finance teams can reconcile input tax credits on stock purchases. Some retailers extend their inventory script to flag any SKU whose purchase price has changed by more than 10 percent since the previous report, which helps catch supplier cost errors before they flow into a BAS. Combining the inventory export with a separate sales export gives your accountant everything needed to lodge on time through the ATO's business portal. For multi-store operators, segment the report by location with a separate worksheet or CSV per store in Sydney, Melbourne, Brisbane, Perth and Adelaide.

Monitoring, logging and troubleshooting cron output

A cron job that silently fails is worse than no job at all, because you believe the report is being generated when it is not. Always log to a file, and have a separate watchdog that pings you if a report file is missing or older than expected. A simple approach is a second cron that runs an hour after the main job and checks the output file's mtime; if it is stale, it sends an SMS via Twilio or a Slack message to your operations channel.

Common failure points include database credentials that expire, PHP version mismatches after a host upgrade, and disk space running out during peak periods. Check disk usage before every major sales event and keep at least 20 percent free on the partition that stores your reports. If you find that wp-cron in WooCommerce is unreliable under low-traffic conditions, disable it from WordPress and drive it from the system crontab instead, which is far more predictable for retailers trading across Australian time zones. The simplest habit that keeps everything running is a five-minute weekly review of your log files; glance at the tail of inventory-report.log each Monday morning, confirm the last run timestamp, and small issues get caught long before they become stock-count surprises during a busy trade period.

Start with one script, one schedule and one inbox, and let the cron daemon do the heavy lifting while you get back to running the shop.