MarketPulse warning signs
Ecommerce Agency Red Flags
Seventeen warning signs, each with what it looks like, why it costs you money and the exact question to ask, plus which ones end the conversation on the spot.
Most flags need one question. A few end the conversation.
The ecommerce agency red flags on this page are the patterns that turn a store project into a dispute: accounts you cannot get back, invoices you did not expect, a shop only one company can edit. Each one costs money in a way you can trace, and nearly every one shows up before you sign, in the proposal, on the call or in the contract draft.
Freelancers and studios can show the same signs, so read “agency” as anyone you pay to work on your store. Each flag below comes with what it looks like, why it costs you, and the question to ask. The table near the end sorts them into flags that end the conversation and flags that need a straight answer before you continue.
What makes something a red flag and not a quirk?
A quirk is a habit you would rather they did not have: slow email replies, a proposal full of jargon, a logo you dislike. A red flag is a pattern that moves money, control or risk from the agency to you. The test is simple: if the thing goes wrong, who pays?
Red flags come in two strengths. Some are dealbreakers, because no answer fixes them: an agency that guarantees first place in Google has already told you how it sells. Others need a question, because a good agency has a good answer and will put it in writing. The question is the point. A provider who answers clearly has removed the flag; a provider who dodges it twice has confirmed it.
Which ownership and access flags matter most?
1. Accounts registered in the agency’s name
What it looks like: They offer to “set everything up for you”: the store account, the domain, the analytics, the ad accounts, all under their email.
Why it costs money: When the relationship ends, you have to negotiate to get your own shop back. The domain matters most, because your email and every link to your shop depend on it.
What to ask: “Whose name and email will be the owner on the store, the domain, analytics and any ad accounts?”
2. Asking for your owner password
What it looks like: “Just send us your login and we’ll take it from there.”
Why it costs money: A shared owner login cannot be limited, you cannot tell who did what, and the only way to cut off access later is to change the password everyone uses. Platforms give providers their own access: Shopify has collaborator accounts for Shopify Partners, with permissions that control which parts of the store they reach, and WordPress has user roles, where an Administrator has every admin feature on the site.
What to ask: “Can you work through your own collaborator or user account, and which permissions do you need?”
3. Contract gives them ownership of your custom work
What it looks like: A clause saying the agency keeps the rights to custom code, design files or the theme changes made for you.
Why it costs money: You pay for the work and then need their permission, or another fee, to have someone else change it.
What to ask: “When the final invoice is paid, who owns the custom code and design files, and when do we receive them?”
4. Write access requested for an audit
What it looks like: An SEO or marketing audit that starts with full admin rights to Search Console or your ad accounts.
Why it costs money: Write access lets someone change settings before you have agreed any work. Google’s own guide Do you need an SEO? advises granting only read access to Search Console for an audit, and no write access at that stage.
What to ask: “Can you do the audit with read-only access first?”
Which sales tactics should worry you?
5. Guaranteed rankings, traffic or sales
What it looks like: “Page one in 90 days, guaranteed,” or a promised sales figure.
Why it costs money: Nobody controls search results or your customers. Google’s guide states that no one can guarantee a #1 ranking on Google, and warns about anyone claiming a special relationship with Google. A guarantee means they will either fail or game something that later hurts you.
What to ask: “What exactly are you guaranteeing, and what happens if it does not happen?”
6. Pressure to sign this week
What it looks like: A discount that expires on Friday, or a start slot that is “about to go”.
Why it costs money: Rushed signatures skip the quote check, and a discount of a few hundred euros is easy to lose on one unpriced gap.
What to ask: “If we sign in three weeks instead, what changes?”
7. A portfolio they cannot explain
What it looks like: Screenshots or mockups only, links to shops that are no longer live, or no clear answer to “what did you build here?”
Why it costs money: You are buying their claimed experience. If the proof does not hold, the price is for learning on your shop.
What to ask: “On this shop, which parts did your team build, and can I speak to the owner?”
8. A proposal that ignores your brief
What it looks like: A standard package with your shop’s name pasted in, and none of your scope lines mentioned.
Why it costs money: They will treat your change requests the same way: as extras to a package. Expect a stream of add-on invoices. A clear ecommerce brief makes this flag easy to spot.
What to ask: “Can you show which of our scope lines S1 to S5 this proposal covers, line by line?”
Which pricing and contract flags cost money later?
9. Vague hours with no breakdown
What it looks like: “Between 40 and 80 hours,” with one total and no list of tasks.
Why it costs money: The range doubles your budget, and with no breakdown you cannot tell which tasks overran.
What to ask: “Can you split the hours by task, and will you agree a cap?”
10. No written change process
What it looks like: “We’re flexible, just tell us what you need.”
Why it costs money: Flexible with no paper means every change is billed later at a rate you never agreed.
What to ask: “How does a change get priced and approved before anyone starts on it?”
11. Full payment upfront
What it looks like: 100% at signing, or a large share before any design or test store exists.
Why it costs money: Once everything is paid, you have nothing left to hold back if the work stalls. A deposit is normal; the full amount leaves you with no lever.
What to ask: “Can the payments follow sign-offs, such as approved design and working test store?”
12. A required long care plan
What it looks like: The build price only applies if you sign a 12-month maintenance plan.
Why it costs money: You commit to a year of fees before you know whether you need them, or whether you want this provider. The retainer vs one-time project guide shows how to size ongoing help.
What to ask: “What does the build cost without the plan, and what is the notice period if we take it?”
13. Undisclosed commissions on tools
What it looks like: Strong recommendations for particular apps, hosting or plugins, with no mention of referral fees.
Why it costs money: You can end up with a tool chosen for their commission, and you pay the monthly fee for years.
What to ask: “Do you earn anything from the tools you recommend?”
Which build and handover flags break the store?
14. No staging or test copy
What it looks like: Changes made straight on the live shop “to save time”.
Why it costs money: Every mistake happens in front of customers. A broken checkout on a Saturday costs a day of sales.
What to ask: “Where will you build and test changes before they go live?”
15. Theme or page builder lock-in
What it looks like: A proprietary theme, a builder only they use, or a theme license bought in their name.
Why it costs money: Another provider cannot easily take over, so the next change costs whatever they ask.
What to ask: “If we move to another provider, can they edit the theme, and in whose name is the license?”
16. No answer on who does the work
What it looks like: A senior person sells the job, and the build goes to unnamed juniors or subcontractors.
Why it costs money: You paid for the senior person’s skill, and someone you never met does the work.
What to ask: “Who will build our shop, how many hours a week, and do you use subcontractors?”
17. Silence about after launch
What it looks like: The proposal ends at “go live”: no bug-fix period, no handover documents, no training.
Why it costs money: Bugs found in week two become billable, and you cannot run the shop without calling them. The after-launch checklist lists what a handover should include.
What to ask: “How many days of free bug fixes come after launch, and what do we receive at handover?”
Which flags end the conversation, and which need a question?
| Flag | Strength | A good answer sounds like |
|---|---|---|
| 1. Accounts in their name | Ends it if they refuse to change | “Everything is in your name; we get collaborator access.” |
| 2. Owner password | Question; ends it if they insist | “We’ll send a collaborator request.” |
| 3. They own the custom work | Question | “It’s yours on final payment.” |
| 4. Write access for an audit | Question | “Read-only is fine for the audit.” |
| 5. Guarantees | Ends it | No good answer exists. |
| 6. Pressure to sign | Question; ends it if repeated | “Take the time you need.” |
| 7. Unexplained portfolio | Question; ends it if the claims fail | “We built the product pages and the stock sync; here is the owner.” |
| 8. Brief ignored | Question | A line-by-line mapping. |
| 9. Vague hours | Question | A task list and a cap. |
| 10. No change process | Question | “Written estimate, your approval, then work.” |
| 11. 100% upfront | Ends it at 100%; question above 50% | Stage payments tied to sign-offs. |
| 12. Required long plan | Question | “The plan is optional; here is the build price alone.” |
| 13. Hidden commissions | Question | A straight yes or no, with the tools named. |
| 14. No staging | Question | “We test on a copy and show you before publishing.” |
| 15. Theme lock-in | Question | A standard theme, license in your name. |
| 16. Unknown builder | Question; ends it after two dodges | Names and weekly hours. |
| 17. Nothing after launch | Question | A stated bug-fix period and a handover list. |
Count what is left after the answers. One flag with a good written answer is fine. Three or more open flags on the same provider is a pattern, and the discovery call scorecard tends to show it as a low total too.
How do you raise a red flag without souring the call?
Ask the question as a process question, about how they work, and avoid sounding like an accusation. Good agencies have ready answers to these questions, because the answers help sell their service.
- Use “we” and “our”. “Our rule is that every account stays in the owner’s name. How do you handle access?”
- Ask for the answer in writing. “Could you add that to the proposal?” turns a nice answer on a call into something you can hold them to.
- Ask once, then once more. A first vague answer can be nerves. A second vague answer to the same question is the answer.
- Write down the exact words. “We’ll sort access later” and “everything is in your name” read very differently in a dispute.
What if you spot a flag after signing?
Act in this order, calmly and in writing:
- List every account and who owns it: store, domain, hosting, analytics, ad accounts, email tool, paid apps.
- Request owner rights on anything in their name, with a date. Keep it friendly and specific.
- Hold the next payment if your contract ties payments to sign-offs, until the open item is fixed.
- Export your data (products, customers, orders) so you have a copy whatever happens.
- Ask for the change process in writing before approving any new work.
If the relationship ends anyway, use the after-launch checklist to remove old access and confirm what you hold.
FAQ
Is asking for a deposit a red flag?
No. A deposit of a third to a half of the project is common and fair, because the provider books time for you. The flag is full payment before any work you can check, or payments tied to dates instead of sign-offs.
Is it a red flag if an agency builds on its own theme?
Only if you cannot take it elsewhere. Ask whether another provider could edit it, where the documentation is, and in whose name the license sits. A theme with clear documentation and a transferable license is fine.
My current agency already holds my accounts. What do I do?
Ask, in writing, for owner rights on each account with a date, and say it is a policy decision on your side. Most providers comply without fuss. Do not stop paying an invoice you owe while you ask; keep the two issues separate.
Are long contracts always a red flag?
No. A long contract with a fair notice period and a clear list of what each month includes can suit a shop with steady work. The flag is a long term you must accept to get the build price, with no way out.
How many red flags before I walk away?
One of the dealbreakers ends it on its own. For the others, count those still open after you asked: one with a good written answer is fine, three on the same provider is a pattern worth walking away from.
Do these red flags apply to freelancers too?
Nearly all of them. Flag 16 changes shape: with a freelancer, ask whether they pass any work on, and who covers when they are ill or on holiday. The agency vs freelancer guide goes through the cover question.
What if the agency is a friend or a local business I know?
Ask the same questions and write down the same answers. Clear terms protect friendships better than goodwill does, because nobody has to remember what was said.
What should you do with this list?
Keep the table open during calls, and read every proposal against flags 8 to 13 before you compare prices. When a flag appears, ask the question on the page and ask for the answer in writing.
If a provider’s answer leaves you unsure, send the wording through the MarketPulse contact form, and we will tell you how we would read it.
Hiring steps that catch flags early
Most red flags show up in the brief replies, the first call or the quote.