The Dashboard summarises the current commercial and operational position. Treat every figure according to its date basis, branch filter and financial status. A recorded payment and a verified payment answer different questions.
- Search by phone before creating a new Customer.
- A Customer is shared across branches.
- A Customer can have several addresses.
- Customer detail connects Orders, contact actions and identity documents.
- Deleting means soft removal; historical Orders keep their relationship.
- Create, edit and send quotations using catalogue offers and quotation lines.
- Terms and validity belong to the quotation document.
- Effective expiry can be derived even when the stored status remains Sent.
- Conversion must preserve customer, branch, commercial offer and line information.
¶ Orders and intake
- Draft intake captures customer, address, product type, deal type, delivery intention and lines.
- The permanent order number is minted on Confirm, not when the draft is first saved.
- Order detail is the main workspace for Trips, lines, payments, refunds, service and audit context.
- Order states are Draft, Confirmed, Delivered, Closed and Cancelled.
- Order relationships support parent/child or linked external records without using a visible number as the database relationship.
The catalogue separates the physical product from the offer being sold:
| Record |
Purpose |
| Inventory Item |
Physical/product master |
| Catalogue Offer |
Sellable/rentable commercial configuration |
| Combo Component |
Product components included in a combination |
| Discount Policy |
Controlled discount rules |
| Control-account mapping |
Deal/category routing for accounting |
Catalogue reads support the Order and quotation pickers. Administrative inventory screens maintain the underlying item master.
¶ Trips and Trip Log
- View Trip queues by branch, type, status, assignment and date.
- Create delivery, pickup, exchange, service and walk-in Trips.
- Assign a Driver and lorry for road work, or a Branch for walk-in work.
- Upload proof, record serials, start, complete, postpone, hold, resume or cancel according to the state machine.
- Trip completion may cause stock movements, recurring schedules and the Order delivery transition.
- Audit history records material changes.
- Record Order payments and counter cash.
- Upload slips and supporting documents.
- Account verifies, flags, resolves, submits and exports through separate actions.
- Payment methods seeded include Cash, Bank Transfer, Cheque, PayEx, EzBeli CC, QR/DuitNow and E-Wallet.
- The AutoCount export action is not a completed external posting integration.
The Itemize queue is Account’s verification surface for Order lines. Lines can be verified, flagged, corrected/unlocked and posted. The current “post” creates internal state and outbox evidence only; it must not be presented as confirmed AutoCount acceptance.
- Request with recipient bank information, amount and reason.
- Manager approval must be independent from the requester.
- Processing and Paid are separate actions.
- Attach supporting and payout documents.
- Rejected, Cancelled and Paid are terminal.
- View rental/rent-to-buy cycles by branch, due date and status.
- Record and verify recurring receipts.
- Link receipts to the correct cycle.
- A cycle becomes Paid only when verified receipts cover the expected amount.
- Void future cycles when the underlying commercial obligation ends.
¶ Collections and defaults
The Collections page is a follow-up work list for overdue balances and recurring cycles. It records contact method, promised action and the next step. Default records support repossession booking, recovery and cure; they do not replace the underlying Order or payment history.
The Inventory area includes:
- Location-level dashboard and stock position.
- Item master and commercial fields.
- Serial-unit detail and movement history.
- Stock movements and transfers.
- Warehouse locations and lorry/mobile locations.
- Inbound stock, checking, repairs and adjustment.
- Driver, vehicle and warranty administration.
Checking handles returned or questionable equipment. A batch or serial is inspected, assigned a condition and moved to the correct zone. The movement is the correction; direct balance editing is prohibited.
- Supplier master.
- Purchase Order creation and line management.
- Partial and full goods receipt.
- Serial capture for serialised products.
- Receipt adjustments.
- Inventory movement created only by receipt.
¶ Transfers and repairs
Transfers move stock between controlled locations with source and destination acknowledgement. Repair records keep repair reason and state separate from stock location. Repair completion must create the proper movement/state change rather than merely closing a screen.
Warranty registrations associate a customer, item/serial and warranty period. Warranty handling is separate from the sales Order lifecycle so service history can continue after the original transaction.
Sleep Test is a first-class product/service area with its own record and intake routes. It is not merely a free-text Order note. Access follows the relevant Sales/module permissions.
Service Requests and Service Actions represent post-sale or operational work. They support request, scheduling and completion states and can trigger the appropriate Trip/service handling without changing historical sales records.
Portal notifications are stored locally and can be marked read. External push delivery is an integration concern. A notification failure must not undo a confirmed Order, Trip assignment or payment.
Settings covers:
- Users, invitations, roles and module permissions.
- Branch access and per-branch permission overrides.
- Work lists for Driver, Warehouse and other selectable participants.
- Branches and managed lookups.
- API tokens for OE/Ops.
- Legacy-sync health.
- Vehicle/fleet synchronisation.
The dedicated Ibnu Sina Ops slice provides:
- Driver Trip list, schedule and detail.
- Proof and serial capture.
- Field cash and pending receipt photographs.
- Preferred lorry and helpers.
- Warehouse queues, loading, returns, unit lookup, movements, checking, inbound and stock views.
This is a client of the Ibnu Sina module through OE. Its unfinished features are tracked on Implementation Status, not treated as missing portal modules.