Building thoughtful software with AI.Notes from the systems behind the work.
A stock ceiling and my empty-shelf guarantee collided on a single supplier case, and the planner settled it by dropping the product with no reason. I ranked the rules, let one store go over on the record, and threw out the agent's first odd-case version because it pushed a stocked store over its own cap.
Read moreA catalog that filed one product family under two labels left sibling definitions with no sales to claim, so I named the pair as one family, let empty siblings borrow from exactly one owner, and pulled unit cost out of the keys I should never have put it in.
The daily sales rate behind my order skipped the days the shelf was empty, so an order worth six to nine months of stock looked like two; now the rate comes from raw calendar days, the proof is pinned to the exact order version, and replay won't borrow another version's story.
Several reviewed catalog rows described the same product on the same shelf, and each one planned its own full case; I made the planner count each family once per store, hand demand out a whole case at a time from one set of stock facts, and cap the result by real shelf room, after trying and then pulling a cross-store leftover carry.
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.
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.