Backend Development 8 min read

Mastering Order Management in a SpringBoot‑Vue E‑Commerce Project

This article walks through the design and implementation of the order module in the Mall project, covering both backend administration and frontend shopping flow, database schema, API design, and available video tutorials for a comprehensive e‑commerce solution.

macrozheng
macrozheng
macrozheng
Mastering Order Management in a SpringBoot‑Vue E‑Commerce Project
Order functionality is a core feature of e‑commerce systems, involving both the front‑end shop and back‑end admin, making its design crucial and widely applicable to any transaction‑based project.

Mall Project Overview

The Mall project is an e‑commerce system built with SpringBoot, Vue, and uni‑app, hosted on GitHub with

60K

stars. It includes front‑end shop and back‑end admin, supporting a complete order workflow along with product, cart, permission, coupon, and member features.

Project URL: https://github.com/macrozheng/mall

Video tutorials: https://www.macrozheng.com/video/

Feature Design

The order feature spans both the back‑end admin system and the front‑end shop, which we will discuss separately.

Back‑End Admin System

The admin order module includes order management, order settings, return reason settings, and return request handling.

Order Management

Admins can view, delete, ship, and track orders from the order list.

In the order detail page, admins can modify recipient info, adjust fees, close orders, and add remarks.

Order Settings

Admins can configure basic settings such as automatic order closure after a certain time.

Return Request Handling

Admins can approve or reject return requests.

Return Reason Settings

Admins can define return reasons for users to select during the return process.

Front‑End Shop System

We illustrate the core order flow in the Mall project from the shop side.

Process Diagram

The complete flow from adding items to the cart to order completion is shown below.

Order Steps

Customers view products in the shop.

After adding items to the cart, customers view the cart.

Clicking checkout creates an order.

Customers proceed to the payment page.

After payment, customers view their orders.

The back‑end system receives the order.

Admins ship the order.

After shipping, the order status becomes "awaiting receipt".

Customers confirm receipt, completing the transaction.

Admins can view order details.

Feature Summary

A mind‑map of the order module’s functions and related fields is provided for quick reference.

Database Design

The database schema for the order module is shown below.

API Design

Refer to the project’s Swagger documentation; APIs prefixed with

Oms

correspond to the order module.

Video Tutorials

Comprehensive video lessons cover the order module’s database and API design, explaining each table and code implementation.

These tutorials are part of the "Mall Video Tutorial (2023 Latest)" series, accessible via the provided QR code.

Conclusion

The article presented the design, database schema, and API design of the Mall project’s order module, emphasizing its importance for any system involving transactions.

Project Source Code

https://github.com/macrozheng/mall

Recommended Reading

Github starred 60K! This Java‑centric e‑commerce tutorial series.

Mall front‑end shop officially released, supporting a full order flow.

Designing product features in e‑commerce systems.

Designing a universal permission system.

New employee takes over a zero‑to‑one project.

Preview the long‑awaited Mall video tutorial.

backende-commercefrontendVueSpringBootOrder Management
macrozheng
Written by

macrozheng

Dedicated to Java tech sharing and dissecting top open-source projects. Topics include Spring Boot, Spring Cloud, Docker, Kubernetes and more. Author’s GitHub project “mall” has 50K+ stars.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.