JP2014160400A - Sales management system and sales management server - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a sales management system capable of tallying sales on the basis of a commodity constitution pattern dealt in by each store and a sales management server.SOLUTION: The sales management system includes: POS terminals installed in each store; store controllers each of which tallies pieces of sales information received from each of POS terminals per commodity in each store; and a center server, including an intensive database which stores sales proceeds per commodity name for each store, a commodity constitution table which stores a commodity constitution pattern per group and a group table which stores a group per store, which tallies pieces of sales information received from each of the store controllers on the basis of the commodity constitution pattern of each store.

Description

  Embodiments described herein relate generally to a sales management system and a sales management server.

  In retail businesses such as supermarkets and convenience stores, so-called POS systems are widely introduced. When this POS system is installed in many stores, it often includes a center server that counts sales for each store.

  The center server receives sales information from the store controller installed in each store, and totals the received sales information.

  On the other hand, the combination of products sold by each store is not completely different from store to store, and has a certain pattern. For example, a store that handles food can be broadly classified into stores that handle daily items and stores that do not handle daily items.

  However, in the conventional sales management system, sales cannot be totaled based on such a product configuration pattern.

JP 2000-339546 A JP 2008-71186 A

  Accordingly, there is a need for a sales management system and a sales management server that can aggregate sales based on the product composition pattern handled by each store.

  In order to solve the above-described problem, an embodiment of the present invention includes a POS terminal installed in each store, a store controller that counts sales information received from each POS terminal for each store, and a store-specific product. It has a consolidated database that stores the sales amount for each name, a product configuration table that stores product configuration patterns by group, and a group table that stores product configuration patterns by group, and stores the sales information received from each store controller A sales management system is provided that includes a center server that counts based on patterns.

