
Go to demo.sellercart.shop and buy the camel overcoat. Pick a size, pay with the test card the checkout gives you, and the shop thanks you for your order. The coat will never arrive. Atelier Nord, the Lisbon label that sells it, does not exist.
The shop around the coat works like any other, and nobody designed it in an editor. It came from a spreadsheet of products, a few lines of terms and seven messages to an AI store builder.
Below is every message, in order, with the spreadsheet. It is public, photos included, so you can send the same messages and get a shop of your own built the same way. The agent writes its own copy every time, so yours will read differently. What repeats is the process, and the process is the point.
An AI store builder needs three things from you: your products, your terms and your taste. Everything between them, from the pages and the layout to the delivery table and the checkout, is the builder's work, and each step is one message.
The builder here is SellerCart. It is part of SellerClaw, a team of AI agents that connects to the stores you already sell on, your suppliers and your ad accounts. You work with it in a chat, in plain language, with nothing to install.
The finished home page. The dark strip at the very top is the one thing the messages did not ask for: it marks the demo.
Three things, and only you have them:
Photos travel inside the spreadsheet as links. If yours sit in a folder on your computer, attach them to the chat with the file, named by SKU.
Create a SellerCart shop for my clothing brand, Atelier Nord. We make knitwear, shirts, trousers, outerwear, accessories and shoes from natural fibres, cut in small batches and finished by hand in our Lisbon studio. Our customers are women and men in the US and Europe who buy fewer, better clothes. Prices in USD; let buyers switch to EUR, GBP and CAD, in the header and under the price. Look: a quiet boutique. Big photos, lots of white space, long product pages.
The agent opens the shop as a draft that only you can see. It takes the web address from the name and checks that nobody has it. The address and the currency are the two things that cannot change later, so a message without a currency gets a question back, never a guess.
Buyers see the shop in the language you choose, from the buttons to the checkout, whatever language you write to the agent in: a seller who writes in Spanish can open a shop in German. If you name none, the agent takes the language of your message, and you can switch it later.
"A quiet boutique" becomes one of the ready-made looks and layouts, adjusted to your words: the typefaces, the colours, how the header and the product cards sit, how a product page reads. Then the agent writes the first version of the home page and sends you a preview.
The extra currencies are for reading. A buyer in London sees prices in pounds, and the basket says what the card will actually be charged in dollars.
Here's our product feed: sellerai.com/atelier-nord.csv. Add it all to the catalog and put every product on the shop at 2.5× cost. Sort them into six collections (Knitwear, Shirts, Trousers & Skirts, Outerwear, Accessories, Shoes), each with its own page, a header photo and a line about it. Rewrite each description for the shop: what it is, the fabric, the fit, how to care for it. On the home page: the newest pieces as a carousel, and a Bestsellers grid with the merino crew, the linen overshirt, the wide wool trousers, the lambswool scarf, the chore jacket and the derby shoes.
Before it loads anything, the agent reads the file back to you: how many products it found, which come in sizes, which rows it could not read and why. It writes to the catalog on your yes. A file only adds and corrects. It never deletes a product you already have.
Each item becomes one product with a size picker, priced from its cost. Our feed carries what each piece costs us, and the shop sells it at two and a half times that. If your file already holds retail prices, say so, and the agent uses those instead.
The descriptions are rewritten for a buyer, with short paragraphs and the details people look for. The collections come from your category names, and each gets a page of its own.
The home page grids re-read the shelf on every visit. A new product joins the carousel by itself, and a price you change shows everywhere at once.
Look at the right column: the price is the feed's cost times two and a half, and the sizes and "Only 5 left" come from its stock column. The third thumbnail is a video, made in message 4.
Delivery, all from our Lisbon studio. United States: Standard $6, 3–5 working days, free over $150; Express $18, 1–2 days. Europe and the UK: Standard $14, 5–8 days, free over $200; Express $32, 2–4 days. Rest of the world: Standard $24, 7–14 days. Returns: 30 days from delivery, free, unworn with tags on; we email a prepaid label and refund within 5 working days. Contact: Rua das Flores 28, Lisbon, Monday to Friday 9:00–18:00, through the contact form. Set up the delivery zones and write Delivery, Returns, Contact, About, Size guide and FAQ pages; our story and size chart are at sellerai.com/atelier-nord.md. Put them in the header and footer menus, and turn on the cookie banner.
This is the longest message, and it has to be. Delivery prices, return windows and contact details are promises buyers will hold you to, so the agent never makes them up. A page still waiting for your terms stays out of the menu until you give them.
The zones go straight into checkout. A buyer in Lyon sees Standard and Express at your prices, with free delivery over the amount you set. The Delivery page restates the same zones, so the two never disagree: change a price later, and the page is rewritten in the same job.
Measurements and rate cards come out as real tables that still read on a phone. The cookie banner asks visitors for consent, and Google Analytics or a Meta pixel connect later with one more message.
Compare the table with message 3: the same zones and prices, laid out for a buyer.
Using our product photos, make a lookbook for the home page: six pictures of the clothes worn outdoors in northern Portugal, soft misty light. Turn the hero photo into a 5-second background video, and make a short video of the camel overcoat for its product page.
Product photos show the item. A shop also needs pictures of the life around it, and the agent makes them from your own product shots, so the clothes in the lookbook are the clothes you sell.
A video starts from a still. The photo of the clothes rail became the slow loop behind the home page headline, and the overcoat got a few seconds of movement after its photos. Each clip takes a few minutes, and pictures and video use the credits that come with your plan.
Have photos from your own shoot? Send them instead, and the agent puts them where they fit.
One photo of the rail, turned into five seconds of movement. It plays behind the headline on every visit.
Run 20% off all knitwear until March 1. Add these customer reviews to the home page: [three quotes, each with a name].
The discount applies at once, with no page to edit. Every knitwear price shows the sale price, the old one struck through and a 20% badge on the photo. It ends by itself when March 1 begins, and the agent warns you if any piece now sells for less than it cost you.
Reviews are the one block the agent will not fill on its own. A quote it wrote under a name it picked would be a fabricated review, so it uses only the words you paste. Atelier Nord is a made-up shop, so its three reviews were made up too, by us. For your shop, paste what real customers wrote, or leave the block out.
Look under each photo: the sale price, then the regular one struck through. Nobody edited these cards; the discount did.
Start a journal with four articles: how to wash and store wool knitwear, why linen gets better with every wash, a ten-piece autumn wardrobe, and a visit to the mill that spins our wool. Show the latest articles on the home page and add Journal to the menu.
The articles go to the team's writer, who drafts each one in the shop's voice. Every article waits for your OK before it goes up. The journal appears with the first one you approve, and the menu item and the home page block appear with it.
Show me the shop on a phone and a laptop, then give me the preview link. I want to place a test order.
Before it reports, the agent photographs the pages at both widths and looks at them, the way you would before showing a shop to anyone. Then it sends the screenshots and the link.
Until the shop first opens, its checkout runs in Stripe's test mode. Pay with card 4242 4242 4242 4242, any future date and any CVC. The order goes all the way to the thank-you page, no money moves, and the test order never counts as a sale.
The end of a test order on the demo shop. Look for the TEST badge next to the title: no money moved.
The builder does the work, and it brings every decision back to you:
Building a shop used to mean weeks of settings before the first product went up. Here it took three inputs and a handful of messages, and the inputs are the part only you could provide anyway: what you sell, on what terms, and how it should feel. If you would rather start from a single line and let the agent ask the rest, that works too: here is the same builder starting from one sentence.
Try the recipe on our feed first. Open SellerCart, paste message 1 and compare your draft with demo.sellercart.shop. Then run it again with your own spreadsheet.
The honest test is your own catalog. A builder that drafts a pretty home page around three sample products has done the easy part; the work is in your whole range with its sizes, prices and stock, your delivery rates at checkout, and pages that state your real terms. Our demo shop was built from a public product feed, so you can send the same messages, compare your result with ours, and then try it on your own spreadsheet.
Ask three questions. Does it load your whole catalog, sizes and prices included, or only generate a theme with placeholder products? Does it set up delivery, checkout and payments, or leave those to you in a dashboard? And does it keep working after launch: new products, sales, replies to buyers, ads? Many tools stop at the first draft. SellerCart's builder is the same agent that runs the shop afterwards.
No. SellerCart is a store of its own, with hosting, pages, cart and checkout included, and buyers pay into your own Stripe account. If you already sell on Amazon, the agent can put your listings on the shop with their photos and prices, joining the sizes and colours of one item into one product. eBay listings work as a starting point too.
Both. Anything buyers read, from the pages and the menus to the name and the look, goes through the agent, so changing one fact updates every page that repeats it. The settings that are yours alone have their own screens on the shop page: payments, delivery prices, markup, discounts, your domain and analytics.
SellerCart comes with a SellerClaw plan and has no price of its own. There is no percentage of your sales: buyers pay into your own Stripe account, and the only fee on a sale is Stripe's card fee. Pictures and videos the agent generates use the credits included in your plan.
Yes. Send a CSV or Excel file with one row per size: name, description, category, photo links, stock and cost. Your columns can keep their own names, in any language; the agent works out which is which and tells you what it skipped. It shows you what it is about to add and loads the file on your yes. A file only adds and corrects: it never deletes a product and never takes one off sale.
Yes, and the shop opens on it. Attach the domain on the shop page, and the agent gives you the exact DNS record to add where you bought it, then checks that the record works. Until the shop opens, it is a draft that only you can preview.
Yes. Until the shop first opens, its checkout runs in Stripe's test mode: pay with card 4242 4242 4242 4242, any future date and any CVC. The order goes all the way to the thank-you page, no money moves, and it never counts as a sale.