Inventory Tracker

How to use this file: paste this whole document into your AI builder (Claude, ChatGPT, Cursor, Lovable, Replit, Type) as context. Then send the build prompts in section 15 one at a time. Do not move to the next phase until the acceptance checks for the current phase pass.

1. The problem

"We find out we're out of something when someone needs it."

A cleaning company, workshop, clinic or small warehouse keeps supplies in a store room and a few vans or shelves. The stock list is a spreadsheet that is right on the day someone counts and wrong a week later. Nobody records what they take, reorders happen when a shelf is already empty, deliveries arrive without anyone checking them against the order, and the yearly count turns up losses nobody can explain.

This blueprint is a shared stock list with quantities per location, kept current by recording every use, delivery and move as it happens (a phone camera and a QR label make that take seconds). Low stock is flagged before it runs out, purchase orders are received against what was ordered, and regular blind counts correct the numbers with a record of every difference.

2. What the real product does

Research basis: Sortly's pricing page and plan comparison table (sortly.com/pricing), October 2026.

What we verified:

1. Plans and prices. Free: $0 for 100 unique items, 1 user license and 2 active jobs. Advanced: $49 a month billed monthly, or $24 a month billed yearly ($288), for 500 items and 2 user licenses. Ultra: $149 a month, or $74 a month billed yearly ($888), for 2,000 items and 5 user licenses. Premium: $299 a month, or $149 a month billed yearly ($1,788), for 5,000 items and 8 user licenses. Enterprise: by quote, for 10,000 or more items and 12 or more user licenses.
2. The yearly prices are introductory. The page says the 50% discount on yearly plans applies only to the first year of a new subscription; after the first year, yearly plans are 20% off. Paid plans have a 14-day free trial, and a credit card is required to start it.
3. Features by plan. Every plan, including Free, has item photos, folders, tags, inventory import, in-app barcode and QR code scanning, offline mobile access and activity history reports. Advanced adds QR label creation, item check-in and check-out, low stock alerts, email alerts and low stock reports. Ultra adds barcode labels, third-party scanner support, purchase orders, pick lists, stock counts, date-based alerts, more reports, and Slack, Microsoft Teams and Amazon Business integrations. Premium adds custom role permissions and QuickBooks Online. API, webhooks and SSO are listed only on Enterprise.
4. History is limited by plan. Activity history is kept for 1 month on Free, 1 year on Advanced, 3 years on Ultra and without limit on Premium and Enterprise.

For a team of 10 people who all record stock, the published plans stop at 8 user licenses (Premium), and purchase orders and stock counts start on Ultra (5 user licenses).

What this blueprint keeps

Items with photos, SKUs, barcodes, units, costs and reorder points; quantities per location; recording use, deliveries, moves between locations and adjustments, each as a permanent movement; low stock alerts that count what is already on order; reorder suggestions grouped by supplier; purchase orders with partial receiving; blind stock counts with variances approved by an admin; QR labels for items and locations; scanning with the phone camera; stock value, low stock and usage reports; a CSV export of every movement.

What this blueprint deliberately leaves out

An offline mobile app, pick lists, jobs and work orders, checking tools in and out to people (see the Equipment Tracker blueprint), serial numbers, lots and expiry dates, several units of measure per item, sales orders and online store sync, accounting integrations, Amazon ordering, and accounting-grade costing (FIFO or weighted average). USB and Bluetooth barcode scanners that type like a keyboard work in the scan box; dedicated scanner hardware does not get special support.

3. Scope of v1

• One company, a handful of locations (a store room, vans, shelves, sites).
• Quantities are whole numbers in each item's unit (bottle, box, case, each). Count in the unit you buy and use; an item has one unit.
• Money in integer cents. Stock value is an estimate using each item's latest unit cost, not an accounting valuation.
• Email through an outbox. If no email provider is configured, emails are logged, not sent.
• A web app that works well on a phone, because most stock is recorded standing at a shelf.

4. Roles

Staff never see unit costs, stock values, supplier prices or purchase order totals. The server enforces this, not only the screens.

5. Data model

All IDs are strings. Timestamps in UTC.

Person

• id, name, email (unique, lowercase), role: admin | staff, default_location_id, active

Location

• id, name (unique), code (short, unique, used in location labels, such as "VAN1"), active

Supplier

• id, name, email, lead_time_days

Item

• id, sku (unique, such as "GC-32"), name, unit, barcode (optional, unique), photo (optional)
• unit_cost_cents, reorder_point, reorder_qty, supplier_id, low_alerted (true after a low stock email, until stock rises above the reorder point again), archived

Movement (append-only; the on-hand quantity is the sum of movements)

• id, at, item_id, location_id, quantity (positive in, negative out)
• type: opening | receive | use | move | adjust | count
• reason (required for adjust), po_line_id, count_id, transfer_id (joins the two sides of a move), person_id

You may keep a balance table (item, location, quantity) for speed, updated in the same transaction as each movement, but it must always equal the sum of movements.

PurchaseOrder

• id, number (PO-0001, sequential), supplier_id, status: draft | sent | partially_received | received | cancelled
• expected_date, sent_at, closed_short (true when an admin closes it with quantities outstanding), notes, created_by

POLine

• id, po_id, item_id, qty_ordered, qty_received, unit_cost_cents

Count

• id, number (C-0001, sequential), location_id, status: open | submitted | approved | cancelled, started_at, started_by, submitted_by, approved_by

CountLine

• count_id, item_id, expected (on hand when the count started), counted (empty until entered), changed_during_count

Event (append-only) and Notification (outbox): id, at, actor, type, data; and id, kind, to_email, subject, body, status: queued | sent | failed | logged, error.

