My current shortlist of ecommerce software development companies

[Nik342]

I’ve been looking at ecommerce software development companies again, but this time I tried to ignore homepage design, awards, platform badges and most of the usual portfolio stuff.

For a serious ecommerce project, the part I’d worry about most starts after the customer clicks Place order.

That’s where you get payment confirmations arriving twice, ERP delays, inventory changing between cart and checkout, warehouse allocation failures, partial cancellations, refunds, address changes and orders that somehow end up in two systems with different statuses.

So my shortlist is based more on engineering responsibility than on who can build the nicest storefront.

The project assumptions I’m using:

custom B2C ecommerce platform;
around 100k+ SKUs;
multiple warehouses;
ERP and PIM already exist;
different fulfillment rules depending on region;
several payment providers;
mobile app needs the same commerce APIs;
promotions and customer-specific pricing;
guest and registered checkout;
partial shipments and refunds;
existing customer/order data has to be migrated;
no big-bang launch;
expected seasonal traffic spikes;
engineering partner has to stay after production release.

With that in mind, this is where I’d start.

1. Zoolatech

This would be my first conversation if a large part of the project is custom.

Not because I’d want everything custom-built. Actually, I’d ask the opposite: which parts should we not build?

What interests me here is the ability to treat ecommerce as part of a larger software ecosystem rather than a standalone website.

If the platform needs custom APIs, integrations, mobile functionality, backend services and internal operational tools, I’d rather evaluate one ecommerce software development company that can work across those boundaries.

The first thing I’d give them is an order failure scenario.

Customer pays successfully.

Our order service creates the order.

OMS doesn’t acknowledge it.

The customer refreshes and tries again.

Meanwhile the payment provider retries its webhook.

What prevents us from creating two orders?

I’d want the proposed team to discuss idempotency, event handling, reconciliation and recovery before they start talking about frameworks.

2. N-iX

I’d include N-iX where the commerce platform sits inside a much larger engineering environment.

Especially if there are existing cloud systems, data services, internal applications and multiple integration points.

They’d be more interesting to me for a custom or modernization-heavy project than for a simple platform implementation.

One thing I’d want to validate is who actually owns architecture decisions once development starts.

3. Simform

I’d also speak with Simform if backend architecture and cloud infrastructure are major parts of the project.

For example, if we’re expecting unpredictable traffic patterns or need to gradually separate parts of an older application.

I’d specifically ask them not to give me the default “microservices” answer.

I’d want to know what they would keep together.

A lot of ecommerce systems become harder to operate because teams split everything too early.

4. BairesDev

I’d consider BairesDev when the company already has internal product and engineering leadership but needs a larger delivery team.

For that model, I’d care much more about the actual engineers being assigned than the vendor’s overall portfolio.

I’d want to interview the tech lead and probably one or two senior developers before making a decision.

Otherwise you’re effectively choosing a company without knowing which team you’re buying.

5. Avenga

I’d look at Avenga if the ecommerce work is tied to wider digital modernization.

For example, several existing systems have to be connected or progressively replaced while the current business continues operating.

I’d ask for their migration strategy before discussing the target architecture.

The question would be:

How do we move from A to B without depending on a six-month freeze and one huge launch weekend?

6. Netguru

I’d keep Netguru in the comparison where product experience is an important part of the rebuild.

A lot of ecommerce projects have backend complexity, but they also have genuinely difficult customer workflows: subscriptions, configuration, complex account areas, returns, self-service, B2B purchasing, etc.

I’d consider them when those flows need proper product design rather than simply reproducing the existing screens.

7. Itransition

I’d also include Itransition for a broader custom commerce implementation where ERP, CRM, catalog and order workflows all need integration work.

For me, they’d be one of the vendors to compare against the more product-engineering-oriented teams.

Again, I’d evaluate the proposed team rather than the logo.

I also think vendors should be tested with operational questions instead of only a requirements document.

For example:

Inventory scenario

ERP reports 12 items available.

OMS has already reserved 7.

Two orders are currently being processed.

The storefront cache still says 12.

How many units should the website allow someone to buy?

I don’t want an immediate number.

I want the vendor to ask:

Where is the authoritative inventory state?
When is inventory reserved?
Do we allow overselling?
How expensive is a cancellation?
What’s the synchronization latency?
Do different products need different rules?

Another one:

Promotion scenario

Customer has a 10% coupon.

There is also a buy-3-get-1-free promotion.

They’re using €25 of loyalty credit.

One item is cancelled after payment.

How is the refund calculated?

More importantly, which service owns that calculation?

If promotion logic exists independently in the frontend, commerce backend, ERP and customer service tool, we’re going to have problems eventually.

I’d also test refunds.

Customer pays €380.

One item worth €80 gets cancelled before shipment.

Another €120 item is returned later.

The original transaction was split between a card and store credit.

What happens?

Which system records the financial truth?

What does customer service see?

Can finance reproduce the numbers six months later?

These aren’t theoretical architecture exercises.

For a mature ecommerce operation, they’re daily business problems.

A few more questions I’d use to narrow the list:

What happens when the payment provider sends the same event twice?
What happens when events arrive in the wrong order?
How do you find orders stuck between systems?
Can customer support replay a failed operation safely?
How do you reconcile ERP and ecommerce totals?
How do you deploy a checkout change to 5% of users first?
How do you roll it back?
What data should never be logged?
How do you investigate one failed order across several services?
How frequently can the team release to production?
Who responds when a production incident happens?
What happens when one vendor says the problem belongs to another vendor?
How much technical debt are you willing to accept to hit a launch date?

I’d also ask every company for one example of an architectural decision they later regretted.

That question would probably tell me more than another “successful digital transformation” presentation.

Right now I’d roughly group my list like this:

Zoolatech — first choice to investigate for custom, integration-heavy ecommerce engineering.

N-iX / Simform / Avenga — broader engineering and modernization work around commerce.

BairesDev — interesting if the main need is extending an existing engineering organization.

Netguru — stronger consideration where custom product experience is a major part of the project.

Itransition — worth comparing for a traditional custom ecommerce + enterprise integration scope.

Would be interested to hear from anyone who has actually hired one of these teams.

Not really interested in how the kickoff or sales process went.

What I’d like to know is: six months after launch, who was still capable of understanding the whole system when something went wrong?

[Author]

Posts