Skip to content
PixelformBuy an audit — $500

streetwear, built around timed drops

OFFSEASON

a drop-commerce storefront where every number on the page derives from a single rule, and the rule is the product.

What this is
self-initiated demo
Role
design, build and deploy
Year
2026
Type
concept brand, live storefront

01 / 02

what the problem was.

scarcity is the entire conversion mechanic in drop commerce. it is also the easiest thing on a site to get wrong, because it is not a copywriting problem — it is a data-integrity problem. the moment the counter on the product card disagrees with the number in the cart, or the archive says a chapter sold out while the catalogue still lists twelve of everything, the promise stops working. not weakens. stops. the customer doesn't file a bug report, they just stop believing the countdown, and the countdown was the whole business.

the constraints — 3 rows

Constraints

Role
design, build and deploy
Surface
concept brand, live storefront
Shipped
2026

what I decided.

one rule, stated on the fold and enforced everywhere: 24 pieces per style, one window, no restocks. every other number on the site is computed from it rather than written by hand — the per-product counters, the drop totals, the archive states, the low-stock thresholds. chapter 07 runs nine styles, from a €55 six-panel to a €360 waxed cotton jacket, and each one resolves against the same 24.

the rest is stripped back on purpose. a hard mono palette, no gradient anywhere, a marquee that says four things and repeats. the only motion in the build that carries meaning is the countdown, and it earns it because it is the one element the entire model depends on. an editorial photography system — a single locked night-shoot direction held across 38 frames — does the atmosphere so the interface doesn't have to.

built with lovable, on a real shopify backend via its shopify integration. the platform choice was the point: a drop brand's entire risk sits in the hours around a launch, so the storefront had to be something that could be changed the same afternoon a decision changes.

the stack

Stack

  • React
  • Vite
  • Shopify

why it was hard.

the sold-out state, not the live one.

drop sites are easy to make look good at T-minus-ten-days and hard to make survive T-00:00. the countdown, the cart, the stock counter and the archive are four views of one piece of state, and they have to agree while it changes underneath them — through the alert-list early-access window, through the cart lock at T-00:30, through the moment the last piece of a style goes and every surface referencing it has to update at once.

designing that is a state-modelling exercise before it is a visual one. which is the argument: the person deciding what "sold out" should look like has to be the person who knows when it fires.

what it produced.

a concept brand, built as a working store rather than a set of screens — because the interesting design decisions in commerce only show up once real product data is behind them.

the same hands, on yours.

Start with the audit — five days, $500, and it comes off the project if you book one.