Ecommerce Development Company: Key Questions Before Hiring

Ecommerce Development Company: Key Questions Before Hiring

Ecommerce Development Company: Key Questions Before Hiring

Ecommerce Development Company: Key Questions Before Hiring

What happens to your store after launch, once the agency invoice is paid? Most buyers ask that question too late. An ecommerce build is more than a website project. It combines a payments system, a security perimeter, a legal compliance surface, and a revenue engine. The questions below separate agencies that understand those responsibilities from agencies that ship polished storefronts and then disappear.

Quick Answer: What questions should I ask a ecommerce development company before hiring?

Ask about platform choice and why it fits your catalog, your ownership of code and accounts, PCI DSS scope for card data, WCAG 2.2 AA accessibility, GDPR and CCPA handling, and measurable performance targets such as Core Web Vitals. Then press on the commercial side: post-launch support SLAs, total cost including licences and hosting, references you can actually contact, and how change requests are priced.

Agencies differ sharply in shape. Some are platform specialists who build only on Shopify or Adobe Commerce. Others are generalist studios that adapt to whatever stack you already run, which can mean broader skills but shallower depth on any one platform. A third group sells templates with light customization, which is cheaper but constrains how far the store can grow.

Before signing, compare platform fit, ownership terms, security testing methods, accessibility audit trails, performance benchmarks, support response times, and the full lifetime cost picture.

Why These Questions Matter More Than the Portfolio

Why These Questions Matter More Than the Portfolio

Every agency has a portfolio. Polished case studies are the easiest thing in the world to produce and the hardest thing to verify. What you can verify is process: how an agency tests security, how it documents accessibility, how it hands over a codebase, and what it charges after launch.

The stakes are concrete. Card data handled badly becomes a breach. An inaccessible checkout becomes a legal complaint, particularly in the European Union, where the European Accessibility Act has applied to ecommerce services since 28 June 2025. A slow store becomes abandoned carts. None of these problems announce themselves during the sales pitch. They surface months after handover, when the agency has moved on to the next client.

So treat the hiring conversation as a technical and commercial audit. The right questions do two jobs at once: they extract information, and they reveal whether the people across the table have thought about these issues before you raised them.

Platform and Architecture Questions

Which platform, and why this one?

Ask the agency to name the platform and justify it against your catalog size, order volume, integration needs, and internal team skills. Shopify, Adobe Commerce, WooCommerce, and BigCommerce all carry different trade-offs in hosting, customization ceiling, and licensing. An agency that recommends the same platform to every client is selling a habit, not a solution.

What happens if we want to leave?

Platform lock-in is real, and migration costs are brutal. Ask how portable the build is, whether custom features live in platform-native code or in fragile third-party plugins, and what a future migration would involve. The answer tells you whether you are renting a store or owning one.

Who owns the code, designs, and accounts?

Get this in writing. Ownership of the repository, design files, domain, hosting account, analytics, and payment processor credentials should transfer to you at handover. Agencies that keep control of accounts gain influence over your business. This is a contract question, not a technical one, and it belongs in the agreement before work starts.

Security and Compliance Questions

How do you keep card data out of scope?

Ask specifically about PCI DSS, the card industry standard whose v4.0 arrived in March 2022 and v4.0.1 in mid-2024. The best answer involves hosted payment fields or tokenization so raw card numbers never touch your servers, which shrinks your compliance burden dramatically. Ask which Self-Assessment Questionnaire applies to the finished build and who completes it.

How do you test against known vulnerabilities?

The OWASP Top 10 is the reference list of web application security risks, and the 2021 edition remains the widely cited version. Ask how the agency tests against it, whether penetration testing is included or extra, and how security patches are handled after launch. A vague answer here is a red flag worth taking seriously.

How is privacy built in?

GDPR has applied since May 2018, and California’s CCPA took effect in January 2020 with the CPRA amendments following in 2023. Ask how consent banners, cookie handling, and data-subject requests are implemented, and whether the agency has worked with privacy counsel before. If your buyers sit in Europe or California, this is not optional decoration.

What is your accessibility track record?

WCAG 2.2 became a W3C Recommendation in October 2023, and the European Accessibility Act now covers ecommerce services. Ask for WCAG 2.2 AA conformance, an audit trail, and examples of remediation work. Automated scans catch perhaps a third of issues; ask whether manual testing with assistive technology is part of the process.

Performance and Quality Questions

What performance targets will you commit to?

Core Web Vitals are Google’s page-experience metrics: Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift. INP replaced First Input Delay as a Core Web Vital in March 2024. Ask for specific Lighthouse or PageSpeed targets, plus a post-launch monitoring plan. “We optimize for speed” is not a target.

How do you define done?

Ask for the acceptance criteria in writing. A definition of done should cover functional testing, cross-browser behavior, mobile checkout flows, payment failure handling, and load testing before peak season. Without it, “done” means “the invoice is due.”

What does your QA process look like?

Ask who tests, on which devices, and whether automated regression tests are part of the deliverable. Stores break quietly: a plugin update kills a payment method, a theme change hides a shipping option. Regression coverage is what catches that.

Commercial and Ongoing Support Questions

What does support actually cost after launch?

Ask for the post-launch support model, response-time SLAs, and the monthly retainer. Then ask what is excluded. Many quotes look reasonable until you discover that hosting, licences, security patches, and plugin renewals sit outside the number.

