[Abstract] This paper focuses on the design concept of a sales information management system, providing a detailed explanation of its functional applications and the page structure of each application module. It also presents the database table creation method and the relationship diagram between the tables. [Keywords] Topology, Functional Architecture, Table Relationships I. System Overview The topology diagram of the sales information management system is shown in Figure 1: (Figure 1: Sales Information Management System Topology Diagram) As can be seen from the diagram, the system has three types of personnel: Sales Personnel: Submit their own data for a period of time to the system, query historical sales data, enter customer information, query customer information, view sales information, and view team announcements. Customer Service Personnel: Answer customer inquiries, conduct follow-up visits regarding product usage, provide product warranty services, enter this after-sales service information into the system, query historical after-sales service records, and query the product usage of a specific customer. Marketing Manager: Obtain sales reports and after-sales service reports, and make macro-control adjustments to sales strategies based on market conditions. II. Overall Design 1. Functional Allocation (1) Login Module The login module includes: user information input, user information review (2) Customer Information Management Module The customer information management module includes: customer information query, customer information addition, customer information modification, customer information deletion (3) Sales Information Management Module The sales information management module includes: sales information query, sales information addition, sales information modification, sales information deletion (4) After-sales Service Information Management Module The after-sales service information management module includes: after-sales service information query, after-sales service information addition, after-sales service information modification, after-sales service information deletion (5) Market Strategy Announcement Module The market strategy announcement module includes: adding new announcements, displaying announcements, deleting announcements, replying to announcements (6) Statistical Report Management Module The statistical report management module includes: generating sales reports, generating after-sales service reports The functional architecture is shown in Figure 2: (Figure 2 Functional Architecture Diagram of Sales Information Management System) 2. Overall Page Structure Diagram (Figure 3 Overall Page Structure Diagram of Sales Information Management System) III. Database Design 1. Data Requirements Based on the analysis of the system functions, the system needs the following information tables: Customer Information Table (customer): Fields include customer ID, customer name, gender, date of birth, home phone number, mobile phone number, address, zip code, and email. Product List (product): Fields include product ID, product name, specifications, manufacturer, product cost price, and remarks. Staff Table (staff): Fields include staff ID, name, password, and type. Sales Information Table (sell): Fields include sales ID, product ID, customer ID, salesperson ID, sales date, sales price, and sales volume. After-Sales Service Information Table (service): Fields include after-sales service ID, sales ID, senior management ID, service type, details of completion status, and customer satisfaction. Market Strategy Information Announcement Table (policy): Fields include announcement ID, employee ID, email, phone number, QQ number, IP address, announcement time, announcement type (to distinguish between announcement and reply), and the corresponding announcement (or reply) content. 2. Logical Structure Design (1) Create Database Create database SELL in SQL SERVER, as shown in Figure 4: (Figure 4 Database creation diagram of Sales Information Management System) (2) Create Table Create customer information table in database SELL as follows: Customer Information Table: Set the customer ID field as the identifier seed, set its increment to 1, and set it as the key. In this way, when performing data access, you do not need to care about the uniqueness of the data record, because the system will assign a different value to the ID field for each record entered into the database. As shown in Figure 5: (Figure 5 Creation of SELL table in Sales Information Management System) Similarly, you can create staff table, sales information table, after-sales service information table, and market strategy information announcement table, etc. (3) Inter-table Relationship Establishing an inter-table relationship diagram is a good practice. This will eliminate some redundant data, because once the trust relationship between the main table and the subordinate table is determined, the database will automatically check whether the data of a certain constraint field in the subordinate table exists in the main table. If it does not exist, an error will be reported. In this system, the inter-table relationship is as follows: The publisher field STAFFID of the announcement information table POLICY is constrained by the ID field of the staff table STAFF. The STAFFID field in the SRVICE table of the after-sales service information table is constrained by the ID field in the STAFF table of the staff table. The STAFID field in the SELL table of the sales information table is constrained by the ID field in the STAFF table of the staff table. The STAFFID field in the SRVICE table of the after-sales service information table is constrained by the ID field in the SELL table of the sales information table, because each after-sales service should have one sales record for the transformer. The PRODUCTID field in the SELL table of the sales information table is constrained by the ID field in the PRODUCT table of the product list, and the CUSTOMERID field is constrained by the ID field in the CUSTOMER table of the customer information table. The resulting table relationships are shown in Figure 6: (Figure 6: Table Relationship Diagram of the Sales Information Management System Database)