Custom business software · A corporate office (client not named)

A purchasing system: request, quotations, order, approval, receipt.

A corporate office bought supplies, equipment and services by email and spreadsheet. We delivered one system that takes a purchase from the first request to the goods arriving, with the approval step where the money is committed.

New purchase order form in the purchasing system

01 The problem

Where it started

  • 01Requests came in by email, so nobody could say what had been asked for, by which department, or what stage it had reached.
  • 02Quotes from suppliers were compared by hand, and the reason for choosing one was not recorded.
  • 03Approval happened in conversation. There was no rule for who signs off what amount, and no record that it happened.
  • 04The purchase order sent to suppliers had to match the form the company already used.

02 What we built

How it works

Purchase requests

Staff raise a request against their department or business unit from a catalogue of items the company buys.

Quotations with scoring

Up to three suppliers quote for each request. The system scores them, weighting cost at 70% and delivery time at 30%, and marks the best. Choosing a different supplier requires a written reason.

Purchase orders

The winning quotation becomes a purchase order with the supplier’s payment terms and the company’s terms and conditions, printed as a PDF in the layout the company already used.

Approval rules

Rules set by amount band decide who must approve, with several levels where needed, such as finance and then purchasing. One person can never approve two levels of the same order.

Goods received

Receiving creates a numbered goods received note, handles part deliveries, and updates stock for items that are stocked.

Supplier payments

Payments are recorded against the order and the supplier’s ledger shows what is still owed.

03 Decisions

Choices that mattered

Approval sits on the order, not the request

We first built approval on requests and quotations as well. Working with the client, that was reduced to one gate, on the purchase order, which is where money is committed.

Terms are copied onto each order

The terms and conditions are stored with each order when it is raised, so reprinting an old order shows the terms it was issued under, not today’s.

A warning when a receipt does not move stock

An office buys services and consumables that are not stocked. The receipt screen says clearly when a line did not change stock, so "received" is never mistaken for "in the stockroom".

Roles sized to the job

The client got five roles that match their team, such as requester and purchase manager, not the full set the platform offers.

Built with: React, FastAPI (Python), PostgreSQL with row-level security, PDF generation. Delivered on our OpesFlux platform.

Need something like this?

Tell us how the job is done today. The first call is free, and you get a written scope and a fixed quote.

Book a free discovery call