A print studio turned its numbered-edition drops into a self-serve storefront

Representative examplesEvery case study in this library is an illustrative composite of the kind of engagement we deliver — written to show our method and standards, not to name clients.

Where they started

Numbered editions of fine-art prints were the studio's entire business, sold to a mailing list the owner had built over years of markets and fairs. Each edition ran on a paper ledger — number, buyer, payment status — and every sale ended with a certificate of authenticity the owner composed and signed by hand before the piece shipped. The owner shoots, scans, and writes everything herself, and both rituals relied on her accuracy under drop-day pressure: an edition number entered twice had sold twice the prior year, the cardinal sin of numbered prints.

What it was costing

Editions sold via a mailing list and manual invoices; every drop meant a night of invoicing, and overselling an edition number — the cardinal sin of numbered prints — happened twice.

What they could see

• Every drop meant a night of invoicing: edition numbers ticked off by hand, payments chased, confirmations written individually.
• An edition number sold twice twice in the prior year — overselling a numbered piece meant refunds and an apology to a collector.
• The mailing list did the selling, but fulfilment ran on the owner's memory and a ledger that one late night could break.
• Certificates of authenticity and shipping notes were composed from scratch per order, hours of writing after every sold-out drop.

The constraints we worked inside

• Edition numbers are the product's promise; the system must make overselling structurally impossible.
• The studio's aesthetic is gallery-quiet; commerce chrome had to disappear.
• The owner shoots, scans, and writes everything — media handling had to be trivial.

What had been tried before

The owner ran drops through a payment-link generator, one link per edition number, pasted into reply emails.

Links didn't know when an edition was gone; a night of pasting under demand pressure was exactly how the double-sell happened — the tool relied on the discipline that fails at midnight.

A booking-calendar app was repurposed to reserve edition numbers before payment was collected.

Reservations without payment held numbers hostage — no-shows blocked real buyers for days, and the ledger still had to be reconciled by hand afterward.

What we proposed

We proposed making the edition itself the inventory unit: each numbered piece becomes its own product record generated from the edition list, so overselling a number is structurally impossible rather than carefully avoided. Product pages would lead with the scan at gallery proportions, with edition metadata set in quiet type — the gallery-quiet aesthetic was a hard requirement. Post-drop admin would automate: invoices, certificates of authenticity, and shipping confirmations generating from the order instead of by hand. Four weeks, one designer, and a storefront the owner runs alone.

Just as important is what we ruled out, and why:

• A marketplace for limited editions — The studio's pricing, collector relationships, and brand live on the mailing list; a marketplace would have taken a cut and inserted a catalog the owner doesn't control.
• A Shopify build with an edition-management app — App-based scarcity approximates what one-product-per-number makes structural; the monthly machinery outweighed four drops a year, and the admin would outgrow a one-person studio.

How the work ran

Delivered by the experience pod — designer over 4 weeks, with working increments reviewed with the client every week.

The stack, and the reasoning

Webflow Ecommerce

The store is a portfolio that happens to sell; Webflow lets product pages read as gallery objects rather than commerce listings, which was the aesthetic brief.

Stripe

Charges, refunds, and payouts sit in one Stripe ledger the owner can reconcile line by line against her edition ledger — the matching ritual that used to run on memory now runs on statements.

Webflow CMS

Edition metadata — number, size, paper, year — becomes fields, and the edition list generates the records, ending hand-built product pages entirely.

Order webhooks

Invoices, certificates, and confirmations trigger from the order event, so post-drop admin runs without the owner touching anything.

What went wrong

How we worked together

Cadence

A 30-minute call each Monday with the owner, plus a shared review link where she marked up pages between studio days.

Client side

The owner was the sole approver and the entire content department: scans, edition metadata, and the drop calendar all came from her.

Decisions

Aesthetic calls were hers alone; the certificate wording took three drafts; everything else followed the edition-ledger logic we agreed in week one.

They provided

High-resolution scans, the edition ledger as the source of truth, her mailing list's expectations as brief notes, and test purchase participation.

What changed

The headline: oversold editions — twice in the prior year, zero since the storefront — 0 → 0, read from Edition ledger. A second check: post-drop admin per edition at 1 evening → 20 min.

Drop night is now an evening off: the announcement goes to the list, the numbers sell themselves, and the owner wakes to a clean order queue instead of a negotiation. The oversell anxiety is gone structurally, not vigilantly — she stopped double-checking the ledger because there is no ledger to check. Collectors receive certificates within minutes, which she says upgraded how the work feels to own. The reclaimed nights went back to printing, and the next edition is already planned larger.

The result was read from Edition ledger against the pre-engagement baseline over the stated window, with a guardrail check on post-drop admin per edition. Where platform-reported numbers and business outcomes differ, this record says which layer it is quoting.

What they own now

• The Webflow project and its edition-record templates under the studio's own login.
• The edition-list import script, keyed to the studio's numbering file format.
• Webhook configuration with the payment-capture sequence documented for the certificate flow.
• A Stripe dashboard walkthrough covering payouts, refunds, and the next drop's test checklist.
• One recorded session on adding a new edition without touching a designer.