For hospitals and medical supply companies
A supply request, from the moment it is raised to the moment it arrives
A hospital coordinator raises the request and the right supplier has it within seconds. Both sides track it and talk about it in one place until it closes — no chain of phone calls, no messages scattered across three apps, no paper to lose.
A demonstration. The stages and their colours are the product's own, not a drawing of them.
Every stage a request goes through, on both screens
- Draft
- Submitted
- Received
- Accepted
- Preparing
- On the way
- Delivered
How it works
The side that owns a stage changes it, and the other side sees it in the same moment — no page refresh, and no phone call asking where the order got to.
- 1
The hospital raises the request
Items, quantities, priority and department in one form. It stays a draft that nobody outside the hospital knows about until it is sent.
- 2
The supplier is told within seconds
The notification reaches the addressed supplier and nobody else — on screen and on the device — not everyone on the platform.
- 3
Both sides follow it to the close
Accepted, then preparing, then on the way, then delivered — with an expected delivery time, and a live location while the rep is sharing one.
Why this platform
Live, actually
A change reaches the other side over a channel belonging to that request, not by polling every few seconds. The message, the stage and the notification all land in the same moment.
Arabic first
The interface is Arabic right-to-left throughout, not a translation laid over an English product. English is one click away for whoever needs it.
Each organization's data is its own
The separation between organizations is enforced inside the database rather than in the interface, so no query can step around it — not through a bug, and not through anything else.
A record of every administrative change
Who changed it, what it was, what it became, and when. Readable by whoever holds the permission, and exportable.
What you get
Requests and their lifecycle
Defined stages and four priorities, with a response window per priority that each organization sets for itself.
A thread with two channels
One channel both sides read, and an internal one the other side never sees — and the difference is written on the message itself, not only coloured.
Attachments
Photos, documents, spreadsheets, video and audio, behind short-lived links that open only for the people on the request.
Delivery and tracking
An expected delivery time the supplier sets, and a live location the rep shares while on the road that is not stored afterwards.
Reporting and export
Response times against the deadline, per-supplier performance, and daily request volume — exported in a file that opens in Excel with Arabic intact.
Tags and search
A tag is created from use rather than from a settings screen nobody visits, and search reaches requests, tags and thread messages from any screen.
Two doors, one platform
Each side has its own entrance, its own screens and its own permissions.
For hospitals
Raise a request, follow it, and talk to the supplier on it.
- Raise a request with its items, priority and department
- Follow every stage live, through to delivery
- Talk to the supplier inside the request itself
For suppliers
Take requests in, prepare them, and deliver on time.
- Take in requests from the hospitals you work with
- Update the stage and the expected delivery time
- Talk to the hospital inside the request itself