Case study
Customer portals for RetroFam and RetrovGames
After the sale, a shopper should not have to email support to find a parcel, start a return, or download an invoice. RetroFam and RetrovGames each have a portal for that. Both open after the customer signs in.
Signed-in customers track orders, start returns, download invoices, and submit trade-ins.
The problem
Both brands sell on Shopify. The work after checkout was scattered: where is the shipment, how does a return start, where is the invoice, what happens to a trade-in. Support was the interface.
What was built
I led the frontend at Retrovgames. Each portal is a Next.js app on a Node.js API. The customer sees orders, shipment tracking, returns, PDF invoices, coupons and gift cards, and a trade-in flow for selling gaming items back.
The same backend pattern serves both brands. The screens, the brand, and the data are not shared with the other brand's customers. Hector, the internal ERP, reads trade-in records from the portal database so warehouse staff can act on them without asking the customer to resend the form.
Where to open them
RetroFam is at app.retrofam.com. RetrovGames is at app.retrovgames.com. Both require a customer sign-in. They are not public demos.