A running build log of a real ERP migration: half a million SKUs moving from a decades-old stack onto Odoo — the data work, the custom modules, the search layer, and the applied AI built along the way. Written as it happens, by the person responsible for it.
Shipments come to the dashboard with in-site tracking, five requirement documents get audited against 212 worklog entries — catching a contradiction no test would flag — and a button three customers had becomes a design for everyone.
read this entry →Instead of forcing forty years of catalog culture onto a modern grid, the store learned to speak catalog: a page-flip viewer with live prices and cart buttons, and exploded-view parts diagrams where the callouts sell the actual part.
read this entry →A payment gate that trusts customers the way the business always has — and un-trusts itself if its watchdog dies. Plus the purchase-history arc closes, and Monday’s scar-tissue essay demonstrates itself in forty-eight hours.
read this entry →How a (mostly) one-person migration stays coherent: no methodology was designed up front — every gate in the pipeline exists because a specific failure happened once, and was never allowed to happen twice.
read this entry →Historical invoices become payable three days after the entry saying they weren’t, a 155-second page gets a one-index fix, and special orders earn a real, auditable checkout step.
read this entry →A brand-new store where your 2018 invoices are already waiting: why legacy history earned its own models, and the archaeology it costs to make old data look effortless.
read this entry →Invoices become payable in the portal — several at once — a checkout bug turns into a philosophy lesson about addresses, and our own documentation gets proven wrong by a probe log.
read this entry →A colleague had an AI build a complete purchasing module. Round one: three blockers, including a collapsed two-person approval gate. Round three: one unused field. The difference was context, not capability.
read this entry →This log is the working record of systems being built, migrated, and kept in production. If you’re working through a problem in the same territory — interesting problems will always receive a reply.