My Works

Case Studies

Each project below is broken down the same way: the problem it solves, what I actually built, the key features, and screens from the real product.

01SaaS · AI & Machine Learning

Flowmerce

AI recommends, the merchant decides.

Visit the site
Duration
6+ months
My role
Product design, full-stack development & ML pipeline
Stack & deliverables
LightGBMscikit-learnSMOTEFastAPIREST APIMLOpsSaaS
flowmerce-web-app.vercel.app

Flowmerce is a SaaS platform that handles e-commerce return claims from end to end. A customer files a claim on a portal carrying the store's own brand; the platform cross-checks it against the merchant's return policy and the customer's history, then recommends a resolution — exchange, refund, repair or refusal — with a confidence score the merchant can accept, override, or let run automatically.

The problem

Online stores process returns by hand, one email at a time. Every claim means re-reading the return policy, digging up the order, and guessing whether the customer is acting in good faith. It is slow, it is inconsistent from one agent to the next, and it is completely blind to repeat abusers — someone refused by one shop simply moves on to the next one.

What I built

I built the whole product — the merchant back-office, the customer claim portal, the public site and its documentation, the REST API stores plug into their checkout, and the machine-learning pipeline behind every decision. A LightGBM model trained on a 50,000-row returns dataset (cleaning, feature engineering, SMOTE rebalancing, GridSearchCV tuning, then served over a FastAPI endpoint) predicts the resolution, while a separate risk score computed across every store on the network flags claims that look fraudulent. The merchant keeps the last word: auto-approval is a switch they flip once they trust the model.

Key features

  • Automatic resolution recommendation — exchange, refund, repair or refusal — with a confidence score on every claim
  • Cross-store fraud score: a customer refused by one shop protects all the others on the network
  • Return policy configurable per product, per reason and per delay, applied automatically
  • A single REST endpoint to connect an existing store, with merchant and developer documentation
  • White-label claim portal running under the merchant's own brand
  • Timestamped decision history and email notifications on every outcome

Screens from the product

Public site & documentation · 4

Merchant workspace · 3

Back-office & datasets · 4

Architecture & ML pipeline · 4

Mobile · 3

02SaaS · Rental management

Costumia

Find it here, try it on in store.

Visit the site
Duration
2–3 months
My role
Product design & full-stack development
Stack & deliverables
SaaSMulti-shop platformBooking & availabilityPublic directory
location-costumes.vercel.app

Costumia is a SaaS platform for costume rental shops in Algeria. Each shop gets its own back-office to run the business — catalogue by size, rentals, deposits and balances due, calendar — and everything it publishes feeds a public directory where customers find a costume in their size at a shop near them, then go and try it on.

The problem

Costume rental shops still run on paper notebooks and phone calls. The same suit gets promised to two customers for the same weekend, nobody knows exactly what a customer still owes, and a shop's stock is invisible to anyone who doesn't walk through the door — so customers ring shop after shop just to ask whether a size is available.

What I built

I built two products on one platform. On the shop side: a dashboard with monthly, total and average revenue and the upcoming rentals with deposit paid and balance due; a three-step rental wizard (date, rental details, customer) that checks availability automatically so an item can never be booked twice; a monthly calendar colour-coded by item type; customer search across the full rental history; a catalogue split into suits, shirts, shoes and accessories; and a shop profile with logo, wilaya, address, social links and a Google Maps pin. On the public side: a directory filtered by wilaya, with no account to create and nothing to pay online — customers see only the sizes actually on the rack, plus the address and opening hours to try the costume on in store.

Key features

  • Public directory filtered by wilaya — no account to create, only sizes actually on the rack
  • Automatic availability checks that stop the same item from being booked twice
  • Deposit and balance due tracked on every rental, with monthly, total and average revenue
  • Three-step rental wizard — date, rental details, customer — and customer search across the full history
  • Monthly calendar colour-coded by item type: suit, shirt, shoes, accessory
  • Item publishing with occasion, price, discount and matching shirt, shoes and accessories

Screens from the product

Public directory · 1

Shop back-office · 7

03Custom e-commerce · Men's fashion

IA Store

An editorial storefront, built from scratch.

Visit the site
Duration
7–30 days
My role
Design, storefront & back-office development
Stack & deliverables
Custom e-commerceAPI integrationAdmin dashboardResponsive
ia-store.vercel.app

IA Store is an online men's fashion store — clothing, shoes and accessories — built around an editorial "Old Money" art direction rather than a generic shop template. Customers browse a filtered premium catalogue and styled outfit selections; the owner runs the whole thing from a custom admin panel.

The problem

Off-the-shelf platforms box a brand into someone else's template, take a cut of every sale, and make an editorial look nearly impossible. The store needed to read like a fashion magazine while staying fully manageable by its owner, with no developer in the loop for day-to-day work.

What I built

