This page compares Ibnu Sina with the 22 shared Sales Module components. As written means the shared purpose applies without an important business-specific change. Differs means Ibnu Sina uses the component with its own workflow. Partial means the component exists but an external connection or control remains incomplete.
| Count | State |
|---|---|
| 5 | As written |
| 16 | Differs |
| 1 | Partial |
| # | Component | State | Ibnu Sina |
|---|---|---|---|
| 1 | Identity, permission, record scope | differs | Shared Hub authentication plus local PBAC, five-branch access and work lists. Role templates are Sales, Operations, Account, Manager and Boss; Driver and Warehouse are work-list identities. The planned all/team record scope is not built. |
| 2 | Settings, numbering, configuration | differs | Product-type codes drive order-number suggestions. The permanent number is minted at confirmation, not draft creation. Branches, statuses, lookups, payment methods and API tokens are configurable. |
| 3 | Item master | differs | A medical-equipment catalogue connects commercial offers to inventory items, serial units, combinations, deal types, discount policies and AutoCount fields. |
| 4 | Chat platform link, lead source | as written | Lead/source values are lookup-driven. The repository does not establish a live ReplyBox or WhatsApp ingestion contract; direct intake remains the authoritative path. |
| # | Component | State | Ibnu Sina |
|---|---|---|---|
| 5 | Customer record, sales roles, quotation | differs | One customer is shared across branches and found by phone. Quotations carry medical-equipment offers and can be converted into orders. Quotation states include Draft, Sent and Expired, with effective-status logic. |
| 6 | Order and lifecycle | differs | Draft → Confirmed → Delivered → Closed, with Cancelled as terminal. Confirmation mints the permanent order number; first completed Hantar marks delivery. |
| 7 | Turning a lead into an order | as written | Order intake supports customer/address creation, commercial lines and draft saving. A dedicated intake request also exists for integration-oriented creation. |
| 22 | Service request | differs | Implemented as service requests and service actions for post-sale/operational handling rather than a generic undefined component. |
| # | Component | State | Ibnu Sina |
|---|---|---|---|
| 8 | Job and trip record | differs | Called a Trip. Seven trip types cover delivery, pickup, exchange, service and walk-in work. Trip lifecycle is separate from Order lifecycle. |
| 9 | Driver | differs | Driver is a work list, not a portal role. Driver-run Trips use a driver and lorry; branch-run walk-ins use a branch. Driver detail, preferred vehicle/helpers and fleet mirroring exist. |
| 10 | Scheduling and dispatch | differs | OE assigns and schedules Trips. A proposed driver can exist before assignment. Warehouse loading can block Trip start. Utopia OE is a broker, not the owner of Ibnu Sina records. |
| # | Component | State | Ibnu Sina |
|---|---|---|---|
| 11 | Billing, payment, deposit | differs | Supports one-off and recurring money, counter cash, several payment methods and order-level outstanding. Commercial paid and Finance-paid use different status sets. |
| 12 | Collecting a payment | differs | Sales, counter or driver can capture according to permission/context. Field cash stays tied to the Order while the Trip records where it was collected. |
| 13 | Payment reconciliation | differs | Recorded → Verified → Submitted to bank → Exported, with Issue Found and Cancelled paths. AutoCount export remains a stub marker/outbox event. |
| 14 | Itemize log and statuses | differs | Order lines follow Pending → Verified → Posted, with Issue Found, Unlocked and Cancelled. Posting to AutoCount is currently a stub. |
| 15 | Refund | as written | Request → manager approval → processing → paid, with separate rejection/cancellation paths and payout evidence. Approver must differ from requester. |
| 16 | Recurring payment | differs | Central to Rent and Rent-to-Buy: scheduled cycles are Due, Paid or Voided; recurring receipts have their own references and verification flow. |
| 17 | Collection/default | differs | Collection follow-ups track promised action and overdue cycles. Default can progress to repossession booked, recovered or cured. |
| # | Component | State | Ibnu Sina |
|---|---|---|---|
| 18 | Inventory and serial tracking | differs | Serial and batch inventory use an append-only movement ledger, warehouse zones, lifecycle state and New/Refurbished/Damaged variants. |
| 19 | Procurement | as written | Suppliers, purchase orders, partial goods receipts, receipt serials and adjustments are implemented; receipt is the stock-moving action. |
| 20 | Warranty and after-sales | as written | Warranty registrations, service requests/actions, repairs and customer identity documents are implemented as separate records. |
| 21 | External systems and reporting | Partial |
Hub identity, fleet, OE/Ops and legacy sync are implemented. AutoCount posting is stubbed, PayEx is not a completed gateway flow, and production enablement requires external verification. |
The following shared principles remain important even where Ibnu Sina differs: