StoreParity
Full-stack seller-operations dashboard with 100% feature parity against a leading marketplace's seller console. Responsive React frontend and admin panel with category management, articles, and localization. Express backend with MongoDB. Built and tested via RDP as the reference service is unavailable in Pakistan.

The reference marketplace console this project had to match isn't accessible in Pakistan, which meant the entire build-and-test loop had to run through RDP into a remote environment just to compare behavior against the real product. On top of that constraint, the target was full feature parity — not an approximation, but a console that a merchant coming from the original platform wouldn't notice was different.
StoreParity is the full-stack seller-operations dashboard that resulted: everything a merchant needs to run their storefront — products, orders, categories, and localization — through a responsive frontend and admin panel backed by an Express/MongoDB API.
What I Built
- Responsive React frontend for product management, order tracking, and analytics
- Admin panel with category management, article/content management, and multi-language localization
- Express + MongoDB backend powering products, orders, and user accounts through unified REST APIs
- Cross-surface API consistency — the same endpoints serve both the storefront-facing site and the internal admin panel
- Localization layer supporting multiple languages and regional formatting
- RDP-based testing workflow built specifically to validate parity against a service unavailable in the local market
Tech Stack
- Frontend: React, responsive design
- Backend: Express, Node.js
- Database: MongoDB
- Testing: RDP-based environment simulation for cross-market parity checks
Key Decisions
Reused the same REST endpoints for both the storefront and the internal admin panel instead of building two API surfaces, trading a bit of endpoint flexibility for guaranteed data consistency between what merchants and admins saw. The localization layer runs as a formatting/translation pass at the API boundary rather than duplicating templates per language, so adding a new locale didn't mean touching business logic. The RDP-based testing workflow was set up early in the project rather than treated as a stopgap, since parity testing against the reference console had to be a repeatable part of every sprint, not a one-off exercise.
Outcome
Delivered a feature-complete seller-operations dashboard with genuine 100% parity against the reference console — proof of both full-stack range and the problem-solving needed to build and validate a product without direct access to the system it had to match.