Frequently asked questions

Sepetya is a cloud e-commerce platform that lets you open and run an online store under your own brand. You manage products, orders, payment and shipping settings, campaigns and customers from one dashboard and publish the store on your own domain.

It suits small businesses opening their first online store as well as stores with large catalogs (within the plan limits). See the solutions pages for themes that fit your industry.

No. The setup wizard guides you step by step from store details to launch; you design the store without code, adding and ordering sections in the theme editor and choosing colours and fonts. Advanced users can add custom scripts with a consent category or connect their own systems with the API and webhooks (API access depends on your plan).

The setup wizard takes you through: store details, language and currency, legal details, theme, first product, shipping, payment, domain, policies and launch. To be ready to launch, the checklist expects your legal details (name, address, tax or identity number), at least one product, a shipping rate and an active payment method; the theme, domain and policies are optional. Customers can only place orders once shipping and payment are set up.

Verifying your account e-mail and, if the company operating the platform requires it, an approved business verification can block launching.

You can sell physical products, digital products (delivered with a download link after the order), services and bundles. Products can have variants (such as colour or size), a unit price (per kg or litre) and personalisation fields that ask the customer for information or a file (text, file upload, date, colour picker). See Products and inventory.

Finding out which permits and documents your products require, and following the platform’s acceptable use policy, is your responsibility.

The store dashboard is available in Turkish and English; you choose the language from the user menu. It is a responsive web app that also works in a mobile browser; there is no separate iOS or Android app.

Yes. You can open several stores with one account and switch between them with the store switcher at the top of the dashboard. Every store has its own plan, invoices, staff and domains.

There is no built-in marketplace integration. The platform is designed so that such integrations can be developed separately on top of the module SDK; you can also connect orders, products and stock to your own system or a marketplace tool with the REST API and webhooks. See the integrations and developers pages for details.

Stores from any industry can be built; the ready-made themes and industry pages are designed separately for fashion and apparel, multi-category stores, electronics, cosmetics, home and living, grocery, jewellery and accessories, and kids and toys. Every theme is structurally different, with its own header, home page sections, product card and footer. Pick your industry on the solutions page and browse the demo stores.

Yes. You add your domain under Online store › SEO & domains and create the DNS records the dashboard shows at your domain provider: a TXT record for ownership and, for routing, a CNAME on a subdomain or an A record on the apex domain. Once the records are verified the domain becomes active. You can connect several domains, make one primary and redirect the others to it. The custom domain feature and the number of domains you can connect depend on your plan. See Domains and SSL.

When it is created, your store gets a ready-made subdomain based on your store address (slug); nothing needs to be set up and this address always works. You can connect your own domain later.

No. Once your domain’s DNS records are verified, the SSL certificate is issued automatically and renewed before it expires; you do nothing to install or renew it. The platform’s subdomains already have a valid certificate. The registration fee of the domain itself belongs to your domain provider.

Yes. You can import your products with a CSV; images are given as addresses (URLs), and the product CSV depends on the bulk operations feature of your plan. You can also add your customers and past orders to the dashboard with a CSV (stock is not changed for orders). You can bulk-upload 301 redirects from old to new addresses as a CSV and connect your domain to the new store. See the migration guide for step-by-step help.

No. Passwords are stored irreversibly, so they cannot be taken from the old platform. When you import your customers their accounts are created without a password; customers set a new one with “forgot password”, or you can send an account invitation e-mail from the dashboard.

Yes. CSV import and export cover products, variants, stock, prices, translations and more; you download the template from the dashboard, fill it in and upload it. Row errors and an error report are shown when the import finishes. CSV operations depend on the bulk operations feature of your plan. You can also select several products in the dashboard and edit fields such as price, tags or categories in bulk.

You can reduce the risk with 301 redirects. You can bulk-upload a CSV that maps old addresses to new pages; chains are flattened and loops are checked. If a page’s address (slug) changes inside the store, an automatic 301 redirect is created. A redirect does not guarantee that rankings are kept, but it tells search engines about the address change correctly. See SEO.

Yes. On Settings › General you can put a storefront password on your store; until the password is removed and the store is launched, only people who know the password can open the storefront. You launch with the “Launch store” button in the dashboard, which also removes the storefront password. For customers to place orders, at least one shipping rate and an active payment method must be set up.

Use the payment apps’ test modes: with iyzico’s test environment (sandbox) or PayTR’s test mode on, no real payment is taken; with Stripe you work with test keys. You can cancel trial orders placed with bank transfer or cash on delivery in the dashboard. While you test, you can keep your store closed behind a storefront password.

For card payments you can use iyzico, PayTR and Stripe; you can also offer bank transfer, cash on delivery (cash or card), pay in store for in-store pickup orders, gift cards and store credit. You set each method’s name, order, country and amount conditions and any surcharge or discount under Online store › Payment settings. See Payment methods.

