B2B auto-parts for garages across Europe.
- Client
- [Name — pending approval]
- Market
- Europe · EUR
- Engagement
- Annual team, since 2026
- Scope
- Product, web, mobile, data, ops
Find the part. See the price. Order.
A garage picks a car — by plate, VIN or by hand — finds the part by number, category, name or factory diagram, sees offers with price and delivery time, and orders. That is the whole promise.
Behind it: technical catalogues from external providers, price lists from dozens of suppliers, customer-specific pricing, a commerce engine that must stay the single source of money, and channels from the web store to WhatsApp.
The client had the business and the suppliers. They needed one team to design and build the platform end to end.
One owner for every truth.
Before any code, we agreed which system owns what. Everything else reads from the owner and never overrides it.
Two rules the customer never sees: a supplier’s name and purchase price never reach the store, and the order re-checks price and stock at checkout.
Every tile on the wall.
- B2B store and a new customer portal
- Carts with groups, comments and alternatives
- Checkout, payments and returns
- Ordering app for garages
- Field CRM app with visits and offline sync
- Voice search in the workshop
- Supplier feed: price lists, stock, delivery terms
- Master catalogue in AtroPIM
- Technical catalogues, ERP and support desk
- Warehouse and a single metrics layer
- Search analytics: why a search failed
- WhatsApp ordering in the customer’s words
- MCP access for customers’ own agents
- Separate stage and production
- Monitoring, logs, backups
- Docs and API reference for partners
Numbers
Agents for volume, people for decisions.
Each task starts in the tracker, becomes a branch and a pull request, passes tests and a preview, and reaches stage only after a person accepts it. Production gets the exact build verified on stage.
Documentation ships with the code: architecture notes, an API reference for partners and runbooks for operations.