The quickest test for choosing an e-commerce consultant is this: before recommending a platform or a channel, does the consultant ask how your orders flow today and what your ad budget returns in each channel? A good e-commerce consultant makes four decisions on data — which platform, which ad channels and budget split, what operating system, which loss to close first in order to grow — presents them with written reasoning, and leaves the accounts, the data and any source code in your name when the work ends. This article gives you six criteria to test that, ten questions for the first meeting and three promises that should end it.
Murat ran e-commerce for a home appliances brand, and two proposals sat on his desk. The first recommended a new platform by the end of the first meeting and put the migration date and the price on the same page. The second asked for a week before quoting anything: to see whose hands an order passes through, from basket to warehouse and from accounting to the courier. Murat chose the first; it looked fast and clear.
Six months later the store was on the new platform, but dealers still ordered by phone, stock synced once a night and invoices were issued by hand every morning. The problem had never been the platform; it was the flow behind the platform, and nobody had drawn that flow. I invented Murat for this article; he is the only invented thing in it.
Choosing an e-commerce consultant is not choosing a platform; it is choosing a decision partner. The wrong consultant picks the wrong platform, and the wrong platform sets the workload for the next two years. This article is the "how to choose" part of the e-commerce decision set. How the price is built is in what e-commerce consulting costs, the platform decision itself in e-commerce platform consulting, and how the work runs on our side on our e-commerce consulting service page.
What does an e-commerce consultant do, and what is outside the job?
An e-commerce consultant answers four questions on data: which platform should the store run on, which ad channels should the budget go to and in what proportion, what system should orders, stock, accounting and shipping flow through, and which loss should be closed first in order to grow? Usually the consultant also stays to see those decisions implemented. What sits outside the job should be just as clear: day-to-day management of ad accounts, running the warehouse, product photography and the daily running of marketplace accounts are separate jobs.
In practice the distinction is this: an e-commerce agency usually builds the store and runs the ads, while an e-commerce consultant decides what gets built, in what order, and where the budget goes. The two roles can sit in the same team; what matters is that the order is never reversed. A platform chosen, or a campaign launched, before the flow and channel data have been read looks fine in the first month; the cost shows up in the months after, in manual work and in ad spend that never comes back.
A buyer who types "Shopify consultant", "İKAS consultant" or "Trendyol consultant" into a search box has usually already chosen the platform or the sales channel. If that choice is right, a consultant who specialises in that ecosystem is fast. But if the question is still "which platform", a consultant who specialises in one platform will naturally stay close to it, and it would not be fair to expect an independent comparison. Ask directly in the meeting: do you receive commission, partnership or referral income from any platform?
Does the consultant map your order flow?
This is the first criterion: before recommending a platform, does the consultant trace every step an order takes from entry to delivery? A flow map makes visible the manual work, the information that breaks between two systems and the places where an order waits. The platform decision is the outcome of that map, not its starting point.
Ask for this in the meeting: "Let's follow one of last week's orders from start to finish together." A good consultant draws that journey by asking questions: which screen does the order land on, when does stock drop, who issues the invoice, how is the shipment created, where does the customer get the tracking information? A weak consultant skips those questions and goes straight to a feature list.
A real example of this order sits in the MKComputer case. This Germany-based technology retailer wanted to dropship more than 200,000 products; the work began with an audit of the supplier's data feed, and no decision on Magento, servers or interface was taken until that audit closed. The result was a platform where stock, price and supplier data update automatically every 5 minutes; the architecture was set not by a platform preference but by the volume and irregularity of the data.
The second half of the flow map is integration. In e-commerce the real load sits behind the storefront: card payments and instalments, e-invoicing, accounting or ERP, carriers, dealer price lists where they exist, and marketplace orders. Does the consultant list those connections by name and test each one with a real order before go-live?
A connection that works on paper can fail in production: two systems may know the same product by different codes, the returns flow may not reverse the invoice, the shipment record may lag on a campaign day. Ask this in the meeting: "If our accounting software has no integration path, when do we find out?" The right answer is "at the flow mapping stage, with an alternative and its cost". "We'll look at it during the build" tells you the surprise has been postponed.
What does the consultant base the platform decision on?
The second criterion is whether the platform decision rests on reasoning or on habit. Whether an off-the-shelf platform or a custom build is right depends on catalogue size, order volume and the integrations you need; the consultant should give that answer in writing, with a cost comparison.
Written reasoning should have three parts. First, the criteria: which need was weighed, and how heavily. Second, the options that were ruled out: why not that platform. Third, the cost: not just the build, but licences, add-ons, maintenance and the hours your team will spend, as a total over several years. Reasoning that does not mention the rejected options is a one-option presentation. I have set out the questions behind this decision separately in the e-commerce platform consulting article.
A warning: "the platform we work with fits every business" is not reasoning; it is a statement of capacity. It matters which platforms a consultant works with, but which one fits your business is a separate question.
Does the consultant look at ad channels and budget through data?
The third criterion is ad channels. A good e-commerce consultant recommends where the budget goes not out of last month's habit but by looking at return on ad spend (ROAS), customer acquisition cost (CAC) and conversion rate per channel: which channel grows, which shrinks, which closes. What consulting sells here is the channel and budget decision, not the day-to-day running of the channel; your current agency or in-house team can keep running the campaigns.
Ask this in the meeting: "How will you measure what our ad budget returns in each channel?" A good answer talks about return measured on the same definition in every channel, about how channel dashboards can each claim the same sale, and about the hypothesis behind the budget split for the first 90 days. A weak answer looks at one channel's dashboard and piles the budget there. A consultant who knows that the channel decision and channel management are separate jobs can produce a workable plan without proposing that you change agencies.
Does the consultant build growth on measurement and conversion?
The fourth criterion is where growth will come from. Buying traffic is not the only way to grow; finding where arriving visitors give up and closing that point is often cheaper. A good consultant validates measurement first — which products sell, where baskets are abandoned, which channel delivers — then compares your conversion rate with your sector's average and ranks the losses by size.
A proposal that treats measurement as a later line item opens the first campaign in the dark. In the SOYLU AVM case the order was the other way round: pixels and conversion tracking were rebuilt from scratch before the campaign and traffic sources were segmented; what made the $1.5M recorded in the campaign's first 6 days readable was that order. If you want to see your own store's tracking tags before the meeting, our free e-commerce site analysis, Diagnoo, checks whether GA4, Meta Pixel and session analytics tags are installed.
The right starting point for that comparison is figures with a known source and sample; we gathered them in the e-commerce conversion rate benchmarks article. Closing the loss through testing and fixes is the work of conversion rate optimisation. A good e-commerce consultant ties the two together: it does not spend budget closing a loss nobody has measured, nor buying new traffic for a loss that cannot be closed.
Whose name are the accounts, the data and the code in?
The fifth criterion is ownership. Platform accounts, the domain, payment and carrier contracts and, where custom development happens, the source code should be opened in the company's name from the start; the consultant should connect only with administrator access, and that access should be removed when the work ends.
An arrangement where the system is opened in the agency's name looks convenient on day one and returns as a cost on the day you want to leave. Order history, the customer list and product data are the business itself; they are your assets, not the consultant's. Have this sentence written into the contract: "All accounts, data and source code belong to the company; administrator access is removed when the work ends." A proposal that objects to that sentence is offering you dependency, not a service.
What evidence should you ask for?
The sixth criterion is evidence, and a wall of logos is not evidence. Ask for three things together: the starting value, the ending value and the time between them, plus which platform and which integrations the work used.
Here is one from our own side, held to the same standard: OdorGo came to us with only the product. The e-commerce site was built on İKAS so that a visitor reaches the purchase step whichever page they land on; Trendyol and Hepsiburada storefronts were opened, and the channels were run in one measurement frame. After eight months, e-commerce, marketplace, retail and stand sales together reached ₺10M in revenue, and in February 2026 the operation was handed over to the brand's own team. The useful information there is less the revenue than the last sentence: the system runs on with its owner.
Then ask for one more thing: a migration or build that did not go to plan. A consultant who can tell you what went wrong and how it was recovered is the one who will describe the coming months honestly too.
Which ten questions do you ask in the first meeting?
The ten questions are a listening device, not a filter. The real information is not in the answer itself but in where the consultant hesitates.
- Before recommending a platform or a channel, how will you read our order flow and what our ad budget returns today?
- Which criteria do you use for the platform decision, and do you also write down the options you ruled out?
- How will you measure what our ad budget returns in each channel, and on what basis will you recommend the split?
- If our accounting or ERP software has no integration path, when and how do we find out?
- How do you test integrations before go-live?
- Do you receive commission, partnership or referral income from any platform?
- On the measurement and conversion side, what would you fix first, and how do you set the order?
- Whose name will the accounts, the domain and the source code be in?
- Can I see the starting and ending figures of a job at a similar scale?
- Is there a situation in which you should turn this work down?
The sixth and tenth questions yield the most. Whatever the answer, the commission question puts on the table the incentives behind the recommendation; you can weigh the advice of a consultant who answers it comfortably more easily. A consultant who answers the tenth with "we take every job" will learn its own scope on your budget. If the store's real problem is traffic, or the warehouse is not yet in order, a good consultant says so in the first meeting and points you to different work.
These questions cover the e-commerce-specific layer of the choice. For the general layer of the relationship — how data is used, whether channels cohere, how the team reacts in a crisis — the eight questions to ask an agency before you sign applies the same discipline to a wider frame.
Which three promises should end the meeting?
Three promises make the rest of the meeting unnecessary the moment you hear them. All three hide the same habit: deciding without looking at your business and your data.
The first is writing the prescription in the first meeting. A platform recommended before anyone has seen your order flow, integration list and catalogue structure, or a budget split proposed before anyone has opened your channel reports, is the prescription the consultant knows best; if it also fits your business best, that is a coincidence. The second is offering to set the system up in the consultant's own name: "we'll open the accounts, don't you worry" is a convenience on day one and a lock on the last. The third is a revenue or conversion guarantee. Sales are set by traffic, price, product, competition and execution together, and a consultant turns none of those dials alone. A range is honesty; a guarantee is a sale.
There is a fourth sign, more dangerous because it is quieter: a price given before the flow has been seen. A price written before the number of integrations is known tells you the scope will later either shrink or grow. I have broken down, line by line, which items make up the price in the article on e-commerce consulting pricing.
What changes for an SME, a growing brand and a manufacturer selling to dealers?
The criteria stay the same; their weights change. At each of the three scales, what you should expect from the consultant concentrates on a different item.
An SME store
For a small store the right answer is usually an off-the-shelf platform, few but solid integrations, and measurement set up from the start. If a consultant recommends custom development at this scale, ask for the reasoning twice; the maintenance load and the dependency can outweigh the flexibility gained. What you need from the consultant is not a big project but the right order: flow first, then platform, then campaign.
A growing brand with its own site and marketplaces
In a growing brand the trouble usually starts when channels multiply. Orders come from the brand's own site, from marketplaces and sometimes from a shop or a stand; the stock is one, but the records sit in several places. The first question for the consultant is whether every order, wherever it comes from, will be processed in one flow; the second is how the budget will be redistributed across channels as customer acquisition cost rises. Running marketplace accounts day to day is separate work and usually sits outside a consulting scope; what matters is that those orders connect to the same stock, invoicing and shipping routine.
A manufacturer selling to dealers and wholesale
On the B2B side the load is not in the storefront but in the rules: dealer-specific price lists, a bulk order screen, account balance visibility, deferred payment and an ERP connection. Ask the consultant not for consumer store examples but how they build a dealer flow that talks to an ERP. Timelines grow at this scale too: in our builds, a standard store on an off-the-shelf platform usually takes six to eight weeks, while adding ERP integration and a dealer flow can extend that to three months.
Agency, independent consultant or in-house team?
The decision depends on where the work sits. If it is one job on one platform — a theme change, an add-on installation, repairing an integration — an independent specialist who knows that platform well is enough and costs less. If the problem is spread across orders, stock, accounting, measurement and growth, one person cannot hold those layers at once; that needs a team.
An in-house team is needed in every case, but for a different role. The person who runs the store every day, adds products, manages orders and reads the reports has to sit on your side. For most mid-sized brands the right model is a hybrid: the consultant maps the flow, builds the platform, trains the team and hands the work over; after that the outside role narrows to new decision points and review. In this model the consultant's success is measured by how unnecessary it makes itself, so put the training session and the handover documents in the contract.
How does INDOLES run this work?
We hold ourselves to the criteria in this article. In e-commerce consulting we look along four axes: platform, ad channels, operating system and growth. The work runs in four steps. First, the current state is read: how an order flows from entry to delivery, ROAS, CAC and conversion rate per channel, and the health of the measurement. Next, the platform, channel and system decisions are made in writing, with a cost comparison. Then builds and integrations are tested with a real order, and conversion losses are lined up in a test backlog. Last, results are read from a dashboard, the team is trained and the work is handed over.
İKAS, Ticimax, İdeaSoft, Shopify and WooCommerce builds sit inside this scope; we make the platform decision on catalogue size, order volume and integration needs rather than brand preference. Our answer to the sixth question is this: INDOLES is a reseller of the İKAS e-commerce platform; because that tie could sway the recommendation, we put the platform decision in writing along with the options ruled out, and İKAS is not the answer for every project. On the channel side we do not propose changing agencies; we measure what the current setup produces on ROAS and CAC and recommend the budget split. Day-to-day management of ad accounts belongs to our performance marketing service, and a tested conversion programme to our conversion rate optimisation service. Platform accounts, the domain and any source code are opened in the company's name from the start. The details are on our e-commerce consulting service page.
Conclusion: the one test to run before comparing proposals
Choosing an e-commerce consultant is an audit of method, not a comparison of decks. A consultant who draws the order flow first, writes the platform and channel decisions down along with the options ruled out, tests integrations with a real order, builds growth on measurement and conversion and leaves the system in your name is a better investment than one who writes the prescription in the first meeting, in every case.
Here is the concrete test you can run today: pick one of last week's orders and put it on paper — which screen it landed on, how many people handled it, how many systems it was typed into by hand and how many times, when the customer received the tracking information. Then ask every consultant you meet the same question: "How will this order flow in the setup you would build?" A consultant who can draw the flow by asking questions knows the method. Think twice before signing with one whose answer starts with a platform name.
Run the same test on us. How we work in e-commerce consulting, from diagnosis to handover, is written out step by step on the service page; put the answers side by side and compare them.