Card payments are paid out to your account directly by the payment provider (iyzico, PayTR or Stripe) under the contract it has with you; the payout schedule and the commission depend on that contract. The platform is not a payment institution and never holds your money; payments do not pass through it. For bank transfer and cash on delivery the collection is between you (or your carrier) and the customer; you mark the order as paid when you receive the money.

Yes. You can offer instalments with iyzico and PayTR; which instalment counts and interest apply depends on your provider contract and settings. You can show an instalment table by card programme on the product page and let customers pick an instalment at checkout from the first digits of their card. Instalments are offered only for Turkish lira orders; Stripe payments are single payments.

Yurtiçi Kargo, Aras Kargo, UPS and DHL Express have a built-in tracking link; for DHL eCommerce (MNG), Sürat, PTT, HepsiJet, Kolay Gelsin, Trendyol Express and Sendeo you enter your tracking address as a template, and you can define carriers that are not listed with your own template. You sign the carrier contract yourself: the platform offers no carrier agreement, creates no labels or barcodes and does not query delivery status from the carrier. You enter the tracking number and the customer receives the tracking link by e-mail. See Carriers.

You create shipping zones (by country, province, district and postcode); for each zone you define a flat rate or a rate based on weight or cart value, a free-shipping threshold and an estimated delivery time. For local delivery you set delivery days and time slots, and for in-store pickup the pickup points (stock locations); customers choose them at checkout. See Shipping and delivery.

Customers pick lines and quantities on the order page in their account to request a return or a cancellation; return reasons are chosen from the list you define. You approve or reject the request per item; products can optionally go back into stock. The refund goes to the cardholder through the payment provider; if the provider declines, you can record the refund manually or issue it as store credit. You set the return window and the explanatory text under Online store › Customer settings. See Orders and returns.

Yes. You can publish your store in several languages (translations are imported and exported as CSV), define markets by language or country with a subfolder or a domain, and show prices in several currencies; exchange rates come automatically from the Central Bank of Türkiye (TCMB) and the ECB or are set by hand, and you can define a price list and a rounding rule per currency. Stripe can be used for foreign cards; you decide which countries you ship to with shipping zones. Customs handling and cross-border logistics integrations are not part of the platform. Multiple languages and currencies depend on the features of your plan. See Languages and currencies.

Yes. The visible order statuses are configured in the dashboard. For orders that come in by phone or message you can create a draft order and e-mail the customer a signed, time-limited payment link. You can tag and archive orders, filter them and export them as CSV.

Both come installed in every new store; you enter your details and activate them. Orders placed with these methods are created awaiting payment; when you receive the money you mark the order as paid in the dashboard. For bank transfer you define your accounts, for cash on delivery the amount and country limits, and you can add a surcharge or discount to either in the payment method rule. See Bank transfer and Cash on delivery.

Yes. You can create gift cards and store credit and set the amount, the validity dates, the minimum cart value and the currency and sales channels they can be used with. Customers apply them in the cart; when a card is used only in part, the rest is paid with another method. Refunds can also be issued as store credit.

Starting templates come ready; you edit the texts in the Online store › Pages list (type “Legal text”), complete them for your business and have them reviewed by your lawyer. At checkout the pre-information form and the distance sales contract are shown right above the “Complete order” button with unticked boxes; when the customer clicks the box or the document name, the document opens filled in with their own details. This is not legal advice. See Legal compliance.

Yes. The documents accepted with an order are stored with the order exactly as accepted (an HTML copy of the text, the time of acceptance and the IP address), e-mailed to the customer and shown on the order page in the customer’s account. Changing a text later does not change the stored copy of earlier orders. Your lawyer or accountant should assess legal retention periods; this is not legal advice.

The privacy notice and explicit consent are presented separately: sign-up, checkout, newsletter and contact forms carry a link to the notice, and commercial message consents are collected with separate, unticked boxes. In the cookie banner accept and reject carry equal weight; analytics, marketing and preference cookies are managed category by category, Google Consent Mode is supported and tracking tools load only for the category that was allowed. Customers can file data export and deletion requests from their accounts; you complete them under Customers › Privacy requests (export and anonymisation). Ask your lawyer whether the texts are sufficient; this is not legal advice.

Yes. If you connect the Nilvera app with your own account, the invoice is issued when the order is paid or shipped (or by hand); an e-Invoice is issued if the buyer is a registered e-Invoice user and an e-Archive invoice otherwise. Documents are issued in your name. You can also attach your own invoice to an order as a PDF or a link. Ask your accountant about the invoicing obligation and content; this is not tax advice. See e-Invoice and e-Archive.

Customers’ e-mail, SMS and call consents are kept on record together with their history (Customers › İYS consents). If you turn on “Upload consents to İYS (NetİYS)” in the NetGSM app, consents and withdrawals are uploaded to İYS; consents without a recorded source are not uploaded. Commercial SMS go only to recipients who have İYS consent. Ask your lawyer about your İYS obligations; this is not legal advice.

