Ibnu Sina Care Sdn Bhd supplies medical equipment through several commercial arrangements: direct purchase, rental, rent-to-buy and supported payment arrangements. Its product areas include medical beds, wheelchairs, oxygen concentrators, ResMed/CPAP equipment, sleep tests, jaundice lamps, Ozempic and accessories.
Unlike a one-off service business, an Ibnu Sina order can continue after delivery. Rental and rent-to-buy orders may generate recurring cycles, equipment remains individually traceable by serial number, and later service, exchange, pickup or repossession activity can occur against the same customer relationship.
| Item | Ibnu Sina |
|---|---|
| Business model | Medical-equipment sale, rental, rent-to-buy and services |
| Legal company | Ibnu Sina Care Sdn Bhd; detailed legal/contact/bank fields remain placeholders in the initial branch seed |
| Active branches | Shah Alam HQ (SA), Sentul Showroom (STL), Johor Bahru (JB), Penang (PG) and Melaka (MK) |
| Main commercial record | Order |
| Main fulfilment record | Trip Log |
| Defining workflows | Serialised equipment movement, delivery/pickup and recurring rental collection |
| Shared identity grant | sales.ibnu-sina.view unless overridden by environment configuration |
| Historical evidence | AppSheet order analysis records 11,779 rows through 17 September 2026 |
| Step | What happens | Main owner |
|---|---|---|
| 1. Enquiry | Find or create one shared customer, normally using phone lookup | Sales |
| 2. Offer | Select the product type, commercial offer and deal type; prepare a quotation when required | Sales |
| 3. Order intake | Create a Draft order with its customer, address, lines and delivery intention | Sales |
| 4. Confirmation | Pass the confirm gate; the permanent customer-facing order number is minted here | Sales / authorised confirmer |
| 5. Preparation | Reserve or prepare equipment, procure missing stock and stage the Trip | Warehouse and Operations |
| 6. Fulfilment | Assign a driver and lorry, or an operating branch for walk-in work; record proof and serial movement | Operations, Driver or Branch |
| 7. Delivery state | The first completed Hantar Trip moves the Order from Confirmed to Delivered |
System |
| 8. Money | Record payments; Account verifies them separately and manages recurring cycles where applicable | Sales, Driver, Account |
| 9. Ongoing service | Handle collection follow-up, service requests, exchange, warranty, sleep-test or return work | Account and Operations |
| 10. Closure | Close only after commercial, fulfilment, stock and money obligations are resolved | Authorised owner |
One Order may have several Trips. A Trip is one fulfilment movement or visit; it is not the whole commercial relationship.
Role names are templates for module permissions, not fixed job titles. Work lists make a person selectable for field work without granting portal permissions.
| Template or work list | Main responsibility |
|---|---|
| Sales | Customers, quotations, orders, first payment, SGS and sleep-test intake |
| Operations | Trips, assignment, staging, handover, counter cash and service/exchange work |
| Account | Payment verification, recurring payments, refunds, itemisation and collections |
| Manager | Wider operational oversight and configurable approvals |
| Boss | Broad read/management oversight according to the permission grid |
| Driver work list | Makes a person selectable for driver work and opens driver Ops screens |
| Warehouse work list | Opens warehouse Ops screens and warehouse work queues |
| Administrator | Locked system-level access, users, roles, branches and integrations |
| Record | Meaning |
|---|---|
| Customer | One person or organisation shared across branches; phone is the main lookup identity |
| Quotation | A proposed commercial offer and its lines before order creation |
| Order | The commercial agreement, totals, customer-facing number and lifecycle |
| Order Line | A sold, rented or service line with verification/accounting state |
| Trip | One delivery, pickup, exchange, service or walk-in fulfilment event |
| Inventory Item | Product master record, including batch or serial tracking behaviour |
| Stock Unit | One individually identified unit and its current lifecycle, zone and condition |
| Stock Movement | Append-only evidence of where stock moved and why |
| Payment | One receipt against an Order; collection and Account verification are separate |
| Recurring Cycle | One scheduled amount due for a rental or rent-to-buy period |
| Refund | Money leaving the business through request, approval, processing and payout |
| Service Request | Post-sale or operational work attached to an Order or asset context |
The commercial catalogue supports BUY, RENT, RENT_TO_BUY and EZBELI_CC. The chosen offer controls pricing and accounting mappings. Rental and rent-to-buy can create recurring schedules after the delivery trigger.
| Trip type | Assignment | Typical stock direction |
|---|---|---|
| Hantar | Driver and lorry | Equipment goes out to the customer |
| Angkat | Driver and lorry | Equipment returns from the customer |
| Exchange | Driver and lorry | One unit returns and another goes out |
| Service | Driver and lorry | Field service; serial/fault rules depend on the work |
| Walk in | Branch | Customer is served at a branch |
| Walk in - Collect | Branch | Customer collects equipment |
| Walk in - Return | Branch | Customer returns equipment |
Inventory is owned inside the Ibnu Sina application. The movement ledger is the history of truth; current stock-unit state and batch on-hand totals are derived views or caches.
Each serialised unit has three separate dimensions:
A lorry can act as a stock location. Warehouse loading moves a unit from warehouse to lorry; driver handover moves it from lorry to the customer. Returns reverse the physical direction and may route the unit into checking.
| Owned by Ibnu Sina Sales Module | Owned elsewhere |
|---|---|
| Customers, quotations, orders, trips, payments, recurring cycles, refunds, collections, inventory, procurement, warehouse checking, service requests, warranties, sleep tests, local roles and branch access | Utopia Hub identity and fleet source, OE gateway, Utopiaspace Ops client, AutoCount destination, PayEx service, legacy AppSheet/Google Sheets source and email/push providers |
| Need | Page |
|---|---|
| Compare the shared design | Component Map |
| Follow the complete journey | End-to-End Workflows |
| Understand a module | Feature Guide |
| Check system-wide controls | Cross-cutting Requirements |
| Check current readiness | Implementation Status |