Chengwu Low-Code Platform: Rapid Universal Inventory System with LogicFlow Workflows

Overview

Inventory management systems are widely used in manufacturing, retail, and wholesale industries to efficiently manage inventory, procurement, sales, finance, and other key processes. Traditional systems often involve high development costs and long cycles. By leveraging the Chengwu low-code platform combined with LogicFlow workflow and AMIS multi-event waiting pattern , a flexible and scalable universal inventory system can be built rapidly, greatly improving development efficiency and optimizing business processes.

This design document describes the core functional modules — inventory management, procurement management, sales management, supplier and customer management, financial management — and integrates them via workflows to achieve multi-functional sequential execution.

Business Requirements Analysis and Workflow Scenarios

2.1 Core Functional Modules

Inventory Management : Track real-time inventory changes, record inventory alert thresholds to avoid stockouts or overstock, and log inbound, outbound, and return operations.

Procurement Management : Record supplier information and purchase orders, manage inbound goods, track order execution status and delivery dates, calculate procurement costs and update inventory.

Sales Management : Track sales orders, record outbound shipments, support customer information and sales price management, calculate gross profit and provide sales reports.

Supplier Management : Record basic supplier information, track order history and delivery performance.

Customer Management : Record basic customer information, manage customer credit, track purchase history and payment status.

Financial Management : Calculate financial data for procurement and sales such as total cost, revenue, gross profit, and generate financial reports for analysis.

2.2 Multi-Functional Sequential Execution Scenarios

Several business scenarios require sequential execution across multiple modules:

Procurement Inbound : After confirming a purchase order, execute inventory update, procurement recording, and financial update.

Sales Outbound : After confirming a sales order, execute inventory reduction, sales record update, and financial settlement.

Inventory Alert and Replenishment : When inventory falls below the alert threshold, trigger a replenishment process and automatically generate a purchase order.

Procurement Return : When goods do not meet requirements, process procurement return, update inventory and financial information.

These operations typically involve sequential execution across multiple modules; using LogicFlow workflow to define the execution order is highly suitable.

System Design and Workflow Definition

3.1 Database Table Design

Based on standard open-source inventory system design, the following database tables cover products, procurement, sales, inventory, and other modules. Field definitions are kept concise for subsequent operations and page generation.

1. Products Table ( products )

Records all product information including name, category, unit, price, etc.

CREATE TABLE `products` (
  `product_id` INT NOT NULL AUTO_INCREMENT COMMENT 'Product ID',
  `product_name` VARCHAR(255) NOT NULL COMMENT 'Product Name',
  `category` VARCHAR(100) NOT NULL COMMENT 'Product Category',
  `unit` VARCHAR(50) NOT NULL COMMENT 'Unit (e.g., piece, box)',
  `purchase_price` DOUBLE NOT NULL COMMENT 'Purchase Price',
  `sale_price` DOUBLE NOT NULL COMMENT 'Sale Price',
  `quantity_in_stock` INT NOT NULL DEFAULT 0 COMMENT 'Current Stock Quantity',
  `reorder_point` INT NOT NULL COMMENT 'Reorder Alert Threshold',
  `status` VARCHAR(50) DEFAULT 'Active' COMMENT 'Product Status (e.g., Active, Inactive)',
  PRIMARY KEY (`product_id`)
) COMMENT='Products Table';

2. Purchase Orders Table ( purchase_orders )

Records each purchase order including supplier, order status, delivery date, etc.

CREATE TABLE `purchase_orders` (
  `order_id` INT NOT NULL AUTO_INCREMENT COMMENT 'Order ID',
  `supplier_id` INT NOT NULL COMMENT 'Supplier ID',
  `order_date` DATETIME NOT NULL COMMENT 'Order Date',
  `delivery_date` DATETIME NOT NULL COMMENT 'Expected Delivery Date',
  `status` VARCHAR(50) DEFAULT 'Pending' COMMENT 'Order Status (Pending, Completed, Cancelled)',
  `total_cost` DOUBLE NOT NULL COMMENT 'Total Order Cost',
  PRIMARY KEY (`order_id`)
) COMMENT='Purchase Orders Table';

3. Purchase Order Details Table ( purchase_order_details )

Records product details for each purchase order including product ID, quantity, price.