It is a figure showing the structure of a sales management system. It is a figure which shows the data structure of an aggregation database. It is a figure which shows the data structure of a goods structure table. It is a figure showing the data composition of a group table. It is a figure which shows the data structure of a goods master. It is a figure which shows the example of the total group selection screen displayed on the input / output part of a center server. It is a figure which shows the example of the total result screen displayed on the input / output part of a center server. It is a flowchart which shows the sales totaling operation | movement based on the product structure of a center server.

  Hereinafter, an embodiment of a sales management system and a sales management server will be described in detail with reference to the drawings.

  The sales management system according to the present embodiment stores a POS terminal installed in each store, a store controller that counts sales information received from each POS terminal by product for each store, and a sales amount for each product name by store. A center server that includes an aggregation database, a product configuration table that stores product configuration patterns for each group, and a group table that stores product configuration patterns for each group, and aggregates the sales information received from each store controller based on the product configuration pattern of the store And comprising.

  FIG. 1 is a diagram showing the configuration of the sales management system of the present embodiment. As shown in FIG. 1, the sales management system includes a POS (Point of sales) terminal 21 installed in each store, a store controller 20 that counts sales information of each POS terminal 21 for each store, and receives from each store. And a center server 10 that tabulates the sales information based on the product configuration of the store.

  The center server 10 is installed in the head office 1. The center server 10 includes a control unit 101 including a CPU that performs arithmetic processing, an input / output unit 102 including input / output devices such as a keyboard, a display, and a mouse, and a storage unit 104 including storage devices such as a ROM, a RAM, and a hard disk drive. And a communication unit 103 that performs communication.

  The storage unit 104 includes an aggregate database (hereinafter referred to as a database) 104A that stores sales amounts for each store, each product configuration, and each product code, a product configuration table 104B that stores product configuration patterns for each group, And a group table 104C for storing a group to which the tempo belongs for each store.

  The communication unit 103 is connected to the store controller 20 of each store 2 through a communication line.

  The store controller 20 is installed in each store 2. The store controller 20 includes a control unit 201 including a CPU that performs arithmetic processing, an input / output unit 202 including input / output devices such as a keyboard, a display, and a mouse, and a storage unit 204 including storage devices such as a ROM, a RAM, and a hard disk drive. And a communication unit 203 that performs communication.

  The storage unit 204 includes a product master 204A that stores sales by department, class, and product code.

  The communication unit 203 connects to the center server 10 and the POS terminal 21 via a communication line.

  The POS terminal 21 counts the sales amount for each transaction every time the subtotal button is pressed. When a closing operation instruction is input, the POS terminal 21 totals the sales amount for that day by department, class, and product code, and transmits the sum to the store controller 20.

  The store controller 20 totals the sales amount received from each POS terminal by department, class, and product code, and transmits it to the center server 10.

  The center server 10 stores the sales amount received from each store controller 20 in the aggregation DB 104A by store, product configuration, and product code.

  FIG. 2 is a diagram illustrating a data configuration of the aggregation DB 104A. As shown in FIG. 2, the aggregation DB 104 </ b> A includes a “store name” that is a store name, a “product configuration” that is a classification indicating the product configuration of each store, a product code that is uniquely assigned to each product, and a sales amount. “Sales” indicating “” is stored.

  The product configuration can include, for example, a “department” of the highest category of the product and a “class” that is a subordinate concept of the department. That is, the product configuration includes a “class” that is a concept lower than the department that is the highest concept of the product classification and is a concept higher than the product code that is the lowest concept of the product classification.

  In the example of each data, the store name is “Ohi store”, the department is “food”, the class is “daily delivery”, the product name is “M milk”, the product code is “123456”, and the sales is “6000”.

  FIG. 3 is a diagram illustrating a data configuration of the product configuration table 104B. As shown in FIG. 3, the product configuration table 104B stores “group”, “department”, and “class” that are uniquely assigned to each product configuration pattern.

  An example of each data is a pattern of product composition such as “A” for the group, “food” for the department, “daily product” for the class, and “canned food”.

  FIG. 4 is a diagram illustrating a data configuration of the group table 104C. As illustrated in FIG. 4, the group table 104 </ b> C stores “store name” and “group”.

  In the example of each data, the store name is “Daijin” and the group is “A”.

  FIG. 5 is a diagram showing a data configuration of the product master 204A. As shown in FIG. 5, the product master 204A stores “department”, “class”, “product name”, and “sales” for each store.

  In the example of each data, the department is “food”, the class is “daily delivery”, the product name is “M milk”, and the sales is “6000”.

  FIG. 6 is a diagram illustrating an example of a total group selection screen displayed on the input / output unit 102 of the center server 10. As shown in FIG. 6, the center server 10 displays a group button 601 for selecting designation of a group and a selection means 602 for selecting a group to be aggregated on the aggregation group selection screen.

  FIG. 7 is a diagram illustrating an example of a summary result screen displayed on the input / output unit 102 of the center server 10. As shown in FIG. 7, the center server 10 displays a store selection menu 701 for selecting a store and a count result 702 based on the product configuration on the count result screen.

  FIG. 8 is a flowchart showing the sales counting operation based on the product configuration of the center server 10. As shown in FIG. 8, in step 801, the center server 10 inputs a store name after designating a group.

  In step 802, the center server 10 searches the group table 104C based on the input store name, and reads the group name to which the store belongs.

  In step 803, the center server 10 searches the product configuration table 104B based on the read group name, and reads the product configuration pattern of the group.

  In step 804, the center server 10 searches the aggregation DB 104A based on the input store name, and totals the sales amount based on the read product configuration.

  In step 805, the center server 10 outputs the aggregation result to the input / output unit 102.

  As described above, the sales management system according to the present embodiment includes the POS terminal 21 installed in each store, the store controller 20 that tabulates the sales information received from each POS terminal 21 by product for each store, The sales information received from each store controller 20 is provided with an aggregation DB 104A for storing the sales amount for each product name, a product configuration table 104B for storing product configuration patterns for each group, and a group table 104C for storing product configuration patterns for each group. And a center server 10 that counts based on the product configuration of the store.

  Therefore, there is an effect that sales can be totaled based on the product composition pattern handled by each store.

  Although several embodiments have been described, these embodiments have been presented by way of example and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are also included in the invention described in the claims and the equivalents thereof.

10: Center server 20: Store controller 21: POS terminal 104A: Aggregation database 104B: Product configuration table 104C: Group table

Claims (5)

POS terminals installed at each store,
A store controller that counts the sales information received from each POS terminal by product for each store;
The sales information received from each store controller, comprising an aggregate database that stores the sales amount for each product name by store, a product configuration table that stores product configuration patterns by group, and a group table that stores product configuration patterns by group A center server that counts based on the product composition pattern of the store;
A sales management system with The product composition pattern is:
The sales management according to claim 1, wherein the sales management pattern is a product composition pattern including at least a classification concept that is a concept lower than a department that is a highest concept of product classification and is a higher concept than a product code that is a lowest concept of product classification. system. An aggregate database that stores the sales amount for each product name by store;
A product composition table for storing product composition patterns by group;
A group table that stores product composition patterns by group;
A control unit that is installed in each store and totals the sales information received from each store controller that counts the sales information received from the POS terminal for each store based on the product configuration pattern of the store;
A sales management server comprising: The product composition pattern is:
The sales management according to claim 3, wherein the sales management pattern is a product composition pattern including at least a classification concept which is a concept lower than a department which is the highest concept of product classification and is higher than a product code which is the lowest concept of product classification. server. The controller is
The sales management server according to claim 4, wherein, for each store, the sales amount totaled based on the product configuration pattern of the store is output to the input / output unit.

Images