Public ecommerce website
Repacks Marketplace
Project owner · Engineering team lead
I lead the engineering team behind Repacks Marketplace and guide its system design and development, shaping how customer actions flow through payments, orders, inventory, and fulfillment. I built across the customer experience, commerce backend, and operations platform—from browsing and collections to accounts, wallets, inventory, and fulfillment. Checkout and payment orchestration are my deepest areas of ownership within that broader work.
Visit gradient.cards (opens in a new tab)THE BRIEF
What needed to be built.
Gradient needed a complete commerce experience: customers had to discover cards, buy packs, manage their collections, sell cards back, and request shipment. The operations team needed connected tools to manage inventory, listings, customer accounts, orders, and fulfillment.
MY CONTRIBUTIONS
My contribution.
Customer experience
- Built search, filters, collections, and bulk actions; added shareable pack-opening results and social previews.
- Connected Cognito, local accounts, and Odoo with guest-cart merging, secure cookies, CSRF checks, and coordinated sessions.
- Built card sell-back, wallet credit, audit trails, and Stripe Connect cashout workflows.
Orders & operations
- Designed separate payment and shipping states, shipment requests, address controls, and cancellation rules.
- Built admin tools for inventory, packs, listings, customers, orders, and validated CSV exports.
- Integrated Odoo and built reconciliation tools for stock discrepancies and duplicate pack assignments.
Payments & recovery
- Designed checkout across Stripe, wallets, and Odoo with durable work leases, safe retries, and partial-payment recovery.
Infrastructure & release
- Configured AWS ECS and Terraform, scoped IAM, Secrets Manager, encrypted S3, and CloudWatch monitoring.
- Added unit, database, and Playwright tests for payments, accounts, admin workflows, and privacy controls.
- Built migration checks, guarded schema rollouts, regression checks, and release runbooks.
WHY THIS MATTERS
A payment can succeed even when the order update fails. A retry can then charge a customer twice or leave inventory out of sync. The challenge is keeping Stripe, wallets, inventory, and Odoo consistent when only part of checkout completes. This design makes retries safe and gives interrupted payments a recovery path, reducing the need for manual reconciliation.
THE RESULT
$144K+ across 4,626 paid orders in under four months of sales.
Delivered shopping, collections, wallet, inventory, and fulfillment workflows across Next.js, FastAPI, and PostgreSQL for a marketplace supporting $144,603.36 in paid-order volume across 4,626 orders in under four months of sales (May 21 to September 16, 2026). I continue to lead the engineering team, translate client requirements into delivery priorities, and develop the payment and operational safeguards behind the product.
Production admin and database snapshot: September 16, 2026. Paid-order volume includes card and wallet purchases, shipping and tax after discounts; it is not net revenue or profit.