TL;DR
To build an inventory tracker with Claude, describe your items, locations, and how stock moves, and ask Claude to record every movement as a row in Postgres. The count comes from the movements, so it always adds up. floo hosts it behind invite-only sign-in, and a morning job posts what is running low.
- Store movements, not just counts. Every number can then be explained.
- Each movement records who made it, from the signed-in user.
- A daily job sends the low-stock list where the team already looks.
Most inventory starts in a spreadsheet with a "qty" column that someone edits by hand. It works until two people edit it in the same afternoon and the count is wrong with no way to know why. An app Claude builds can fix the root cause, not just the screen.
1. Describe the stock
Build an inventory tracker. Items have a SKU, a name, a unit, and a reorder point. We keep stock in two locations: the warehouse and the shop. Stock changes when we receive a delivery, sell, move between locations, or correct a count. Record each change as a movement with the quantity, the location, a note, and the person who made it. Show current stock per item and location, computed from the movements. Show a list of items below their reorder point.
The key sentence is "computed from the movements." It is the difference between a tracker and a shared number.
2. Host it
[app]
name = "inventory"
access_mode = "accounts"
[services.web]
type = "web"
path = "."
port = 3000
ingress = "public"
[managed.default]
type = "postgres"
[cron.low-stock]
schedule = "0 12 * * 1-5"
command = "node scripts/low-stock-alert.js"
service = "web"
access_mode = "accounts"makes it invite-only, and every request carries the person's email inX-Floo-User-Email. Claude saves that on each movement.[managed.default]gives the app Postgres. Dev and prod have separate databases.[cron.low-stock]runs weekdays at noon UTC, 7am in New York in winter. Store the chat webhook withfloo env set CHAT_WEBHOOK_URL --stdin --app inventory.
In Claude chat with the floo connector, describe the tracker and Claude creates the app with sign-in and Postgres for you.
3. Bring the current counts in
Export the sheet as CSV and have Claude write an import that creates one "opening count" movement per item and location. Run it against dev first:
floo run --service web -- node scripts/import-stock.js stock.csv
Check the totals match the sheet before anyone starts using the app.
Things to get right
- Corrections are movements too. A stock count that finds 3 fewer items adds a -3 correction with a note. Never edit past rows.
- Moves are two rows. -5 from the warehouse and +5 to the shop, written in one database transaction.
- Make the phone page fast. Whoever receives deliveries uses a phone. One screen: scan or search, quantity, save.
- Let the morning job run twice safely. A manual
floo cron run low-stockshould send the same list, not double anything.
For the general case of moving a spreadsheet into an app, see how to replace a spreadsheet with an app Claude builds. For the alert, see how to run a daily job in an app Claude built. For where each kind of data should live, see database vs cache vs queue vs object storage.
Frequently asked questions
Can Claude build an inventory tracker?
Yes. Describe your items, where they are kept, and how stock moves in and out. Claude writes the tables, the pages to record movements, and the low-stock view. On floo the tracker runs with a Postgres database, invite-only sign-in, and a scheduled job for alerts.
Should an inventory app store the stock count or the movements?
The movements. Record every receipt, sale, transfer, and correction as a row, and compute the count from them. The count is then always explainable, and a mistake is fixed with a correcting row instead of an edit nobody can trace.
How do I get a low-stock alert?
Add a cron job to floo.app.toml that runs each morning, finds items below their reorder point, and posts the list to your team chat or email.