01 — The problem
Where purchase requests get stuck today
Most purchasing starts in a spreadsheet or an inbox. A requester emails a quote, someone copies it into a PO template, and the approval chain depends on who remembers the rules. Which amount needed the CFO again?
Off-the-shelf procurement systems often impose their own approval model. Your process has exceptions: preferred vendors that skip a step, capital purchases needing a second signer, blanket purchase orders drawn down over a year. When those rules live in one head, every absence slows the queue.
02 — What to build
What your purchase order system should cover
Start small but precise:
Purchase requests with item, quantity, estimated cost, cost center and attached quote
Approval thresholds by amount and category, routed automatically
Purchase orders generated from approved requests, each with a unique purchase order number
Vendor records with status: preferred, approved or on hold
Budget view showing committed versus remaining spend per cost center
Roles
requester, approver, procurement officer, finance (read-only)
Audit trail of who approved what, and when
03 — How to build it
How to build a procurement app with Henosia
Create a private project, a sandbox where nothing goes live until you publish.
Add representative mock data
a few months of requests, vendors and cost centers as CSV files.
Connect a database for structured tables.
Describe the workflow in Plan mode
The agent asks about thresholds, exceptions and roles, then proposes a plan. Nothing is built until you choose to build.
Build a first version and walk a request from submission to PO.
Test and iterate with edge cases: split orders, rejections, vendors on hold.
Publish with access limited to your company domain and the right roles.
A Plan-mode prompt might look like this:
Build a purchase request and PO app for our operations team.
Requests under $2,500 need manager approval; $2,500 to $25,000 also need finance;
anything above that also needs the CFO. Capital items always need finance.
Approved requests become POs with a sequential PO number and vendor details.
Block requests to vendors marked "on hold" and show budget remaining per cost center.Paste it into a private Henosia project in Plan mode. The agent asks questions and proposes a plan first.
04 — Before you go live
Before real spend data goes in
Before production, decide:
- Who owns the approval rules and signs off on threshold changes
- Read versus write access: should the app also write POs to another system?
- Integrations, scoped one by one. Henosia can work with data connections and API-based data; scope each integration per system, data direction and access level.
- Who approves publishing and who sees financial fields
In a Henosia webinar, Danish e-commerce company 4tal shared a fitting principle: use deterministic rules for stable steps like threshold routing, and keep a human in the loop where judgment is needed.
If approvals are the bottleneck across departments, see our approval workflow app guide.
Start a private project in Henosia, load your request history as mock data and plan your PO process.
Start a private project05 — FAQ
Frequently asked questions
What is purchase order software?
Purchase order software manages the path from purchase request to approved purchase order. It captures what is being bought, routes the request to approvers by amount or category, issues a numbered PO to the vendor and keeps an audit trail. A custom version follows your own thresholds.
How much does a custom purchase order system cost?
It depends on scope: approval rules, roles, integrations with finance systems and how much testing you need. Henosia shortens the build itself, because process owners can plan and generate a first version with AI. Integration work, data cleanup and testing still take real effort and belong in the budget.
Do I need developers to build a procurement app?
Not for a first version. A procurement lead can describe the workflow in Plan mode and build without writing code themselves. For production, involve IT when you connect live financial data, set write access to other systems or define who approves publishing.
Who can see purchase orders and budgets in the app?
You decide. Henosia Authentication ties apps to your company domain and supports more granular app-level access, plus optional IP restriction. Requesters, approvers and finance can get different views, and outside vendors access only where it makes sense. Confirm specific security requirements with Henosia for your setup.