How are change requests priced?

Ask for the hourly or fixed rate, the approval process, and how scope creep is handled mid-project. A phased plan with clear milestones protects both sides. If the agency cannot describe its change process, it does not have one.

Can we talk to your references?

Ask for two or three clients with stores comparable to yours and permission to contact them. Then ask the references a sharper question than “were they good”: what went wrong, and how did the agency respond? Every project has a rough patch. The response to it is the real signal.

When you compare vendors, the same discipline applies as when buyers weigh other high-stakes purchases. A structured checklist beats a gut feeling, whether you are evaluating a managed detection response checklist for security operations or the AI chatbot security questions that increasingly shape storefront tooling decisions.

Questions About Timeline, Team, and Fit

Who actually does the work?

Ask who will work on your project day to day, whether any work is outsourced, and what happens if your account manager leaves mid-build. Meet the developers as well as the sales team.

What is the phased plan?

Ask for milestones, dependencies, and the launch date with a buffer. Then ask what the agency’s last three projects did against their original timelines. Slippage is normal; silence about slippage is not.

What do you wish clients asked you more often?

This one is disarmingly useful. The answer reveals what the agency considers its own risk areas, and it often surfaces the question you did not know to ask.

A Comparison Framework for Shortlisting Agencies

Question area Weak answer Strong answer
Platform choice “We build everything on X” Justifies platform against catalog, integrations, team skills
Ownership Vague, deferred to contract Written transfer of code, accounts, credentials at handover
PCI DSS “The platform handles it” Explains tokenization, SAQ scope, who completes it
Accessibility “We add alt tags” WCAG 2.2 AA, manual testing, audit trail
Performance “Fast by default” Named Core Web Vitals targets plus monitoring plan
Support “We’re always here” Defined SLA, retainer cost, exclusions listed

Run every shortlisted agency through the same grid. The gaps become obvious fast.

Practical Tips and Common Mistakes

The most common mistake is treating the sales deck as evidence. Ask for artifacts instead: a sample handover document, a redacted security test report, a performance audit from a live store. Agencies that do this work well usually keep the receipts.

Second, separate the build quote from the lifetime cost. Add twelve months of hosting, licences, maintenance, and plugin renewals to every proposal before comparing totals. The cheapest build is often the most expensive store.

Third, verify claims about adjacent technology before you commit. If a vendor bundles hardware or subscription products into the storefront, apply the same scrutiny buyers use when they read a Rillabox review before ordering or check a Ray-Ban Meta Skyler buyer’s guide before committing. The pattern holds everywhere: independent verification beats vendor enthusiasm.

Fourth, put the boring things in the contract: ownership, SLA credits, change-request rates, and the handover checklist. Fifth, plan the handover before launch, not after. Ask for a walkthrough recording, credential inventory, and documentation as deliverables.

Finally, remember that adjacent decisions carry the same shape. Investors comparing Fidelity money market funds ask about fees and access; sneaker buyers checking Air Jordan 3 Pure Money releases ask about authenticity and resale risk. Hiring an ecommerce agency is the same discipline applied to a bigger number: know what you are buying, who controls it, and what it costs after the honeymoon.

Conclusion

The right agency will welcome these questions, because good ones have answers ready. They know their PCI scope, they can name their accessibility process, and they have handover documents they are proud to show. The wrong agency will treat scrutiny as friction.

So ask everything, write down the answers, and compare vendors against the same grid. Insist on ownership terms, measurable performance targets, a named support SLA, and references you can call. Then decide. A store built on clear answers is a store you can actually run, grow, and one day sell, migrate, or rebuild without asking anyone’s permission.

FAQ

How many agencies should I shortlist before hiring?

Three is usually the practical number. Fewer than three gives you no comparison baseline, and more than five turns into a full-time procurement project. Send the same written question set to each, and compare the answers side by side rather than relying on memory of the calls.

Should I choose the cheapest quote?

Rarely. The cheapest quote often excludes hosting, licences, maintenance, and security patching, which reappear as monthly costs later. Compare total first-year cost, not build cost. A quote that is 20 percent higher but includes support and documentation is frequently the better deal.

Do I need an agency with experience in my specific industry?

It helps but matters less than platform depth and process discipline. A grocery store and a fashion retailer share most technical requirements: payments, tax, shipping, returns, and search. Industry knowledge shortens discovery; strong engineering prevents expensive mistakes. Weight the second more heavily.

What should the contract include about ownership?

It should state that all custom code, designs, documentation, and account credentials transfer to you on final payment. It should also list the specific accounts: repository, hosting, domain, analytics, payment processor, and email. Vague ownership language is the single most expensive clause to fix later.

How do I evaluate an agency’s accessibility claims?

Ask for a recent WCAG 2.2 AA audit report, even a redacted one, and ask whether testing included manual checks with screen readers and keyboard navigation. Automated tools alone miss too much. If the agency cannot produce evidence, treat the claim as aspirational rather than delivered.

What happens if the agency misses the launch date?

Check the contract for milestone dates and remedies before signing. Ask what the agency’s last three projects did against their original timelines. Reasonable buffers and phased launches are normal; penalties, credits, or a documented recovery plan show the agency takes dates seriously.

on this page