Multi-User Order Management via Segmented Payment Records
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional service architectures do not support cooperative ordering operations among multiple users, limiting order management authority to only the initiator and causing inconveniences in multi-person ordering scenarios.
Innovation Solution
An order management method and system that associates multiple user identifiers with a service device identifier in an order identifier code, allowing each user to manage their payment records and orders through a user historical payment record, enabling multiple users to have authority over order management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a conventional service architecture supports only single user ordering operations, then the system structure remains simple, but it cannot support cooperative ordering operations of multiple users
Solution Approach 1:
The system segments the order management function by creating separate user historical payment records for each user identifier. Each user can independently query and manage their own payment records through the order management portal, while the server maintains a unified order data record that includes all user identifiers. This segmentation allows multi-user support without requiring complete system redesign.
Solution Approach 2:
The order management portal is designed with universal functionality that serves multiple users. The portal can handle ordering operations, payment management, and order queries for any user identifier, making it a multi-functional system that accommodates both single-user and multi-user scenarios without requiring separate interfaces.
2Ease of operation
If only the order initiator has authority to pay and manage the order, then the management process is simple, but other ordering users have no authority causing inconveniences in multi-person ordering scenarios
Solution Approach 1:
The system segments order management authority by creating separate user historical payment records for each user. Each user can independently query and manage their own payment records through the order management portal. The server maintains a unified order data record that includes all user identifiers, allowing each user to have independent access and management capabilities without requiring complex permission systems.
3Adaptability or versatility
If an order can be identified only based on ordering information of the order initiator, then the order identification process is simple, but it cannot be identified based on ordering information of other ordering users
Solution Approach 1:
The system merges multiple user identifiers into a single order data record structure. The order identifier code includes both the service device identifier and multiple user identifiers associated with the service device. This merging allows the system to identify and track orders from any user's perspective while maintaining a unified data structure that consolidates all user information in one record.
Data Source
AI summary
An order management method and system based on multi-person ordering are provided. The method includes: obtaining order payment data corresponding to an order data record, where the order data record is created according to a service device identifier and a user identifier included in an ordering service request received each time; according to a respective user identifier included in an order identifier code of the order data record, adding the order payment data to a user historical payment record corresponding to the respective user identifier, where the order identifier code of the order data record includes the service device identifier and a plurality of user identifiers associated with the service device identifier; sending each user historical payment record to each user terminal such that the user terminal manages the order data record.


