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.
Account statements come off the bench rebuilt around the data’s reality, a one-line search request opens an archaeology dig, and last week’s pricing flag gets closed on schedule.
read this entry →386 commits promoted behind fail-closed gates, the helpdesk email saga gets its ending, a payment feature that was already there, and the enrichment machine’s control sample earns its keep.
read this entry →Running a new store while the legacy ERP is still the boss: what flows which way, why web orders wear a disguise, and a sync monitor that turns “did it work?” into a row in a table.
read this entry →A three-module merge from a second developer lands clean behind a fail-closed production guardrail, quick reorder ships, and Monday’s pricing lesson pays rent within the week.
read this entry →Eight pricing tiers, ten quantity breaks per rule, and one absolute promise: the customer always gets the lowest price. Why the pricing engine became the migration’s clearest case for building custom.
read this entry →The easy fix that lied, a statement feature parked rather than shipped with wrong numbers, a built-in read before it gets overridden, and why you diff every merge.
read this entry →Carrying an Algolia-powered search experience across the migration when no connector existed: a friendly hostile takeover of the shop page, and a sync that grew from throwaway script to code-owned infrastructure.
read this entry →Evaluating a payment connector, DevTools showed raw card data hitting our own server. The vendor said sandbox-only. The source code said otherwise — so we walked.
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.