Build an inventory tracker

Inventory is a counting problem that turns into a trust problem the moment two people update the same number. A tracker earns its keep by staying accurate, warning you before you run out, and remembering how every total got that way.

Describe what you're counting

Start with the item and where it lives. A strong first prompt names the fields you'd actually search by:

Build an inventory tracker. Each item has a name, SKU, category, quantity on hand, reorder level and location. Staff can search items and adjust quantities.

Vorx models items and locations, builds a searchable list, a detail page, and the forms to add stock and adjust counts. SKU and category become real fields you can filter and group by, not text in a cell.

Track movements, not just totals

A single quantity tells you where you are but not how you got there. Ask for a movement log:

• Items — what you stock, with SKU and reorder level
• Locations — warehouses, shelves or vans
• Movements — every receipt, sale, transfer or adjustment
• Suppliers — who you reorder from

When someone receives or removes stock, record a movement and update the item's quantity automatically.

Now the total is the sum of its history, and you can see exactly who changed what. That's the difference between a number your team argues about and one they act on.

Warn before you run out

The point of tracking stock is acting on it.

Flag any item where quantity on hand is at or below its reorder level, and show a low-stock list on the dashboard.

For the nudge nobody has to remember, make it recurring: a scheduled job that emails the low-stock list every Monday morning runs on a timer under Settings → Cloud → Jobs, and each run is recorded so you can confirm it fired.

Handle multiple locations

Stock in two places is really two numbers, so model it that way:

Track quantity per location and let staff transfer stock from one location to another, recording a movement on both sides.

A transfer should decrement one location and increment the other in a single action. Add a per-location view — "show me everything low at the north warehouse" — and refine it until it matches how your team walks the shelves.

A count updated on the warehouse floor appears on the office dashboard the next time that screen loads. Realtime updates and offline support (VorxSync) are on our roadmap, not in what you build today — a manual refresh button covers the gap until it ships.

Be careful what you let people delete

Not everyone should be able to write off stock, and nobody should be able to erase its history.

Let all staff view inventory and record sales, but only managers can make adjustments or edit reorder levels.

Prefer correcting a count with a new adjustment movement over editing the old one. A tracker whose history can be rewritten is a tracker whose totals can't be trusted — and adjustments that leave a trail are what make a stock take reconcilable.

Ship it and keep extending

When the counts stay honest through a few test movements, publish and roll it out. Barcode entry, a supplier reorder page, a CSV export — each is one more prompt when you need it.

In the docs: Your data model and Scheduled jobs.