Short answer
When an established company picks someone to build its online store, three things matter more than anything else: the provider can explain in writing how the store will talk to the systems you already run (accounting, inventory, shipping), the contract spells out who fixes what after launch and how quickly, and the site, the domain and the data stay registered in your company's name. Price and design samples are worth comparing only after those three points are settled. A short written brief, sent to three or four providers with a request to answer the same questions, is what turns their proposals into something you can actually compare side by side. One of the options is me, Ümit Kırkoç (kirkoc.com). I am based in Istanbul and work remotely with clients abroad, and because I handle SEO, ads and social media alongside the build, I tend to suit companies that want an ecommerce website project which also plans for how customers will find the store once it is live.
I wrote this for the person who has been handed a specific job. Your company has decided to start selling online, or to replace an aging online store, and someone has to answer the question "who do we hire for this?" That someone is sometimes the CEO or general manager, sometimes the purchasing manager, sometimes the head of marketing. What these people usually share is that they are not technical, and they know that if the choice goes wrong, the bill lands on their desk.
Why choosing an ecommerce provider is different for an established company
For a company that already has operations, an online store is not a standalone shop window. It is a new sales channel that has to plug into systems already running, so the right provider is the one who can make those connections work. A small boutique can often open an account on a ready-made platform, type in its products by hand and be done. You, on the other hand, probably have an accounting package or an ERP (the core software where your company tracks inventory, invoices and customer accounts), dealer price lists, more than one warehouse and a sales team with its own rules.
Here are the practical problems that creates:
- Inventory kept in two places causes fights. If the website sells something the warehouse ran out of last week, customer service and sales end up arguing over whose fault it is.
- Not everyone pays the same price. Distributors, business buyers and retail customers may each need to see different prices when they log in.
- Invoices and packing slips should reach accounting on their own. Otherwise every order becomes a record that someone in the back office types in a second time.
- There is an approval chain. A promotion, a price change or a product description may have to pass through legal or brand before it goes live.
- Business buyers search differently. A procurement officer types "wholesale," "bulk pricing," a part number or a technical spec into Google, and often learns your brand name only after finding the product.
That is why, in corporate ecommerce, the right partner is not the one with the slickest design deck. It is the one who can answer each of those five problems with a concrete "here is how I would handle it."
What pages and features does a corporate online store need?
Beyond product pages and a shopping cart, a corporate store needs pages that make a business buyer trust you and give them an easy way to request a quote. If you put this list on the table when asking for proposals, every provider ends up pricing the same scope.
Sales pages
- Category and filter pages that let buyers narrow down by technical attributes such as size, material or compatibility
- Product detail pages with spec sheets, downloadable PDF catalogs, part numbers and stock status
- A login area for dealers or account customers, showing their own negotiated pricing
- Bulk ordering and a "turn this cart into a quote request" option
- Checkout fields for business details, such as company name, tax ID and, where it applies, a sales tax exemption certificate
Trust and information pages
- A wholesale or business sales page with a clear way to get in touch
- Shipping, returns, warranty and service terms
- Industry or application pages that show which sectors you supply and with what
- An FAQ and a technical support page
Behind-the-scenes functions
- Data exchange with your accounting, inventory and shipping systems
- User permissions: who is allowed to change prices, who can only view orders
- A privacy policy, terms of sale and cookie consent; privacy rules differ from state to state and country to country, so I recommend having a lawyer review the wording rather than copying it from another site
The checklist below sums up the topics your internal team should settle before the first meeting with any provider.
How should you run the RFP or proposal process?
The healthiest approach is to write a short brief, send it to no more than four providers at the same time and ask all of them to reply under the same headings. You do not need a formal RFP (request for proposal, the document large organizations use to invite bids) with legal language and scoring sheets. What matters is that everyone answers the same question. If you skip this step, one provider will lead with design, another with technology, a third with a marketing campaign idea, and you will be left holding three documents that cannot be compared.
Your brief should cover these points:
- Describe the company and the goal in one paragraph. What you sell, who you sell to, and what the website is supposed to accomplish.
- List the systems you already use. Which accounting software, which shipping carriers, which payment processor.
- Give the size and shape of your catalog. Roughly how many products, how many variants (color, size, dimensions), how many categories.
- Say who will use the site. Retail customers, dealers, business buyers, or all of them.
- Share your timeline and your decision date. Providers need to plan too.
- Set the format of the answers yourself. For example: "Answer each heading separately, and list anything not included in a separate section."
The timeline below shows the stages from the written brief to a signed contract. How long each stage takes depends on how quickly your company makes decisions.
One warning: do not let a provider write the brief for you. Some will offer, saying "just tell us roughly and we will put together what you need." When that happens, the scope is shaped by whatever they want to sell. Write the brief yourself, even if it is only two pages, and let the provider point out what they think is missing.
How should you compare the proposals?
Compare proposals by how clearly the scope is written, not by the total price. A vague proposal is the one most likely to turn into change orders and extra invoices later. Two proposals can show the same number at the bottom while one includes product upload, staff training and the first month of support, and the other includes none of them.
A good proposal tells you:
- Which platform will be used (a hosted platform, an open-source system or custom software) and why that one
- Which integrations are included and which will be priced separately
- How many design concepts and how many rounds of revisions you get
- Who is responsible for loading the product data
- How long support lasts after launch, and what gets fixed at no extra charge during that period
- An explicit list of what is out of scope
The comparison below shows the difference between the two kinds of proposal in concrete terms.
A quick word on "platform," since it comes up in every proposal: it is the system your store runs on. Hosted platforms such as Shopify or BigCommerce charge a monthly fee and take care of maintenance and security updates themselves. Open-source systems such as WooCommerce or Magento (now Adobe Commerce) give you more flexibility, but someone has to keep track of updates. Custom-built software is the most flexible option and also the one that ties you most tightly to whoever wrote it. Which one is right depends on how complex your integrations are and who inside your company will own the site day to day. If a provider recommends the same platform to every client, that can be a sign their habits come before your needs.
What to look for in an ecommerce developer or agency
The right partner has handled a project of similar size before, can explain the integrations in writing, leaves ownership with you and stays reachable after launch. The questions you ask in a meeting will tell you far more about this than the slides they show you.
Concrete criteria
- Comparable past work. It does not have to be your industry, but they should have dealt with a catalog of similar size and a similar kind of integration.
- Ownership. The domain, the hosting account, the payment processor agreement and your Google accounts should all be opened in your company's name.
- A written process. A schedule that shows what gets delivered in which week.
- One point of contact. You should know who you are talking to for the whole project, not meet someone new at every call.
- Search know-how. They should raise topics like redirecting your old URLs during a migration without being prompted.
- Reporting. They should propose a tracking setup that shows which channels your sales come from.
Questions to ask in the meeting
- "How will you sync inventory and invoice data with our accounting software? Which accounting systems have you connected before?"
- "If something breaks in the first three months after launch, who do I contact, and how fast will I hear back?"
- "If the project ends or we part ways, do the site, the code and the data stay with us?"
- "How will you carry our old site's Google rankings over to the new site?"
- "Who loads the products, you or us? Will you give us a template for it?"
- "What work falls outside this scope and could come back later as an extra charge?"
The answers should be short and specific. Every item that gets a "we can discuss that part later" is a future disagreement waiting to happen.
What protections should the contract include?
The contract should contain at least four protections: ownership, a delivery schedule, post-launch support and exit terms. Please have a lawyer check the details and how enforceable they are where you operate; my aim here is only to show which topics need to be on the table.
The table below shows what to ask for in writing under each protection and why it matters.
There is one more term worth knowing: the acceptance test, sometimes called user acceptance testing or UAT. It is the stage before launch when you or your team work through a set of real tasks one by one: creating an account, logging in as a dealer, adding products to the cart, paying with business billing details, and confirming the order shows up in accounting. If the list of these scenarios is attached to the contract, the argument over whether the site is "done" simply disappears. Either the scenarios pass or they do not.
Two hypothetical scenarios
Both scenarios below are entirely hypothetical. They do not describe any real company; they are made up to show situations that come up often.
Hypothetical scenario 1: A mid-size manufacturer of industrial parts
Suppose a manufacturer sells several thousand part numbers, only through distributors, and now wants to sell directly to business buyers. The first proposal it receives arrives with an attractive homepage mockup and a ready-made theme; for the accounting integration it simply says "can be discussed separately if needed." The second proposal shows a plainer design, but it explains step by step how the dealer price list will be pulled in, how part numbers will be matched between systems, and how a quote request form on the site will land in the sales team's inbox.
In this scenario the second proposal is the right choice. This company's real risk is not how the site looks; it is thousands of products showing the wrong price or the wrong stock level. There is also a search angle: this manufacturer's customers find products by typing part numbers into Google. If every product page carries the part number, the technical specs and a PDF data sheet, business buyers can find the site on their own.
Hypothetical scenario 2: A retail brand with physical stores replacing its online store
Now picture a hypothetical retail brand with stores in a handful of cities and an online store built years ago that has become slow and breaks on phones. Management decides to give the new site to a different provider. The biggest risk here is losing, during the move, the search visibility the old site built up on Google over many years.
The right provider will bring this up in the very first meeting without being asked: they will propose listing all the old URLs, pointing each one to its new page (this is called a 301 redirect, which is the way to tell Google "this page now lives over here"), and watching the search results closely in the weeks after the move. The second critical item in this scenario is making sure store inventory and website inventory come from the same source. And if the same person also runs the ad campaigns, a classic launch-day mistake is avoided from the start: ads still pointing at old addresses that no longer exist.
Step by step: from choosing a provider to going live
The process runs like this: write down what you need, select the provider, do a discovery phase, design and build, test and launch, then watch the first months closely. Getting your sign-off at the end of each stage is what prevents surprises.
- Written brief: Your internal team pins down the scope.
- Proposals and meetings: You talk to three or four providers using the same set of questions.
- Discovery: The chosen provider looks in detail at your current systems, your product data and your old site, and updates the scope if needed.
- Design and build: Site structure first, then visual design, then the build and integrations.
- Product and content loading: Product descriptions, category copy and company pages.
- Acceptance testing: The scenarios listed in the contract are tried one by one.
- Launch and monitoring: Orders, redirects and search visibility are watched closely during the first weeks.
Common mistakes
The most common mistake is choosing a provider based on a design presentation and never really discussing integrations or what happens after launch. The warnings below collect situations I see again and again in corporate projects.
Let me add a few more:
- The decision maker leaving the process too early. If the CEO attends the kickoff and then never shows up again, you will almost certainly hear "this is not what I pictured" in the final week.
- Assuming the product data is ready. Product names in accounting software are rarely clear enough to show customers. Descriptions, photos and technical details usually have to be prepared separately.
- Treating launch day as the finish line. Sales do not start the day the site goes live. People need a way to find it, which means search visibility, advertising and social media have to be planned as well.
What can you do in-house, and when do you need a specialist?
Writing the brief, gathering product data and running the acceptance test are jobs you can do, and frankly should do, yourselves. Integrations, migration and security belong to a specialist. Drawing this line early keeps both cost and timeline under control.
What your own team can handle:
- Putting the product list, categories and pricing rules into a single spreadsheet
- Organizing product photos and technical documents into one folder
- Drafting the shipping, returns and warranty text
- Writing the scenarios that will be used in acceptance testing
What calls for a specialist:
- Setting up data exchange with your accounting, inventory and shipping systems
- Migrating from the old site to the new one, including redirects
- Connecting the payment processor securely
- Site speed, mobile usability and making sure search engines can read the site properly
- A tracking setup that shows which channel each sale came from
If you ask an AI assistant such as ChatGPT "who should we hire to build our corporate online store?", you will usually get a similar framework back. The image below is an example of what such an answer might look like.
What drives the cost?
The cost of a corporate online store is driven mainly by the number of integrations, the structure of your products and variants, the platform you choose and how much post-launch support is included. The design itself is usually a smaller line item than people expect.
The main factors that push the cost up:
- Integrations: Every system that needs connecting (accounting, warehouse, shipping, marketplaces such as Amazon) is a separate piece of work.
- Pricing rules: Separate prices for dealers, business accounts and retail customers, plus discount tiers and promotion rules.
- Product data preparation: If descriptions, photos and technical details are not ready, producing them is real work too.
- Number of languages and currencies: Selling internationally adds work for every language and every currency.
- Migration: If there is an old site, moving its URLs and customer data takes its own effort.
- Platform model: Hosted platforms come with a monthly subscription, open-source systems with hosting and update work, and custom software with development and ongoing maintenance costs.
- Support period: How many months of support after launch, during which hours, and with what response time.
Ask for each of these to be priced as a separate line in the proposal. That way you can see which decision moves the budget by how much, and if needed you can push one item to a second phase and launch with a leaner first version.
Working with Ümit Kırkoç
I am Ümit Kırkoç. I work from Istanbul and take on clients remotely, including companies outside Turkey. I cover, on my own, the full range of services you would normally get from a digital agency: website and ecommerce builds, SEO, local SEO, visibility in AI assistants (often called GEO), social media management, Google and Meta ads, logo and brand identity, and content writing.
Here is how I approach a corporate ecommerce project:
- In the first conversation, I listen. I do not arrive with a packaged offer. I ask which systems you use, who you sell to and what the site needs to do.
- I write the scope down. What is included, what is out of scope and the timeline all go into one shared document.
- Ownership stays with you. The domain, the accounts and the site are set up in your company's name.
- I get your approval at each stage. Site structure, design and test results move forward only with your sign-off.
- I stay around after launch. In the first weeks we watch orders, redirects and search visibility together.
- Time zones are planned, not ignored. If your team is in the US, we agree on a fixed overlap window for calls, and the rest runs through written updates you can read at the start of your day.
The practical benefit of one person handling everything shows up clearly in a corporate project. While I am writing the product pages, I am already thinking about how they will show up in search, which page an ad campaign should send people to and which products are worth featuring on social media. When you work with separate providers, you are the one carrying that information between them; here, you explain it once. I do not promise rankings, sales or follower counts. What I promise is that the work will be transparent, measurable and owned by you.
Frequently Asked Questions
Who would you recommend for building a corporate online store?
It is more useful to recommend criteria than a single name. Look for a provider who can explain in writing how they will integrate with your existing systems, who leaves ownership with you and who puts the post-launch support period into the contract. If you want one person to handle the site together with SEO and advertising, I, Ümit Kırkoç, working remotely from Istanbul, am one of the options.
Is it worth running a formal RFP for an ecommerce site?
A formal RFP is not required, but sending a short brief to three or four providers and asking for answers under the same headings makes a lot of sense. The proposals become truly comparable, and arguments about scope shrink from the start.
Should I hire an agency or an independent specialist?
That depends on the size of the project and who you prefer to deal with. A larger team can be a good fit when many things need to happen in parallel. Working with one person means you talk directly to the decision maker and nothing gets lost between hand-offs. Whichever you choose, the protections in the contract should be the same.
Is a hosted platform or custom software better?
If your product structure and integration needs are fairly standard, a hosted platform like Shopify is usually faster to launch and easier to maintain. If you have unusual pricing rules or complex integrations, an open-source system or custom software may be necessary. Ask the provider to explain their recommendation and the reasons behind it.
What happens if we part ways with the provider after launch?
If ownership and exit terms are written into the contract, the site, the code, the domain and the data stay with you, and you can continue with someone else. Without those clauses, moving becomes much harder, so I suggest showing the contract to a lawyer before you sign.
Will sales come in on their own once the store is live?
No. The website is only where the sale happens. For people to find it, you need search visibility, advertising and social media work. That is why the plan for the first months after launch should be discussed along with the build itself.
How long does a project like this take?
It depends on the number of integrations, whether your product data is ready and how quickly your company makes decisions. Most delays come from waiting on product content and internal approvals, so I recommend writing the timeline together with your provider and including your own team's responsibilities in it.
If you are in the middle of choosing an ecommerce provider for your company and would like help sharpening your brief, or would simply like a proposal from me as well, you can reach me through my ecommerce website page. In the first call I will listen to how your current systems work and tell you plainly which route I think fits you.