Skip to content
CraftSoftware System

Web platform · Retail

Harvest MarketConcept

A fresh-produce storefront with delivery slots, substitutions, and an admin that the store team updates themselves.

Concept interface with demo data. Not a client project.
Client
No client (concept)

Concept project — no real client. Created to show how we would approach this kind of product.

Industry
Retail
Platforms
Web, Mobile web
Delivery scope
  • Brand-led UI design
  • Storefront
  • Delivery slot engine
  • Admin
  • Payment integration
Technologies
  • Next.js
  • Headless CMS
  • Paystack
  • PostgreSQL

Overview

The scenario

Harvest Market imagines a neighbourhood grocer taking orders on WhatsApp. The concept moves ordering to a fast mobile-first storefront while keeping the personal touch customers value.

The problem

Orders arrive as chat messages that staff copy into notebooks, prices change daily, and substitutions cause disputes at the door.

Our solution

Customers shop a live catalogue, choose a delivery slot, and set substitution preferences per item. Staff update prices and stock from a simple admin and pack from a printed pick list.

User journey

How someone actually uses it

  1. 1

    Browse

    Customers shop by aisle or search, with today's prices.

  2. 2

    Choose a slot

    Available delivery windows are shown before checkout.

  3. 3

    Set substitutions

    For each item: allow a similar product, or don't substitute.

  4. 4

    Pay

    Checkout through a payment provider, or pay on delivery where enabled.

  5. 5

    Receive

    Customers get updates when their order is packed and on the way.

Web

Product screens

4 screens from the web application.

Screen 1 of 4: Storefront home: today's produce and next delivery slot.

Swipe, use the arrow keys, or pick a thumbnail. Screens are concept designs with demo data.

Read descriptions of all 4 screens
  1. 1. Web

    Storefront home: today's produce and next delivery slot.

    Storefront home page with produce categories and a delivery slot banner

  2. 2. Web

    Aisle view with daily prices.

    Vegetable aisle listing products with prices and add buttons

  3. 3. Web

    Checkout: pick a slot and set substitutions.

    Checkout step showing delivery slots and substitution preferences

  4. 4. Web

    Admin: today's orders, capacity, and low stock.

    Admin dashboard for today's orders and stock

Key features

What it does

  • 01

    Daily pricing

    Staff update prices and availability in minutes.

  • 02

    Delivery slots

    Capacity-limited windows so the team isn't overbooked.

  • 03

    Substitution choices

    Clear preferences reduce disputes at delivery.

  • 04

    Online payment

    Integrated payment with order confirmation.

  • 05

    Pick lists

    Orders grouped by aisle for faster packing.

  • 06

    Editable content

    Promotions and banners managed without a developer.

Approach

Design and development

Design

Mobile-first, image-led product cards with prices always visible. Checkout reduced to three steps and tested on low-end Android phones.

Development

Next.js storefront with server-rendered catalogue pages, a headless CMS for content, and a slot engine that enforces capacity in the database.

More work

All projects
ConceptWeb platform· Distribution

Ledgerly Ops

An operations dashboard that unifies orders, stock, and invoices so a growing distributor can stop reconciling spreadsheets.

  • Next.js
  • TypeScript
  • PostgreSQL
View Case Study
ConceptAI & automation· Professional services

Triage Assist

An AI intake flow that reads incoming documents, extracts key fields, and routes each case to the right reviewer for confirmation.

  • Python
  • LLM APIs
  • Queue workers
View Case Study
ConceptBlockchain· Agriculture

Provenance Trace

A traceability record that follows each batch from farm to shelf, with a public verification page behind every product QR code.

  • Solidity
  • Node.js
  • Next.js
View Case Study

Want something like Harvest Market?
Let's build yours.

We'll start from your users and constraints, not a template. Tell us about your project and we'll reply with questions and next steps.