The Problem · Purchasing by Spreadsheet

Still Raising Purchase Orders by Hand?

A number typed into a spreadsheet. An approval chased down a WhatsApp thread. A PDF emailed to a supplier and forgotten. If that's how purchase orders get raised in your company, the process isn't just slow — it's invisible, and that's where the money goes.

Inside the product
The complete procure-to-pay flow: Software + Physical Supply
Software LayerPhysical & Commercial Layer

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

0
Audit trail on a WhatsApp-approved order
3-way
Matching once POs are structured
Free
Full requisition-to-PO software for unlimited users

A manual purchase order process relies on spreadsheets, email and messaging apps to raise, approve and send POs. It breaks in predictable ways: approvals stall because there's no routing, numbers get keyed twice and disagree, there's no reliable audit trail, and finance can't see what's been committed until the invoice arrives. Replacing it with a structured requisition-to-PO workflow gives every purchase a defined approval path, a matched PO, and a record — so orders move faster and spend is visible before it's committed rather than after.

What you get with Lapasar

No more spreadsheet POs

Purchase orders are generated from an approved requisition, not typed into a shared sheet that anyone can overwrite.

Approvals that route themselves

Requests follow a defined approval path by value and category — no more chasing sign-off across email and chat.

A record of every order

Who requested, who approved, what was ordered and when — captured automatically as an audit trail.

Three-way matching

PO, goods-received note and invoice reconcile before payment, so what's ordered, delivered and billed all agree.

How Lapasar replaces the manual PO

01

Raise a requisition, not a spreadsheet row

Requesters pick from a catalogue; the request carries its own price, category and cost centre from the start.

02

Route approvals automatically

The request follows a defined approval path by value and policy — approvers act in one place, on the record.

03

Generate the PO and match it

An approved requisition becomes a purchase order; goods-received notes and invoices then reconcile against it automatically.

Start browsing on mall.lapasar.com

Where the manual PO process actually breaks

The manual purchase order process rarely fails all at once — it leaks. An approval sits unread in an inbox for three days. A number is keyed into the spreadsheet, then keyed again into the supplier's email, and the two don't match. A verbal 'yes' over a call becomes an order with no paper behind it. None of these are dramatic, but together they mean purchasing is slow, error-prone and — most damagingly — invisible.

The invisibility is the real problem. When POs live in spreadsheets and chat threads, finance has no reliable view of what's been committed. The first time a cost becomes visible is when the invoice lands, by which point the money is already spent and the chance to question it has passed.

  • Approvals stall with no routing and no reminders
  • Numbers rekeyed across sheet, email and supplier disagree
  • Verbal or chat approvals leave no audit trail
  • Committed spend is invisible until the invoice arrives

Browse live stock & pricing on mall.lapasar.com

What a structured PO workflow gives you

Replacing the manual process doesn't mean adding bureaucracy — it means the sequence a purchase already follows becomes controlled and reportable. A requisition is raised against a catalogue, so it carries the correct price, category and cost centre from the outset. It routes to the right approver by value and policy. Once approved, it becomes a purchase order automatically, and the goods-received note and invoice reconcile against that PO before payment.

The by-product of that structure is the thing the spreadsheet could never give you: a live view of committed spend and a complete record of who ordered what and who approved it. Auditors get a trail; finance gets forward visibility; requesters get a faster answer than a chased WhatsApp message ever delivered.

  • Requisitions priced and coded from a catalogue
  • Approval routing by value, category and cost centre
  • Automatic PO generation from an approved request
  • Three-way matching before payment is released
The complete procure-to-pay flow: Software + Physical Supply
Software LayerPhysical & Commercial Layer

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

See contract pricing on mall.lapasar.com

Count the cost before you switch

It helps to quantify the drag before committing to change. The approval-workflow cost calculator estimates what your current sign-off process costs in delay and handling time — a useful baseline against which a structured workflow pays for itself, especially since the software itself is free for unlimited users.

From there the move is incremental: put requisitions on a catalogue, switch approvals to a routed workflow, and let approved requests generate matched purchase orders. The spreadsheet and the WhatsApp thread stop being the system of record — and purchasing becomes something finance can see before the money is spent.

Explore the catalogue on mall.lapasar.com

Common questions

What's wrong with raising purchase orders in a spreadsheet?
A spreadsheet PO has no approval routing, no reliable audit trail and no link to the invoice that follows. Numbers get rekeyed and disagree, anyone can overwrite the sheet, and finance can't see what's been committed until the bill arrives. It records purchasing but doesn't control it.
Why are email and WhatsApp approvals a problem?
Chat and email approvals leave no structured record. There's no defined path, no reminder when sign-off stalls, and no way to prove later who approved what. When an auditor or finance asks, the trail is scattered across inboxes and threads rather than captured against the order.
How does a structured PO workflow speed up approvals?
Requests route automatically to the right approver by value and policy, so nothing waits in an inbox for someone to notice it. Approvers act in one place, on the record, and an approved request becomes a purchase order without rekeying — turning days of chasing into a defined, reportable flow.
What does it cost to replace our manual PO process?
Lapasar's requisition-to-PO software is free for unlimited users — there are no licence or per-seat fees. Use the approval-workflow cost calculator to estimate what your current manual process costs in delay and handling, then weigh that against a structured workflow that carries no software cost.
How does Lapasar replace a manual purchase order process?
Requesters raise a requisition from a catalogue; it routes through a defined approval path; and once approved it becomes a purchase order that goods-received notes and invoices reconcile against automatically. Every step is recorded, so committed spend is visible before the invoice arrives, not after.

Didn't find your answer?

Ask us directly — WhatsApp or email, whichever suits you.

Retire the PO spreadsheet

See requisitions, routed approvals and matched purchase orders working on your own buying — book a demo and leave the WhatsApp thread behind.

Prefer to talk to a real person?

Our team replies fast on WhatsApp and email — no forms, no waiting.