What it takes to open an online store — the full checklist

Say "open an online store" and most people picture the website first — product cards, a cart button, a checkout form. But a store isn't opened by the site, it's opened by what happens after someone clicks "place order": whether the payment actually goes through, who delivers the parcel, what happens if the item comes back. A site can look finished and still be an unfinished store the moment the first disputed order arrives.

The list below splits into three parts: what the site needs technically, which documents and rules protect you, and how the day-to-day work actually runs. Most people finish the first part completely and put off the other two — then pay for it on the first order that goes wrong. Each item names exactly what to decide, and what happens when the decision gets skipped.

The technical part: what a working store is made of

1. Choosing a platform

An off-the-shelf platform gets you started fast, but fees, monthly cost and long-term flexibility differ between options. Once order volume grows and you need a custom integration — inventory software, a courier system — the limits of a template platform start to show. The choice should follow the size of the store, not whichever tool is trending. Writing down a rough number of products and categories in advance makes comparing platforms much easier.

2. A payment solution

Accepting card payment requires an agreement with a bank or payment provider — adding a "pay" button on its own is not enough. 3D Secure support, a clear message on a failed transaction, and payment that doesn't break between a mobile browser and the checkout page are the places where a real order is most often lost. Offering a second option, such as cash on delivery, also cuts the number of abandoned checkouts.

3. Domain, hosting and certificate

Your own domain, hosting that stays up, and an SSL certificate (https in the address bar) are the baseline. Without a certificate the browser shows a "not secure" warning, and that is exactly where a visitor leaves — on the payment page. Hosting speed gets overlooked just as often — a slow-loading store loses the visitor before they ever reach a product page.

4. The mobile experience

Most online shopping happens on a phone. Adding to cart, entering an address and the checkout form all need to work comfortably with one thumb. A form that looks perfect on a desktop screen often turns long and tiring on mobile. Testing checkout on an actual phone, with an actual thumb, is more reliable than trusting a browser's "mobile view" mode.

The legal part: what protects you

5. Registering the business

Formal registration as a sole trader or a company, and a tax number, is something to settle before launch, not after the first complaint. Plenty of sellers run on "message us" through social media without this step, but signing an agreement with a payment provider requires it. Tax obligations vary by product type and sales volume — clarifying that with an accountant up front is cheaper than a fine later.

6. Terms of use and a privacy notice

The site needs to say, in writing, who you are, how to reach you, and what customer data gets collected. It doesn't need to read like a legal filing — plain language in a place people can actually find is enough. A store that can only be reached through a social media account earns less trust than one with a real address and a contact form.

7. A return and exchange policy

You set this rule yourself and state it clearly on the site — it can differ by product category, since clothing, electronics and food each need a different approach. Without a written rule, every disputed order gets negotiated individually, and that costs both time and trust. Showing the policy before checkout, rather than after a complaint, is the cheaper place to spend that effort.

8. Protecting customer data

Name, phone, address, card details — the question is where they're stored and who can see them. Handing card data to the payment provider instead of storing it on your own server lowers your risk and removes obligations you don't want to carry. Keeping only the data an order actually needs is the simplest rule that protects you in a dispute.

The operational part: from order to delivery

9. Stock and inventory

If a product shows as "in stock" on the site but isn't in the warehouse, that customer is gone for good. Stock needs to update close to real time — even manually, once a day — as a minimum. If the same product sells through the site and through social media at once, stock needs to be managed from one place, or the same item risks getting sold twice.

10. Choosing delivery

Your own courier, a third-party service or the national postal operator — the right choice depends on speed within the city, regional reach and cost. When delivery time isn't stated on the site, the customer assumes the worst case, and sometimes cancels instead of waiting to find out. If delivery covers several cities, stating a separate timeframe per region keeps expectations matched to reality.

11. Order confirmation and notifications

After placing an order, a customer shouldn't be left wondering whether it went through. An automatic confirmation (SMS or email) and a notice when the status changes handle most support questions before they're ever asked. When status moves through stages like "preparing", "on the way" and "delivered", the "where is my order" call happens far less often.

12. Customer support

Who answers, on which channel (phone, WhatsApp, email), and roughly how fast — this needs deciding in advance. An order that gets no reply is the most common reason a store earns its first bad review. Response times outside working hours are worth stating on the site too — staying silent about it is the worst option of all.

How to read this list

• A gap in the technical part shows up immediately, on the first order — payment fails, the site is awkward on a phone.
• A gap in the legal part shows up in a dispute — with no written return policy, it isn't clear who resolves the disagreement or how.
• A gap in the operational part shows up as you grow — manually tracked stock and unanswered messages stop keeping up.

A finished website and an open store are not the same thing — the gap is whether the delivery, return and payment rules are actually written down.

Running all of this in parallel on your own isn't simple — most of the lost time sits exactly where platform choice overlaps with payment integration. See how we approach online store projects and talk to us about which step matters first at your stage.