Skip to main content
Flowray.
Menu

Case study

FixyJO

FixyJO helps repair shops manage work across branches. Flowray designed and built it, and handles its operation. Shops in Jordan use it to track each device from drop-off to collection, with technician commissions, stock, and branch accounts linked to the same record.

FixyJO owner dashboard showing a live dispatch panel titled Decisions first, counts for aged repairs and technician balances, and a repair pipeline reading Received 6, Diagnosed 1, In repair 0, Ready 2, Picked up 43.
Owner view See what needs your attention across branches, including overdue repairs and technician balances.View full-size image ↗
FixyJO technician home showing a tab of 40 JOD owed to the shop, labelled as the same number the owner sees, above four open repair jobs with status chips.
Technician view A view of repair jobs and balances for the technician doing the work.View full-size image ↗

One number, two roles

The owner's dashboard shows Techs owe you — 40 JOD. The technician's home shows My tab — 40 JOD, labelled as the same number the owner sees.

The owner and technician see the same balance in their own views of the system.

The same FixyJO owner dashboard rendered in Arabic with a fully mirrored right-to-left layout, showing identical figures.
Arabic, right to left The same screen and figures, arranged for reading in Arabic. Both languages are part of the interface design.View full-size image ↗
Operation
Multi-branch device repair—intake, diagnosis, parts, handover
Problem
There was no single reliable record for branch stock and technician balances.
System
A repair-management platform in Arabic and English, used daily

Inside the product

  • Repairs and decisions that need the owner’s attention across branches.
  • Technician jobs and balances in the same system the owner uses.
  • Arabic and English interfaces designed as part of the same product.
Open fixyjo.comDiscuss a Similar Project