Blog

How to choose an eCommerce agency without getting it wrong

Method, skills, transparency and operating capacity: the criteria for judging an eCommerce agency before you give it your project.

Published 25 July 2026 — Last reviewed: 25 July 2026 — Author: Roberto Di Stefano

Choosing an eCommerce agency does not mean finding someone who can install a platform or switch on an ad campaign. It means finding a partner who can understand your catalogue, processes, technology, marketing and business goals.

This article answers one precise question: what should you assess before you hand an eCommerce project to an agency?

No single choice suits every company. A B2B project with price lists and ERP integrations needs different skills from a fashion shop built around campaigns, merchandising and repeat purchases. So apply the criteria to your real context, rather than choosing on portfolio, price or the platform being proposed alone. You can also read the other articles on the eCommerce blog.

Start from the problem the agency has to solve

Before you assess agencies, be clear about what you are handing over.

The project may cover:

  • building a new eCommerce;
  • taking over an existing platform;
  • an upgrade;
  • a migration;
  • integration with the ERP or management system;
  • SEO;
  • campaigns;
  • email marketing;
  • CRO;
  • strategic consulting;
  • coordination between several suppliers.

A generic request such as “we want to grow our eCommerce” easily produces proposals that are hard to compare.

It is more useful to define:

  • your current situation;
  • goals;
  • platform;
  • systems in use;
  • problem areas;
  • work already covered in-house;
  • missing skills;
  • constraints;
  • priorities.

The agency should help you sharpen the problem, not just turn a vague request into a standard quote.

Assess whether it can combine development and marketing

An eCommerce does not grow on code alone, and it cannot be run on campaigns alone.

Development and marketing constantly affect each other:

  • a change to the catalogue affects SEO and feeds;
  • a new checkout affects tracking and conversions;
  • a campaign needs consistent landing pages;
  • a migration involves URLs, redirects and data;
  • an email automation depends on the technical events available;
  • a performance problem can reduce the effectiveness of acquisition.

An agency does not have to do everything in-house, but it must be able to coordinate different skills and make responsibilities clear.

When you talk to them, ask:

  • who will handle development;
  • who will handle marketing and data;
  • how the teams communicate;
  • who coordinates priorities;
  • how external suppliers are managed;
  • how the impact of changes is assessed.

You can discover Zeno Web's integrated approach as an eCommerce agency to see how development and marketing are coordinated on a single project.

Check that the method can be explained

A good method should not be presented in abstract words. It should be describable through steps, responsibilities and tools.

The agency should be able to explain:

  • how it gathers requirements;
  • how it analyses the project;
  • how it sets priorities;
  • how it manages tasks and tickets;
  • how it shares documentation;
  • how changes and releases are approved;
  • how it measures results;
  • how it updates the roadmap.

If the method changes completely at every meeting, the project risks depending on whatever is urgent at the moment.

A process that is too rigid can be just as problematic. The aim is not to apply a standard procedure with no adjustments, but to have a structure solid enough to make the work understandable.

References must be verifiable and relevant

A broad portfolio can help, but it is not enough on its own.

Check whether the projects shown let you understand:

  • what the problem was;
  • what work was done;
  • what the agency's role was;
  • which platform was used;
  • whether the project is still live;
  • whether the stated results have a period and a source;
  • whether the client authorised publication.

The agency does not need to have worked in exactly your sector. It may matter more that it has dealt with:

  • similar catalogues;
  • comparable integrations;
  • B2B processes;
  • marketplaces;
  • multi-language management;
  • customisable products;
  • repeat-purchase logic;
  • complex migrations.

A similar process is often more useful than a similar product.

Be wary of:

  • percentages with no context;
  • results with no time period;
  • logos with no explanation;
  • cases where it is unclear what the agency actually did.

Ask who will really work on the project

The agency's name does not automatically tell you who will handle the work.

Before you commit, it helps to understand:

  • who your contact will be;
  • who will gather the requirements;
  • who will develop;
  • who will check the work;
  • who will run the campaigns;
  • who will interpret the data;
  • who decides when things get blocked.

A large team is no guarantee. Equally, a smaller structure is not necessarily a limit.

