Back to portfolio

Project page

View storefront

Ecommerce system

Allora Store

A premium single store ecommerce build with a polished storefront and a serious admin layer behind it.

The storefront handles browsing, product pages, checkout, and order tracking. Behind it, the admin handles branding, homepage sections, products, orders, subscribers, policies, analytics, and payments without turning every change into developer work.

  • Acquisition ready
  • Stripe + Paystack
  • Storefront + Admin
Storefront

Homepage, product pages, checkout, order tracking, and wishlist.

Admin

Branding, merchandising, products, orders, subscribers, and coupons.

Foundation

React, Node, MongoDB, Cloudinary, Stripe, Paystack, and Playwright.

Allora Store homepage hero preview
Allora Store admin My Store preview
My Store Branding, hero content, categories, policies, trust sections, and support details are managed from one admin surface.

Overview

The storefront is only half the story.

Allora Store is built around the kind of commerce flow that needs more than a good looking landing page. The public experience includes real product detail pages, variant based selection, search, category browsing, new arrivals, wishlist behavior, checkout, order tracking, and support pages.

The admin mirrors that seriousness with usable control over merchandising, catalog structure, operational settings, customer communication, and payment readiness.

Storefront

Built to browse and convert

Responsive homepage sections, category flow, search, related products, saved items, checkout, and order tracking.

Product model

Variant driven by design

Multiple images, option switching, stock aware cart behavior, variant image mapping, and search friendly product URLs.

Operations

Admin for day to day control

Orders, coupons, subscribers, homepage edits, policy content, support details, and catalog imports all live inside the app.

Delivery

Ready for real deployment

Stripe and Paystack support, email flows, analytics hooks, SEO metadata, structured data, sitemap, and production checks.

Admin

The control layer matters.

This side of the product is built for actual store ownership. Routine updates stay inside the system: branding, homepage sections, product management, support details, policies, categories, coupons, order handling, and subscriber operations.

My Store acts as the main control center, while products, orders, subscribers, and super admin tasks each have their own working surface.

My Store

Hero content, promo sections, support details, categories, FAQ, policies, analytics IDs, trust blocks, and brand rail.

Products

Create, edit, delete, upload images, assign variants, and move catalog data in or out with CSV.

Orders and subscribers

Filter and update orders, resend emails, archive delivered orders, export subscribers, and handle delivery status visibility.

Foundation

Operational enough to hand over.

  • Stripe Checkout Sessions and Paystack support with payment readiness checks
  • Resend powered emails for orders, subscribers, welcome flows, and owner notifications
  • GA4 and Meta Pixel support with consent based analytics initialization
  • Canonical tags, Open Graph, structured data, robots.txt, and sitemap.xml
  • Responsive image delivery, accessibility improvements, reduced motion handling, and Playwright coverage

Project page

Open the storefront, then think about the handoff.

The public side is polished. The admin side is what makes the build useful to run.