Owned catalogue
130 products and four subscription tiers held in the project’s own database across six currencies. Everything is controlled in the admin; the commerce platform holds payment handles only.
LOADING
A luxury brand with a 130-product catalogue across six currencies, four subscription tiers and a gift-carrying checkout flow \u2014 with the commerce platform deliberately confined to processing payment and nothing else.
130 products and four subscription tiers held in the project’s own database across six currencies. Everything is controlled in the admin; the commerce platform holds payment handles only.
A themed intermediate checkout page carrying gift data as line-item properties, so the purchase experience stays inside the brand rather than dropping to a generic cart.
A locked editorial standard enforced across every product record — the kind of constraint that usually erodes within a month unless it is written into the system rather than the brief.
Built before the Baseline Week became standard. The catalogue and checkout are instrumented well enough to measure from here, but there is no signed pre-deployment record to measure against, and inventing one retrospectively is exactly what this site exists to refuse.
We would rather show an empty measurement than a plausible one. A number nobody can check is worth less than an honest blank.
The catalogue migration failed silently on large inserts — truncation with no error. Splitting it into small batches fixed it, and the general rule stuck: a bulk operation that fails quietly is more dangerous than one that crashes, so every migration since is chunked and verified by count rather than by absence of an error.