Issue reporting
Problem reports that arrive by phone and email are easy to lose. This tool gives customers one form, asks for the details you need, and puts each report into a tracker with photos and an owner. It suits any business that looks into product problems, such as a bike shop handling warranty claims or a food maker tracing a batch.
Tools Python · Flask · PostgreSQL · Claude
Built for AngelFire Ammunition
A Kansas ammunition manufacturer in Saint Marys.
The problem
A manufacturer needs to know where its complaints come from: which production lot, which product, what went wrong. Complaints arrived with no link to a lot or product, so there was nothing to investigate them against.
What I did
I built an online report form that opens only after a customer enters a real lot number from their box, then the product code. Every report filed through the form lands in a staff tracker, already tied to its lot and product.
The result
Reported issues fell by just over half, and each remaining report arrives tied to a real box, with its lot and product attached. Staff spend less time on complaints, complaint statuses are tracked for the first time, and a replacement is now decided with the lot and product in hand. A lot that draws repeat reports stands out sooner, so the company can respond faster.
Try it Demo data
The lot check a customer passes first, built from the live page's own markup, with invented lots. The invented lots and their box codes are listed at the top of the sample.
The staff tracker, rendered from its own templates with invented reports.
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.