TKAN Template: A Limited-Drop Store for Made-to-Order

TKAN template: a capsule-drop store built around scarcity

TKAN is a ready-made store for brands that sell in limited runs rather than from stock. The public side covers the live drop, a lookbook, size selection and a waitlist, and the member area holds a bag, preorders and order status. Cloning it into your own project costs no credits.

It is the odd one out among the five store templates, because it is not built around a permanent catalogue. Everything on the page assumes the run closes, and that assumption changes what you need to edit.

What is inside the TKAN template?

The structure follows how a drop actually sells: build anticipation, show the goods honestly, take reservations against a counter, then close the door. Each section carries one job, and there are fewer of them than in a conventional shop.

The size table is the part worth studying. It gives garment measurements laid flat rather than body sizes, adds a fit note per size, and tells you to size down if you are between two. In made-to-order that is not a nicety: you cannot resell a returned unit that was cut for one person.

The member area tracks something a normal shop has no reason to show: how far along the production run is, and the promise of a photo before dispatch. That block exists because customers here wait weeks between paying and receiving, and silence in that gap is what generates support email.

What actually works, and what is only a front end?

Everything visible works as an interface. Size selection holds a unit, the bag counts up, the countdown runs, the checkout screens advance, the member area switches between bag, preorders and order status. The gallery preview lets you confirm all of that before you clone anything.

What does not exist is anything behind the glass. There is no stock ledger, so the counter of reserved units is a number on a page rather than a claim about inventory. Two people can hold the same unit, and nothing in the template will notice.

The bag also empties on reload, because no database sits underneath. That is fine for a demonstration and unacceptable for a launch, and it is the single most important thing to fix before you send the link anywhere. Real storage and real accounts come from the Supabase connector.

Payments are absent by default too. The demo says the card is charged when the run is cut, which is exactly right for made-to-order, and implementing it means connecting Stripe rather than editing the wording. How that connection works is covered in payments in an AI-built app.

Who is this template right for, and who should skip it?

It fits anyone who makes to order in a fixed run: small fashion labels, furniture makers, ceramicists, print runs, instrument builders, a band selling a merch drop. Anything where you cut the number that sold and then stop.

It fits preorder launches outside fashion too. Swap the size table for a specification table and the same frame works for a hardware batch or a limited book edition. The scarcity mechanics stay intact, which is what you came for.

Skip it for a normal shop with continuous stock. If you restock, discount and run hundreds of SKUs, the countdown and the run counter fight you the whole way, and you will spend edits removing the best parts of this template. Start from a conventional storefront instead, as described in how to build an online store with AI.

Skip it as well when returns are routine. The whole page argues that nothing is left over, which is the wrong promise if your business assumes a share comes back.

Is cloning cheaper than describing a drop store from scratch?

A build from a written description costs 6 credits and produces exactly what your text asked for. A clone costs nothing and only bills you for the differences, and you can see the frame working before you commit to it.

For a drop launch the clone almost always wins, because this structure is unusual enough that describing it accurately is hard. A prompt that produces a countdown tied to a run counter, a hold timer and a preorder path for the next volume is a long prompt, and long prompts are where details get lost.

Building from scratch wins when your sale is a straightforward one. If you simply want product cards, a cart and a checkout, this template is a detour through machinery you do not need.

Plan the page count before you start. A single scrolling page covers most drops. If each piece needs its own address for search and sharing, that is a platform: 12 credits for the first three pages and 3 credits for each page after.

How do you rebuild it around your own drop?

Content before cosmetics. Each edit costs 3 credits, so getting the order right saves real money over a launch week.

1. Replace the brand and the promise. Name, the line under it, the footer. One edit covers all three.
2. Set the run. Number of pieces, units cut, reservation share, the lock date the countdown counts to.
3. Swap the lookbook. Your photographs, your captions. This section carries most of the persuasion.
4. Rewrite the size table. Your measurements and your fit advice, or a specification table if you are not selling clothing.
5. Change the currency and shipping. The demo prices are in pounds sterling with a flat shipping line, which almost certainly is not yours.
6. Wire the list and the payment. Waitlist emails through Resend, charges through Stripe, reservations stored in Supabase.

The hold timer deserves a decision rather than a default. Twenty minutes is a reasonable pressure for a fashion drop and far too short for a considered purchase. Change the number, or remove the hold entirely and let people reserve at their own pace.

What does it cost to get to a real launch?

The clone is free, so the meter starts at the first edit. A drop store reaching launch usually takes six to ten edits, plus the connector work, which costs no credits but does cost an afternoon.

Free gives you 5 credits. Pro is $25 a month for 200 credits, which is about 66 edits or 33 builds, and Business is $99 a month for 800 credits. Every build opens in a sandbox before delivery, so a version that does not run never reaches you.

On the free tier the template route is the only one that fits: a build from scratch needs 6 credits and you have 5, but the clone is free and leaves room for a first edit. Your brand name on a working drop page costs nothing to see.

Which edits do people ask for most?

"Make it nine pieces instead of seven and show the fabric on each card." "Add a second size run for women with its own measurement table." "Replace the twenty-minute hold with a simple reserve button and no timer."

Trust requests come up quickly, and they matter more here than in a normal shop because the customer pays before the thing exists: "add a section explaining how made-to-order works, with dispatch timing and the refund policy stated plainly."

Phone requests are worth making early: "on mobile, show the lookbook as a swipeable row and pin the reserve button to the bottom of the screen." Drop launches spread through social links, and social links open on phones.

Where does this template stop?

A counter is not inventory. Reserved units are displayed, not tracked, so overselling is possible until real storage sits behind the page. For a run of a few hundred units that is a genuine business risk, not a cosmetic gap.

Sizing and production stay your job. The template can present a size chart beautifully and cannot tell you whether your grading is right. Same for lead times: the four to six week promise in the demo is text, not a schedule.

Complex commerce logic arrives through edits, not one prompt. Tiered member pricing, per-country shipping rules, partial refunds on a cancelled run: reachable, but as a sequence of changes. On a genuinely complex product Zugo does not replace a development team, and the source is always exportable to GitHub. The wider view of what these builds can carry is in does it work for e-commerce.

A simple build takes about a minute, so testing the idea is cheap. Open the gallery at zugo.dev, clone TKAN, put your next drop into it, and see whether a run counter changes how the page reads.