Saturday, May 30, 2026

Model the thing generally enough and one schema serves a fridge, a walk-in, and whatever comes next.

Reworked the gasket catalog from refrigerator-specific into a generic asset-and-parts model — so the same data layer handles any piece of equipment and any part that fits it. Ported the store onto it, wrote the SEO plan, and specced the field app.

Shipped

• Generic catalog — one schema for any asset, its parts, and the profiles that fit
• Store ported — find-a-gasket form polished: custom-cut, OEM part #, loading states
• Catalog seeded — confirmed dimensions across the major equipment brands
• SEO plan — national parts store plus a free installer-network directory
• Field-ops app spec — a mobile inspection/install tool, scoped and backlogged
• KPI named — Mean Time Between Service: how often a site actually needs work

Notes

The reframe from "refrigerator" to "asset" is the kind of generalization that pays off for years. Every later feature gets to assume one model instead of special-casing its way around the data.