Building a Complete E‑Commerce Site Solo with an Open‑Source Java Platform

Client Background and Project Goal

A beauty‑influencer with 300k+ followers needed a private‑domain e‑commerce system to retain customers, replacing unstable live‑stream sales. The required features included an H5 mobile site, a WeChat mini‑program, order management, and promotional tools such as group‑buy and flash‑sale.

Choosing an Open‑Source Solution

Instead of building everything from scratch or using AI‑generated code, the author was advised to use an existing open‑source project. The recommended CRMEB Java edition (v3.0) offered a complete codebase under the Apache‑2.0 license, free for commercial use.

Technology Stack Overview

Backend: SpringBoot 2.2.6 + SpringSecurity + MyBatis‑Plus 3.3.1 Database & Cache: MySQL 8.0 (utf8mb4 charset) + Redis (used for queue throttling)

Build Tool: Maven 3.6 API Docs: swagger‑bootstrap‑ui Admin UI: Vue 2 + Element UI Mobile Frontend: uni‑app (single codebase for H5, public account, and WeChat mini‑program)

The project follows a clear front‑back separation with three directories: admin (PC admin), app (mobile), and crmeb (backend API).

License and Community

The Apache‑2.0 license means no encryption, no commercial fees, and minimal legal risk for delivery. The Gitee repository has over 12k stars and regular updates, indicating an active community.

Deployment Walk‑through and Pitfalls

Environment Preparation : Install JDK 1.8, MySQL 8.0, and Redis.

Clone Repository : git clone https://gitee.com/ZhongBangKeJi/crmeb_java Create Database : Execute the provided initialization SQL.

Configure : Edit crmeb/application.yml with DB URL, Redis address, and file‑upload path.

Build and Run Backend : mvn clean package then start the service.

Start Frontend : In admin run npm install && npm run dev and set the API endpoint.

Two common issues:

MySQL version : Documentation mentions 5.7, but the project expects 8.0; ensure the charset is utf8mb4.

Redis not started : The service starts without error, but queue‑related features remain silent.

A demo account (username: demo, password: crmeb.com) is provided for quick exploration.

Customization Highlights

API Design

The system follows RESTful conventions; Swagger auto‑generates documentation, making it easy to locate controllers, services, and mappers for any module.

Fine‑Grained Permissions

Spring Security enables button‑level permissions, allowing the client to restrict actions (e.g., “operations can view but not delete”) without hard‑coding conditionals.

Form Generator

Backend forms are built with a drag‑and‑drop generator, drastically reducing manual component coding.

Code Readability

Consistent comments and directory conventions are documented at doc.crmeb.com, easing future maintenance.

UI Theming with the Theme Marketplace

The v3.0 theme marketplace offers industry‑specific templates. Selecting a beauty‑industry template and importing it replaces the entire UI in minutes, saving roughly a week of front‑end styling work. The marketplace also supports DIY visual editing, allowing non‑technical operators to compose pages with “super components” that bind data (users, products, coupons) to interactive elements.

Built‑In Marketing Modules

CRMEB includes ready‑made features such as group‑buy, bargain, flash‑sale, coupons, sign‑in, points, membership levels, and distribution/fission. These can be enabled via backend configuration, eliminating the need to develop marketing logic from scratch. The distribution module, in particular, turned a separate development effort into a zero‑cost feature for the client.

Pros and Cons (Based on Real Delivery)

Free commercial use without encryption.

Modern, mainstream technology stack.

Easy to extend and customize.

Comprehensive documentation and demo.

Theme marketplace significantly reduces UI effort.

Responsive official support channel.

Things to watch out for:

The system is sizable; newcomers need time to understand its structure.

Theme quality varies; careful selection is required.

Current Java edition supports only single‑tenant; multi‑tenant needs a different solution.

Conclusion

For freelancers or teams needing to launch an e‑commerce store quickly without heavy front‑end work, the CRMEB Java open‑source project provides a solid foundation that covers about 80% of common functionality, leaving only business‑specific customizations to implement.

Project resources:

Gitee: https://gitee.com/ZhongBangKeJi/crmeb_java

GitHub: https://github.com/crmeb/crmeb_java

Documentation: https://doc.crmeb.com/java