Search for "procurement software" and you'll find two kinds of product. One is enterprise suites built for multinationals, with long implementation projects and pricing to match. The other is generic purchasing tools designed for office supplies and SaaS subscriptions, where the buyer and the approver sit in the same building.

Neither fits a Malaysian construction or O&G SME very well. Your requests start on a site, not at a desk. Approvals depend on the value, the category, and sometimes the project. Materials are bought against BQ lines, and a single director may be approving purchases for several companies at once.

A site office desk with a laptop showing a procurement dashboard, a ticked checklist, a hard hat and rolled drawings, with a construction site and crane outside the window

This guide is a practical way to judge procurement software for that reality — what to check, what to ask, and how to test it before you commit.

Step 1: Write Down Your Current Process First

Before comparing any products, map how a purchase actually moves through your company today:

  1. Request — who raises it, from where (site, store, office), and how (WhatsApp, requisition book, email, phone call)?
  2. Approval — who approves what? Is it by value, by category, by project, or all three?
  3. Purchase order — who issues the PO, and how is the vendor chosen?
  4. Delivery — how is receipt confirmed on site?
  5. Payment and settlement — how does finance match the invoice to the PO and the approval?

Mark where things get stuck or lost. That list becomes your evaluation criteria. A system that's excellent at step 3 but doesn't help with steps 1 and 2 won't fix the problems you actually have. (If most of your approvals currently happen in a group chat, start with our guide to moving approvals off WhatsApp.)

Step 2: The Seven Things to Check

1. Can site teams raise requests easily?

If raising a requisition is harder than sending a photo on WhatsApp, the site team won't do it — and the system will quietly fail. Check that requests can be raised from a phone, with photos and quotations attached, by people who aren't procurement specialists.

2. Does approval routing match your real chain?

Look for multi-tier approvals that route automatically by value and category, so a RM500 consumables order and a RM80,000 equipment hire don't go through the same path. The system should enforce who can approve what — not rely on people remembering.

3. Is everything on one connected record?

The requisition, the approval, the PO, the delivery, and the settlement should link to each other. When someone asks "who approved this, against which request, and was it paid?", the answer should take seconds. This is what an unbroken audit trail means in practice — and it's the difference between a purchasing tool and a procurement record.

4. Can the audit trail be edited?

Ask directly: can an approval or a PO be changed after the fact without leaving a trace? A useful audit trail is timestamped and append-only — corrections are recorded as new entries, not overwrites.

5. Is there a proper vendor register?

Purchases should be made against known, approved vendors — with their details held once, not retyped on every PO. A shared vendor register also makes it easier to see how much you spend with each supplier across projects.

6. Does it handle more than one company?

Many Malaysian contractors run several entities: a main company, subsidiaries, JV vehicles for specific projects. Check whether the software can keep separate companies, approval hierarchies, and records in one login, or whether you'd need a separate subscription for each. (See how multi-company routing works in Bilaro.)

7. Can you see spend against budget?

Approvers should be able to see what's already been committed before approving more. Even basic visibility — spend by project, category, or vendor — catches overruns weeks earlier than a month-end spreadsheet.

Step 3: Check the Malaysian Specifics

A lot of procurement software is built for other markets. For a Malaysian SME, a few local details matter:

  • Pricing in MYR. Prices in USD move with the exchange rate, which makes budgeting harder. Check the currency, whether the price is per month or per year, and whether SST or other charges are added on top.
  • How users are counted. Some systems charge for every user, including site staff who only raise a few requests a month. Find out who counts as a user and what extra users cost.
  • e-Invoicing. LHDN's e-Invoice rollout affects how businesses issue and keep invoice records. Ask each vendor precisely what their software does: does it prepare and organise procurement records, or does it submit to LHDN's MyInvois system? Those are different things, and your accountant should confirm what your company needs. (Our e-Invoice page explains how Bilaro approaches this.)
  • Support hours and location. When a site can't submit a request at 7 AM, a support team twelve time zones away doesn't help much.
  • Where the data is kept. Ask where your records are stored and what happens to them if you cancel. Your procurement history is yours; you should be able to export it.

Step 4: Questions to Ask Every Vendor

Keep these short and specific, and ask for a live answer rather than a slide:

  • Can you show me a site user raising a request on a phone, start to finish?
  • How would you set up our approval chain — by value, by category, and by project?
  • If an approved PO is changed, what does the record show?
  • How are users counted, and what happens to the price when we add a site team?
  • Can we run more than one company under one account?
  • What exactly does your system do for LHDN e-Invoicing — and what doesn't it do?
  • How long does setup take, and who does it?
  • If we leave, how do we get our data out?

A vendor who answers these clearly, with the product on screen, is usually a safer choice than one with a longer feature list.

Step 5: Run the Trial on a Real Project

Most procurement software offers a free trial or a demo. A demo shows you what the product can do; a trial shows you whether your team will actually use it.

To get a useful answer from a trial:

  • Pick one live project with a steady flow of purchases and a cooperative project manager.
  • Set up your real approval chain, including the awkward exceptions.
  • Use real requests for two or three weeks — not a test scenario.
  • Ask the site team and the approvers, not just the office, whether it's faster or slower than before.
  • Check the record at the end. Pick a few purchases and see whether you can trace each one from request to payment without asking anyone.

If the trial ends and the site team has quietly gone back to WhatsApp, that tells you more than any feature comparison.

When a Simpler Setup Is Enough

Procurement software isn't always the right answer. If you're a small team with a handful of purchases a month, one person approving everything, and no audits or client reporting to worry about, a well-kept spreadsheet and a clear rule for who approves what may be enough for now.

The case for software gets stronger when purchases come from several sites, more than one person approves, you run more than one company, or you need to show a clean record to a client, an auditor, or a lender.

Where Bilaro Fits

Bilaro is procurement software built specifically for Malaysian construction and O&G SMEs. It covers the flow in this guide — site requisitions, multi-tier approval routing, PO issuance, a vendor register, and settlement — linked in one timestamped audit trail. Plans are priced in MYR and include up to 10 users per company, with multi-company support on the higher tiers. Full details are on the pricing page.

The best way to judge it is the way this guide suggests: run it on one real project for the length of the trial and see whether your team keeps using it.

What is the most important feature to look for in procurement software?

For construction and O&G teams, it's usually how easily site staff can raise requests and how well approvals route automatically. If requests are hard to raise, people go back to WhatsApp and the system is never used. After that, look for one connected record linking the requisition, approval, PO, and payment.

How much does procurement software cost in Malaysia?

It varies widely, from enterprise suites with implementation fees to monthly SaaS subscriptions. When comparing, check the currency, whether the price is monthly or annual, how users are counted, and what extra users or companies cost. Bilaro's plans are listed in MYR on its pricing page, with a 30-day free trial.

Does procurement software handle LHDN e-Invoicing?

It depends on the product. Some tools prepare and organise procurement records for e-Invoicing, while submitting e-Invoices to LHDN's MyInvois system is a separate step. Ask each vendor exactly what their software does and doesn't do, and confirm your company's requirements with your accountant.

How long should a procurement software trial last?

Long enough to run real purchases on at least one live project — typically two to four weeks. That's usually enough to see whether site teams and approvers actually use the system, and whether you can trace a purchase from request to payment at the end.