Inventory counts
Counting stock is easier when the counts are scheduled and every change leaves a record. This tool sets up regular counts, converts between the sizes you buy in and the sizes you sell in, and keeps a history of each adjustment. It fits any shop that buys by the case and sells by the piece.
Tools Python · Flask · PostgreSQL · BigCommerce · Claude
Built for AngelFire Ammunition
A Kansas ammunition manufacturer in Saint Marys.
The problem
The store keeps one stock number per product, with no record of who changed it or why. Counting the shelf, and repackaging the same ammunition from one box size into another, both change those numbers, and both needed a way to be checked and traced.
What I did
I built scheduled shelf counts, with printable worksheets, that show discrepancies as counts are entered. I also built box-size conversions that only run when the rounds divide into whole boxes. Conversions are validated before anything is written, and a count correction can never be sent twice.
The result
A shelf count takes less time, and corrections update the store automatically. Repackaging causes fewer round-count errors. When a number looks wrong, the app's history helps explain it: every change made through the app records the level before, the level after, who made it and where it came from.
Try it Demo data
Cycle counts and box-size conversions, rendered from the app's own templates with invented products.
Interactive samples use invented data, including invented names and prices. Pictures of the samples show the same invented data. Prices in screenshots of shipped marketing are already public.