A register that suits a shop floor
The retail POS screen is a product grid with a barcode/SKU field and category filters — set once as the tenant's default counter.
Farexa runs the checkout, the stock behind it, and the reports that explain the day — so a barcode scanned at the register is already reflected in the low-stock watchlist and the branch's numbers.
The recurring problem in retail isn't the till. It's that the till is an island. Stock lives in a spreadsheet that's accurate on Monday, the accountant rebuilds the day from a spike of receipts, and nobody can say what a branch actually made until somebody sits down with a calculator. Every one of those gaps is a place where the number quietly stops being true.
Farexa closes them by refusing to separate the pieces. The register is a sales order, so it draws on the same stock records as goods receipts and transfers. The customer attached at checkout is the same customer record the rest of the platform knows, carrying their order history and outstanding balance. The coupon the cashier scans was created once and validates against the platform's own rules.
What that buys a branch manager is a day that reconciles itself. Sales filter by cashier and by branch. The inventory dashboard shows the low-stock watchlist and what's already out of stock, against stock the counter has actually been depleting. And when the product mix drifts, dead stock gets written off as a recorded adjustment with a reason on it, rather than quietly disappearing from a spreadsheet.
The retail POS screen is a product grid with a barcode/SKU field and category filters — set once as the tenant's default counter.
Checkout draws on the same inventory records as stock-in, transfers, and adjustments, so there is no nightly reconciliation between till and stock.
The inventory dashboard surfaces what is running down and what has already run out, ranked by available quantity.
Run more than one shop with its own stock, move goods between them as recorded transfers, and keep branch context on the reporting.
Build coupons and promotions centrally; the counter enforces them instead of trusting the cashier's arithmetic.
Attach a sale to a customer and it joins their order history and balance — and their statement.
Filter the day by who rang it up and where, then export to Excel, CSV, or PDF for whoever needs it.
Write off dead stock as an inventory adjustment with a reason attached, so shrinkage is a recorded decision rather than a gap.
Yes. A sale at the register is a sales order against the same inventory records used by goods receipts and transfers, so the low-stock watchlist reflects what the counter has been selling. There is no separate end-of-day sync between till and stock.
Yes. Branches each carry their own stock, goods move between them as recorded transfers, and sales reporting keeps branch context — so you can read one shop's day or compare them.
Yes. Roles decide what a cashier can reach, and refunds sit behind their own permission. Coupons and promotions are defined centrally and validated at the counter, so discounts follow the rule rather than the cashier.
Sales filtered by cashier and by branch, refunds, and the inventory dashboard's low-stock and out-of-stock watchlists. Reports export to Excel, CSV, or PDF.
Yes. VAT is calculated per line against the tenant's tax settings, and the same order prints as an 80mm thermal receipt or a full A4 tax invoice carrying your business name, address, and contact details.
Book a walkthrough with your own products, branches, and tax rules, and see the day reconcile without a spreadsheet.