Building thoughtful software with AI.Notes from the systems behind the work.
A send-to-tracker button on the sale report matches every selected store to its own workflow before sending, builds one PDF per store, and counts sent, skipped and failed instead of showing one green banner. Plus the timeout bug underneath that left run records stuck as started.
Read moreLetting my vendor credit report treat a digits-only promotion tag as a percentage was a mistake I pulled the same day; I now take the rate from structured data or work it out from the sale itself, with a headline that counts only claimable rows.
The report claimed the full register discount from suppliers. Each row now works out the vendor share from wholesale cost, keeps the register figure beside it, and labels the rows that still fall back to it.
The sale tag in my point-of-sale system sits on a single package, not on a product, so I moved the on-sale report down to package rows and found the parts that still overcount.
Building a report to flag one product with two live package tags in the same store led to a day of fixing what it meant by the same item: an unmerged per-package feed, split rows added together, one size bucket for loose flower, selling-floor stock only, and product IDs instead of names. Unreachable stores still get skipped without a word.
The register quotes pre-packaged flower per gram, so my staff sale sheet printed jar prices that were short by the package weight. I now read the weight off the end of the product name, and the fallbacks around that parser still worry me.
The Unspecified card on my discount report filtered for the literal word instead of the rows with no supplier, which SQL can never match. A shared marker and one filter builder fixed the drill-down, with a few gaps I can still see in the diff.