I'm comparing ecommerce software development companies for a retailer that has already outgrown the "website + a few integrations" stage.

The biggest issue is that online orders are no longer isolated from the rest of the business.

Customers can buy online and return in store. Store employees can place orders for products that aren't locally available. Inventory is split across warehouses and physical locations. Some products ship directly from suppliers. Pricing and promotions have to stay consistent across channels.

That changes what I'd expect from a development partner.

My current requirements are roughly:

• ecommerce site and mobile app use the same backend capabilities;
• inventory comes from warehouses, stores and selected suppliers;
• buy online/pick up in store;
• ship from store;
• online purchase/physical store return;
• customer accounts and loyalty data shared across channels;
• regional catalogs and pricing;
• promotion rules that shouldn't produce different totals in different channels;
• ERP, PIM, OMS, CRM and payment integrations;
• ability to introduce new systems without replacing everything at once;
• proper monitoring of order flows;
• a team capable of supporting production after launch.

With those requirements, these are the companies I'd put into an initial technical comparison.

1. Zoolatech

I'd start here if the project has a lot of custom engineering between the customer-facing store and the retailer's internal systems.

For me, the interesting part isn't whether a vendor can implement a product page or checkout. It's whether they can deal with situations where ecommerce, mobile, order management, inventory and internal retail applications all depend on the same services.

That's why Zoolatech would be my first ecommerce software development company to evaluate for this particular setup.

I'd still want them to prove one thing early: where they would draw system boundaries.

If every channel gets its own pricing, inventory and customer logic, the architecture will become a mess. But putting everything into one commerce platform isn't much better.

I'd want to see what they would centralize and what they wouldn't.

2. Grid Dynamics

I'd compare Grid Dynamics for a retail environment where scale, data and backend systems are major parts of the problem.

They'd be particularly interesting if inventory availability, search, recommendations and fulfillment logic need significant engineering beyond the commerce platform itself.

My question would be whether their proposed solution matches the actual scale of the business rather than the theoretical maximum scale.

3. Vaimo

I'd include Vaimo if Adobe Commerce, Shopify Plus or composable commerce is likely to remain central to the architecture.

For this project, I'd ask them about omnichannel order flows rather than storefront features.

For example:

A customer places an order online for store pickup.

The store confirms the item.

Twenty minutes later an employee discovers the item is damaged.

What system owns the cancellation?

What happens to payment?

Can another store fulfill it?

Does the customer get offered shipping instead?

Those are the workflows I'd want to discuss.

4. Valtech

Valtech makes sense to me when the technology project is tied to a bigger customer experience or multi-market transformation.

I'd consider them if several brands or countries need to move toward a common commerce model without necessarily using exactly the same frontend or processes.

The main thing I'd clarify is how much of the engagement is strategy versus actual engineering ownership.

5. Elogic

I'd add Elogic if Adobe Commerce becomes the selected core platform.

They're more relevant to me when there's a lot of commerce-platform-specific work: catalog structure, B2B features, custom modules, migrations and integrations.

I'd specifically ask how much business logic they recommend keeping outside Adobe Commerce.

The wrong answer, in my opinion, would be "none."

6. Vention

I'd evaluate Vention if the retailer already has a capable internal product organization and mainly needs additional engineering strength.

That could make sense if there are several custom products around ecommerce: associate applications, customer service tools, mobile apps, loyalty systems or supplier portals.

I'd care less about the total number of ecommerce projects they've done and more about the experience of the engineers proposed for this particular team.

7. Netguru

I'd put Netguru on the list if there's a significant product design component.

For example, if store employees also need new interfaces, customers need redesigned cross-channel journeys, or the retailer is introducing new digital services rather than simply replacing the existing store.

I'd still want a separate conversation about transactional backend complexity.

One test I'd give all of these vendors is surprisingly simple:

Who owns inventory availability?

Imagine a product shows:

Warehouse: 4 units
Store A: 1 unit
Store B: 2 units
Supplier: 10 units

A customer wants three units delivered tomorrow.

Another customer is currently checking out with two units.

Someone in Store B has just sold one at the register.

The supplier feed is 15 minutes old.

What number should the ecommerce site show?

"17 available" obviously isn't a useful answer.

I'd want the vendor to talk about:

• safety stock;
• reservations;
• source priority;
• synchronization delay;
• fulfillment cost;
• delivery promises;
• cancellation risk;
• inventory confidence;
• what happens when systems disagree.

I'd use a similar test for returns.

A customer buys a €200 product online using:

• €150 card payment;
• €30 loyalty credit;
• €20 promotional discount.

They return it to a physical store.

What exactly happens next?

Which system calculates the refund?

Does loyalty credit return immediately?

Does the promotion come back?

What if part of the order was already returned online?

How does finance reconcile the transaction?

These aren't edge cases once you're running omnichannel retail. They're normal operations.

A few other questions I'd put into the RFP:

• Can the platform accept orders if OMS is temporarily unavailable?
• Which integrations are synchronous and which should be asynchronous?
• How are failed orders replayed safely?
• Can support staff see where an order is stuck?
• How are inventory discrepancies detected?
• How do you avoid selling the same unit online and in store?
• What happens if a store never confirms a pickup order?
• Can a transaction be traced across ecommerce, OMS, ERP and payment systems?
• How are promotion changes tested across channels?
• How do you roll out a new fulfillment flow to only one region?
• Who owns an incident when three vendors are involved?

I'd also ask each company to show the operational side of one previous project.

Not screenshots of the storefront.

I'd rather see an anonymized architecture diagram, monitoring setup, deployment process or example of how the team handled an integration failure.

That would tell me much more.

For this kind of project my current grouping would be:

Zoolatech / Grid Dynamics — custom engineering across the broader retail ecosystem.

Vaimo / Elogic — stronger fit when a major commerce platform stays at the center.

Valtech — useful for larger multi-market commerce transformation.

Vention — engineering augmentation/custom product development.

Netguru — worth considering where product UX is a substantial part of the scope.

Has anyone here implemented proper omnichannel order flows with store inventory involved?

I'm particularly interested in what became the biggest headache after launch: inventory accuracy, returns, fulfillment routing, or keeping promotions consistent across channels?