- Search by phone before creating a Customer.
- Create or select the Customer and an address.
- Choose product type and the commercial offer/deal type.
- Add Order lines and commercial details.
- Save as Draft. The internal
ISCB-YYYY-NNNNN identity exists, but the customer-facing number is not consumed yet.
- Record a quotation first when required, or continue with direct order intake.
- Run the Confirm Gate. Validation covers the required customer, address, lines and deal-specific data.
- Confirmation atomically mints the customer-facing order number and changes the Order to
CONFIRMED.
DRAFT → CONFIRMED → DELIVERED → CLOSED
└──────────────→ CANCELLED
The first completed Hantar Trip is the delivery trigger. Other Trips do not independently close the Order.
- Create a Draft quotation for the customer and branch.
- Add commercial catalogue lines and terms.
- Send the quotation; it becomes
SENT.
- Its effective status may become expired according to validity rules.
- Convert through the supported Order creation path, retaining customer and line context.
Repository status vocabulary includes Draft, Sent and Expired. Conversion behaviour must be interpreted through the quotation service rather than assuming Encik Beku’s five-status model.
- Create a
Hantar Trip under a Confirmed Order.
- OE proposes or assigns a Driver and lorry.
- Warehouse stages the required lines.
- Warehouse scans units from warehouse to the lorry and completes loading. A short load requires a reason.
- Driver starts the Trip only after the loading gate passes.
- Driver captures delivery/order documents, customer identity when required, at least two product photos and the required serials.
- Driver records any cash collected against the Order.
- Driver marks Trip Done.
- The system records the lorry-to-customer stock movement and sets the first-delivery trigger.
- The Order becomes
DELIVERED; rental hooks may create recurring cycles.
¶ 4. Pickup, return and exchange
- Schedule and assign the Trip.
- Driver records the returning serial and evidence.
- Trip completion moves the unit from customer to lorry.
- Warehouse receives it from lorry into Checking.
- Checking decides Ready, Repair, Scrap or another approved destination.
- Prepare the outgoing replacement unit.
- Record both outgoing and incoming serials.
- Complete separate physical movements for both units.
- Record the fault/reason and preserve the relation to the Order.
Walk-in, Walk-in Collect and Walk-in Return are assigned to a branch rather than a driver. Branch staff complete the proof and serial steps appropriate to the direction.
| Action |
Result |
| Upload proof |
BOOKED → PENDING_TO_CHECK |
| Job Done |
PENDING_TO_CHECK → JOB_DONE |
| On Hold |
Open Trip → ON_HOLD |
| Resume |
ON_HOLD → BOOKED |
| Postpone |
Old Trip → POSTPONE; a new Booked Trip is created for the agreed date |
| Cancel |
Any non-terminal Trip → CANCELLED; the Order remains |
¶ 6. One-off payment and verification
- Sales, counter staff or an authorised Driver records a payment against the Order.
- The payment starts as
RECORDED.
- Upload the slip or supporting document when required.
- Account either verifies it or marks
ISSUE_FOUND.
- Resolving an issue returns it to
RECORDED.
- Verified money can be submitted to bank.
- Export currently changes the record to
EXPORTED and creates a deterministic batch/outbox marker; it does not prove AutoCount received a document.
RECORDED → VERIFIED → SUBMITTED_TO_BANK → EXPORTED
↓
ISSUE_FOUND → RECORDED
└──────────────→ CANCELLED (from any non-terminal state)
- Eligible delivery creates the rental or rent-to-buy schedule.
- Each
recurring_cycle stores the expected amount and due date.
- Account records one or more recurring payments.
- Verified recurring money covering the expected amount changes the cycle to
PAID.
- If verified money later falls below the amount, the cycle can return to
DUE.
- Cancellation/conversion may void the remaining tail.
- Collection follow-up uses due/overdue cycles to record contact and promised action.
- Continued default can lead to a repossession Trip; recovery or cure ends the default path.
- An authorised user requests the refund with amount, bank details and reason.
- A different Manager approves it, or rejects it.
- Account starts processing an approved request.
- Upload payout proof.
- Mark Paid only when the money has actually left the business.
- Paid refunds feed the Order’s owed calculation.
REQUESTED → MANAGER_APPROVED → PROCESSING → PAID
├────────────→ REJECTED
└────────────→ CANCELLED
¶ 9. Itemisation and accounting handoff
- Order lines enter
PENDING verification.
- Account verifies a valid line or marks an issue.
- Issue correction returns it through the controlled state.
- A privileged unlock allows correction after verification.
- Posting changes the line to
POSTED and writes the batch/outbox marker.
- The current code does not create a real AutoCount transaction. Reconciliation outside the application remains required.
¶ 10. Procurement and goods receipt
- Maintain the Supplier, including its optional AutoCount supplier code.
- Create a Purchase Order and its lines.
- Approve/advance the PO through its supported service actions.
- Receive all or part of a line.
- For serial items, capture every received serial.
- Goods receipt calls the Inventory service and creates inbound Stock Movements.
- Record a receipt adjustment rather than rewriting received history.
- Leave outstanding quantities open until fully received or deliberately closed.
¶ 11. Warehouse checking and stock correction
- Receive returned stock into Checking.
- Inspect by serial or batch.
- Decide its condition and destination: Ready, Repair or Scrap.
- Record the movement. Never directly edit current balances.
- Use transfer workflows for warehouse-to-warehouse movement.
- Destination receipt completes the transfer.
- Use a controlled adjustment with reason/evidence for physical count differences.
- Hub-side processes deliver AppSheet/Google Sheets row events into
legacy_mirror tables.
- Ingestion records run/state and queues projection work.
- Projection maps source identities into Customers, Orders, Trips, payments, refunds and itemisation.
- Idempotent mappings prevent duplicates and out-of-order guards protect newer operational state.
- Health endpoints expose stalled projection or unresolved issues.
- Operators investigate the last failed run/mapping instead of manually editing projected records.
¶ 13. Ops and OE integration
- User signs in through the shared Hub.
- OE asks the Ibnu Sina backend whether the invited local user may enter.
- The production Ops build must include
ibnu-sina in its registry and enabled-BU environment.
- The app sends the Hub JWT plus
X-OE-BU: ibnu-sina through OE.
/ops endpoints enforce user ownership/work-list rules.
/oe endpoints use the scoped machine token for assignment and board operations.
Ibnu Sina remains the source of its Orders, Trips, payments and stock. OE does not store or reinterpret them.