Storrd: Creating Digital Infrastructure for a Convenience Store
How a retail store chain hired an Odoo Architect and an Odoo Consultant.
Challenge
Storrd is a convenience store business selling everyday essentials alongside fresh prepared food, trading from early until late, with an order-ahead channel as well. That range is what makes the operation difficult. Ambient groceries and fresh food behave completely differently: one has a shelf life measured in months, the other in hours, and the same system has to buy, count, price and sell both. The shops are small, with little room to hold stock, and convenience margins are thin enough that inaccurate stock figures show up quickly in both waste and lost sales. Order-ahead places a second demand on the same inventory. All of it runs through one system, which makes that system central to the business rather than administrative.
Two requests went in, months apart. The first was an Odoo architect: eight years designing ERP and CRM systems across pharmaceuticals, automotive, electronics, e-commerce and healthcare, working in Odoo alongside Python, FastAPI, PostgreSQL, Docker and React, with a record of integration work such as telephony, marketing automation, communication APIs because an ERP earns its place only once everything around it can talk to it. The second came once the structure was settled: an Odoo consultant with nine years inside that ecosystem specifically, across finance, accounting, logistics and payments, and four full-cycle implementations behind them.
Storrd already employed Odoo consultants, so nobody we put forward was going to be taken on trust by people who could assess them inside one conversation. Shortlisting went to candidates with full implementations taken through go-live and then lived with afterwards, because the hard part of Odoo is not the configuration, but when business has moved and the system has not. The Managing Director interviewed personally, with the company’s own consultants and supply chain managers in the process, and the first engagement was confirmed 52 hours after the request opened.
Outcome
Storrd was not missing knowledge. The company had Odoo consultants and supply chain managers who knew exactly what they wanted. What it needed was someone to design the structure underneath all of it, and then, once that was settled, someone to do the domain work on finance and logistics inside it.
- Two separate requests, with the first engagement in 52 hours.
- Odoo architecture first, then Odoo consultant across finance, logistics and supply chain.
- Added alongside the company’s own Odoo consultants and supply chain managers, where the work was judged by people who knew the platform.
- Four months of engagement covering inventory, point of sale, purchasing and supply chain inside one system.
A Strategic, Multi-Phase Hiring Approach
Phase: Request
Two separate requests one by one: an Odoo architect to design the structure, and an Odoo consultant later, once there was a structure for the finance and logistics work to sit in.
Phase: Matching
Weighting went to full-cycle implementations taken through go-live and supported afterwards, and for the architect to integration work connecting Odoo to the systems around it, with 3 of 6 shortlisted reaching interview.
Phase: Interviews
The Managing Director interviewed personally, with the company’s own Odoo consultants and supply chain managers taking part, and the first match was confirmed 52 hours after the request opened.
Phase: Engagement
Both engagements opened with part-time monthly workload, hour caps, daily hour tracker for visibility, and monthly reports with commitments.
Phase: Support
The work was moving from architecture to operations from month to month with workloads and hour caps changed and approved from the account.
