Skip to main content
ECOMMERCE & SYSTEM DESIGN

DR. GAMES: THE INTELLIGENT FULFILLMENT ENGINE

Hybrid gaming marketplace & fulfillment engine

Hybrid
Fulfillment paths
Schema-gated
Checkout validity
Atomic
Wallet ops
Realtime
Ops thread
gaming-store2.vercel.app/en
Watch on LinkedIn
01 — Overview

The problem worth engineering

Dr. Games tackles the unique complexity of the digital gaming market where 'products' aren't just static items.

They are dynamic services requiring specific user inputs (Player IDs, Region locks, Account Credentials) before purchase. The core challenge was building a backend that treats 'Manual Fulfillment' and 'API Automation' as interchangeable strategies.

The system allows admins to configure a game as 'Provider-based' (injecting API keys for services like Twelve.sa) or 'Manual' (routing to an admin queue). Crucially, it enforces a strict 'Pre-purchase Resolution' flow: users cannot proceed to checkout until they resolve all required credentials specific to their chosen items, ensuring 100% valid orders and reducing operational friction.

Built with Next.js SSR featuring advanced caching strategies using revalidate tags and path-based revalidation for optimal performance. Implemented multi-language support with high-performance server-side filtering and pagination, ensuring fast page loads across all locales.

Integrated Google OAuth 2.0 with refresh token rotation using Passport.js for secure, persistent authentication. The platform supports multi-currency transactions with real-time exchange rate conversion and localized pricing.

Additionally, it features a robust real-time support chat system for seamless communication between users and administrators during the fulfillment process.

  • Hybrid fulfillment strategy: provider API automation and manual admin queues as interchangeable order paths.
  • Dynamic requirement engine — per-game credential schemas resolved before checkout so every order is valid.
  • Multi-currency wallet + OPay/Paymob with atomic credit/debit and real-time fulfillment chat.
02 — Deep-Dive Modules

How it was built, system by system

01 / 11
Engineered a 'Dynamic Requirement Engine'
Core Engine & Business LogicModule 03

Engineered a 'Dynamic Requirement Engine'

Admins define input schemas per game (e.g., 'Player ID' for PUBG, 'Email/Pass' for Steam). The frontend dynamically renders these forms and validates user input before adding to cart.

Core Engine & Business Logic1
Real-Time, Media & Tracking2
Commerce, Checkout & Payments3
Auth, Security & Compliance2
Data, State & Performance3

Related Projects

Explore more of my work

smoke
logo

"If Your Dreams do not scare you, they are too small !"

Got a project? Let’s vibe together and
make it ninjaa-precise—get in touch!

Call Me Now !

mail

noordragon2004@gmail.com

address

from egypt,mansoura

phone

+20 1145838187