You enter your store and legal details (name, address, tax or identity number, MERSİS, KEP, ETBİS and so on) in the dashboard; the seller details are shown on every storefront page and in the relevant documents. Which details are mandatory depends on your business type; you make applications such as the ETBİS registration yourself, the platform does not make them for you. This is not legal advice.

In the Online store › Pages list, next to your custom pages, you find the documents of type “Legal text”: the privacy notice, privacy and cookie, distance sales contract, pre-information, returns, delivery and shipping, terms of use and seller details texts come as editable drafts. The texts cannot be deleted but are edited per language; every save keeps a new version, and you can return to an earlier version from the version history. Placeholders in the text (such as seller and order details) are filled with real values on the storefront and in the order. The templates are not final valid texts; review them with your lawyer before publishing. This is not legal advice.

The return and cancellation flow is ready: the return window (in days) and the return conditions text are set under Online store › Customer settings; the text is shown on the “Returns and exchanges” tab of the product page, at checkout and on the return request form. You can also append published policy pages such as returns and delivery to the order e-mails you choose (Notifications › Customer notifications). The scope, exceptions and periods of the right of withdrawal depend on the legislation; preparing that text is your responsibility and you should consult your lawyer. This is not legal advice.

Use the abuse report form. Your report is recorded and reviewed by the responsible team; where necessary the content may be removed or action taken against the store. If you are forwarding a court or authority order, include its date and reference number in the description. This is not legal advice.

In the platform’s data processing agreement template, the seller (you) is defined as the controller of your store customers’ personal data and the platform as the processor. The template is a draft and is completed by the company operating the platform. Assess the roles and obligations in your own situation with your lawyer; this is not legal advice.

Yes. The platform is designed API-first: the store dashboard, the storefront and external integrations all use the same REST API service, and the store management endpoints (/api/v1) are described by an OpenAPI 3.1 document. You reach orders, products, stock, customers, campaigns and content with an API key, and receive events in your own system through webhooks as they happen. Creating API keys and defining webhooks depends on the features of your plan; see the developers page for details.

You create keys under Settings › API keys. A key is valid only in your own store and is limited by separate view or edit scopes for areas such as products, stock, orders, customers, campaigns and content. You can give it an expiry date and revoke it at any moment. Staff management, plan and invoice changes, API key management, the audit log and store deletion cannot be granted to a key. When you create a key that can change data, a one-time code sent to your e-mail is asked for as confirmation. A key is shown only once, when it is created.

You can subscribe to events such as an order being created, updated, paid, cancelled, fulfilled, delivered or refunded, and to product, category, stock, customer, return request, payment, shipment, abandoned cart, campaign, newsletter and e-invoice events; if you like, you can limit them by the channel the order came from (for example only the online store). Every request is signed in the Standard Webhooks format (webhook-id, webhook-timestamp, webhook-signature; HMAC-SHA256): you verify the signature with your webhook secret, check the timestamp and deduplicate by webhook-id. Failed deliveries are retried at growing intervals; from the delivery log under Settings › Webhooks you can retry by hand, replay and send a test request. An endpoint that fails many times in a row is turned off and you are notified.

Yes. API requests are limited per minute, per API key (per IP address for requests without a key); endpoints such as sign-in, sign-up, password reset, contact forms and review submission have their own stricter limits. When the limit is exceeded the API returns 429 (rate_limited); wait a moment and try again. If you update many products or stock records, you can use the dashboard’s CSV import and bulk operations instead of sending requests one by one (some depend on your plan).

The module SDK offers a contract for payment, shipping, SMS, e-invoice and İYS consent registry providers, storefront scripts (such as pixels, with a cookie consent category), server-side event sending, product feeds and integrations that need catalog or order synchronisation (for example marketplaces). A module defines a per-store settings form (with encrypted secret fields), event listeners, scheduled jobs and dashboard actions, and uses the product, stock and order API and SSRF-protected HTTP access. Modules are compiled with the platform; no code is uploaded from the dashboard. A new module is written by the team operating the platform or by developers and is released together with the platform.

The storefront writes events such as page and product views, add to cart, checkout start, purchase, search, sign-up and login to window.dataLayer in GA4 e-commerce format; Google Tag Manager or your own script can use them. The item id is the variant id. You can add your own JavaScript under Online store › Storefront settings › Custom scripts, choosing its cookie consent category; the code loads only when the visitor has allowed that category.

Responses are JSON: successful responses come in { "data": … }, and lists are paginated (page and limit; at most 100 records per page). Money amounts are integers in the smallest unit (for example priceMinor: 12990 = 129.90) with a currency code, and dates are ISO 8601 (UTC). Errors come in a common structure with an error code, a message and a request id; error messages are in Turkish or English according to the Accept-Language header.