How to choose an e-commerce infrastructure? Ready-made, open source or custom
How to choose an e-commerce infrastructure? Compares a ready-made package, open source and custom development on flexibility, integration and ownership.
When choosing an e-commerce infrastructure there are three paths: a ready-made package on a rental model, an installation on an open source core, and custom development. The decision depends on whether your product structure is standard, on ERP and marketplace connections, on who will own the software and the data, and on who will take on maintenance. First write down your sales model and your integration list, then choose the path.
You have three quotes on your desk. One says a store can be opened quickly on a rental model, the second proposes an installation on an open source core, and the third talks about writing software from scratch. All three look reasonable. The difference shows up at the first marketplace connection, the first data exchange with the ERP, or the question “can we add this feature?” So an infrastructure is chosen not by looking at the storefront but by looking at the work that will run behind the store. In this article we compare the three paths on flexibility, integration and ownership, and list the questions to ask before you decide.
An e-commerce infrastructure is the software layer that makes an online store’s catalog, cart, payment, order, stock and shipping work on the same data structure. The storefront the customer sees is only the visible face of this layer; the real work is linking an order to stock, payment, invoice and delivery with the right records.
What parts does an e-commerce site infrastructure consist of?
- Storefront and catalog: category, product, variant, search, filter and comparison.
- Cart and payment: campaign, coupon, payment method and cart rules.
- Order and stock: order status, warehouse, stock visibility and return records.
- Connections: ERP, accounting, e-invoice, cargo, marketplace and supplier data.
- Management: roles, reports, content and SEO settings.
- Maintenance: security updates, backup, version upgrades and bug fixes.
Choosing an infrastructure means choosing who sets up each of these six parts, with what effort and how flexibly. Behind the same storefront image there can be very different maintenance loads.
How do a ready-made package, open source and custom software differ?
- Ready-made package: an e-commerce service run by the provider, mostly offered on a monthly rental model and shaped by settings. The provider does the setup, and the provider also draws the limits.
- Open source installation: an installation of a core whose source code is public, on your server or at a hosting service, adapted with themes and plug-ins.
- Custom development: an infrastructure designed from scratch around your business’s rules, mostly together with a software team. Flexibility is highest; scope and maintenance responsibility are also the topics that most need to be written down clearly.
| Criterion | Ready-made package (rental model) | Open source installation | Custom development |
|---|---|---|---|
| Speed of start | Starts quickly with a ready template; the limit is the areas the template offers. | Setup and theme work are needed; the core is ready. | Analysis and development are needed; the preparation time can be the longest of the paths. |
| Flexibility | As much as settings and plug-ins allow; harder if your business rule falls outside them. | You have code access; every custom change brings a maintenance load. | Built to your business rule; the limit is the scope of the work written. |
| Integration | Ready connections are limited to the list offered; for others the API terms are decisive. | Needs a plug-in or custom code; plug-in quality varies. | ERP, marketplace and cargo connections are designed as part of the project. |
| Ownership | The software and often the data sit with the provider; look in the contract for the terms for taking your data out. | The core belongs to the community and the code you write is yours; read the license terms. | Depending on the contract, the source code and data can belong to you; ask for this in writing. |
| Maintenance load | Updates and security are mostly with the provider. | Updates, security and plug-in compatibility mostly fall to you. | Depends on a maintenance agreement or an in-house team. |
| When it fits | A standard product structure, few connections, a wish to test quickly. | You have a technical team and want freedom over the code. | You have your own business rules such as variants, quantity and delivery date, or dealer-specific prices. |
The statements in the table describe general tendencies. Verify the limits of a specific product from the demo and the contract text.
What questions are asked when comparing e-commerce infrastructure sites?
Before putting the quotes side by side, write your own answers. The quotes are read against these answers; if it is the other way round, the quote with the most attractive presentation wins, not the one that fits your business most closely.
- Is your product structure standard? Do you have rules such as variants, technical specifications, quantity tiers or delivery dates?
- Is the sale to individuals, to businesses or both? Will a dealer or quote flow be needed?
- Which data will flow in which direction with the ERP and accounting: product, stock, price, order, invoice?
- Are marketplace and cargo connections needed from day one, or will they be added later?
- Who owns the source code and the data? If you leave the provider, in what form do you get your data?
- Who does security updates, version upgrades and bug fixes, and on what terms?
- Is your own team enough for campaign, payment method and interface changes, or will you depend on the supplier?
- When a new language, a new currency or a second warehouse arrives, can the infrastructure carry it?
Why is the ownership question the one noticed latest?
In the first year nobody asks about source code or data export; the store is running. The trouble starts when you want to change provider or connect with a new system. In what form and on what terms will the customer list, product catalog and order history come to you? Getting this answer at the contract stage is much easier than bargaining for it later.
How should total cost be read?
The first item in a quote is usually a small part of the total cost. Hosting, payment infrastructure commissions, the setup and maintenance of connections, design changes and the time your team will spend also count. When comparing the three paths, fill in the same items separately for each quote; an item left blank is usually an item you take on yourself.
Where do Excel, WhatsApp and social media sales work?
Starting without an infrastructure is not always wrong. For a brand that starts with a few products and a few orders, a product sheet, orders over WhatsApp and manual invoices can be enough in the first months; you measure demand without investing.
This arrangement breaks in three cases: when the same product starts to be sold in two places, when more than one person takes orders, and when stock is kept in a file. A product that has been sold keeps showing as in stock, payments and orders do not match, and customers call to ask the status of their order. The time to move to an infrastructure usually comes with one of these signs.
What are the common pitfalls of each path?
- Ready-made package: every request outside the template is put on hold on the “roadmap”; no solution can be found for a system that is outside the list of connections.
- Open source: plug-ins clash with each other, security gaps accumulate as version upgrades are postponed, and the knowledge leaves when the person who did the installation leaves.
- Custom development: undocumented code creates dependence on a single developer; if the scope is not written clearly, the project grows before it is finished.
Where does YazSis Smart E-Commerce fit in this choice?
YazSis Smart E-Commerce is an infrastructure specific to your brand, set up according to your sales model rather than sold as a ready-made template. B2C and B2B sales, product and variant management, campaigns, payment, cargo, marketplace and ERP connections are designed in the same data flow. For the logic of data flows you can look at the integration page, and for the ERP side the ERP page. Which data will flow in which direction with which system is decided within the project scope.
The setup proceeds in five steps:
- Discovery: the product structure, customer types, price and operations rules are worked out.
- Experience design: a brand-specific store, categories and purchase journey are designed.
- Integration: ERP, accounting, payment, cargo and marketplaces are connected.
- Data and testing: product, customer and order data are verified; critical scenarios are tried out.
- Launch and growth: the store goes live and is developed with conversion and operations data.
To see which path fits your sales model, you can look at the Smart E-Commerce page and, in the discovery stage, talk through your own product structure and connection list together.
Frequently asked questions
What is an e-commerce infrastructure?
It is the software layer that makes an online store’s catalog, cart, payment, order, stock and shipping work on the same data structure. The storefront is the visible part of this layer; ERP, marketplace and cargo connections are also part of the infrastructure.
Should I choose a ready-made package or custom software?
If your product structure is standard and you need few connections, a ready-made package can be enough. If you have rules of your own, such as variants, quantity and delivery date, dealer-specific prices or deep data flow with an ERP, an infrastructure set up specifically for you requires fewer compromises. First write down your rules, then choose the path.
Is an open source infrastructure cheaper because there is no license fee?
There may be no license fee; however, the effort of installation, hosting, security updates, plug-in compatibility and bug fixing falls to you. The total cost needs to be assessed together with these items.
Is it hard to change an e-commerce infrastructure later?
It is not easy, because product, customer and order data must be moved, the address structure redirected and the connections rebuilt. That is why data being exportable and the ownership terms should be asked about at the selection stage.
Can B2C and B2B sales be done on the same infrastructure?
YazSis Smart E-Commerce manages the individual and corporate sales models on the same platform. Price, quote and permission rules are set in the discovery stage according to your sales model.
More articles
What is employee onboarding? Process stages, owners and checklist
What is onboarding? It is more than a first-day welcome. It is a process in which paperwork, account, asset assignment, training and orientation steps are shared across departments; this article separates the stages and the owners.
November 21, 2026 · 8 min readMobile app or web app? Choosing between native, mobile web and PWA for staff
Make employees download an app, or let them use the phone browser? We compare native apps, mobile-friendly web and PWAs on installation, notifications, camera and maintenance effort.
November 21, 2026 · 8 min readPeriodic inspection of work equipment in Turkey: intervals and equipment list
Which work equipment must be periodically inspected in Turkey, and where are the maximum intervals set? We summarise the current Turkish regulation, give a sample interval table and show how to track inspection dates.
November 21, 2026 · 8 min read