Case study: a B2B e-shop ready in weeks, not months

The example below is illustrative and generalises the typical course of our projects. Specific figures depend on the scope and context of the brief.

A wholesale distributor of technical goods needed to replace an ageing ordering system with a modern B2B e-shop. The challenge was not nice templates but individual pricing for hundreds of partners, multi-step order approval, and integration with an existing ERP.

What the client needed

We started on site with the client. We mapped how an order actually flows, who approves a purchase above a certain amount, and how individual price lists are calculated. That context became the foundation of the solution — rather than something we discovered during testing.

How we built it

We built the solution on the ShopSys framework and Symfony, with logic split into clearly defined steps within UseCases and a focus on SOLID, DRY and KISS. AI helped produce the repetitive parts — data models, integration adapters, test scenarios — while the team concentrated on the business rules that required judgement.

• Individual price lists and discount tiers for partners.
• Multi-step order approval.
• Two-way ERP synchronisation over an API.

The result

Because the context was understood, we avoided the most expensive line item in any project — reworking a misread brief. The client received a working system in a matter of weeks rather than months, and maintenance stayed cheap because the architecture was clean and modular from the start.

How we work, and what that gives you

The order that decided this project is the one we use on every brief: understand the context first, then build, and keep the architecture in steps that can be tested on their own. Which is why a change after launch is not a step into the dark.

If you are facing something similar, get in touch — the first consultation carries no obligation. How we work is on our how we work page.