← All articles

·6 min read

Stop Approving Purchases in WhatsApp Chats: Set Up a Digital Purchase Approval Workflow

If purchase requests in your business still run on WhatsApp messages, paper forms and verbal OKs, you are probably overspending without knowing it. Here is how to set up a digital purchase approval workflow that staff will actually use.

  • approval workflow
  • procurement
  • purchase order
  • internal controls
  • spend control
  • operations
  • automation
  • sme
Stop Approving Purchases in WhatsApp Chats: Set Up a Digital Purchase Approval Workflow

It is 9 p.m. A branch manager sends you a blurry photo of a supplier quotation on WhatsApp: Boss, can I order this? You are at dinner, so you reply ok. Three weeks later the same items arrive twice, because another staff member asked your partner in a different chat group. Nobody can find who approved what, or why. If this sounds familiar, your business has outgrown chat-based approvals. This guide explains how to set up a digital purchase approval workflow step by step: how to set approval tiers, what the process looks like, which tools fit your size and budget, and how to get your team to use it.

Why WhatsApp approvals cost more than you think

WhatsApp is great for talking, but it was never designed to control spending. In growing distributors, contractors, multi-branch shops and F&B businesses, we see the same problems again and again:

  • Duplicate orders. Two people request the same item in two different chats, and both get approved.
  • Overspending. An OK given on a phone screen rarely includes a check against the monthly budget.
  • No audit trail. When the tax office, an auditor or a business partner asks why a payment was made, the answer is buried in thousands of messages, or in a phone that a staff member took home when they resigned.
  • Slow decisions. Requests get lost under other messages, so urgent purchases wait while the owner scrolls.
  • Fraud risk. Without a record matching request, order, delivery and invoice, inflated prices or ghost deliveries are hard to spot.

Even small leaks add up. If a business spending Rp 300 million a month on purchases loses just 3% to duplicates and unchecked prices, that is Rp 9 million every month.

Design your approval tiers and spending limits first

Before choosing any software, write your rules down on one page. Tools only automate rules; they cannot invent good ones for you.

Set limits by amount

A simple three-tier structure works for most SMEs. For example:

  • Below Rp 2 million: approved by the branch or site manager.
  • Rp 2 million to Rp 15 million: approved by the operations or finance manager.
  • Above Rp 15 million: approved by the owner or director.

Adjust the numbers to your business. A contractor buying cement weekly will need higher limits than a café buying cleaning supplies.

Add a budget check

Give each branch, project or department a monthly budget per category. A request that fits the budget follows the normal tier. A request that exceeds it goes one level higher automatically, even if the amount is small.

Decide who can request and from which suppliers

Limit who can raise purchase requests, and keep a list of approved suppliers with agreed prices. Routine items from approved suppliers at agreed prices can move fast; new suppliers or price changes need an extra look.

What a digital purchase approval workflow looks like

A good workflow follows the money from the first request to the final payment. Here is the typical flow:

  1. Purchase request (PR). Staff fill in a short form on their phone: item, quantity, estimated price, supplier, reason, and a photo of the quotation.
  2. Approval. The system sends it to the right approver based on amount and budget. The approver gets a notification and can approve, reject or ask a question with one tap.
  3. Purchase order (PO). Once approved, a numbered PO is created and sent to the supplier. No PO number, no order.
  4. Goods received. The warehouse or store records what actually arrived, with quantities and a photo of the delivery note.
  5. Invoice matching and payment. Finance checks that the PO, goods received and supplier invoice match (often called a three-way match) before paying.

Every step is timestamped with a name. When someone asks who approved this, the answer takes ten seconds, not ten hours.

Your options: from simple tools to an ERP or custom build

Option 1: Forms and spreadsheets

Google Forms or Microsoft Forms feeding a shared spreadsheet, with email or WhatsApp notifications. Cost: close to zero if you already pay for Google Workspace or Microsoft 365. Good for a single location with a few dozen requests a month. Weakness: approvals and budget checks are mostly manual, and spreadsheets break easily when many people edit them.

Option 2: Workflow and approval apps

Tools like Zoho Creator, Kissflow or Jotform Approvals let you build forms with automatic routing by amount. Expect roughly Rp 300,000 to Rp 3 million per month depending on users, plus a few days of setup. Good for 2 to 10 branches that want proper approvals without changing their accounting system.

Option 3: The purchasing module in an ERP or accounting system

If you already use, or plan to use, systems like Odoo, Accurate or Jurnal, check their purchasing features. The big advantage is that POs, stock and payables are connected. Subscriptions range from a few hundred thousand to several million rupiah per month, and implementation with a partner often costs Rp 20 million to Rp 150 million depending on complexity. Good if you also need inventory and accounting cleaned up.

Option 4: Custom build

A purpose-built app makes sense when your process is unusual, for example project-based budgets for contractors, or integration with an existing in-house system. A focused purchasing app typically costs Rp 60 million to Rp 200 million to build, plus ongoing maintenance. Do not start here unless the standard options truly do not fit.

Our honest advice: most SMEs should start with Option 2 or 3. You can always customise later once you know exactly what you need.

Getting staff to actually use it

The most common failure is not the software. It is people going back to WhatsApp because it feels faster. To prevent that:

  • Make one firm rule: no PO number, no payment. Finance must refuse invoices without one. This rule does more than any training.
  • The owner must use it too. If you still approve things in chat, everyone else will as well.
  • Keep it mobile and short. If the request form takes more than two minutes, people will avoid it.
  • Set approval response times, for example 24 hours, with automatic reminders, so staff do not feel blocked.
  • Create an emergency path. A broken freezer at 10 p.m. cannot wait. Allow an urgent purchase with a request recorded the next morning.
  • Pilot in one branch for a month, fix the annoying parts, then roll out.

You can still use WhatsApp, but for notifications that link to the system, not for the approval itself.

Your next step

This week, write your approval rules on one page: who can request, the spending tiers, and who approves each tier. Then count how many purchase requests you handle per month. Those two pieces of information will tell you which option fits. If you would like help choosing a tool or designing the workflow, talk to the CodeWorks team. We will review your current process and give you a realistic plan and estimate, with no obligation.