Full Stack / Systems
RAN Technology
Computer shopping. Repair services. One connected place.
- My role
- Full-stack development · end to end
- Project period
- 2026
- Current stage
- Built implementation
The storefront connects computer-product discovery with access to repair services.
A problem worth
connecting.
RAN Technology brings computer shopping and repair requests into one website. Customers can browse products, build a cart or plan a PC, then book a repair or request a quote without moving to a separate service channel.
Built forComputer-product customers and repair-service staff
The work behind
the interface.
I built the project end to end as the full-stack developer, including the customer-facing website, backend API, database integration and administration features. The work connected product discovery and checkout with a separate repair-booking and quotation workflow.
A storefront, with a workshop behind it.
A closer look.
Actual screens from the project. Select a view or open it at full size.
Customers browse and filter the catalogue, check stock and add computer products to their cart.
How the pieces connect.
Follow an action through the system.
- 01
Explore
Customers browse products or choose a computer repair service.
- 02
Request
The React client sends cart, order, booking or quotation actions to the API.
- 03
Handle
Express routes and controllers apply the relevant purchase or service workflow.
- 04
Record
Supabase stores orders, stock and service requests; Cloudinary holds product images.
- 05
Follow through
Staff manage orders, repair bookings and quote requests through the administration tools.
What the platform does.
Product discovery
Product browsing, filtering, reviews and PC build pages help customers explore computer products.
Accounts and checkout
Customer accounts, shopping carts and checkout connect browsing to an order.
Order management
The API creates orders and updates stock so purchase activity is reflected in the database.
Repair bookings
Customers choose a repair service and submit a booking for staff to manage.
Quotes and follow-up
Repair quote requests, booking statuses and reminders support the service workflow.
Shop administration
Administration features and contact-message handling give staff a way to manage the store and its requests.
This is where the learning happened.
The hard part.
Product ordering and repair services share customer information, but they need different workflows and status changes. Both had to connect cleanly across the interface, API and database.
How I approached it
I organised the backend into routes and controllers, and used database migrations to support repair quotations, booking statuses and reminders. This kept the shopping and service flows distinct while giving them a shared data foundation.
Tools behind the work.
- Frontend
- ReactTypeScriptViteTailwind CSSZustand
- Backend
- Node.jsExpressTypeScript
- Data & media
- Supabase PostgreSQLCloudinaryDatabase migrations
- Deployment configuration
- Vercel
Where it stands.
- A customer-facing storefront and computer-repair experience.
- Connected product, order, stock, booking and quotation workflows.
- Backend routes, database integration and administration features.
- Vercel deployment configuration included in the project.