Skip to content
VEXA

VEXA GLOBAL

Remote worldwide

Custom business systems for companies that have outgrown spreadsheets.

Stock and warehouse systems, operations dashboards and workflow automation, built around the process you already run. Fixed scope, fixed price, and the software, its data and the accounts it runs on are in your company’s name from the first day.

Replies within 1 business day · Mon-Fri 09:00-18:00 MYT (UTC+8)

Stock · Receiving
Stock on handGoods receivingTransfers
All itemsBelow reorderLocation: Plant 1
SKUDescriptionBinOn handReorder ptStatus
AL-6061-T6-25X3Aluminium bar 25mm x 3mA-04-231280OK
SS-304-SHT-1.5Stainless sheet 1.5mmA-07-19640OK
FST-M8-40-ZPHex bolt M8 x 40 zincC-11-11840600OK
BRG-6204-2RSBearing 6204 2RSC-02-424060OK
SEA-NBR-70-32O-ring NBR 70 32mmD-01-3604250OK
PNT-EPX-GRY-5LEpoxy primer grey 5LE-09-22812OK
FIG. 01 — Stock on hand

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

02 · WorkAnonymised

Three systems, described in enough detail to judge us.

Manufacturing

Warehouse and inventory system

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

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.

03 · TermsIn writing

Our terms, in writing.

Three numbers that go into every proposal, and the clause that matters most.

3

client systems built and still supported. Two are described above; the third is on the work page.

3

working days from the scoping call to a written, fixed-price quote.

1

business day to a reply, Mon-Fri 09:00-18:00 MYT (UTC+8).

Ownership

The software, its database and the accounts it runs on are registered to your company and transferred on final payment. If you stop working with us, everything keeps running and any other developer can pick it up.

04 · ProcessSix stages

How an engagement runs.

Two of these stages are ours to commit to in writing. The rest depend on how quickly your team can answer questions, which is why the plan says so.

Engagement sequenceSix stages in order: scoping call, process walkthrough on site or on video, written proposal within three working days, build drops, handover, then thirty days of aftercare. Two client obligations sit below the line: supplying current spreadsheets, and returning feedback within three working days.
FIG. 06 — How an engagement runs

Sequence, not to scale. Durations are fixed in the written proposal.

05 · Questions

Two questions we get every week.

You were only registered in 2025. Why trust you with this?
The company is new. The work is not — the systems on this site are in daily use, and we will walk you through any of them on a call. The protection you should ask for is structural rather than sentimental: the software, its data and the accounts it runs on are in your company's name from the start, so the worst case is that you hire someone else to continue from a running system.
We run on Excel and WhatsApp. Is that a problem?
No. It is the normal starting point, and it is useful — the spreadsheet everyone emails around is a specification written by the people who do the work. We import it, keep the parts that match how you operate, and put the rest in a database so two people can work at once.

Send us the spreadsheet everyone emails around. We will tell you what is automatable and what is not.

Not ready to talk? Read how the warehouse system was built.

CallWhatsAppBook a call