We build the store that lets you sell your products from your own site: platform choice, category and product structure, design, and payment and shipping integration. The platform is chosen to fit your business; it can be WooCommerce, Shopify, a Turkish platform such as ikas, or a custom-coded store.
Platform
WooCommerce · Shopify · iyzico · PayTR
01Who it is for
A good fit
Orders come in by message, payment arrives by bank transfer, shipping codes are written by hand. We put the products into a catalogue structure and connect card payment and shipment tracking to the site; the answers to questions that used to come by message sit on the product page.
Products, prices and stock live somewhere, but it is not clear how they get onto a site. We start from the shape of the product data: which product has which variants, which details are mandatory for every product.
Monthly costs have grown, a flow you need cannot be built on the platform, or the site is slow. We first separate what comes from the platform and what comes from the setup. If the decision is to move, product, category and page URLs are 301-redirected to their new counterparts.
Selling to end customers alongside dealers or wholesale. Here price, shipping and return rules must not clash with the dealer channel; we settle that when writing the scope.
Not a fit
Running your store on marketplaces, or syncing stock between a marketplace and the site, is not part of this work. If such an integration is needed, it is discussed and scoped separately.
Once a store is live, it needs order confirmation, shipping, returns and customer questions every day. If it is not clear who will do that, we suggest talking that through first.
These connections are outside the scope of this page. If the project needs one, we discuss what is required and scope it separately.
02Platform
WordPress · WooCommerce · PHP
When
When the store will carry a lot of content (a blog, guide pages, campaign pages), when you want to keep the server and all the data in your own hands, and when being able to add a custom flow in code matters. iyzico and PayTR have WooCommerce plugins; shipping is set up with a plugin or a custom integration.
The trade-off
The server, security and updates are your responsibility. WordPress, WooCommerce and plugins need regular updates; who does that maintenance is written down before handover.
Shopify
When
When you do not want to deal with servers and updates, your team wants to work quickly in a ready-made admin panel, and your product structure fits the platform’s mould. Hosting, security updates and the checkout infrastructure are Shopify’s.
The trade-off
The monthly subscription and the fees of the apps you use are an ongoing cost. Working with a payment provider in Turkey depends on that provider having a Shopify connection; we check that, and any additional transaction fee the platform charges, before setup.
When
When ready-made connections to Turkish payment providers, banks’ virtual POS services and carriers will speed things up, and support in Turkish matters. Our job is then to design the platform around your brand, set up the category and product structure and test the connections.
The trade-off
Design and flows stay within what the platform allows. If you leave, the format in which you can take your product and order data varies from platform to platform; we ask about it before the choice is made.
React · TypeScript · PostgreSQL
When
When there is a flow that ready-made platforms cannot fit: a product configurator that prices by size, dealer-specific prices with an approval step, subscription selling, or a store that has to work closely with existing software. Card details never pass through or stay on your server; payment is taken on the payment provider’s own secure payment screen.
The trade-off
The option with the most build work. The server, security and every new feature are software work from then on; the setup cost is higher, in exchange there is no platform subscription and no app fees.
03Deliverables
04Process
We talk about what you sell, how many products and variants you have, who will prepare orders, and which payment provider and carrier you work with or want to work with. If there is an existing store, we list its page URLs and the pages that get traffic.
Output
Scope document and platform recommendation
We prepare the category tree, the filters and the product data template. Whether your team enters the product data or it is imported from a file is settled here. We fill in a handful of sample products to the template and design with that real data.
Output
Category tree, product data template and sample products
We first present the product page and the checkout steps for approval, because that is where the sale happens. Then we complete the home, category and account screens in the same language.
Output
Approved desktop and mobile designs
We build the store in a test environment, connect payments in the payment provider’s test mode, and connect shipping with the details the carrier gives you. If your virtual POS application is still in progress, the site will be ready with the pages its review may ask for.
Output
A working store in the test environment
We try successful payment, a declined card, instalment payment, cancellation and return one by one, and check that the shipment record is created and the customer emails go out. After switching to live mode we place a real order and refund it to verify the chain end to end.
Output
The live store and a record of the test scenarios
We run a training session in the admin panel with the people who will manage orders, and hand over accounts and documents.
Output
Handover pack: access list, order guide and source files
05Risks
A virtual POS or payment provider application is made with your company’s documents, and whoever reviews it may want to see pages on the site such as contact details, delivery and return terms and the distance sales agreement. We suggest applying at the start of the project, and have those pages ready early in the test environment.
Writing the same product as “navy” in one place and “dark blue” in another breaks filters and stock tracking. We prepare the product data template with mandatory fields and fixed value lists, and check the file before importing it.
If product and category pages that rank in search are not redirected to their new URLs, that traffic is lost. We list the old URLs and 301-redirect each one to its new counterpart.
A payment flow that works in testing can fail to take orders live because of a wrong key or a missing setting. The launch-day checklist includes a real order in live mode and its refund.
06Example
A WordPress-based catalogue site for a furniture company: four product categories, product pages with prices and dimensions, and a similar-products area; product enquiries are sent via WhatsApp. The site has no basket and no online payment.
Website · Furniture
07Cost
Once the scope is agreed in writing, we prepare an itemised proposal. Platform subscriptions, app fees, the payment provider’s commission and shipping charges are your costs and not part of our proposal; our recommendation states which of them will apply.
08Ownership & handover
Handover list
It depends on your number of products, the custom flows you need, who will run the store and how you want the running costs structured. If a ready-made platform does the job, we recommend it; we only recommend custom code when a need does not fit the ready-made platforms. The proposal sets out the comparison and our reasoning.
No. A virtual POS or payment provider application is made in your name with your company’s own documents, and the agreement is between you and the bank or provider. We make sure the site has the pages the review may ask for, and once approved we set up and test the integration.
Each has a different commission structure, instalment options and settlement schedule, and these depend on the agreement you make. We suggest you collect the offers and we compare them together. We tell you which ones have a ready connection on the platform you choose.
Instalments depend on the options your bank or payment provider defines for you. We show the defined instalment options on the product page and at checkout, and add instalment payment to the test scenarios.
When an order is confirmed, it lets you create the shipment record from the admin panel and have the tracking number sent to the customer automatically; nobody types shipment details by hand. We can set it up with Yurtiçi, Aras and MNG. It requires an agreement with the carrier in your name and the integration details the carrier provides.
No. The content of these texts is the responsibility of you and your legal adviser. We make sure they sit in the right place on the site, that the pre-information form and distance sales agreement are shown and confirmed before the order, and that the confirmation is recorded with the order.
Yes. We first check in which format product, customer and order data can be exported from the current platform, and which pages get search traffic. In the migration we move the data and 301-redirect the old URLs to the new ones.
Those connections are not part of this service. If the project needs one, we discuss what is required and scope it separately.
Rufy Studio
Send us your number of products, your current store’s address if you have one, and the payment provider and carrier you work with; our platform recommendation starts from there.