Building thoughtful software with AI.Notes from the systems behind the work.
A good seller got an order of zero because its stock records had barely started, so a stockout looked like dead demand. I added a rule that reads the shape of the sales, backtested it, closed a second hole in the covered check, and caught my replay tool crying wolf.
Read moreA daily blind count, where the sheet hides the expected quantity, lost stock in its first version before anyone counted it, because a missing package quantity came through as zero and got skipped.
The order planner rounded a product to whole cases across all the stores, and when one store's line was blocked it re-split the cases without it, so the leftover landed on a store that never asked for it. Now the blocked share is planned, then removed, and the total only ever rounds down.
The bulk tagging tool treated a package as one thing while the point-of-sale system kept a row per room, so I moved writes to every stocked row and made the receipt admit it never reads room tags directly.
An empty-shelf floor in my ordering system turned tiny demand into full-case suggestions and blinded the small-order check behind it; the floor now needs real demand, and two sibling paths got the same treatment.
The discount tool counted package age from the producer's packed date, falling back to the last edit time. I had just bound its bulk write to a hash of the previewed plan; now age counts from the store's first receive event, unknown stays unknown and is never marked down, and the history read splits slow windows in half instead of failing.
The gateway's live tag route always named the whole batch, so tagging one line of stock would replace tags in every room it was split into. Now it names the row when it has one, and the receipt says which scope it actually sent.
One code path in my ordering system ignored the vendor's minimum-order setting and rounded every small shortage up to a full case. It now holds those lines for review with the real need still visible, still buys when a busy shelf is empty, and finally counts the back room.
A starter-case change for new products exposed that missing shelf counts and missing sales were being filled in as zeros, so readiness now checks how each number was obtained, the sales window keeps its first day, and only a narrow set of complete-window no-sale rows may count as a real zero.
The register feed and my spreadsheet catalog never shared IDs, so I put the links in their own table, link only on one exact brand-and-name match, and read sales through one route so nothing counts twice.
Sold-through packages kept landing in my planner's can't-find pile, so I taught it to check the report day's snapshot and the store's transaction history, matching only exact package IDs.
A display minimum applied to every eligible row meant allowed items with no recent sales could still get suggested orders, and the group planner ignored its own skip reason. The floor now applies only to required items, and the planner now respects that reason.
A round-to-full-cases button that skipped anything over one case led me to a cart field named for cases that actually held items, plus a hidden-product check that disappeared during a catalog move.
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.
A new screen turns a supplier price drop into a credit request and a register-update note, and the first version listed a product once for every store that stocked it.
A name matcher in my ordering system's sync glued unrelated products into one inflated count and dropped sales rows, so I switched live rows to the register system's own IDs, then lost more time to a server that was still building old code.
Hiding a product from one store was a single database write. Keeping it off real orders meant checks in the cart, checkout, reissued orders and the suggestion report, which as I read it would otherwise have flagged a hidden item and maybe suggested a full case of it.
Two pages in my ordering system had their own idea of when to buy more. I moved the rule into one module, rewrote its order gate twice in under an hour, fixed a badge that could say order now next to a zero, and added a button that builds an editable draft from the same rule.
The agent's new splitter cuts a store's group demand across the products my buyer marked, where a zero means yes and a blank means no. Rounding every share on its own breaks the total, the test signs off on an overshoot, and four different weight readers disagree about unlabeled products.