For a real catalogue and real traffic
E-commerce development — WooCommerce or bespoke, decided by your warehouse
WooCommerce from 60 million toman while the catalogue is under 500 products and there is one warehouse. A bespoke .NET and React shop from 250 once stock, shipping or accounting stop fitting a plugin.
The decision that actually matters
Every shop project starts with one question, and it is not about design. It is: how many warehouses, and what happens to stock while a customer is paying?
WooCommerce is the right answer when the catalogue is under about 500 products, stock lives in one place, shipping is one or two carriers, and nothing has to reconcile with an accounting system in real time. It is cheaper, it is faster to launch, and pretending otherwise to sell a bigger build is dishonest.
A bespoke shop is the right answer when any of those breaks: several warehouses or branches, stock that must be reserved the moment a cart is created, expiry dates or batches, multi-carrier shipping with different rules, or a stock and invoice feed into the system you already run. Plugins can be stacked to fake this. They fail under load, and they fail on the day of your biggest campaign.
What you get either way
- A catalogue with filters and search that work in Persian — including the half-space, Arabic and Persian letter variants, and plurals
- An Iranian payment gateway, SMS notifications and invoicing
- A checkout tested on a phone on a slow connection, because that is how most orders arrive
- Product pages with structured data, so search results show price and availability
- Migration from your current shop with the URLs preserved, so rankings survive the move
Only in a bespoke build
- Multiple warehouses and branches, with stock reserved at cart creation rather than at payment
- Multi-carrier shipping with per-carrier rules, zones and prices
- A stock and order feed into your accounting or ERP, in both directions
- A vendor panel, if the shop is going to become a marketplace
- Load behaviour you can predict, because we test the payment path under concurrency before launch
How we build a shop
The catalogue comes first, not the homepage. We model products, variants, attributes and stock, then design around what the data actually is — which is why our shops do not have a beautiful homepage over a catalogue nobody can filter.
Payment is tested under concurrency: two customers buying the last item at the same time is a scenario, not a surprise. And a migration keeps its URLs and its redirects, because a shop that loses its rankings on launch day has not been launched, it has been demoted.
E-commerce prices, 2026
WooCommerce · from
one-off
- Under 500 products, one warehouse
- A bespoke theme, no page builder
- Gateway, SMS and shipping
- Six weeks
Bespoke .NET and React · from
one-off
- Multiple warehouses, stock reservation
- Multi-carrier shipping
- Accounting and ERP integration
- Eight to twelve weeks
Multi-vendor marketplace · from
one-off
- Vendor and operator panels
- Automatic multi-party settlement
- Commission rules and payouts
- Twelve weeks and up
Questions about e-commerce development
How much does an online shop cost?
A WooCommerce shop starts at 60 million toman and a bespoke .NET shop at 250. A multi-vendor marketplace starts at 450. What moves the number is the catalogue size, the number of warehouses, and how many systems the shop has to talk to.
WooCommerce or bespoke — how do we decide?
By your warehouse and your order volume, not by budget. Under 500 products, one warehouse and simple shipping: WooCommerce, and we will tell you so. Multiple warehouses, stock reservation, batches or a live link to accounting: bespoke, because the plugin version of that breaks under load.
Can you migrate our existing shop without losing rankings?
Yes, and it is a planned part of the work rather than an afterthought. Products, customers and orders are migrated, every old URL gets a 301 to its new address, and we watch Search Console for the first weeks after the move.
Which payment gateways do you support?
The Iranian gateways, Zarinpal by default, with others added on request. Note that Iranian gateways do not accept foreign cards; if you sell abroad, that is a business arrangement to solve before the build, not a plugin.
Can the shop connect to our accounting software?
In a bespoke build, yes — orders out, stock and prices in, in both directions. With WooCommerce it depends entirely on what your accounting system exposes; we check that before quoting rather than after.
Start your shop with a number
Tell us the catalogue size, how many warehouses you run and what it has to connect to. We reply by the next working morning with the route, the price and the weeks.