6. Recording stock

Worked examples (seed data in section 14, applied in order)

7. Purchase orders

Receiving more than is outstanding on a line is refused: "Ordered 8, 0 received; you can receive up to 8." Extra units that arrive anyway are recorded by an admin as an adjustment with the reason Found.

8. Business rules

• R1. No negative stock. No movement may take a location below zero. Check and write in one transaction so two people taking the last unit at the same moment cannot both succeed; the second gets "Only 0 on hand at Van 2."
• R2. Movements are permanent. Movements and events are never edited or deleted. Mistakes are corrected by an adjustment with a reason.
• R3. On order. An item's on-order quantity is the outstanding quantity on its sent and partially received purchase orders.
• R4. Low stock. An item is low when its total on hand across locations is at or below its reorder point. The first time it becomes low, every admin gets one email and low_alerted is set; nothing more is sent until the total rises above the reorder point, which clears low_alerted.
• R5. Reorder suggestions. Suggest an item when on hand plus on order is at or below the reorder point; the suggested quantity is the item's reorder quantity, at its current unit cost.
• R6. Unit cost. Receiving a purchase order line sets the item's unit cost to that line's unit cost. Stock value is quantity times the current unit cost.
• R7. Counts. An admin or staff member starts a count for one location; each line records the on-hand quantity at that moment as expected. Counts are blind: counters never see expected quantities. Lines whose item has a movement at that location after the count started are flagged "Changed during count" and must be recounted or confirmed by the approver. On approval, each line with a difference posts one count movement of counted minus the current on-hand quantity.
• R8. Archiving. Items are archived, never deleted, and only when they have nothing on hand and nothing on order. Locations can be deactivated only when empty.
• R9. Visibility. Staff never see costs, values or purchase order totals (section 4).
• R10. Units. An item's unit cannot change once it has movements; create a new item instead.

9. Screens

1. Items (home). Search by name, SKU or barcode; filter by location, supplier and low stock. Each row: photo, name, SKU, total on hand and unit, a "Low" badge with the on-order quantity, and (admins) value.
2. Item page. Photo, details, quantity at each location, on order, and the full movement history. Buttons: Use and Move for everyone; Adjust and Edit for admins. On a phone, Use defaults to the person's default location with a quantity stepper.
3. Location page (opened from a location label). Every item at that location with its quantity and a one-tap Use.
4. Scan. Opens the camera and reads QR codes and common barcodes (UPC, EAN, Code 128) using a scanning library or the browser's barcode detector, with a text box for typing or a keyboard-style scanner. A match on barcode or SKU opens the item; a location code opens the location.
5. Purchase orders and Reorder suggestions (admins), with Receive available to everyone on sent orders.
6. Counts. Start, enter quantities (blind), submit; admins review variances in units and value and approve.
7. Reports (admins): stock value by location and by supplier, low stock with on order, usage by item over the last 30 or 90 days, movement export.
8. Labels, Locations, Suppliers, People, Settings and Outbox (admins).

10. Notifications

Write every email to the outbox first, then send it. With no provider configured, set status logged. A daily job (protected by a CRON_SECRET header) sends overdue reminders and retries failed emails. A failed email never blocks the action that caused it.

11. Time

All "now" reads go through one function that adds the development clock offset, so overdue purchase orders and usage windows can be tested by moving the clock.

12. Labels, scanning and export

• Item labels show the name, SKU and a QR code for the item's page URL (/i/). Location labels show the location name and a QR code for /l/. Both print on US Letter sheets of 30 labels (3 columns by 10 rows, the common 1 by 2⅝ inch address label size). Any phone camera opens these links; the person must be signed in.
• The movement export is a CSV of every movement: date and time, SKU, item, location, type, quantity, person, reason, purchase order number, count number.

Using the Inventory Tracker blueprint above, build Phase 1 only.

1. Set up the data model from section 5 exactly, with a real database.
2. Add sign-in with the platform's built-in auth or Google sign-in limited to our company email domain. A signed-in email must match an active Person; anyone else sees "Ask an admin to add you."
3. Build People, Locations, Suppliers and Items (create, edit, photo upload, archive with R8 and R10), the Items list and the Item page (section 9, screens 1 and 2) without the Use, Move and Adjust buttons, enforcing R9 on the server.
4. Load the seed data from section 14, with dates relative to today, including the movement history.
5. Add a "sign in as" switcher, a "move the clock forward" control and a "reset to seed data" button, all visible only in development.

When you're done, list what you built and anything in the spec you had to interpret.

Using the Inventory Tracker blueprint above, build Phase 2 only.

1. Add Use, Move and Adjust (section 6) on the Item and Location pages, with R1, R2 and R4, all on the server.
2. Write the low stock email (section 10) to the outbox and build the Outbox screen.
3. Build the Labels screen and the Location page (section 12 and section 9, screen 3), and the Scan screen (screen 4).

When you're done, list what you built and anything in the spec you had to interpret.

Using the Inventory Tracker blueprint above, build Phase 3 only.

1. Build Purchase orders and Reorder suggestions (section 7 and section 9, screen 5) with R3, R5 and R6.
2. Write the purchase order emails and the overdue reminder (section 10) to the outbox, with the daily job.

When you're done, list what you built and anything in the spec you had to interpret.

Using the Inventory Tracker blueprint above, build Phase 4 only.

1. Build Counts (section 9, screen 6) with R7, and the count submitted email.
2. Build Reports and the movement export (section 9, screen 7, and section 12).

When you're done, list what you built and anything in the spec you had to interpret.