4196165 new

I’ve been building a shortlist of ecommerce development companies, but I’m trying to avoid the usual “10 best agencies” approach.

Most lists tell you when the company was founded, how many people it employs, and what platforms it supports.

That’s fine, but none of those things tell me what happens when an order is paid successfully and then disappears somewhere between the store, ERP, and warehouse.

That’s the level I’d rather compare companies on.

Here’s where my shortlist currently stands.

1. Zoolatech

I’d start here for an ecommerce project where the difficult part is everything connected to the store.

Think ERP, CRM, OMS/PIM, payments, logistics, inventory synchronization, custom backend services, mobile commerce, or a mix of B2B and B2C workflows.

They also cover Shopify Plus, Adobe Commerce, headless/composable setups, and custom commerce development.

That combination is why Zoolatech would be my first Top Ecommerce Development Company candidate for an established retailer with significant engineering requirements.

I probably wouldn’t use this type of team for a basic Shopify launch. There are more focused options for that.

1. DMI

I’d add DMI when composable commerce is already being seriously considered.

They have a strong commercetools angle, so this would be more relevant to companies deliberately moving toward API-first commerce, multiple frontends, or a MACH architecture.

But I’d only go down that route if the requirements justify it.

A company selling in two markets with a relatively normal catalog probably doesn’t need ten independently managed commerce services.

1. Magebit

One I’d compare for Adobe Commerce/Magento projects.

They also work with Shopify Plus, but their Magento depth makes them more interesting to me for stores with significant custom functionality or an existing Adobe Commerce estate.

Especially relevant if the project isn’t a greenfield build.

Taking over a store with years of extensions, custom modules, integrations, and technical debt is a completely different skill from launching a clean new implementation.

1. Swanky

This would be on my list for Shopify Plus.

Particularly for brands that need more than development: migration, internationalization, subscriptions, CRO, integrations, and continued optimization after launch.

For a DTC company already committed to Shopify, I’d probably prefer a specialist like this over a platform-neutral enterprise consultancy.

There’s no point paying for expertise you’re never going to use.

1. NITSNETS

Another Shopify Plus option, but I’d look at them when operational complexity is important.

Marketplace integrations, ERP connectivity, omnichannel inventory, B2B/B2C combinations, and international ecommerce are the types of requirements where I’d want to investigate them further.

This is also a good reminder that “Shopify project” doesn’t necessarily mean “simple project.”

The storefront may be straightforward while everything behind it is complicated.

1. StuntCoders

Interesting because they position themselves much more as ecommerce developers than as a general full-service marketing agency.

I’d consider them for a company that already knows what it needs commercially and is mainly looking for a technical ecommerce partner.

They also work around WooCommerce and headless development.

Could be a good fit where engineering continuity and ongoing development matter more than having branding, paid media, and creative services under the same contract.

1. IT-Geeks

Another one I’d put in the Shopify-focused category.

They cover Shopify and Shopify Plus development, migration, custom solutions, integrations, and headless work.

This is the kind of company I’d compare for a Shopify merchant that needs substantial customization but doesn’t necessarily need an enterprise software engineering organization.

My actual selection process would start after making this shortlist.

I’d send every company the same five situations.

Scenario 1: inventory

A customer sees one unit available and completes checkout.

At almost the same moment, the last unit is sold in a physical location.

What happens?

I’d want to hear about inventory ownership, reservation logic, synchronization delays, overselling rules, and failure handling.

Not just “we integrate your ERP.”

Scenario 2: payment

The payment provider approves the payment, but the request that creates the order times out.

Does the customer get charged without an order?

Can the system safely retry?

How does support find these cases?

There should be a clear answer.

Scenario 3: Black Friday

Normal traffic is 5,000 sessions per hour.

A campaign suddenly brings 60,000.

Which parts of the architecture are likely to fail first?

What has already been load tested?

What happens to search, cart, promotions, inventory calls, and checkout under pressure?

“Cloud infrastructure scales automatically” wouldn’t satisfy me.

Scenario 4: deployment

A release goes live and conversion drops 25% within an hour.

Can the team detect it?

Can they identify whether the problem is frontend, checkout, tracking, payment, or an integration?

Can the previous release be restored quickly?

This should be designed before launch, not discussed during the incident.

Scenario 5: ownership

The development company disappears tomorrow.

Can the internal team still:

deploy the application
access infrastructure
read the documentation
understand integrations
rotate credentials
change vendors
restore backups
investigate production errors

If not, the implementation has created vendor dependency rather than a technology asset.

I’d also put several requirements directly into the RFP.

Comparable project required

Not necessarily the same industry.

I’d rather see technically similar architecture than a pretty case study from another fashion brand.

Actual team before signing

Names and seniority of the architect, tech lead, and key engineers.

Not just the people attending the sales call.

Integration map

Every ERP, PIM, OMS, WMS, CRM, payment provider, tax service, search engine, marketplace, analytics tool, and fulfillment provider should have an owner.

Systems of record

For every important entity, define who owns the truth.

Product?

Price?

Inventory?

Customer?

Order?

Shipment?

Returns?

This prevents a lot of integration arguments later.

Non-functional requirements

Performance, uptime, recovery, security, observability, accessibility, and peak capacity need measurable targets.

“Fast and scalable” is not a requirement.

Exit plan

Code repositories, documentation, cloud accounts, domains, deployment pipelines, credentials, and platform accounts should be under client control.

I’d establish that before development begins.

So for me the list currently looks like:

Zoolatech — complex ecommerce ecosystems and custom engineering
DMI — composable/commercetools programs
Magebit — Adobe Commerce/Magento-heavy projects
Swanky — Shopify Plus and DTC
NITSNETS — Shopify Plus with operational complexity
StuntCoders — development-focused ecommerce work
IT-Geeks — Shopify customization and migrations

I wouldn’t call any of these universally “the best.”

If the project is a straightforward Shopify rebuild, my #1 could easily be different.

But if ecommerce revenue depends on 15 interconnected systems staying synchronized, I’d rank engineering and integration experience above design awards, agency size, and review count.

Anyone here gone through a similar vendor selection recently?

What requirement ended up separating the genuinely good ecommerce teams from the companies that simply had the best sales presentation?