I designed and developed both sides of the store. The storefront opens on a full-bleed editorial hero, then unfolds a premium catalogue with tabs (all, best sellers, new arrivals, sale), promo and best-seller badges, wishlist, product pages and a "Looks & outfits" section that sells complete styles rather than single items. Behind it, the admin panel handles the catalogue, product pages, stock and orders. The store is also the first shop plugged into Flowmerce's return API, so its claims are processed automatically.

Key features

  • Editorial art direction: full-bleed hero, serif typography, magazine-style layout
  • Premium catalogue with tabs — all, best sellers, new arrivals, sale — and promo badges
  • Product pages with variants, pricing in DA, wishlist and cart
  • "Looks & outfits" section selling complete styles instead of single items
  • Custom admin panel for catalogue, stock and orders — no developer needed
  • Connected to the Flowmerce API for automated return handling

Screens from the product

Storefront · 1

Back-office · 2

04Custom e-commerce · Beauty

Almasse Beauty

Authentic cosmetics, delivered across all 58 wilayas.

Visit the site
Duration
7–30 days
My role
Design, storefront & admin development
Stack & deliverables
Custom e-commerceAPI integrationAdmin dashboardResponsive
almasse-beauty.vercel.app

Almasse Beauty is an online beauty store selling hand-picked makeup and skincare from real brands — Huda Beauty, Rare Beauty, Fenty, Maybelline, NYX, e.l.f., Estée Lauder. It pairs a soft, brand-led storefront with an admin space precise enough to run the shop day to day: revenue, order pipeline, shade-level stock and customer accounts.

The problem

In a market flooded with counterfeits, customers will not prepay for cosmetics they cannot verify. The shop had to earn trust before it could sell: prove the products are genuine, name the brands it carries, and let people pay only once the parcel is in their hands.

What I built

I built the storefront around that promise — a brand wall of the houses actually stocked, an authenticity guarantee, cash on delivery, and delivery to the 58 wilayas with 77 pickup desks, all stated above the fold. The catalogue filters by brand and by status (new, best sellers, sale) and goes down to the individual shade. The admin space gives the owner a monthly read on orders and revenue, a status pipeline from "to confirm" to "in preparation", a low-stock watchlist per variant, and product, pack and customer management.

Key features

  • Brand wall and authenticity guarantee placed above the fold to build trust first
  • Catalogue filtered by brand and by status — new, best sellers, sale — down to the shade
  • Cash on delivery, 58 wilayas covered and 77 pickup desks
  • Admin dashboard: monthly orders, revenue excluding cancellations, claims awaiting an answer
  • Order pipeline with per-order status, plus a low-stock watchlist at variant level
  • Product, pack and customer account management

Screens from the product

Storefront · 2

Admin space · 2

05Marketplace · Event venue booking

LIUDOR

The right venue for every event, booked with confidence.

Duration
1–3 months
My role
Product design & full-stack development
Stack & deliverables
MarketplaceBooking & availabilityPayment workflowAdmin dashboard
LIUDOR

LIUDOR — Lieux d'Or — is a marketplace for event venues in Algeria. Customers search wedding halls, conference rooms and reception venues by wilaya, date, guest count and event type, compare capacity, equipment, services and prices, then send a booking request. Venue owners manage their listings and availability from their own space, and the LIUDOR team verifies every venue and every payment in between.

The problem

Organising a wedding or a seminar in Algeria still means calling venues one by one: photos that don't match reality, prices given only over the phone, no way to tell whether a date is free, and deposits handed over with no guarantee. On the other side, owners track requests and dates by hand.

What I built

I built the three sides of the marketplace. The public site offers a search across wilaya, date (single or multi-day), guest count and event type, popular categories and destinations, and detailed venue pages: verified badge, photo gallery, capacity, parking and accommodation, equipment, optional services with their prices, a live availability calendar, a map and similar venues. Booking requests reach the LIUDOR team first, who call the customer to confirm the date and the payment — and only customers whose booking was confirmed can leave a review. Owners get a space to list venues, open or close dates by day or by period, and confirm or cancel requests while tracking what LIUDOR has paid out. An admin back-office validates new venues and manages customers, owners, the blog and testimonials.

Key features

  • Search by wilaya, date — single or multi-day — guest count and event type
  • Venue pages with verified badge, equipment, priced optional services and a live availability calendar
  • Payments checked and recorded by the LIUDOR team before any booking is confirmed
  • Reviews reserved for customers whose booking was actually confirmed
  • Owner space: open or close dates by day or period, confirm or cancel requests, track payouts
  • Admin back-office to validate venues and manage customers, owners, blog and testimonials

Screens from the product

Public site · 2

Owner space · 3

Administration · 1

Have a project like these?

Tell me what you need to build. I'll come back with a clear scope, a timeline and a quote.

Get in Touch
Contact Me

Work Inquiry

Logo