Use case

Inventory tracking your spreadsheet gave up on.

The stock sheet is wrong the moment two people edit it. Reorders happen when someone notices an empty shelf, and the annual count is a scandal. A generated inventory system records movements instead of totals - so stock levels are always derived, always current, and reorder points actually fire.

What your generated system includes

Data model

  • Items: SKU, description, unit, reorder point, supplier
  • Locations - warehouses, shelves, vans, sites
  • Movements: in, out, transfer, adjustment - who and when
  • Suppliers with lead times

The flow

  • Receive: log incoming against a PO or delivery
  • Issue: log outgoing to a job, order, or person
  • Transfer between locations with both sides recorded
  • Counts reconcile as explicit adjustments, not overwrites

Automations

  • Reorder alert when stock crosses the item's point
  • Draft reorder grouped by supplier for your approval
  • Weekly movement digest and slow-mover flag
  • Discrepancy alert when a count diverges past a threshold

Views

  • Live stock by item and by location
  • Movement history per item - the full story
  • Value on hand, if you track cost
  • Team logging on phones via the responsive UI

Try this exact prompt

Paste into Chromoly

Build an inventory system. We stock about 300 SKUs across a main warehouse and two vans. Every movement gets logged: receiving against deliveries, issues to jobs, transfers between locations. Each item has a reorder point - alert me when stock crosses it and draft a reorder grouped by supplier for my approval. Monthly counts reconcile as adjustments with a reason. Show live stock by location and full movement history per item.

Movement-based tracking is the load-bearing choice - totals are computed from history, so the number on screen always has an explanation behind it.

Why movements beat totals

A spreadsheet stores totals, and totals lie: overwritten cells have no history, and no one can say why the count is off. A system that stores movements derives the totals - every number traces to who logged what, when. Discrepancies become findable events instead of annual mysteries.

It's also what makes automation trustworthy: a reorder alert firing off a derived, auditable number is worth acting on. One firing off cell B37 is not.

Frequently asked questions

Can this handle barcodes?

V1 works with SKU entry and search on any device - fast enough for most small operations. Camera-based barcode scanning isn't in V1; if scanning hardware writes to a spreadsheet or sends webhooks, that stream can feed the system.

We have items in customer sites too - can locations be anything?

Yes - locations are your list: warehouses, vehicles, job sites, customer premises. Transfers between any of them are first-class movements with both sides logged.

Who maintains the system after it's built?

Chromoly does - monitoring, security patches, AI model upgrades, and integration migrations are platform-owned for the lifetime of the account. Changes you request run through a dependency-aware preview showing the blast radius before anything ships.

Can I import my existing data?

Yes - export your current spreadsheet or tool to CSV and import with column mapping, or attach the spreadsheet to your prompt and Chromoly shapes the data model from it directly.

Know what you have without walking the shelves

Describe your process in plain language. Preview the working system free - deploy when it's right.

Start free →

150 credits/month free forever · EU-hosted · maintained for life