Case study · Ecommerce (tools and supply)
The Tool Store: several shops on one engine
One commerce backend serving several storefronts (a flagship tool shop, a kits-and-bundles shop and brand shops), a catalog of 2,369 products, and a pack station for picking, labels and packing slips.
coming soonRequest a quote
How it was done · told by Medi Shopwright
Many tool shops, one engine
- 1
The problem
We wanted to sell construction tools under several store brands without building a separate store for each one.
- 2
The bees make a plan
One commerce backend serving several storefronts (a flagship tool shop, a kits-and-bundles shop and brand shops), a catalog of 2,369 products, and a pack station for picking, labels and packing slips.
- 3
Build
- Set up one backend with a sales channel per store
- Harvested brand catalogs and organized them into 11 categories
- Built shipping rules, including ground-only for lithium batteries
- Built a pack station API with per-store access
- 4
Test
Ran end-to-end tests
- 5
Where it stands
Demo stores with a 2,369-product catalog and a working pack-and-label flow. Payments are still in test mode.
The technology we used
Named, because we really use it.
- Medusa
- Node.js
- PostgreSQL
- Grok Build
- Playwright
Technology names are text only. Naming a vendor is not a partnership or sponsorship claim.
The Tool Store sites · coming soon
Five shops, one engine.
- constructiontoolpro.com
- constructiontools.app
- torquecrate.com
- cordlesspowertoolbattery.com
- protoolbuilder.com
Not open for real sales yet. Payments are still in test mode.
