I fixed the catalog sync bug I said I'd fix
Cross-posted from Shipped With AI , my build log about learning to ship small tools with AI coding assistants. Originally published August 29, 2026, as the sixth post on the site. Status check, up front: this is a bug fix to a prototype, not a client story. No shop has signed up to use this tool. What changed is that a limitation I described in an earlier post no longer exists. In an earlier post…
I fixed the catalog sync bug I mentioned I would fix. The previous post about the product catalog tool revealed that the editing tool and the public catalog were split into two separate HTML files, causing a limitation where editing changes weren't reflected on the public catalog page. In this update, I addressed that specific issue.
Both files now share a browser storage key (localStorage) for saving and loading product data. The public catalog page now loads from that shared key first, falling back to its original hardcoded list as seed data if no changes have been saved yet. Each product carries a published flag, which the catalog filters out, ensuring that editing doesn't immediately make a half-written product visible to customers.
To verify the fix, I tested the behavior using a headless browser, confirming that changes made in the update tool appeared on the catalog page and that drafts remained hidden. This fix closed a previously mentioned gap between what the tool was supposed to do and what it actually did. The catalog prototype now behaves as initially described, with no new features, clients, or revenue generated.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