What matters is real operating capacity:

  • the skills available;
  • clear responsibilities;
  • continuity;
  • documentation;
  • the ability to replace a person without losing context;
  • a workload that fits the project.

To look only at the comparison between organisational models, read eCommerce agency or freelancer: which to choose.

Transparency on costs, scope and responsibility

A professional quote should let you see what is included and what is not.

Check that these are made clear:

  • activities;
  • deliverables;
  • responsibilities;
  • dependencies on the client;
  • licences;
  • external services;
  • environments;
  • migrations;
  • testing;
  • training;
  • maintenance;
  • how extra work is requested.

Overly generic wording can lead to misunderstandings.

For example, “integration with the ERP” does not describe:

  • which data;
  • in which direction;
  • how often;
  • through which interface;
  • who supplies the documentation;
  • how errors are handled.

Transparency is not just showing the price. It is making the scope understandable.

Want an opinion on your specific case?

Thirty minutes, no sales pitch: you tell us the situation and we tell you how we read it.

No commitment: if now is not the right time, we will tell you.

Assess how the agency uses data

A results-oriented agency must know how to tell data, interpretation and decisions apart.

Ask:

  • which KPIs will be used;
  • from which sources;
  • how often;
  • who will analyse them;
  • how they will be tied to the work being done;
  • how tracking or attribution problems will be handled.

Total revenue is not enough to judge the whole project.

Depending on the context, these can be useful:

  • conversions;
  • average order value;
  • margins;
  • acquisition cost;
  • repeat purchases;
  • performance by category;
  • errors;
  • availability;
  • speed;
  • traffic quality;
  • reduced manual work.

Zeno Web also uses Shop Analyzer, its own monitoring and analysis suite, to link the technical and the commercial reading of a shop. It does not replace analytics, Search Console, advertising platforms or the ERP: it brings them together in one overall view.

The questions to ask before you choose

Before you sign, try to get concrete answers to these questions:

  1. Who will handle the project?
  2. Which activities will be done in-house?
  3. Which activities will depend on external partners?
  4. How are requirements gathered?
  5. How is the roadmap defined?
  6. How are urgent and extra requests handled?
  7. Who owns the accounts, the domain and the code?
  8. How are changes documented?
  9. Which data will be analysed?
  10. How is quality checked before release?
  11. What happens after go-live?
  12. How are licences and external services handled?

The answers do not have to be identical from one agency to another. But they should be consistent, understandable and workable.

Do not choose on the platform alone

Technology specialisation matters, especially when the project needs upgrades, customisations or integrations.

However, claiming to know PrestaShop, Shopify or another platform is not enough.

You need to assess:

  • experience with the version;
  • code quality;
  • how customisations are managed;
  • knowledge of integrations;
  • ability to work in staging;
  • testing procedures;
  • understanding of SEO and tracking;
  • future maintenance.

The technology must be tied to the business model.

A reliable agency should be able to explain not only why a platform is suitable, but also what limits it brings.

The first meeting should bring more clarity

After the first meeting you should understand better:

  • the problem;
  • priorities;
  • risks;
  • missing information;
  • next steps.

You do not need to receive a complete solution straight away.

In some cases the agency should stop and ask for:

  • access;
  • documentation;
  • data;
  • specifications;
  • a review of the ERP;
  • a technical analysis.

An immediate proposal can be useful for simple projects. On complex projects, promising a solution before gathering information can point to a superficial assessment.

Choose an agency that can make the project manageable

The best choice is not necessarily the agency with the most services, the most certifications or the biggest portfolio.

It is the one that can make these understandable:

  • goals;
  • responsibilities;
  • activities;
  • data;
  • risks;
  • decisions.

A good partner does not remove the complexity of the project. It organises it.

If you are evaluating a new agency, start from a clear description of your current situation and ask for a method before you ask for a promise.

Want to start from your eCommerce data?

With Shop Analyzer you can analyse your online store yourself and see what comes up, before you even talk to us.

No commitment: if now is not the right time, we will tell you.

Have a question about a specific case?

Write to us: we reply with a read of your situation, no sales steps.

No automatic quote: first we work out whether we can be useful to you.