Retail systems / Data / Operator workflow

The counter deserved a better system.

Moving beyond an older Arabic Access-based POS, with a simpler way to manage product data.

Implemented work2026

An older Arabic Access-based POS had become the starting point for a broader retail-system change. The work was to migrate the catalogue into Aronium without losing control of the data—and make product changes easier for the people handling them every day.

Move the operation, not just the files

The larger migration, as described by the project operator, began with exporting data from an older Arabic Microsoft Access-based POS, cleaning it and preparing it for Aronium. Hardware practicality, cashier usability, user permissions and safe product mapping were part of the system change—not afterthoughts.

Fewer steps between a product and its record

A collaborative, local browser-based product auditing tool provided a simpler path to review and prepare bulk edits than handling individual items one by one inside the POS. Staff could work through products and produce structured changes for reconciliation with Aronium. The documented path uses checked export and import steps; a continuously running automatic sync service is not independently established.

881records in a reviewed export
170existing prices changed
142new product records added

Separate what can change from what must remain

A later, documented import passed through a one-row pilot, distinct update and new-product batches, held records and comparisons against SQLite snapshots. The compared databases support 170 price changes and 142 additions while preserving existing documents and payment rows. Uncertain stock and product identities were not quietly treated as clean data.

Repair the unexpected, without resetting the business

Three duplicate barcode assignments later stopped Aronium at startup. Rather than replacing the whole database, the response isolated the conflict, compared copies, checked integrity, backed up the live state and applied a narrowly scoped repair. The operator reported that the POS reopened. Later cleanup reversed unintended tax-field changes; anomalous stock values still required separate attention.

What the evidence can carry

The legacy migration and staff workflow come from the project operator's first-person account. The audited export, database comparisons, import files, logs and checkout screenshot support a specific later stage. This was collaborative work; the source code and exact division of authorship of the local web app have not been recovered. No formal client acceptance, automatic live synchronization or complete physical inventory audit is claimed.

Work and tools Microsoft Access legacy data, Aronium, local browser-based auditing, product mapping, CSV workflows, SQLite verification, user access, PowerShell safeguards and cashier-facing review.

Original client files, barcodes, commercial prices and staff data are omitted. The point here is the migration and the operating method, not a claim to own every component of a collaborative system.