To start an online store, prepare the material that lets you make real decisions: a focused set of products with workable prices, usable photos, accurate product facts, a brand direction, short trust pages, and payment and shipping settings you have checked with a real order.

Gaps in that material don’t stay hidden. A theme can cover one for a while with placeholder text, but it comes back when you write the product page, calculate delivery costs, or receive the first order. In Setka, our product, the material is also what the store is built from: Setka generates the store around your products, facts, and direction, so the more complete they are, the closer the first version is to one you can publish. If you are weighing a theme against a generated store, our comparison of an AI-generated store and a Shopify theme makes that trade-off concrete.

Products and prices

Start with the catalog you can actually finish. There is no ideal number of products for a first launch. Choose the smallest group that feels like a real collection and that you can explain, photograph, stock, and ship. A small, coherent catalog is far stronger than a large one with missing details.

For each product, record the selling price and the numbers behind it. Include your product cost, target margin, and shipping weight. Add packaging, payment fees, and other meaningful costs. A price can look healthy on the product page and still leave very little once the order is packed and sent.

Be clear about what is available now and what is planned for later. Do not build the launch around a future collection unless customers can easily understand its status. Your first catalog should make sense without you standing beside every shopper to explain it.

Product media you can realistically produce

Use media you can create consistently. Phone photos in clean, even light are more useful than polished stock images that do not show the real product. A simple background, steady framing, and repeatable crop will take you further than waiting indefinitely for a perfect studio shoot.

Aim for a few useful images per product: a main view, a close detail, something that shows scale or texture, and any angle a buyer would want to inspect before paying. For clothing, bags, containers, or anything with an important interior, show that too. The exact set varies by product, but customers should always know what they are buying.

You don’t need AI-generated media. Bring the product images you want customers to see: Setka places them in the store’s image slots and uses them to present and merchandise your products. Where the generated direction calls for an image you don’t have yet, Setka leaves a placeholder with a prompt describing what to shoot. Keep a separate folder for each product and give files clear names that identify both the item and the view. That small bit of organization makes later replacements much easier.

The facts behind every product

Good copy needs a factual boundary. Prepare a simple sheet for each product with the information a customer could reasonably ask for: materials, dimensions, care instructions, ingredients, origin, and compatibility. Include weight, what comes in the package, what does not, warnings, and intended use whenever they matter.

Write those facts plainly. “Fits 13-inch laptops” tells the customer something useful. “Designed for modern everyday carry” does not, unless you explain what that means. When a detail is still unknown, mark it as pending rather than letting a writer or AI tool fill the gap with a plausible guess.

This sheet is useful whether you write every sentence yourself or use a tool to help. Setka can generate or refine copy, preserve wording you already have, or combine the two. The product facts keep that copy grounded in what you actually sell.

Brand direction without a finished brand system

You don’t need a complete brand system before you begin. A logo and a fixed color palette help if you already have them; neither is a prerequisite. If you have a font in mind, write down its name: Setka uses it without a font file. What you do need is enough direction to keep the store from falling back on generic defaults.

Describe the tone and mood in ordinary language. Then share two or three references and explain what you would borrow from each: quiet typography, a dense product grid, warm color, generous whitespace, or a particular style of photography. Add one or two things the store should avoid. “Minimal” is only a label. “Quiet and tactile, with no glossy tech gradients” is useful guidance.

Once those notes exist, turn them into a store brief with your goals, customer context, catalog, facts, and references. The brief does not need polished prose. It just needs a clear point of view.

Trust basics

Customers often check the practical pages before they pay. Have a returns policy, shipping information, and a contact or About page ready for launch. They can be brief, but they need to be accurate.

State the return window and process, who pays for return shipping when relevant, where you ship, expected dispatch and delivery times, and how customers can contact you. Resolve any uncertain details before publishing instead of covering them with vague wording. A short policy that matches the business you run is more useful than a long one written for a company you may become someday.

Payment and shipping decisions

In Setka, you connect your Stripe account, choose the store’s currency (each store uses one), and enable payment methods in Stripe; the ones you enable appear at checkout. Setka has no payment test mode yet, so publish, place a real order on your phone, and refund it before you launch. Check the payment result, the order confirmation, the customer email, and the order where you will manage it. Run the same path on a desktop too. A finished-looking payment button is not the same as a working checkout.

Decide how tax applies in the markets you serve, then configure only what you can support. In Setka you set tax manually by product type. Set shipping zones, rates, and delivery estimates before launch. Setka’s shipping rules live in the admin: rates can depend on order value, not weight, and local pickup is available. Offer pickup when it matches how your customers like to receive orders.

Keep the first version narrow when your logistics are narrow. You can add countries, delivery services, and promotions later. The launch store should promise only what you can reliably deliver now.

A short pre-launch checklist

Use this as a final pass to catch missing work.

  • Products are selected, priced, and checked against cost, margin, and shipping weight.
  • Every product has usable media.
  • Product fact sheets are complete and reviewed.
  • Tone, mood, references, and clear exclusions are written down.
  • Returns, shipping, contact, and About information is present and accurate.
  • Payment is connected.
  • Tax settings, shipping zones, rates, and pickup options have been reviewed.
  • The homepage, product pages, cart, and checkout have been checked on mobile.
  • The most important product page has been refined beyond its first draft.
  • The store is published with a working way for customers to get help.
  • After publishing, a real order has gone through and been refunded.

Good preparation saves rounds of rework

Every complete input removes a round of questions from the build. Missing facts become placeholders. Missing media turns into a layout compromise. Undecided shipping becomes an unpleasant surprise for the customer.

That is the handoff Setka is built around. You bring the products, catalog, facts, and brand direction. Setka turns them into one store-wide direction and generates the homepage, collections, product pages, navigation, and cart from it, with no theme to pick or adapt. Then you describe changes, edit exact copy, preview, and publish. Every change saves a storefront-wide version, so you can try a new direction and return to the earlier one.

Preparation is done when you have enough accurate material for a useful first version. Next, turn those inputs into a store brief, then follow how to launch your first online store without a developer.