Selected work · Army Gadget
Rebuilding a webshop in flight.
Army Gadget (formerly armytech) is an Iranian e-commerce platform with an integrated backoffice — stock, accounting, site content, multi-gateway payments, and an in-store point-of-sale bridge. We took the codebase over mid-build and are refactoring it toward production-grade without taking the site offline.
- Client
- Army Gadget (rebrand from armytech)
- Year
- 2026 → ongoing
- Role
- Engineering takeover, refactor, ongoing dev
- Stack
- React · Node · PostgreSQL
The situation
The shop was already live when we came in. Customers were buying, deliveries were going out, and the backoffice was doing about half of what the team needed.A rebuild-from-scratch wasn't an option — the lights couldn't go off — so we took the codebase over as it was.
What we inherited was a system that had outgrown its first implementation: thousand-line modules, business logic and presentation tightly coupled, payment integrations duplicated across files, and no test coverage on any of the paths that touch money or stock. Familiar territory for a project that shipped fast — and exactly the work we like best.
The work
Refactor in flight, not from scratch.
The discipline of taking over a live product: make the system understandable, then testable, then changeable — in that order — without dropping a single order on the floor.
01
Decompose the monoliths
Thousand-line modules became domain-shaped: cart, catalog, checkout, stock, payments. Each one lives behind a contract its caller can trust.
02
Tests where the money lives
Coverage went on the paths where mistakes cost cash first — checkout, payment-gateway responses, stock decrements, invoice generation. The rest follows over time.
03
A backoffice that does the job
Stock, accounting, page content, and site settings were spread across half-finished surfaces. We collapsed them into one admin the team can run the shop from.
04
Ship without taking the shop down
Customers were buying throughout. Refactors land behind feature flags, gates, and dual-write paths where they need to — no maintenance pages, no late-night cutovers.
The shape of it
Three surfaces, one system.
Storefront
armytech.shop
Persian-language webshop. RTL throughout, Jalali calendar, multi-gateway Iranian payments, and a content layer the team edits without touching code.
Backoffice
Admin & operations
Stock, accounting, orders, returns, and site content. Built for the people running the shop — barcode scanning, PDF invoicing, multi-warehouse stock.
POS bridge
In-store ↔ online
A bridge between the physical point-of-sale and the online catalog so stock counts stay honest in both places.
Where it is
The site is live at armytech.shop. The refactor is ongoing, and a visual rebuild is on the roadmap. New features ship alongside the cleanup — that's the deal when you take a project over: the bills keep getting paid while you clean the wiring.
When the refactor lands its real milestone — coverage on every money path, a clean domain layer, a redesigned storefront, a backoffice the team uses without complaint — this case study gets the long-form follow-up it deserves, with screenshots.
Inherited a codebase? We can help with that.
Engineering takeovers are a thing we do well. Tell us what you've got.