Skip to content
VEXA

Three systems we built and still support.

We do not publish client names or logos without written permission. If you are evaluating us, ask and we will arrange a call with a client who has agreed to speak.

01 · FeaturedAnonymised

Manufacturing

Warehouse and inventory system

The situation

Stock lived in a shared spreadsheet. Receiving was written on paper and keyed in at the end of the shift, so the figure on screen was always a few hours behind the shelf. Nobody could say what had been reserved against an order without asking the storeman.

What we built

  • Every stock movement records the item, the location and the person, so nothing moves without a trace
  • Receiving, transfers and corrections as three simple screens a storeman uses from a phone
  • Reorder points set per item by the supervisor, with alerts by email
  • Count sheets, difference reports and a file the accounts team can open

What they operate today

Movements are recorded as they happen. Supervisors read stock off the system instead of asking. The reorder list is produced automatically rather than remembered.

How a stock record is keptThree kinds of record: items, locations, and every movement. Each movement records which item, which location, how many, when and who, so stock can only change with a trace, and the system will not let a count go below zero.ItemsCodeDescriptionReorder levelLocationsAreaShelf and binEvery movementWhich itemWhich locationHow manyWhenWho
FIG. 02 — How stock stays accurate
Sector
Manufacturing
Status
In use, supported by us
Ownership
The software, its database and hosting, all in the client's name
02 · CaseAnonymised

Manufacturing

Multi-module operations platform

Staff records, device assignments and complaint email each sat in a different spreadsheet, owned by a different person, with no agreement on which copy was current.

  • Staff dashboards, with each role seeing its own operation
  • Device and asset tracking that keeps assignment history
  • Email analytics reporting off the same records
  • Each role can only see and change what it is allowed to

Modules

  • Staff
  • ▸ Devices
  • Email analytics
  • Access control
  • Reports

Devices by department

AsseMachQualStorLogiMainPlanFinaHRITSaleAdmi

IT · 9 devices awaiting return from leavers

Devices assigned
214
Unassigned in stores
26
Access reviews due
3
FIG. 04 — Operations dashboard

Redrawn from a system we built. Sample values, not client data.

One platform holds the records the company argues about. Access is granted by role, and changes leave a trail.

03 · CaseAnonymised

Quality and logistics

Complaint email triage

Complaint email arrived in one shared inbox. Sorting it by hand meant the urgent items surfaced late, and the monthly summary was rebuilt by reading back through the inbox.

  • Plain rules that read the subject, the sender and how long a message has waited, with nothing an auditor needs explained
  • Routing to quality, logistics or sales, with escalation after 48 hours
  • Every message is logged, so the monthly report is produced automatically instead of counted by hand
  • A daily summary report every evening
How complaint email is sortedEmail arrives, is sorted by plain rules, sent to quality, logistics or sales, logged, and summarised in a daily report at six in the evening. Three example rules are shown: a mention of a rejection is marked urgent, mail from a key customer goes to quality, and anything unanswered for two days is escalated.
FIG. 03 — Complaint email, sorted automatically

Redrawn from a system we built. Sample values, not client data.

Messages are sorted on arrival and land with the team that owns them. The monthly figures come out of the system on their own.

Want the build notes on the warehouse system? We will walk you through it in twenty minutes, on your own stock problem.

CallWhatsAppBook a call