Verdant Template: A Houseplant Store Built on Aftercare

Verdant template: a plant shop that sells reassurance, not just plants

Verdant is a ready-made storefront for houseplants, one of the five store templates in the Zugo gallery. It filters products by how much light a room gets, explains care in plain language, upsells a potting service and promises a replacement if the plant dies. Cloning it costs no credits.

What makes it worth studying is not the layout. It is that the whole page is built around the customer's real objection, which is not price but the fear of killing the thing they just bought.

What is inside the Verdant template?

The structure reads as a conventional shop until you notice that every section is answering a doubt rather than describing a product. That is a pattern worth stealing even if you never sell a plant.

Notice what is missing: there is no long about-us section, no blog teaser and no newsletter block competing for attention. A shop with nine products does not need them, and adding them is the fastest way to make a small catalogue feel emptier than it is.

The care library is intentionally anticlimactic. It states that the whole method is a finger in the soil, matching the plant to your light, and repotting once a year. Selling something as easy and then publishing a thousand-word care manual undoes the sale.

Why does the light filter matter more than the design?

The catalogue filters by how bright the buyer's room is, not by plant family or price. That single choice converts a browsing problem into a question the customer can actually answer, and it removes the most common cause of a returned or dead plant.

The transferable idea is that the filter should match the constraint the buyer already has in their head. A bike shop filters by rider height, a paint shop by the room, a mattress shop by how you sleep. Categories that mirror your warehouse are convenient for you and useless to them.

The filter here works on real product data, so it is not a decorative dropdown. If you replace the products with your own and keep the attribute, the filter keeps working. If you replace the attribute with something your customer cannot self-assess, it stops earning its place on the page.

What works out of the box, and what only looks wired?

The storefront behaves properly. Filtering, adding to the cart, the cart counter, the drawer, the account screens and the mobile layout all respond. You can confirm every bit of that in the gallery preview before you clone anything, which is a good habit with any template.

What is not there is a shop behind the shop. There is no stock ledger and no order record, so the cart is a working interface over nothing. It also empties when the page reloads, because the template carries no storage. That is acceptable in a demonstration and never in a launch.

Payment is a separate step. The checkout is a set of screens, and taking real money means connecting Stripe to it. The practical detail people miss is that it also means deciding on shipping rules and tax before you publish, not after the first order. The wider picture is in can AI build with payments.

Accounts are the same story. The sign-in screen exists, the reminder list renders, and neither is backed by an identity system until Supabase sits underneath. Test the whole path in a second browser before you send the link to anyone.

Who is Verdant a good starting point for?

It fits any small shop where the product needs aftercare and the customer is nervous: plants, aquariums, sourdough starters, bonsai, garden bulbs, reptiles and their supplies. Anywhere a purchase can visibly fail in the buyer's hands within a month.

It fits a nursery with a modest online selection too. Nine products is a real constraint of the demo content, not of the template, and going to twenty or thirty is an edit. Going to several hundred with seasonal availability is a different project that needs a database from day one.

It is the wrong start for a broad general shop. If your catalogue spans unrelated departments, the light filter and the care library are dead weight, and you would be paying to remove the parts that make this template good. A plainer storefront is described in how to build an online store with AI.

It is also the wrong start if you sell wholesale. Trade pricing, purchase orders and minimum quantities are a different sales motion, and none of it is on this page.

Can you keep the care reminders promise?

Not with the template alone, and this is the honest catch. The page promises that the account tracks each plant's watering interval and nudges the customer the day before, which is genuinely the best feature of the business it describes. The template renders the list; it does not send anything.

Email reminders are reachable: the Resend connector handles sending, and Supabase holds the schedule and who owns which plant. That combination is a real project rather than a chat edit, and it is worth scoping before you advertise the feature.

The demo copy mentions text messages, and messaging is not part of the connector set. Either change that line to email, or treat the messaging piece as separate work with a provider you choose. Promising a channel you have not built is the kind of detail customers remember.

The same applies to the guarantee. A free replacement within a month is a business commitment, not a feature: it needs someone reading claims and shipping plants. Leave the promise on the page only if you intend to honour it.

How do you restock it with your own catalogue?

Content before cosmetics, as always. Each edit costs 3 credits, and rewriting the same section twice is the usual way people lose them.

1. Replace the brand and the promise line. Name, tagline, footer, guarantee wording.
2. Load your products. Names, photographs, prices, and the one attribute your filter depends on.
3. Rewrite the filter to your constraint. Light works for plants; yours might be room size, skill level or pet safety.
4. Rewrite the care library. Short, specific to what you sell, and honest about the failure modes.
5. Set currency, shipping and tax. The demo numbers are placeholders and always wrong for someone.
6. Connect payment and storage, then publish. The project sits at an address like yourshop.zugo.run, with your own domain layered on.

Keep the pet-safety flags or replace them with an equivalent warning label. Small trust markers like that carry more weight on a product page than another paragraph of description, and they cost one edit to add across the whole catalogue.

What does it cost to get to a selling store?

The clone is free and calls no AI, so nothing is spent until the first edit. A storefront reaching a publishable state usually takes six to nine edits, plus the connector work, which costs no credits but does take an afternoon.

Free gives you 5 credits. Pro is $25 a month for 200 credits, roughly 16 platforms, 33 builds or 66 edits, and Business is $99 a month for 800 credits. Every build runs in a sandbox before it is handed over, so a version that fails to open never reaches you.

On the free tier the template path is the only one that fits, since a build from scratch costs 6 credits and you start with 5. The clone is free and leaves room for one edit, which is enough to see your own products on a working shelf. What the free tier does and does not cover is spelled out in is it really free.

If every plant needs its own page for search, that is a multi-page platform: 12 credits for the first three pages and 3 for each after. A simple build takes about a minute; a multi-page one takes several.

Where does the template stop?

A cart is not a shop. Without storage and payment behind it, nothing is recorded and nothing is charged. That gap is two connectors and a working session, not one chat message, and it should be planned rather than discovered.

Stock and logistics stay outside. The page cannot know that you sold your last fiddle leaf fig this morning. For a nine-product shelf you can manage that by hand; past a few dozen lines you need real inventory.

Care advice is your expertise, not the builder's. It will format whatever you write beautifully, and it cannot tell you whether the watering interval you published is right for your climate. On a genuinely complex product Zugo does not replace a development team, and the source is always exportable to GitHub if you outgrow the builder.

A simple build takes about a minute, so trying it costs almost nothing. Open the gallery at zugo.dev, clone Verdant, and swap in six of your own products with the filter set to your customer's real constraint. That one change tells you whether this frame fits your shop.