Project · WRK-004

Bakery Store Ordering & Shift Planner

An ordering and scheduling tool for a four-store bakery. Store managers submit from a mini program; the central kitchen sees everything in one place.

Online
Bakery Store Ordering & Shift Planner
Category
Mini Program
Status
Online
Created
Feb 17, 2025
Updated
Sep 8, 2026
  • WeChat Mini Program
  • Vue 3
  • Node.js
  • PostgreSQL

Project background

The client is a local bakery with four stores and one central kitchen. Every evening, store managers posted tomorrow's bread order in a group chat, and someone in the kitchen copied dozens of messages into a spreadsheet.

Problem

  • Messages got missed, so some stores ran short and others had leftovers;
  • Shifts lived in a shared spreadsheet, and nobody knew who changed what;
  • The owner wanted to see waste per store but had to scroll back through chats at month end.

Approach

We didn't build an ERP. We built two things: ordering and scheduling. Managers submit from a mini program; the kitchen and the owner use a web dashboard.

Key features

  • Daily store orders, with "copy yesterday's order" for the usual case;
  • Automatic cut-off at 21:00 — later changes need the kitchen's OK;
  • Kitchen summary by product, ready to print as a production sheet;
  • Drag-and-drop weekly shifts with conflict warnings;
  • Simple weekly reports on orders and write-offs per store.

Architecture

Native mini program on the store side, Vue 3 for the dashboard, a Node.js API and PostgreSQL. Runs on a single cloud server with daily backups.

What we handled

Requirements, interaction design, mini program and dashboard development, deployment, and on-site support during the first month.

How it went

In week one we visited two stores to watch how managers placed orders at night. That's why "copy yesterday" ended up as the biggest button — most nights they only change a few numbers.

Screenshots

The screenshot shows the scheduling and summary dashboard. Store names and figures have been anonymised.

What went wrong

Holiday orders look nothing like a normal day, so "copy yesterday" caused mistakes. We added "copy the same day last week".

Outcome

The kitchen no longer transcribes chat messages and has a production sheet within ten minutes of cut-off. Emergency transfers between stores dropped too.

Current status

Live. Small changes every quarter.

Next

The client wants ingredient inventory. We're still deciding whether it belongs in the same system.