← Internal Portal RetailFlow Internal INTERNAL

Legacy POS & Inventory Systems: Integration Feasibility

IT Note · Office of the CIO · 24 February 2026

Initiative: Inventory Optimisation Author: M. Kim

To: Dr. Priya Sharma, Inventory Optimisation working group
From: Marcus Kim, Chief Information Officer

Priya asked IT for a frank assessment of what our legacy estate can and cannot feed an AI forecasting platform. Short version: the data exists, but getting it out cleanly and frequently enough is the hard part.

The estate

SystemVendor / ageIntegration surface
Point of SaleRetailMaster, deployed 2014No public API; nightly flat-file export only
Inventory / stock controlStockTrak, deployed 2011Direct DB read possible; no documented schema
PurchasingMix of StockTrak + spreadsheetsLargely manual
OnlineShopify PlusFull REST/GraphQL API, no concerns

What is feasible

What is not feasible (without significant work)

Caution: StockTrak is out of vendor support as of mid-2024. Any extraction we build is unsupported and undocumented. We have one person, Raj Patel, who knows its schema; that is a key-person risk.
Note: I support Priya's single-category pilot. It lets us validate the nightly extraction and SKU reconciliation on a small slice before we attempt anything estate-wide. A full POS replacement is a separate, larger conversation for FY27.

IT can have the StockTrak replica and a Shopify feed standing in a staging environment within roughly six weeks of go-ahead.

Marcus Kim, Chief Information Officer

Fictional company. RetailFlow is a teaching scenario for Curtin University executive education, not a real business.