CREATE TABLE `purchase_order_details` (
  `order_id` INT NOT NULL COMMENT 'Order ID, references purchase_orders',
  `product_id` INT NOT NULL COMMENT 'Product ID, references products',
  `quantity` INT NOT NULL COMMENT 'Purchase Quantity',
  `price` DOUBLE NOT NULL COMMENT 'Product Purchase Unit Price',
  `total` DOUBLE NOT NULL COMMENT 'Line Total (Quantity * Unit Price)',
  PRIMARY KEY (`order_id`, `product_id`)
) COMMENT='Purchase Order Details Table';

4. Sales Orders Table ( sales_orders )

Records each sales order including customer, order date, delivery date, etc.

CREATE TABLE `sales_orders` (
  `order_id` INT NOT NULL AUTO_INCREMENT COMMENT 'Order ID',
  `customer_id` INT NOT NULL COMMENT 'Customer ID',
  `order_date` DATETIME NOT NULL COMMENT 'Order Date',
  `delivery_date` DATETIME NOT NULL COMMENT 'Expected Delivery Date',
  `status` VARCHAR(50) DEFAULT 'Pending' COMMENT 'Order Status (Pending, Shipped, Completed)',
  `total_amount` DOUBLE NOT NULL COMMENT 'Total Order Amount',
  PRIMARY KEY (`order_id`)
) COMMENT='Sales Orders Table';

5. Sales Order Details Table ( sales_order_details )

Records product information for each sales order including product ID, quantity, price.

CREATE TABLE `sales_order_details` (
  `order_id` INT NOT NULL COMMENT 'Order ID, references sales_orders',
  `product_id` INT NOT NULL COMMENT 'Product ID, references products',
  `quantity` INT NOT NULL COMMENT 'Sales Quantity',
  `price` DOUBLE NOT NULL COMMENT 'Product Sales Unit Price',
  `total` DOUBLE NOT NULL COMMENT 'Line Total (Quantity * Unit Price)',
  PRIMARY KEY (`order_id`, `product_id`)
) COMMENT='Sales Order Details Table';

6. Inventory Transactions Table ( inventory_transactions )

Records every inventory change including product ID, transaction type (Purchase, Sale, Return, etc.).

CREATE TABLE `inventory_transactions` (
  `transaction_id` INT NOT NULL AUTO_INCREMENT COMMENT 'Transaction ID',
  `product_id` INT NOT NULL COMMENT 'Product ID, references products',
  `transaction_type` VARCHAR(50) NOT NULL COMMENT 'Transaction Type (Purchase, Sale, Return, etc.)',
  `quantity` INT NOT NULL COMMENT 'Quantity Change',
  `transaction_date` DATETIME NOT NULL COMMENT 'Transaction Date',
  `order_id` INT DEFAULT NULL COMMENT 'Associated Order ID (nullable)',
  PRIMARY KEY (`transaction_id`)
) COMMENT='Inventory Transactions Table';

Workflow Design and Implementation

4.1 Workflow Design Scenarios

Several scenarios in the inventory system involve sequential execution across multiple functional modules. LogicFlow workflow is well-suited for handling these cross-module operations. Common workflow scenarios include:

1. Procurement Inbound Workflow

Workflow Name : Procurement Inbound Workflow

Description : When a purchase order is confirmed, execute inventory update, procurement recording, and financial update.

Workflow Steps :

Validate Purchase Order : Check if the purchase order is confirmed and in receiving state.

Update Inventory : Increase product stock quantities based on purchase order details.

Record Procurement Inbound : Log inbound information into the inventory_transactions table.

Update Purchase Order Status : Set purchase order status to "Received".

Update Financial Information : Calculate procurement cost and update financial module expenditures.

2. Sales Outbound Workflow

Workflow Name : Sales Outbound Workflow

Description : After confirming a sales order, update inventory and record sales-related financial information.

Workflow Steps :

Validate Sales Order : Confirm the sales order is completed and awaiting shipment.

Update Inventory : Decrease stock quantities based on sales order details.

Record Sales Outbound : Log outbound information into the inventory_transactions table.

Update Sales Order Status : Set sales order status to "Completed".

Update Financial Information : Calculate sales gross profit and update financial module.

Conclusion

By combining the Chengwu low-code platform with LogicFlow workflow , a universal inventory management system can be implemented rapidly. The system uses workflows to achieve sequential execution across multiple functional modules, ensuring data consistency and operational automation. The low-code nature of the platform provides high flexibility and extensibility, allowing enterprises to customize functions and optimize processes according to actual needs.

Integrating core modules such as procurement, sales, inventory, and finance effectively improves enterprise management efficiency, reduces manual operations, and enhances operational transparency and traceability. Leveraging the advantages of the low-code platform, developers can easily respond to changing business requirements and quickly adapt to market and industry developments.