The problem with email and WhatsApp approvals
In many Malaysian companies, purchase approval still happens in an inbox or a chat group. A requester emails a manager, the manager forwards it to finance, someone replies 'ok proceed', and the order goes ahead. It feels fast, but it leaves no reliable record: approvals are scattered across threads, the amount approved may not match the order placed, and when an auditor asks who authorised a spend, the answer is a search through months of messages.
Requisition software replaces that with structure. Every request is raised the same way, routed the same way, and recorded the same way. The approval is attached to the request, the request is attached to the order, and the whole chain is queryable — so 'who approved this?' takes seconds, not an afternoon.
- Email and chat approvals leave no reliable, single record
- The amount approved often drifts from the amount ordered
- Audits become a search through message history
Routing that matches your approval matrix
Not every purchase needs the same approvers. A small stationery order and a large capital request should follow different paths, and most organisations already have a delegation-of-authority matrix that says so. The problem is enforcing it when approvals are manual — people forget a step, skip a level, or route to whoever is nearest.
Requisition software encodes the matrix. Requests route automatically by amount, category and cost centre to the approvers who should see them, escalate when someone is unavailable, and cannot skip a required level. The policy stops being a document people are meant to remember and becomes the way the system behaves. The approval-workflow cost calculator estimates the time your current approval routing consumes.
Requisition
Cart built from managed catalogue
Approval
Multi-level budget checks
Purchase Order
Auto-generated & dispatched
Fulfilment
Own warehouses & fleet across Peninsular Malaysia
Invoice & Match
10,000+
suppliers onboarded
2M+
skus in catalogue
Peninsular
malaysia coverage
From approved request to purchase order, without rekeying
A requisition that is approved but then manually retyped into a purchase order reintroduces the exact errors the workflow was meant to remove — a wrong quantity, a changed price, a different item. The value of a connected request-to-approve flow is that the approved requisition becomes the purchase order directly.
On Lapasar, because the requisition is built against a managed catalogue with real contracted prices, conversion is one step: the approved request is turned into a PO carrying the same items, prices and cost centre, then sent to the supplier. What was approved is what is ordered, and what is ordered is what will be matched against the invoice — a clean line from request to payment.