Custom E-Commerce
Software
An online sales platform built around your product structure, pricing rules and the accounting/ERP system you use. Payment, shipping, e-invoicing and marketplace connections are planned from the start, and the panel is shaped around your team's daily work.
Which systems does one order pass through?
When a customer hits “Buy”, stock, payment, shipping, invoicing and accounting steps run in sequence. If a step fails, the following steps never fire and what was already done is rolled back.
↳ Pick a scenario and press “Place order”.
- Order
- Stock
- Payment
- Shipping
- e-Invoice
- ERP
- No order yet.
Illustrative flow; order number and steps are examples.
The store's engine: modules built around your business
Products, variants and stock
Size and color variants, bundles, per-warehouse stock, barcode and SKU fields: the product record is modeled on how your business actually sells.
Payments: iyzico, PayTR and bank virtual POS
3D Secure checkout, installment options, full and partial refund flows. Card data is never stored on your server; the payment form runs on the payment provider's infrastructure.
Shipping integration
Shipment creation and barcode/label printing with carriers such as Yurtiçi, Aras and MNG; the tracking number is sent to the customer automatically by email or SMS.
e-Fatura and e-Arşiv invoicing
Once an order is confirmed, the invoice is issued through your e-invoicing provider or accounting software under Turkey's e-Fatura/e-Arşiv system, and the PDF link is attached to the order.
ERP and accounting connection
Customer accounts, stock and orders sync with software such as Paraşüt, Logo and Mikro. We decide up front which system is the source of truth for each type of data.
Marketplace sync
Stock, price and order sync with Trendyol and Hepsiburada. Because every channel sells from a single stock pool, the same item can't be sold twice on two channels.
B2B dealer and wholesale sales
Dealer-specific price lists, discount groups, minimum order quantities, customer accounts and credit limits. Retail and wholesale are managed from the same panel.
Campaign and coupon rules
Buy X pay for Y, category discounts, free-shipping thresholds, single-use coupons. Rules are switched on and off in the panel, with no code changes.
Legal requirements
Consent to the Turkish pre-contract information form and distance sales agreement, the KVKK (Turkey's Personal Data Protection Law) privacy notice, cookie consent management and the post-order contract email are built into the flow.
Subscription package, open source or custom software
All three have their place. The choice depends on your product count, your sales channels and the workload on the accounting side. Pick an option and see which layers of the architecture are under your control.
Custom e-commerce software
A platform built from scratch around your order, stock and pricing rules.
Pros
- Special flows such as B2B, dealers and made-to-order
- Two-way, controlled data flow with your ERP and marketplaces
- Only the code you need; speed targets set from day one
Watch out for
- Higher initial investment and longer timeline
- Requires developer support for maintenance
Best suited for
Businesses with complex operations where packages struggle even with plugins.
What determines the price
In e-commerce projects, the price depends far more on business rules and integrations than on the number of pages. Switch on the factors that apply to your project and watch the scope grow.
Lean
The exact price and timeline are finalized in the proposal, based on the scope document.
What the proposal includes, and what we discuss separately
To avoid surprises later, we write the scope out line by line at the start. The layers below are the framework of a typical project.
Storefront
IncludedHome, categories and filters, product detail, search, cart, member and guest checkout, order tracking, account pages. Mobile-first design.
Hover over or tap a layer.
Services that go with an e-commerce project
What continues after launch?
An e-commerce site isn't finished once it goes live: payment and shipping companies update their APIs, campaigns bring new visuals, security patches are released. These are the areas we keep track of under a maintenance agreement.
Let's talk about your project
Book a call ↗Security updates: tracking framework and package versions and patching vulnerabilities.
Database and file backups, with restore tests run at regular intervals.
Updating integrations when shipping, payment and marketplace APIs change.
Monitoring error logs and reporting failed order, payment and invoice transfers.
Core Web Vitals monitoring: stepping in when new campaign visuals or plugins slow the site down.
New feature requests: estimated and scheduled as separate work items.
From scope document to first order
- 01
Discovery and scope
We go through your product structure, order flow, accounting/ERP software and sales channels. Output: a scope document with a module list and an integration map.
- 02
Storefront and panel design
Home, category, product, cart and checkout steps, plus the admin panel screens, are designed in Figma and submitted for your approval.
- 03
Development and integrations
The storefront and panel are built; payment, shipping, invoicing and ERP connections are set up in a test (sandbox) environment first.
- 04
Testing, launch and training
We place low-value test orders with a real card, run refund scenarios and check on mobile, then train your team on the panel.
Frequently Asked
Questions
Custom software isn't the right answer for every business. If you have few products and a standard flow, a subscription package gets you started faster and for less. Custom software makes sense where packages struggle even with plugins: B2B pricing, complex variant structures, two-way stock sync with an ERP, made-to-order production. We assess this openly in our first meeting.
The domain, server/hosting account, SSL and payment provider merchant account are opened in your company's name; we work as an authorized user. The terms for delivery and use of the source code are set out separately in the contract.
The application is made in your company's name, and the payment provider asks for documents such as your tax certificate, signature circular and certificate of activity. We get the site ready for the provider's review (contact details, return policy, contract pages) and complete the integration once the API credentials arrive.
If your current system offers an export (CSV, XML or API), products, categories, customers and past orders are migrated. 301 redirects are set up from old product URLs to the new ones so your pages don't drop out of search results. For security reasons customer passwords may not be transferable; in that case we plan a password-reset email to customers.
It depends on the number of modules, the integrations and when your content is ready. A standard B2C store and a project with ERP and dealer modules are very different undertakings. Once the scope document is final, a stage-by-stage timeline is included in the proposal.
By default, product information and images come from you; we prepare an Excel template for bulk upload. Product photography and product description writing can be quoted separately.
We work to Google's Core Web Vitals thresholds: LCP of 2.5 seconds or less, INP of 200 ms or less, CLS of 0.1 or less. Meaningful URL structures for product and category pages, structured data (Product, BreadcrumbList), a sitemap and canonical tags are part of the foundation.
Bug fixes in the period right after launch are covered by the project. After that, we can set up a monthly maintenance agreement covering security updates, backups, integration upkeep and small changes; new modules are planned separately.