Short answer
Setting up an online shop starts with the platform decision: a ready-made platform if your flow is standard, otherwise plug-ins, integrations or a custom build. Before launch you need payment, delivery and returns, legal texts and ETBİS registration, invoicing, product data and GA4 purchase tracking; one real test order checks them all together.
It is Friday evening and the last check before a Monday opening is under way. The photos are uploaded, the design is ready, the payment page opens. Someone places a test order: the payment goes through, but the order email never arrives, the record that reaches the courier has no address and accounting does not know what the invoice needs. To avoid a weekend like that, we look at how to set up an online shop by starting with the decisions, before the design.
This article covers the platform choice first, then the seven jobs that must be ready before launch, then what to watch in the first weeks. We do not recommend a particular platform or payment provider; we show which questions to ask when you choose.
Ready-made platform or custom build
There are three common routes, and the difference between them is who maintains what.
| Option | When it fits | What to watch |
|---|---|---|
| Ready-made (rented) platform | Your product, basket, payment and delivery flow is standard and you want to open quickly | The platform looks after servers and updates. If you need a rule it does not offer, you depend on a plug-in or a side service. |
| Open-source software that you host | You want more freedom over design and content and have a team that can run the software | Hosting, backups, security updates and speed are your responsibility. |
| Custom build | Your price, stock, membership or order rules fit no ready-made system, or you need a deep link to an ERP or warehouse | The start takes longer, and every later change is development work. |
Two questions are enough to decide. First: is your product, basket, payment and delivery flow standard? If so, start on a ready-made platform. If not, second: can a plug-in or an integration cover what is missing? If it can, a ready-made platform still does the job. If it cannot, a custom build comes into play, or a hybrid with a ready-made storefront and custom payment and stock handling.
The weight of this decision shows after launch. On a ready-made platform the first set-up is short, but if a rule you want months later is not available, your options are limited; in a custom build the start is long, but the flow runs on your own rules. So decide for the needs of the first year, not for today’s.
Before you look at platform names, put the decision on one written page: how many products, how many variants, which payment methods, which delivery options, and where stock is kept. If you will also sell on marketplaces, the same page feeds the marketplace integration decision.
Seven jobs before launch
The list below is in order. Every step ends with a proof that it is ready.
1. Company registration and ETBİS
According to the Ministry of Trade, service providers engaged in electronic commerce have to register with the Electronic Commerce Information System (ETBİS) before they start trading; registration is done through e-Devlet. If you sell only through a marketplace, confirm how the duty applies to you on the Ministry’s page and with your accountant. Proof it is ready: registration is complete and one person is named to report any changes.
2. Legal texts
Under the Regulation on Distance Contracts, a consumer may withdraw from the contract within fourteen days without giving a reason. A consumer who was not properly informed about the right of withdrawal is not bound by the fourteen-day period; in that case the right ends one year after the withdrawal period would have ended. The seller also has to prove the information was given. So the site needs: pre-contract information, the distance sales contract, withdrawal and returns terms, a privacy notice for personal data and a cookie notice. Do not copy the texts from a template; have a lawyer write them for your actual flow (who pays return shipping, which products cannot be returned). If you will contact customers by email or SMS, see email and SMS consent in Turkey for the consent side. Proof it is ready: the contract confirmation works on the payment page and a record of the accepted text is kept.
3. Payment
You choose the payment methods, such as cards and bank transfer, and the provider. Providers differ in how long their application and approval take, so start the application before the design is finished. Test four cases before launch: successful payment, failed payment, abandoned payment and refund. Proof it is ready: in each of the four cases the customer sees the right message and the order has the right status.
4. Delivery and returns
Set up your courier agreement, the regions you deliver to, how shipping cost is calculated and the returns flow. We cover how to write the returns and withdrawal page in a separate article. Decide from day one how orders reach the courier (by hand from a panel or through an integration); a manual flow copes in the first week but is the first thing to jam as orders grow. Proof it is ready: in the test order the tracking number reaches the customer.
5. Invoicing
Decide at the outset how you will issue invoices. The Revenue Administration’s e-Arşiv invoice application is one route: taxpayers in the scheme issue an e-Arşiv invoice for sales to taxpayers who are not registered for e-Fatura and to buyers who are not taxpayers. Agree with your accountant, in writing, which route you will use, whether the invoice is created automatically with the order or by hand, and who corrects the invoice when a return comes in. Proof it is ready: an invoice is issued for the test order and goes to the customer.
6. Product data
For every product, the title, description, images, variants (size, colour), stock, price and, where relevant, barcode should be in one table before you start. Bad data uploaded in bulk gets corrected one product at a time later. We cover which shots to take and what sizes to prepare in our product photo guide. Product structured data, which tells Google the price and availability on a product page, lays the ground for showing your product in search results with price and stock status; check whether your platform generates it on the product page. Speed matters here too: in why a fast site sells more we explained how to measure product, basket and payment pages separately. Write titles and descriptions in the words customers search for; internal codes find no match in search. Proof it is ready: no empty cells in the table, and every product has at least one image and a price.
7. Measurement
Google Analytics’ ecommerce documentation recommends the events view_item, add_to_cart, begin_checkout and purchase. A transaction ID (transaction_id) is required on the purchase event; send a unique one for every order. For the whole set-up, see the GA4 setup checklist. Proof it is ready: the test order appears in the GA4 realtime report, once and with the right amount.
Launch day: one real test order
The seven jobs are tested together with a real order. Before launch you or someone close to you puts a single product in the basket, completes the payment and ticks off the path the order takes:
| Stage | What to check |
|---|---|
| Order | Did the confirmation email reach the customer, and does the order show in the admin panel? |
| Payment | Are the amount and method right, and does a refund attempt work? |
| Stock | Did the stock of the sold product go down? |
| Delivery | Did the address and phone number reach the courier record in full? |
| Invoice | Was an invoice created, with correct details? |
| Measurement | Did the order show once in GA4, with the right amount? |
If any of these six rows does not complete, the launch date should move; it is far more expensive when your first real customer finds out.
What to watch in the first weeks
In the first two weeks, look at order rather than sales targets. Open the order list every day and check that the payment, delivery and invoice steps all completed; an order that sticks is often the first sign that the next one will stick for the same reason. Once a week, read the drop between add to cart and begin checkout, and between begin checkout and purchase, in GA4; visitors lost at the payment step usually point to a technical snag or an unexpected shipping cost. We wrote up how to get the site known to Google step by step in how a new site gets into Google. Set up customer service too: write down once where order questions, return requests and delivery complaints go and who answers them within what time. Every return request also tests whether your returns terms match the real flow. After the third week, look at which products are viewed but not added to the basket and start improving those product pages. The steps for collecting reviews from delivered orders are in our customer reviews guide.
Common mistakes
- Starting with the design. When the platform, payment and invoicing decisions change later, part of the design is redone.
- Copying the legal texts from a template. If the returns terms do not match your real flow, the text creates problems instead of protecting you.
- Leaving the payment application to the end. The approval time is not in your hands, and the launch date gets stuck on it.
- Issuing invoices by hand and expecting to grow. Manual invoices work in the first weeks and turn into late invoices in a campaign week.
- Leaving measurement until after launch. The first days’ data is the most valuable for fixing product and payment pages, and it cannot be recovered.
- Launching without a test order. Only a real order shows where the seven jobs connect.
We run the set-up together with the shop, integration and measurement in our e-commerce service; the site and software side is covered by our web and software service.
Common questions
Do I need a company to set up an online shop?
The status you sell under (sole trader, tradesperson or company) depends on your tax position. ETBİS registration, invoicing and the payment provider application vary with that status. So before you build the site, agree with your accountant which status you will sell under and which registrations are needed.
Is a ready-made platform or custom software better?
If your product, basket, payment and delivery flow is standard, a ready-made platform is usually enough and opens sooner. If your price, stock or order rules fit no ready-made system and no plug-in or integration covers them, a custom build or a hybrid is worth considering. Your flow decides which one is better.
How long does an online shop take to get ready?
It depends on the number of products, the payment provider’s approval, how long the legal texts and the invoicing set-up take, and the integrations, so a single figure would mislead. Build the calendar by starting first with the jobs that can take longest: the payment application, product data and legal texts.
There is one job you can do today: on a single page, write down the number of products, the variants, the payment and delivery options, where stock is kept and who will issue the invoices. That page decides both the platform choice and the order of the seven jobs above.
Sources
- Ministry of Trade (Türkiye): Electronic Commerce Information System (ETBİS)
- Regulation on Distance Contracts (mevzuat.gov.tr, in Turkish)
- Turkish Revenue Administration (GİB): About e-Arşiv invoices
- Google Analytics developer documentation: Measure ecommerce
- Google Search Central: Intro to Product structured data
This article is general information, not legal, financial or technical advice. Platforms, their rules and the law change over time, so some details may have changed since 11 November 2026 or contain small errors. Before you make a decision for your business, check the current official sources or write to us.