Decision system

Abstract

To provide a decision-making system that allows for more optimal product sales and improves customer and employee satisfaction. [Solution] In a decision system including a store system S and a headquarters system H for each store, the headquarters system H includes a decision server 10 which comprises: a planned labor cost calculation unit that calculates the planned labor costs for a store for a predetermined period; a planned price determination unit that determines the planned price of goods for a store for a predetermined period using the planned labor costs for a predetermined period calculated by the planned labor cost calculation unit; a benefit granting determination unit (planned coupon determination unit) that determines the granting of benefits for a store for a predetermined period; and a benefit granting determination unit (planned benefit determination unit) that determines the granting of allowances to employees who come to work at the store for a predetermined period.

Description

Technical Field

[0001] The present invention relates to a decision-making system.

Background Art

[0002] A system for determining a product display method based on product sales prediction is known (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0008] Figure 1 is an explanatory diagram illustrating the configuration of the store system S and the headquarters system H. The store system S and headquarters system H are applicable to various types of businesses (supermarkets, convenience stores, drugstores, home centers, consumer electronics retailers, etc.). As indicated by the arrows in Figure 1, the store system S (some or all of the devices within the store system S) and the headquarters system H (some or all of the devices within the headquarters system H) can communicate with each other, for example, via the internet. Although not shown in Figure 1, a store system S exists for each store.

[0009] (Store System S) The store system S is the store-side system. The store system S includes a registration and settlement device 20, a registration device 21, a settlement device 22, a transaction status management device 23 (not shown), and a store controller 24 (not shown). The devices within the store system S can communicate with each other via LAN (which may be wired or wireless).

[0010] The registration and payment device 20 performs a registration process to register products and a payment process to settle the price of the products registered through the registration process. The registration and payment device 20 may be a device that registers products based on the actions of a store clerk and settles the payment based on the actions of a store clerk. The registration and payment device 20 may be a device that registers products based on the actions of a customer and settles the payment based on the actions of a customer (a fully self-service device). The registration and payment device 20 may be a device that registers products based on the actions of a store clerk and settles the payment based on the actions of a customer (a face-to-face semi-self-service device). The registration and payment device 20 may be a device that has multiple operating modes (for example, a fully self-service mode, a face-to-face semi-self-service mode). The registration and payment device 20 can obtain customer identification information from a medium (such as a membership card) brought by the customer.

[0011] The registration device 21 registers products based on the store clerk's operation. The payment device 22 processes payments based on the customer's operation. The registration device 21 transmits the product registration information to the payment device 22 (either directly or via the store controller 24). The payment device 22 receives the registration information transmitted by the registration device 21 and processes the payment. In other words, the registration device 21 and the payment device 22 constitute a semi-self-service system. The registration device 21 and the payment device 22 can obtain customer identification information from a medium brought by the customer.

[0012] The transaction status management device 23 (e.g., a personal computer) is used by store employees to manage the devices installed in the store (monitoring and controlling processing status, operating status, etc.). The store controller 24 (e.g., a server) sends and receives various information.

[0013] The store system S may also include a mobile terminal 30 (not shown) that registers products based on customer operations at the sales floor, and a payment device 25 (not shown) that settles the payment for the products registered by the mobile terminal 30. The mobile terminal 30 may be the customer's smartphone or a smartphone provided by the store. The mobile terminal 30 may be integrated with a shopping cart. The payment device 25 settles payments based on customer operations, similar to the payment device 22. The payment device 25 can obtain customer identification information from a medium brought by the customer. If the mobile terminal 30 is the customer's smartphone, the customer can be identified by using the mobile terminal 30, so the payment device 25 can obtain customer identification information without using a medium. For example, when the mobile terminal 30 initiates shopping using a dedicated registration app, customer identification information (for example, customer identification information associated with the mobile terminal 30 when downloading the dedicated app) is sent to the transaction server 13A, and at the time of settlement, it is sent from the transaction server 13A to the payment device 25. Furthermore, in the case of a web-based system, when accessing the transaction server 13A, customer identification information (for example, customer identification information generated when the customer registered in advance and stored as a cookie) is sent to the transaction server 13A, and at the time of settlement, it is sent from the transaction server 13A to the settlement device 25. Therefore, if the mobile terminal 30 is the customer's smartphone, the settlement device 25 does not need to obtain customer identification information from the medium brought by the customer.

[0014] (Headquarters System H) Headquarters System H is the headquarters system. Headquarters System H includes a decision server 10, a demand forecasting server 11, a work shift management server 12, a transaction server 13A, a history management server 13B, a product management server 13C, a customer management server 13D, a special sale management server 13E, a coupon management server 13F, an employee management server 13G, and a allowance management server 13H. The devices within Headquarters System H can communicate with each other via LAN (which can be wired or wireless).

[0015] (Transaction Server 13A) The transaction server 13A manages the transactions of the business day. Specifically, the transaction server 13A stores the transaction file of the business day. The transaction file is a file that stores (saves) transaction information. The transaction information includes, as data items, for example, transaction identification information, transaction date and time, store identification information, device identification information, product registration information, and settlement information. The transaction information of a transaction in which a customer is identified further includes customer identification information as a data item.

[0016] The transaction server 13A receives transaction information from the registration settlement device 20 or the settlement device 22 (or receives transaction information from the store controller 24) and stores it in the transaction file. For example, after the completion of a transaction (after the completion of the settlement process), the registration settlement device 20 or the settlement device 22 transmits the transaction information to the transaction server 13A (directly or via the store controller 24), and the transaction server 13A that has received the transaction information stores the received transaction information in the transaction file. When the registration settlement device 20 or the settlement device 22 has acquired customer identification information, it transmits the transaction information including the customer identification information to the transaction server 13A, and when it has not acquired customer identification information, it transmits the transaction information not including the customer identification information to the transaction server 13A.

[0017] (History management server 13B) The history management server 13B manages the history of transactions. For example, the history management server 13B receives the transaction information of the business day from the transaction server 13A after the end of business and stores (accumulates) it. Also, the history management server 13B may analyze (classify and aggregate) the transaction information by customer attribute (or by customer) and store the analysis information related to the customer. Further, the history management server 13B may analyze (classify and aggregate) the transaction information by product classification (or by product) and store the analysis information related to the product.

[0018] (Product management server 13C) The product management server 13C manages products. Specifically, the product management server 13C stores the product master (product file). The product master is a file that stores product information. Product information includes data items such as product identification information (e.g., JAN code), product name, and price (selling price). Product information may also include data items such as cost (purchase price).

[0019] (Customer management server 13D) The customer management server 13D manages customers (registered customers (members)). Specifically, the customer management server 13D stores the customer master (customer file). The customer master is a file that stores customer information. Customer information includes data items such as customer identification information, registered name (name, etc.), date of birth, gender, contact information (email address, telephone number, etc.), store identification information of the registered store (main store), and registration date.

[0020] Furthermore, the customer management server 13D manages customer points (rewards). Specifically, the customer management server 13D stores a points file. The points file is a file that stores point information. The point information includes data items such as customer identification information and the current number of points (number of points available). The customer management server 13D updates the number of points stored in the points file. For example, the customer management server 13D accesses the history management server 13B (referencing the transaction file added for the relevant business day) and, for each customer, adds the number of points awarded (points according to the purchase amount; for example, 1 point for every 200 yen) to the current number of points and subtracts the number of points used (paid) from the current number of points. Alternatively, the customer management server 13D may access the transaction server 13A and, for each customer, add the number of points awarded to the current number of points and subtract the number of points used from the current number of points.

[0021] (Special Sale Management Server 13E) The special sale management server 13E manages special sales. Specifically, the special sale management server 13E stores special sale files. Special sale files are files that store special sale information. Special sale information includes data items such as the date and time of the special sale, product identification information (product identification information for the products included in the special sale), and the special sale price.

[0022] For products whose product identification information is stored in the special sale file as a special sale item for the relevant date and time, the special sale price in the special sale file is applied. For products whose product identification information is not stored in the special sale file as a special sale item for the relevant date and time, the price in the product master is applied. In other words, the registration and settlement device 20 queries the product management server 13C and the special sale management server 13E for a given product. If the registration and settlement device 20 obtains the price of the product from the product management server 13C and the special sale price of the product from the special sale management server 13E as a response, it registers the product at the special sale price obtained from the special sale management server 13E. If the registration and settlement device 20 obtains the price of the product from the product management server 13C but does not obtain the special sale price of the product from the special sale management server 13E as a response, it registers the product at the price obtained from the product management server 13C.

[0023] Furthermore, in addition to the sale price, the special sale information may also store discount information (for example, 10% off, 20 yen off, etc.) as a data item.

[0024] (Variable price management server 13E) As will be explained in more detail later, in addition to cases where products are sold at a price lower than the standard price (the price stored in the product master), there are also cases where products are sold at a price higher than the standard price (where a price higher than the standard price is set as the planned price). In this case, the data item "Special Sale Price" in the special sale information will store a price higher than the standard price. Alternatively, the data item "Value Discount Information" in the special sale information will store information such as a 10% increase or a 20 yen increase. Considering these points, the special sale management server 13E may be referred to as the variable price management server 13E, the special sale file as the variable price file, the special sale information as the variable price information, the data item "Special Sale Price" in the special sale information as the "Price After Change", and the data item "Value Discount Information" in the special sale information as the "Variable Price Information".

[0025] (Coupon management server 13F) The coupon management server 13F manages coupons. Specifically, the coupon management server 13F stores coupon files. Coupon files are files that store coupon information. Coupon information includes data items such as coupon identification information, customer identification information (customer identification information of customers to whom the coupon is to be issued; left blank if there are no conditions), coupon issuance period, coupon issuance date and time (left blank if not issued), coupon validity period, product identification information (product identification information of the product to which the coupon applies), coupon details (information indicating the content of the coupon, such as half price / free gift for purchases totaling 1000 yen or more; the condition of purchase totaling 1000 yen or more is not required), and status classification (not issued "0", issued but unused "1", used "2", etc.).

[0026] (Employee management server 13G) The employee management server 13G manages employees (staff). Specifically, the employee management server 13G stores the employee master (employee file). The employee master is a file that stores employee information. The employee information includes data items such as employee identification information, name, contact information, employment type (e.g., full-time employee, part-time employee, temporary employee, etc.), and wage information (e.g., for full-time employees, salary amount and bonus amount, hourly wage equivalent of salary amount and bonus amount, and for part-time / temporary employees, information showing the hourly wage).

[0027] (Allowance management server 13H) The allowance management server 13H manages allowances for employees. Specifically, the allowance management server 13H stores allowance files. Allowance files are files that store allowance information. Allowance information includes data items such as the allowance grant date, employee identification information (employee identification information of employees eligible for allowances), allowance details (information indicating the amount of the allowance to be granted, such as a special daily allowance of 300 yen), and status classification (not granted "0", granted "1", etc.). Allowances stored in the allowance information may be granted the following day or on a predetermined date (for example, they may be transferred to each employee's bank account the following day, or transferred together with each employee's salary on payday). (You could also have the money transferred to each employee's bank account.)

[0028] (Demand forecasting server 11) The demand forecasting server 11 uses transaction information stored in the history management server 13B to forecast demand (e.g., number of visitors, sales) for a predetermined period in the future (in this embodiment, one business day one week from now). The demand forecasting server 11 may further use other information (e.g., weather information, event information, new product information, etc.) to forecast demand for a predetermined period in the future.

[0029] (Work shift management server 12) The work shift management server 12 manages work shifts. Specifically, the work shift management server 12 stores work shift files (work schedule files). A work shift file is a file that stores work shift information (work schedule information). Work shift information includes data items such as date and time, store identification information, employee identification information (employee identification information of employees scheduled to work), and change details (date and time of change if the shift is changed, employee identification information of the employee after the change). Note that working hours (time slot, length) vary depending on the employee. In other words, not all employees work during the same time slot (for example, from 9 am to 5 pm).

[0030] (Decision Server 10) The decision server 10 determines the price of the product. For example, the decision server 10 determines the planned price (described later) of the product for a predetermined period (one business day one week later). Details will be provided later.

[0031] Figure 2 is an explanatory diagram illustrating some of the functions of the headquarters system H. As shown in Figure 2, the headquarters system H includes a transaction information storage unit 100, a demand forecasting unit 101, a forecast result storage unit 102, a work shift determination unit 103, a work shift information storage unit 104, an employee information storage unit 105, a labor cost calculation unit 106, a labor cost storage unit 108, a planned price determination unit 110A, a special sale information storage unit 111, a work shift change unit 200, a planned price adjustment unit (adjusted price determination unit) 203A, an evaluation unit 300, a product information storage unit 301, a reward unit 302, a coupon storage unit 306, a point storage unit 307, and a allowance storage unit 308. The labor cost calculation unit 106 includes a planned labor cost calculation unit 107 and a modified labor cost calculation unit 201. The personnel cost storage unit 108 includes a planned personnel cost storage unit 109 and a revised personnel cost storage unit 202. The reward unit 302 includes a coupon reward unit (reward coupon determination unit) 303, a point reward unit (reward point determination unit) 304, and an allowance reward unit (reward allowance determination unit) 305.

[0032] (Headquarters Terminal 14) There exists a terminal (headquarters terminal 14; not shown) that can communicate with one or more servers within the headquarters system H (for example, a demand forecasting server 11, a work shift management server 12, etc.). There may be two or more headquarters terminals 14. The headquarters terminal 14 may or may not be part of the headquarters system H.

[0033] (Relationship with various servers) The transaction information storage unit 100 is a function of the history management server 13B. In other words, the storage unit of the history management server 13B constitutes (realizes) the transaction information storage unit 100.

[0034] The demand forecasting unit 101 and the forecast result storage unit 102 are functions of the demand forecasting server 11. In other words, the processing unit (CPU) of the demand forecasting server 11 constitutes the demand forecasting unit 101. Also, the storage unit of the demand forecasting server 11 constitutes the forecast result storage unit 102.

[0035] The work shift determination unit 103, the work shift information storage unit 104, and the work shift change unit 200 are functions of the work shift management server 12. In other words, the processing unit (CPU) of the work shift management server 12 constitutes the work shift determination unit 103 and the work shift change unit 200. Also, the storage unit of the work shift management server 12 constitutes the work shift information storage unit 104.

[0036] The employee information storage unit 105 is a function of the employee management server 13G. In other words, the storage unit of the employee management server 13G constitutes the employee information storage unit 105.

[0037] The personnel cost calculation unit 106 (planned personnel cost calculation unit 107, revised personnel cost calculation unit 201), personnel cost storage unit 108 (planned personnel cost storage unit 109, revised personnel cost storage unit 202), planned price determination unit 110A, planned price adjustment unit 203A, evaluation unit 300, and rebate unit 302 (coupon rebate unit 303, point rebate unit 304, allowance rebate unit 305) are functions of the decision server 10. In other words, the processing unit (CPU) of the decision server 10 constitutes the personnel cost calculation unit 106, planned price determination unit 110A, planned price adjustment unit 203A, evaluation unit 300, and rebate unit 302. Also, the storage unit of the decision server 10 constitutes the personnel cost storage unit 108.

[0038] The special sale information storage unit 111 is a function of the special sale management server 13E. In other words, the storage unit of the special sale management server 13E constitutes the special sale information storage unit 111.

[0039] The product information storage unit 301 is a function of the product management server 13C. In other words, the storage unit of the product management server 13C constitutes the product information storage unit 301.

[0040] The coupon storage unit 306 is a function of the coupon management server 13F. In other words, the storage unit of the coupon management server 13F constitutes the coupon storage unit 306.

[0041] The point storage unit 307 is a function of the customer management server 13D. In other words, the storage unit of the customer management server 13D constitutes the point storage unit 307.

[0042] The allowance storage unit 308 is a function of the allowance management server 13H. In other words, the storage unit of the allowance management server 13H constitutes the allowance storage unit 308.

[0043] (Explanation of each function) The following explanation describes any one store, but the same principles apply to other stores as well. The transaction information storage unit 100 stores transaction information for each past business day. The demand forecasting unit 101 uses the transaction information stored in the transaction information storage unit 100 (transaction information for many past business days) to forecast demand (e.g., number of visitors, sales) for a predetermined period in the future (one business day one week from now). The demand forecasting unit 101 may further use other information (e.g., weather information, event information, new product information, etc.) to forecast demand for a predetermined period in the future. The forecast result storage unit 102 stores the forecast results (e.g., forecast number of visitors, forecast sales) predicted by the demand forecasting unit 101.

[0044] The work shift determination unit 103 determines the work shifts. Specifically, the work shift determination unit 103 determines the work shifts in accordance with the timing of the demand forecast by the demand forecasting unit 101. In other words, if the demand forecasting unit 101 forecasts the demand for a business day N days in the future, the work shift determination unit 103 determines the work shifts for that business day N days in the future (i.e., it determines the work shifts N days in advance for each business day). In this example, since the demand forecasting unit 101 forecasts the demand for a business day one week in the future, the work shift determination unit 103 determines the work shifts for that business day one week in the future (i.e., it determines the work shifts one week in advance for each business day). Note that the timing of the demand forecasting by the demand forecasting unit 101 and the timing of the work shift determination by the work shift determination unit 103 do not have to come first, and there may be a small gap between the two timings.

[0045] The work shift determination unit 103 may determine work shifts based on information entered via the screen. The work shift determination unit 103 may accept input of work schedules (scheduled workers, scheduled work hours) from one month in advance for each business day, and finalize the work schedule (i.e., determine the work shift) one week in advance. For example, the headquarters terminal 14 (not shown) displays a work shift screen (work schedule reception screen) that accepts input operations (schedule input operations) for work schedules for each time slot on each business day from one month to one week in advance. The headquarters terminal 14 accepts work schedules for each time slot on each business day from one month to one week in advance as appropriate via the work schedule reception screen. The work shift determination unit 103 may finalize the work schedule for the business day one week in advance based on the information received via the work schedule reception screen. In addition, each employee may operate the headquarters terminal 14 (work schedule reception screen) according to their own wishes (schedules), for example. Additionally, the administrator may take into consideration the wishes of each employee and operate the headquarters terminal 14 (work schedule registration screen).

[0046] Furthermore, as indicated by the dashed arrow Y, the work shift determination unit 103 may determine the work shifts while taking into account the forecast results from the demand forecasting unit 101. In other words, the work shifts may be determined in a way that balances, to some extent, with the forecast results of the demand forecast.

[0047] As an example, the work shift determination unit 103 increases the number of employees working from the predetermined standard number (increasing the number of employees from the standard number according to the level of the predicted sales) if the predicted sales are higher than a predetermined standard sales by a predetermined amount (predicted sales > standard sales + predetermined amount), decreases the number of employees working from the standard number (decreasing the number of employees from the standard number according to the level of the predicted sales) if the predicted sales are lower than a predetermined amount (predicted sales < standard sales - predetermined amount), and maintains the number of employees working at the standard number if the difference between the predicted sales and the standard sales is within a predetermined amount. The work shift determination unit 103 may also determine whether to increase / decrease / maintain the number of employees based on the percentage increase / decrease of the predicted sales relative to the standard sales (increase / decrease rate) instead of the difference (amount) between the predicted sales and the standard sales.

[0048] For example, the work shift determination unit 103 increases the number of employees on duty from the predetermined standard number (increases the number of employees from the standard number in proportion to the increase in the number of predicted visitors) if the predicted number of visitors is higher than a predetermined standard number of visitors by a predetermined number (predicted number of visitors > standard number of visitors + predetermined number), decreases the number of employees on duty from the standard number (decreases the number of employees from the standard number in proportion to the decrease in the number of predicted visitors) if the predicted number of visitors is lower than a predetermined number of visitors by a predetermined number (predicted number of visitors < standard sales - predetermined number), and maintains the number of employees on duty at the standard number if the difference between the predicted number of visitors and the standard number of visitors is within a predetermined number. The work shift determination unit 103 may also determine whether to increase / decrease / maintain the number of employees based on the percentage increase or decrease of the predicted number of visitors relative to the standard number of visitors (increase / decrease rate) instead of the difference (number of people) between the predicted number of visitors and the standard number of visitors.

[0049] The work shift information storage unit 104 stores work shift information. Specifically, the work shift information storage unit 104 stores work shift information that shows the work shift determined by the work shift determination unit 103. The work shift information storage unit 104 also stores the changes to the work shift made by the work shift change unit 200 in the work shift information. A work shift may be changed more than once, but the work shift information storage unit 104 stores at least the most recent change (it may store the details of each change as a history, or it may overwrite the previous change with the current change).

[0050] The work shift change unit 200 modifies the work shift determined by the work shift determination unit 103 (work shift information stored in the work shift information storage unit 104). Specifically, the work shift change unit 200 stores the changes to the work shift determined by the work shift determination unit 103 in the work shift information storage unit 104.

[0051] The work shift change unit 200 may change work shifts based on information entered via the screen. The work shift change unit 200 may accept input of changes to work schedules (scheduled workers, scheduled working hours) for each business day from one week in advance to the day before, and make changes as needed. For example, the headquarters terminal 14 (not shown) displays a work shift screen (work schedule change acceptance screen) that accepts changes to work schedules (schedule change operations) for each time slot on each business day from one week in advance to the day before. The headquarters terminal 14 accepts changes to work schedules for each time slot on each business day from one week in advance to the day before as needed via the work schedule change acceptance screen. The work shift change unit 200 may change work shifts as needed based on the information received via the work schedule change acceptance screen. In addition, each employee may operate the headquarters terminal 14 (work schedule change acceptance screen) according to their own wishes (schedules), for example. Alternatively, an administrator may operate the headquarters terminal 14 (work schedule change acceptance screen) in response to an employee's application (request), etc.

[0052] The employee information storage unit 105 stores employee information. The planned personnel cost calculation unit 107 calculates planned personnel costs. Specifically, the planned personnel cost calculation unit 107 calculates planned personnel costs in accordance with the timing of the work shift determination by the work shift determination unit 103. In other words, if the work shift determination unit 103 determines the work shift for a business day N days in the future, the planned personnel cost calculation unit 107 calculates the planned personnel costs for that business day N days in the future (i.e., it calculates the planned personnel costs N days in advance for each business day). In this example, since the work shift determination unit 103 determines the work shift for a business day one week in the future, the planned personnel cost calculation unit 107 calculates the planned personnel costs for that business day one week in the future (i.e., it calculates the planned personnel costs one week in advance for each business day). Note that there may be some time between the timing of the work shift determination by the work shift determination unit 103 and the timing of the planned personnel cost calculation by the planned personnel cost calculation unit 107.

[0053] Specifically, the planned labor cost calculation unit 107 uses the work shift information (work shift information determined by the work shift determination unit 103) stored in the work shift information storage unit 104 and the employee information (wage information) stored in the employee information storage unit 105 to calculate the planned labor cost (labor cost for a business day one week later). For example, the planned labor cost calculation unit 107 may calculate the labor cost for each time slot (by summing the hourly wage amounts (hourly wage equivalent amounts) of all scheduled workers for each time slot), and then sum up the labor costs for each time slot to calculate the planned labor cost. The planned labor cost storage unit 109 stores the planned labor cost calculated by the planned labor cost calculation unit 107.

[0054] The revised personnel cost calculation unit 201 calculates the revised personnel cost (personnel cost after the work shift change) when the details of the work shift change are stored in the work shift information storage unit 104 (i.e., when the work shift change unit 200 has made a change to the work shift). Specifically, the revised personnel cost calculation unit 201 calculates the revised personnel cost after the end of the acceptance period for work shift changes by the work shift change unit 200 (1 week prior to the day before) (for example, before the start of business on the business day).

[0055] Specifically, the revised personnel cost calculation unit 201 calculates the revised personnel cost using the work shift information stored in the work shift information storage unit 104 (work shift information determined by the work shift determination unit 103, and the changes made by the work shift change unit 200 (latest changes)) and the employee information (wage information) stored in the employee information storage unit 105. For example, the revised personnel cost calculation unit 201 may calculate the personnel cost for each time slot, similar to the planned personnel cost calculation unit 107, and then sum up the personnel costs for each time slot to calculate the revised personnel cost. The revised personnel cost storage unit 202 stores the revised personnel cost calculated by the revised personnel cost calculation unit 201.

[0056] The estimated price determination unit 110A determines the estimated price. Specifically, the estimated price determination unit 110A determines the estimated price in accordance with the timing of the calculation of estimated labor costs by the estimated labor cost calculation unit 107. In other words, if the estimated labor cost calculation unit 107 calculates the estimated labor costs for a business day N days from now, the estimated price determination unit 110A determines the estimated price for that business day N days from now (i.e., it determines the estimated price N days in advance for each business day). In this example, since the estimated labor cost calculation unit 107 calculates the estimated labor costs for a business day one week from now, the estimated price determination unit 110A determines the estimated price for that business day one week from now (i.e., it calculates the estimated price one week in advance for each business day). Note that there may be some time between the timing of the calculation of estimated labor costs by the estimated labor cost calculation unit 107 and the timing of the determination of the estimated price by the estimated price determination unit 110A.

[0057] Specifically, the estimated price determination unit 110A uses the forecast results stored in the forecast result storage unit 102 and the estimated labor costs stored in the estimated labor cost storage unit 109 to determine the estimated price (estimated price for a business day one week from now).

[0058] The planned price determination unit 110A determines a price higher than the standard price as the planned price if the planned labor costs are high relative to the projected sales (or projected number of visitors) and the balance between projected sales (or projected number of visitors) and projected labor costs is poor. The planned price determination unit 110A determines a price lower than the standard price as the planned price if the planned labor costs are low relative to the projected sales (or projected number of visitors) and the balance between projected sales (or projected number of visitors) and projected labor costs is poor. The planned price determination unit 110A determines the standard price as the planned price if the balance between projected sales (or projected number of visitors) and projected labor costs is good.

[0059] The difference between the standard price and the planned price is intended to bridge the gap between standard labor costs and planned labor costs (reduce the discrepancy). The planned price may be lower or higher than the standard price, but it is a special sale price relative to the standard price.

[0060] A table (or formula) showing the relationship between sales (or number of visitors) and labor costs is prepared (for example, stored in the memory of the decision server 10). When a sales (or number of visitors) is input to the above table (or formula), the corresponding labor cost (standard labor cost) is output. Also, when a labor cost is input to the above table (or formula), the corresponding sales (standard sales) or number of visitors (standard number of visitors) is output. The planned price determination unit 110A may determine the planned price using the above table (or formula).

[0061] For example, the estimated price determination unit 110A may determine the estimated price using the following procedure (1)(2).

[0062] (1) The planned price determination unit 110A uses the above table (or formula) to identify (obtain) the standard labor costs corresponding to the projected sales (or projected number of customers). (2) If the estimated labor costs are higher than the standard labor costs by a predetermined amount (estimated labor costs > standard labor costs + predetermined amount), the estimated price determination unit 110A determines a price higher than the standard price as the estimated price (the higher the estimated labor costs, the higher the estimated price may be determined). If the estimated labor costs are lower than the standard labor costs by a predetermined amount (forecasted labor costs < base labor costs - predetermined amount), the estimated price determination unit 110A determines a price lower than the standard price as the estimated price (the lower the estimated labor costs, the lower the estimated price may be determined). If the difference between the estimated labor costs and the standard labor costs is within a predetermined amount, the estimated price determination unit 110A determines the standard price as the estimated price.

[0063] Furthermore, the estimated price determination unit 110A may determine a price higher than the standard price as the estimated price when the estimated labor costs are higher than the standard labor costs (estimated labor costs > standard labor costs), and may determine a price lower than the standard price as the estimated price when the estimated labor costs are lower than the standard labor costs (forecasted labor costs < base labor costs).

[0064] The estimated price determination unit 110A may determine the estimated price based on the percentage increase or decrease of the estimated labor costs relative to the standard labor costs, instead of the difference (amount) between the estimated labor costs and the standard labor costs.

[0065] The products for which the estimated price determination unit 110A determines the estimated price may be predetermined products (one or more predetermined products) or all products. If predetermined products are selected as the target products, the standard price will remain for products other than the target products (products other than the one or more predetermined products).

[0066] The difference between the standard price and the planned price is intended to cover the difference between standard labor costs and planned labor costs. If the number of products covered is small, the burden of covering the difference will be concentrated, resulting in a larger impact on each product (and a larger fluctuation range in the planned price relative to the standard price). Conversely, if the number of products covered is large, the burden of covering the difference will be distributed, resulting in a smaller impact on each product (and a smaller fluctuation range in the planned price relative to the standard price).

[0067] The special sale information storage unit 111 stores special sale information (variable price information). Specifically, the special sale information storage unit 111 stores the information (target product, planned price) determined by the planned price determination unit 110A as special sale information (variable price information).

[0068] The planned price adjustment unit 203A adjusts the planned price when the changed labor costs are stored in the changed labor cost storage unit 202 (i.e., when there has been a change in the work shift by the work shift change unit 200). Specifically, the planned price adjustment unit 203A adjusts the planned price in accordance with the timing of the calculation of the changed labor costs by the changed labor cost calculation unit 201. In other words, the planned price adjustment unit 203A adjusts the planned price after the end of the acceptance period for work shift changes by the work shift change unit 200 (1 week to the day before) (for example, before the start of business on a business day).

[0069] Specifically, the planned price adjustment unit 203A determines the adjusted price (adjusted planned price) using the forecast results stored in the forecast result storage unit 102 and the revised labor costs stored in the revised labor cost storage unit 202.

[0070] The method by which the planned price adjustment unit 203A determines the adjusted price based on the forecast results and the revised labor costs is the same as the method by which the planned price determination unit 110A determines the planned price based on the forecast results and the planned labor costs. In other words, a table (or formula) showing the relationship between sales (or number of customers) and labor costs may be prepared, and the planned price adjustment unit 203A may use this table (or formula) to determine the adjusted price.

[0071] The adjusted price determined by the planned price adjustment unit 203A is stored in the special sale information storage unit 111. In other words, the planned price (the planned price determined by the planned price determination unit 110A) stored in the special sale information storage unit 111 is updated by the adjusted price (the adjusted price determined by the planned price adjustment unit 203A). Note that the larger the difference between the planned labor costs and the changed labor costs, the larger the difference between the planned price and the adjusted price. Therefore, if the difference between the planned labor costs and the changed labor costs is small, the adjusted price may be the same as the planned price. If the adjusted price is the same as the planned price, the planned price stored in the special sale information storage unit 111 is maintained (that is, if labor costs do not change much even if there is a change in work shifts, the planned price is maintained).

[0072] In other words, if there is a change in the work shift, the labor cost calculation unit 201 recalculates the labor costs, and the planned price adjustment unit 203A automatically changes the planned price according to the change in labor costs. It is also possible to allow employees (staff) to confirm that the planned price has changed. Furthermore, while the planned price change is performed automatically without employee intervention, it may also be performed based on an employee's confirmation action (for example, an action confirming the change).

[0073] The evaluation unit 300 evaluates the balance between actual sales (or actual number of customers) and actual labor costs after the end of business hours (for example, the day after a business day).

[0074] Specifically, the evaluation unit 300 uses the transaction information stored in the transaction information storage unit 100 (transaction information for the business day being evaluated) and the actual labor costs stored in the labor cost storage unit 108 (i.e., if the changed labor costs for the business day being evaluated are stored in the changed labor cost storage unit 202 (i.e., if there has been a change in the work shift), the changed labor costs; and if the changed labor costs for the business day being evaluated are not stored in the changed labor cost storage unit 202 (i.e., if there has been no change in the work shift), the planned labor costs stored in the planned labor cost storage unit 109) to evaluate the balance between actual sales (or actual number of customers) and actual labor costs.

[0075] A table (or formula) showing the relationship between sales (or number of customers) and labor costs may be prepared, and the evaluation unit 300 may use the table (or formula) to evaluate the balance between actual sales (or actual number of customers) and actual labor costs. Specifically, the evaluation unit 300 may evaluate the balance between actual sales (or actual number of customers) and actual labor costs using the following procedure (1) and (2).

[0076] (1) The evaluation unit 300 uses the above table (or formula) to identify the standard labor cost corresponding to the actual sales (or actual number of customers). (2) The evaluation unit 300 shall evaluate that actual labor costs are low relative to actual sales (or actual number of customers) if actual labor costs are lower than standard labor costs by a predetermined amount (actual labor costs < standard labor costs - predetermined amount). The evaluation unit 300 shall evaluate that actual labor costs are high relative to actual sales (or actual number of customers) if actual labor costs are higher than standard labor costs by a predetermined amount (actual labor costs > standard labor costs + predetermined amount). The evaluation unit 300 shall evaluate that the balance between actual sales (or actual number of customers) and actual labor costs is appropriate if the difference between actual labor costs and standard labor costs is within a predetermined amount. The evaluation unit 300 may evaluate based on the percentage increase or decrease of actual labor costs relative to standard labor costs (increase or decrease rate) instead of the difference (amount) between actual labor costs and standard labor costs.

[0077] Similarly, in the other example (described later), the evaluation unit 300 evaluates the balance between actual sales (or actual number of customers) and actual labor costs after the end of business hours (for example, the day after a business day).

[0078] If the evaluation unit 300 evaluates that actual labor costs are low compared to actual sales (or actual number of customers), it will determine whether it is necessary to return a portion of the store's profits to the customers. For example, the evaluation unit 300 may determine whether it is necessary to return a portion of the store's profits to the customers by following the steps (1) to (5) below. (1) The evaluation unit 300 uses the above table (or formula) to identify the standard sales revenue corresponding to the actual labor costs. (2) The evaluation unit 300 obtains an amount obtained by subtracting the standard sales from the actual sales. This amount is the excess of the actual sales to the standard sales. (3) The evaluation unit 300 refers to the special sale information storage unit 111 and the product information storage unit 301 and subtracts the planned price from the standard price for each target product. (4) The evaluation unit 300 multiplies the amount in (3) by the number of units sold (actual number of units sold or predetermined number of units) for each target product, and sums up the amounts obtained by multiplying for each target product (summing up for all target products). This sum is, so to speak, the amount that has already been refunded by the planned price (refunded amount). (5) The evaluation unit 300 determines that a refund is necessary if the amount obtained by subtracting the total amount (refunded amount) from the excess amount in (2) is positive (i.e., the refund has not been fully covered by the discount on the day).

[0079] Similarly, in the other example (described later), the evaluation unit 300 will determine whether a refund is necessary. Note that the total amount (refunded amount) in (4) above is "the amount already refunded based on the planned price," but in the other example 1 (described later), it will be "the converted amount of planned coupons already refunded," in the other example 2 (described later), it will be "the converted amount of planned points already refunded," and in the other example 3 (described later), it will be "the converted amount of planned allowances that have already been decided to be refunded."

[0080] The coupon redemption unit 303 makes decisions regarding the issuance of redemption coupons. Redemption coupons are coupons that are issued retrospectively as a reward to customers. The coupon redemption unit 303 makes decisions regarding the issuance of redemption coupons if the evaluation unit 300 determines that it is necessary to return a portion of the store's profits.

[0081] For example, the coupon redemption unit 303 may decide on the issuance of redemption coupons in the following procedure (1)(2).

[0082] (1) The coupon redemption unit 303 determines the products eligible for the redemption coupon and the customers to whom it will be awarded. For example, the coupon redemption unit 303 determines that certain products (one or more predetermined products) are eligible products for the planned coupon. For example, the coupon redemption unit 303 determines that customers who had transactions on the business day to be evaluated (customers identified from customer identification information in the transaction information for that business day) are eligible customers. The coupon redemption unit 303 may also determine that some of the customers who had transactions on the business day to be evaluated are eligible customers (e.g., valued customers based on purchase history among customers who had transactions on the business day to be evaluated, customers selected by lottery among customers who had transactions on the business day to be evaluated). (2) The coupon redemption unit 303 determines the content of the redemption coupon (gift amount, discount amount, etc.). For example, the coupon redemption unit 303 determines the content of the redemption coupon based on the redemption target value and the recipients (number of customers eligible for redemption coupons, number of customers eligible for redemption points, number of employees eligible for redemption allowances). If the redemption target value is large, the content of the redemption coupon will be large. If there are many eligible products or customers, the content of the redemption coupon will be small. The coupon redemption unit 303 may also determine the content of the redemption coupon using a mathematical formula. The coupon redemption unit 303 stores the determined information about the redemption coupon (eligible products for the redemption coupon, eligible customers for the redemption coupon, content of the redemption coupon, etc.) in the coupon storage unit 306.

[0083] The period for issuing the discount coupon may be, for example, one month from the day following the decision by the coupon redemption unit 303 (the details of the discount coupon may be printed on the receipt on the first visit during that period). The discount coupon may also be issued as an electronic coupon via the network the day following the decision by the coupon redemption unit 303. The period during which the discount coupon can be used may be, for example, one month from the date of issuance.

[0084] The points redemption unit 304 makes decisions regarding the awarding of redemption points. Redemption points are points awarded retrospectively as a reward to the customer. The points redemption unit 304 makes decisions regarding the awarding of redemption points if the evaluation unit 300 determines that it is necessary to return a portion of the store's profits.

[0085] For example, the point redemption unit 304 may decide on the awarding of redemption points by following the procedures (1) and (2) below.

[0086] (1) The point reward unit 304 determines which customers are eligible to receive reward points. For example, the point reward unit 304 determines which customers are eligible to receive points are those who had a transaction on the business day being evaluated. The point reward unit 304 may also determine which customers are eligible to receive points are those who have a transaction on the business day being evaluated (e.g., some customers who have a transaction on the business day being evaluated are valued customers based on their purchase history, or some customers who have a transaction on the business day being evaluated are selected by lottery). (2) The point redemption unit 304 determines the content of the redemption points (number of points to be awarded). For example, the point redemption unit 304 determines the content of the redemption points based on the eligible valuation amount and the eligible recipients (number of customers eligible for redemption points, number of employees eligible for redemption allowances, number of customers eligible for redemption coupons). If the eligible valuation amount is large, the content of the redemption points will be large. If there are many eligible customers, the content of the redemption points will be small. The point redemption unit 304 may also determine the content of the redemption points using a mathematical formula. The point redemption unit 304 stores the determined content of the redemption points (number of points to be awarded) in the point storage unit 307.

[0087] The timing of awarding the reward points may be the day after the decision by the points reward department 304, five days later, or on a designated date.

[0088] The Allowance and Rebate Department 305 makes decisions regarding the granting of rebate allowances. Rebate allowances are allowances granted retrospectively as a return to employees. The Allowance and Rebate Department 305 makes decisions regarding the granting of rebate allowances if the Evaluation Department 300 determines that a portion of the store's profits should be returned to employees.

[0089] For example, the allowance rebate unit 305 may decide on the granting of the rebate in the following procedure (1)(2).

[0090] (1) The allowance distribution unit 305 determines which employees are eligible for the allowance. For example, the allowance distribution unit 305 determines which employees are eligible for the allowance if they worked on the business day subject to evaluation. The allowance distribution unit 305 may also determine which employees are eligible for the allowance if they are some of the employees who worked on the business day subject to evaluation (for example, employees who worked for more than the prescribed hours on the business day subject to evaluation, or part-time employees, etc., who worked on the business day subject to evaluation). (2) The allowance redemption unit 305 determines the details of the redemption allowance (such as the amount of the allowance to be granted, like a special daily allowance of 300 yen). For example, the allowance redemption unit 305 determines the details of the redemption allowance based on the eligible evaluation amount and the recipients of the redemption (the number of employees eligible for the redemption allowance, the number of customers eligible for the redemption coupon, the number of customers eligible for the redemption points). If the eligible evaluation amount is large, the details of the redemption allowance will be large. If there are many eligible employees, the details of the redemption allowance will be small. The allowance redemption unit 305 may also determine the details of the redemption allowance using a mathematical formula. The allowance redemption unit 305 stores the determined details of the redemption allowance (e.g., employees eligible for the redemption allowance, details of the redemption allowance) in the allowance storage unit 308.

[0091] Furthermore, the timing of the payment of the rebate allowance may be the day after the decision by the Rebate Rebate Department 305, five days later, or on a designated date. In other words, it is sufficient that the rebate allowance is deposited into the bank account of the eligible employee.

[0092] The distribution of reward coupons to customers by the coupon reward unit 303, reward points to customers by the point reward unit 304, and reward allowances to employees by the allowance reward unit 305 can be predetermined. For example, the ratio of reward coupons:reward points:reward allowances may be 25:25:50. Alternatively, one of the three may be awarded (for example, reward coupons:reward points:reward allowances = 100:0:0), or two of the three may be awarded (for example, reward coupons:reward points:reward allowances = 50:50:0).

[0093] Figure 3 is a flowchart illustrating an example of the operation of part of the headquarters system H. Specifically, the flowchart in Figure 3(A) shows the operation one week prior to each business day. The flowchart in Figure 3(B) shows the operation before the start of business on the business day. The flowchart in Figure 3(C) shows the operation after the end of business on each business day (for example, the next day).

[0094] (Flowchart in Figure 3(A)) Step S10: The demand forecasting unit 101 forecasts the demand for a business day one week in advance (e.g., number of visitors, sales). The demand forecasting unit 101 stores the forecast results (e.g., forecast number of visitors, forecast sales) in the forecast result storage unit 102. The process then proceeds to step S11.

[0095] Step S11: The work shift determination unit 103 determines the work shifts for the business days one week from now. The work shift determination unit 103 stores the determined work shifts in the work shift information storage unit 104. The process then proceeds to step S12.

[0096] Step S12: The planned personnel cost calculation unit 107 calculates the planned personnel costs for the business days one week from now. The planned personnel cost calculation unit 107 stores the calculated planned personnel costs in the planned personnel cost storage unit 109. The process then proceeds to step S13.

[0097] Step S13: The planned price determination unit 110A determines the planned price for the business day one week from now. The planned price determination unit 110A stores the determined planned price in the special sale information storage unit 111. This flowchart then ends.

[0098] (Flowchart in Figure 3(B)) Step S20: The modified labor cost calculation unit 201 determines whether there has been a change in the work shift. The modified labor cost calculation unit 201 determines that there has been a change in the work shift if the change is stored in the work shift information storage unit 104. If there has been a change in the work shift (Step S20: YES), proceed to Step S21. If there has been no change in the work shift (Step S20: NO), this flowchart ends.

[0099] Step S21: The revised personnel cost calculation unit 201 calculates the revised personnel costs. The revised personnel cost calculation unit 201 stores the calculated revised personnel costs in the revised personnel cost storage unit 202. The process then proceeds to step S22.

[0100] Step S22: The planned price adjustment unit 203A determines the adjustment price. The planned price adjustment unit 203A stores the determined adjustment price in the special sale information storage unit 111. In other words, the planned price stored in the special sale information storage unit 111 (the planned price determined by the planned price determination unit 110A in step S13 of Figure 3(A)) is updated by the adjustment price (the adjustment price determined by the planned price adjustment unit 203A in step S22 of Figure 3(B)) (if the adjustment price becomes the same as the planned price, the planned price is maintained). This flowchart then ends.

[0101] (Flowchart in Figure 3(C)) Step S30: The evaluation unit 300 evaluates the balance between actual sales (or actual number of customers) and actual labor costs. Then proceed to step S31.

[0102] Step S31: The evaluation unit 300 determines, as an evaluation result, whether the actual labor costs are lower than the actual sales. If the actual labor costs are lower than the actual sales (Step S31: YES), proceed to Step S32. If the actual labor costs are not lower than the actual sales (Step S31: NO), this flowchart ends.

[0103] Step S32: The evaluation unit 300 determines whether it is necessary to return a portion of the store's profits. If it is necessary to return a portion (Step S32: YES), proceed to Step S33. If it is not necessary to return a portion (Step S32: NO), this flowchart ends.

[0104] Step S33: The coupon redemption unit 303 determines the customers eligible for the redemption coupon and the content of the redemption coupon. The coupon redemption unit 303 stores the determined information (eligible customers for the redemption coupon and content of the redemption coupon) in the coupon storage unit 306. This flowchart then ends.

[0105] In step S33, the coupon redemption unit 303 determines the customers eligible for redemption coupons and the content of the redemption coupons. However, instead of this, or in addition, the point redemption unit 304 may determine the customers eligible for redemption points and the content of the redemption points, or the allowance redemption unit 305 may determine the employees eligible for redemption allowances and the content of the redemption allowances.

[0106] [Another example 1] Figure 4 is an explanatory diagram illustrating the functions of Alternative Example 1. Specifically, Figure 4 shows the area within dashed line P in Figure 2. In other words, the configuration within dashed line P in Figure 2 is such that the planned price determination unit 110A determines the planned price and stores it in the special sale information storage unit 111, and when there is a change in the work shift, the planned price adjustment unit 203A determines the adjusted price (adjusts the planned price) and stores it in the special sale information storage unit 111. In contrast, the configuration of Alternative Example 1 differs in that the planned coupon determination unit 110B determines the allocation of planned coupons and stores it in the coupon storage unit 306, and when there is a change in the work shift, the planned coupon adjustment unit 203B adjusts the planned coupons and stores them in the coupon storage unit 306. The rest of Alternative Example 1 is the same as the configuration shown in Figure 2. Note that the planned coupon determination unit 110B and the planned coupon adjustment unit 203B are functions of the determination server 10.

[0107] The planned coupon determination unit 110B determines the issuance of planned coupons. Planned coupons are coupons that are scheduled to be issued in the future (specifically, on a business day one week from now) based on projected sales (or projected number of visitors) and projected labor costs. Planned coupons are intended to cover the difference between standard labor costs and projected labor costs (reduce the discrepancy).

[0108] The planned coupon determination unit 110B uses the prediction results stored in the prediction result storage unit 102 and the planned labor costs stored in the planned labor cost storage unit 109 to determine whether to issue planned coupons. Alternatively, a table (or formula) showing the relationship between sales (or number of visitors) and labor costs may be prepared, and the planned coupon determination unit 110B may use this table (or formula) to determine whether to issue planned coupons.

[0109] For example, the scheduled coupon determination unit 110B may determine the allocation of scheduled coupons in the following procedure (1) to (4).

[0110] (1) The planned coupon determination unit 110B uses the above table (or formula) to identify (obtain) the standard labor costs corresponding to the projected sales (or projected number of visitors). (2) The planned coupon determination unit 110B decides not to grant a planned coupon if the planned personnel costs are not lower than the standard personnel costs (planned personnel costs ≥ standard personnel costs). The planned coupon determination unit 110B decides to grant a planned coupon if the planned personnel costs are lower than the standard personnel costs (planned personnel costs < standard personnel costs). The planned coupon determination unit 110B may also decide to grant a planned coupon if the planned personnel costs are lower than the standard personnel costs by a predetermined amount (predicted personnel costs < base personnel costs - predetermined amount), rather than if the planned personnel costs are lower than the standard personnel costs (planned personnel costs < standard personnel costs). The planned coupon determination unit 110B may also decide whether or not to grant a planned coupon based on the percentage increase or decrease of the planned personnel costs relative to the standard personnel costs (increase / decrease rate) instead of the difference (amount) between the planned personnel costs and the standard personnel costs. (3) When the planned coupon determination unit 110B decides to grant a planned coupon, it determines the products to which the planned coupon will be granted and the customers to whom it will be granted. For example, the planned coupon determination unit 110B may determine that certain products (one or more predetermined products) are the products to which the planned coupon will be granted. For example, the planned coupon determination unit 110B may determine that good customers based on their purchase history are the customers to whom the coupon will be granted. The planned coupon determination unit 110B may also determine that customers selected by lottery from all customers are the customers to whom the coupon will be granted. (4) The planned coupon determination unit 110B determines the content of the planned coupon (gift amount, discount amount, etc.). For example, the planned coupon determination unit 110B determines the content of the planned coupon based on the amount obtained by subtracting the planned labor costs from the standard labor costs, the number of target products, and the number of customers to whom the coupon is to be given. If the amount obtained by subtracting the planned labor costs from the standard labor costs is large, the content of the planned coupon will be large. If there are many target products or customers to whom the coupon is to be given, the content of the planned coupon will be small. The planned coupon determination unit 110B may also determine the content of the planned coupon using a mathematical formula. If the planned coupon determination unit 110B decides to give a planned coupon, it stores the determined content (target products for the planned coupon, customers to whom the planned coupon is to be given, content of the planned coupon, etc.) in the coupon storage unit 306.

[0111] The Scheduled Coupon Adjustment Unit 203B adjusts the scheduled coupons when the changed labor costs are stored in the Changed Labor Cost Storage Unit 202 (i.e., when there has been a change in the work shift by the Work Shift Change Unit 200). Specifically, the Scheduled Coupon Adjustment Unit 203B adjusts the scheduled coupons in accordance with the timing of the calculation of the changed labor costs by the Changed Labor Cost Calculation Unit 201. In other words, the Scheduled Coupon Adjustment Unit 203B adjusts the scheduled coupons after the end of the acceptance period for work shift changes by the Work Shift Change Unit 200 (1 week to the day before) (for example, before the start of business on the business day).

[0112] Specifically, the planned coupon adjustment unit 203B adjusts the planned coupons using the forecast results stored in the forecast result storage unit 102 and the revised labor costs stored in the revised labor cost storage unit 202. The method by which the planned coupon adjustment unit 203B adjusts the planned coupons based on the forecast results and revised labor costs is the same as the method by which the planned coupon determination unit 110B determines the allocation of planned coupons based on the forecast results and planned labor costs. In other words, a table (or formula) showing the relationship between sales (or number of visitors) and labor costs may be prepared, and the planned coupon adjustment unit 203B may use this table (or formula) to determine (re-determine) the allocation of planned coupons as an adjustment.

[0113] The decisions made by the scheduled coupon adjustment unit 203B (adjusted adjustments) are stored in the coupon storage unit 306. In other words, the contents stored in the coupon storage unit 306 (the contents decided by the scheduled coupon determination unit 110B) are updated when the work shift changes. However, if the difference between the scheduled labor costs and the changed labor costs is small, the contents stored in the coupon storage unit 306 are maintained (i.e., if labor costs do not change much even if the work shift changes, the original scheduled coupons are maintained).

[0114] [Another example 2] Figure 5 is an explanatory diagram illustrating the functions of Alternative Example 2. Specifically, Figure 5 shows the area within the dashed line P in Figure 2. In other words, the configuration within the dashed line P in Figure 2 is such that the planned price determination unit 110A determines the planned price and stores it in the special sale information storage unit 111, and when there is a change in the work shift, the planned price adjustment unit 203A determines the adjusted price (adjusts the planned price) and stores it in the special sale information storage unit 111. In contrast, the configuration of Alternative Example 2 differs in that the planned point determination unit 110C determines the allocation of planned points and stores it in the point storage unit 307, and when there is a change in the work shift, the planned point adjustment unit 203C adjusts the planned points and stores it in the point storage unit 307. The rest of Alternative Example 2 is the same as the configuration shown in Figure 2. Note that the planned point determination unit 110C and the planned point adjustment unit 203C are functions of the determination server 10.

[0115] The planned points determination unit 110C determines the allocation of planned points. Planned points are points that are scheduled to be allocated in the future (specifically, on a business day one week from now) based on projected sales (or projected number of visitors) and projected labor costs. Planned points are used to cover the difference between standard labor costs and projected labor costs (reduce the discrepancy).

[0116] The planned points determination unit 110C determines the allocation of planned points using the prediction results stored in the prediction result storage unit 102 and the planned labor costs stored in the planned labor cost storage unit 109. Alternatively, a table (or formula) showing the relationship between sales (or number of visitors) and labor costs may be prepared, and the planned points determination unit 110C may use this table (or formula) to determine the allocation of planned points.

[0117] For example, the planned point determination unit 110C may determine the allocation of planned points by following the steps (1) to (4) below.

[0118] (1) The planned point determination unit 110C uses the above table (or formula) to identify (obtain) the standard labor costs corresponding to the predicted sales (or predicted number of visitors). (2) The planned points determination unit 110C decides not to award planned points if the planned personnel costs are not lower than the standard personnel costs (planned personnel costs ≥ standard personnel costs). The planned points determination unit 110C decides to award planned points if the planned personnel costs are lower than the standard personnel costs (planned personnel costs < standard personnel costs). The planned points determination unit 110C may also decide to award planned points if the planned personnel costs are lower than the standard personnel costs by a predetermined amount (predicted personnel costs < base personnel costs - predetermined amount), rather than if the planned personnel costs are lower than the standard personnel costs (planned personnel costs < standard personnel costs). The planned points determination unit 110C may also decide whether or not to award planned points based on the percentage increase or decrease of the planned personnel costs relative to the standard personnel costs (increase / decrease rate) instead of the difference (amount) between the planned personnel costs and the standard personnel costs. (3) When the planned points determination unit 110C decides to award planned points, it determines which customers will receive the planned points. For example, the planned points determination unit 110C may determine which customers will receive the points based on their purchase history. The planned points determination unit 110C may also determine which customers will receive the points by selecting them by lottery from all customers. (4) The planned points determination unit 110C determines the content of the planned points (number of points to be awarded). For example, the planned points determination unit 110C determines the content of the planned points based on the amount obtained by subtracting the planned labor costs from the standard labor costs and the number of customers to whom the points will be awarded. If the amount obtained by subtracting the planned labor costs from the standard labor costs is large, the content of the planned points will be large. If there are many customers to whom the points will be awarded, the content of the planned points will be small. The planned points determination unit 110C may also determine the content of the planned points using a mathematical formula. If the planned points determination unit 110C decides to award planned points, it stores the determined content (customers to whom the planned points will be awarded, content of the planned points, etc.) in the point storage unit 307.

[0119] The Scheduled Points Adjustment Unit 203C adjusts the scheduled points when the changed personnel costs are stored in the Changed Personnel Cost Storage Unit 202 (i.e., when there has been a change in the work shift by the Work Shift Change Unit 200). Specifically, the Scheduled Points Adjustment Unit 203C adjusts the scheduled points in accordance with the timing of the calculation of the changed personnel costs by the Changed Personnel Cost Calculation Unit 201. In other words, the Scheduled Points Adjustment Unit 203C adjusts the scheduled points after the end of the acceptance period for work shift changes by the Work Shift Change Unit 200 (1 week prior to the day before) (for example, before the start of business on the day of the business).

[0120] Specifically, the planned points adjustment unit 203C adjusts the planned points using the forecast results stored in the forecast result storage unit 102 and the revised labor costs stored in the revised labor cost storage unit 202. The method by which the planned points adjustment unit 203C adjusts the planned points based on the forecast results and revised labor costs is the same as the method by which the planned points determination unit 110C determines the allocation of planned points based on the forecast results and planned labor costs. In other words, a table (or formula) showing the relationship between sales (or number of visitors) and labor costs may be prepared, and the planned points adjustment unit 203C may use this table (or formula) to determine (redetermine) the allocation of planned points as an adjustment.

[0121] The decision made by the planned point adjustment unit 203C (the adjusted adjustment) is stored in the point storage unit 307. In other words, the contents stored in the point storage unit 307 (the contents decided by the planned point determination unit 110C) are updated when the work shift changes. However, if the difference between the planned labor costs and the changed labor costs is small, the contents stored in the point storage unit 307 are maintained (that is, if labor costs do not change much even if the work shift changes, the original planned points are maintained).

[0122] [Another example 3] Figure 6 is an explanatory diagram illustrating the functions of Alternative Example 3. Specifically, Figure 6 shows the area within the dashed line P in Figure 2. In other words, the configuration within the dashed line P in Figure 2 is such that the planned price determination unit 110A determines the planned price and stores it in the special sale information storage unit 111, and when there is a change in the work shift, the planned price adjustment unit 203A determines the adjusted price (adjusts the planned price) and stores it in the special sale information storage unit 111. In contrast, the configuration of Alternative Example 3 differs in that the planned allowance determination unit 110D determines the allocation of planned allowances and stores it in the allowance storage unit 308, and when there is a change in the work shift, the planned allowance adjustment unit 203D adjusts the planned allowance and stores it in the allowance storage unit 308. The other parts of Alternative Example 3 are the same as the configuration shown in Figure 2. Note that the planned allowance determination unit 110D and the planned allowance adjustment unit 203D are functions of the determination server 10.

[0123] The planned allowance determination unit 110D determines the payment of planned allowances. Planned allowances are allowances that are scheduled to be paid in the future (specifically, on a business day one week from now) and are determined based on projected sales (or projected number of customers) and projected personnel costs. Planned allowances are intended to cover the difference between standard personnel costs and projected personnel costs (reduce the discrepancy).

[0124] The planned allowance determination unit 110D uses the forecast results stored in the forecast result storage unit 102 and the planned personnel costs stored in the planned personnel cost storage unit 109 to determine the amount of the planned allowance. Alternatively, a table (or formula) showing the relationship between sales (or number of customers) and personnel costs may be prepared, and the planned allowance determination unit 110D may use this table (or formula) to determine the amount of the planned allowance.

[0125] For example, the planned allowance determination unit 110D may determine the granting of the planned allowance by following the steps (1) to (4) below.

[0126] (1) The planned allowance determination unit 110D uses the above table (or formula) to identify (obtain) the standard labor costs corresponding to the projected sales (or projected number of customers). (2) The planned allowance determination unit 110D decides not to grant a planned allowance if the planned personnel costs are not lower than the standard personnel costs (planned personnel costs ≥ standard personnel costs). The planned allowance determination unit 110D decides to grant a planned allowance if the planned personnel costs are lower than the standard personnel costs (planned personnel costs < standard personnel costs). The planned allowance determination unit 110D may also decide to grant a planned allowance if the planned personnel costs are lower than the standard personnel costs by a predetermined amount (predicted personnel costs < base personnel costs - predetermined amount), rather than if the planned personnel costs are lower than the standard personnel costs (planned personnel costs < standard personnel costs). The planned allowance determination unit 110D may also decide whether or not to grant a planned allowance based on the percentage increase or decrease of the planned personnel costs relative to the standard personnel costs (increase / decrease rate) instead of the difference (amount) between the planned personnel costs and the standard personnel costs. (3) If the planned allowance determination unit 110D decides to grant a planned allowance, it determines which employees are eligible to receive the planned allowance. For example, it may determine that all employees scheduled to work on the business day in question (the business day one week later) are eligible to receive the planned allowance. The planned allowance determination unit 110D may also limit the employees eligible to receive the planned allowance to part-time workers, temporary workers, etc. (4) The planned allowance determination unit 110D determines the details of the planned allowance (such as the amount of the allowance to be granted, like a special daily allowance of 300 yen). For example, the planned allowance determination unit 110D determines the details of the planned allowance based on the amount obtained by subtracting the planned personnel costs from the standard personnel costs and the number of employees to whom the allowance is granted. If the amount obtained by subtracting the planned personnel costs from the standard personnel costs is large, the details of the planned allowance will be large. If there are many employees to whom the allowance is granted, the details of the planned allowance will be small. The planned allowance determination unit 110D may also determine the details of the planned allowance using a mathematical formula. If the planned allowance determination unit 110D decides to grant the planned allowance, it stores the determined details (employees to whom the planned allowance is granted, details of the planned allowance, etc.) in the allowance storage unit 308.

[0127] The planned allowance adjustment unit 203D adjusts the planned allowance when the changed personnel costs are stored in the changed personnel cost storage unit 202 (i.e., when there has been a change in the work shift by the work shift change unit 200). Specifically, the planned allowance adjustment unit 203D adjusts the planned allowance in accordance with the timing of the calculation of the changed personnel costs by the changed personnel cost calculation unit 201. In other words, the planned allowance adjustment unit 203D adjusts the planned allowance after the end of the acceptance period for changes to the work shift by the work shift change unit 200 (1 week to the day before) (for example, before the start of business on a business day).

[0128] Specifically, the planned allowance adjustment unit 203D adjusts the planned allowance using the forecast results stored in the forecast result storage unit 102 and the revised personnel costs stored in the revised personnel cost storage unit 202. The method by which the planned allowance adjustment unit 203D adjusts the planned allowance based on the forecast results and revised personnel costs is the same as the method by which the planned allowance determination unit 110D determines the amount of the planned allowance based on the forecast results and planned personnel costs. In other words, a table (or formula) showing the relationship between sales (or number of customers) and personnel costs may be prepared, and the planned allowance adjustment unit 203D may use the table (or formula) to determine (redetermine) the amount of the planned allowance as an adjustment.

[0129] The decision made by the planned allowance adjustment unit 203D (the adjusted adjustment) is stored in the allowance storage unit 308. In other words, the contents stored in the allowance storage unit 308 (the contents decided by the planned allowance determination unit 110D) are updated when the work shift changes. However, if the difference between the planned personnel costs and the changed personnel costs is small, the contents stored in the allowance storage unit 308 are maintained (that is, if personnel costs do not change much even if the work shift changes, the original planned allowance is maintained).

[0130] (Items subject to the estimated price) The planned price determination unit 110A explained that the target products for which it determines the planned price may be predetermined products (one or more products determined in advance) or all products. For example, the target products may be determined as shown in (1) to (4). Note that (1) to (4) may be combined as appropriate.

[0131] (1) Determine the target products based on sales forecasts (demand forecasts). For example, the system automatically (without requiring any action from a store employee) selects the top N products based on their projected sales (or projected sales quantity). Alternatively, the system can display the top N products based on projected sales (or projected sales quantity) on the screen, allowing the store employee to select the target product. Note that the number N may be specified by the store employee (the same applies to (2) and (3) below). (2) The target products will be determined based on sales performance (sales history). For example, the system automatically determines the top N products based on sales (or sales volume) over a specified period (the past month). Alternatively, the system can display the top N products based on sales (or sales volume) over the specified period on a screen, allowing the employee to select the target product. (3) Determine the target products based on the profit margin (or profit amount) of the products. For example, the system automatically selects the top N products based on their profit margin (or profit amount). Alternatively, it can display these top N products on the screen for the employee to select, allowing the employee to determine the target product. The profit margin of a product can be calculated by referencing the product master data (selling price, cost). (4) Determine the target products by excluding specific products. For example, exclude a specific product from the top N items in (1) to (3) above. In other words, determine the top N items by excluding a specific product. Examples of specific products are (a) to (e) below. (a) Tobacco, alcohol, pharmaceuticals (Type 2, Type 3) This product will be excluded because it is not suitable for price changes (planned prices). (b) Products that require staff intervention (cooking, heating, portioning, packaging), such as hot snacks. The sale of this product would place a burden on the staff (employees), contradicting and conflicting with the basic policy (the policy of lowering prices when the number of staff is relatively small compared to how busy the store is), and disrupting the balance, therefore it will be excluded. (c)Fresh products If prices were to be raised, the risk of waste would increase, so it will be excluded. (d) Frozen products If a price increase is implemented and the customer notices it after registration and cancels the order, for example near the register (registration and payment device 20, etc.), the order will be excluded because it would create quality (refrigeration) problems and increase the workload for the staff (a greater workload compared to canceling other items, as the item must be returned to its original position immediately). (e) Products from a specific manufacturer (identifiable by JAN code) We will exclude products as needed, in response to branding requests from manufacturers. Specific products from specific manufacturers may be excluded.

[0132] (Products eligible for planned coupons and cashback coupons) The products eligible for planned coupons and discount coupons may be determined in the same way as the products eligible for planned prices.

[0133] (Determination of the planned price) The planned price determination unit 110A is described as determining a price higher than the standard price as the planned price if the planned labor costs are higher than the standard labor costs by a predetermined amount, and determining a price lower than the standard price as the planned price if the planned labor costs are lower than the standard labor costs by a predetermined amount. However, the determination may also be made by considering the profit margin (or profit amount). For example, the planned price may be determined for each target product in a way that maintains a predetermined profit margin (or does not result in a price below cost). For example, if the store clerk sets (inputs) the planned price on the display screen, it may be made so that an amount below the predetermined profit margin (or an amount that results in a price below cost) cannot be entered.

[0134] (Details of planned coupons and redemption coupons) The details of planned coupons and discount coupons (especially discount amounts) may be determined in the same way as the planned price.

[0135] (Report based on the difference between standard labor costs and planned labor costs) The planned price determination unit 110A may notify the system that the difference between the standard labor cost and the planned labor cost has exceeded a predetermined value if the difference exceeds a predetermined value (for example, if a price higher than the standard price is determined as the planned price, or if a price lower than the standard price is determined as the planned price). (For example, output to the headquarters terminal 14 so that it is displayed, voice-outputted, or printed on the headquarters terminal 14, or output to the mobile terminal (not shown) used by an employee so that it is displayed or voice-outputted on the mobile terminal. The same applies hereinafter.) The same applies to the planned price adjustment unit 203A.

[0136] If the planned price determination unit 110A determines a price higher than the standard price as the planned price (for example, if it determines a price higher than the standard price based on the fact that planned labor costs > standard labor costs + predetermined amount, or if it determines a price higher than the standard price based on the fact that planned labor costs > standard labor costs), it may notify that a price higher than the standard price has been determined as the planned price, or the planned price itself. It may also notify the standard price / planned price of the target product. The same applies if a price lower than the standard price is determined as the planned price. The same applies to the planned price adjustment unit 203A.

[0137] The scheduled coupon determination unit 110B may notify that the difference between standard labor costs and scheduled labor costs has exceeded a predetermined value if the difference between standard labor costs and scheduled labor costs exceeds a predetermined value (for example, if it has decided to grant scheduled coupons). The same applies to the scheduled coupon adjustment unit 203B.

[0138] The scheduled coupon determination unit 110B may notify the system that it has decided to grant a scheduled coupon (for example, if it decides to grant a scheduled coupon based on the fact that predicted personnel costs < base personnel costs - predetermined amount, or if it decides to grant a scheduled coupon based on the fact that scheduled personnel costs < standard personnel costs). It may also notify the system of the products / contents of the scheduled coupon. The same applies to the scheduled coupon adjustment unit 203B.

[0139] The planned points determination unit 110C may notify that the difference between standard labor costs and planned labor costs has exceeded a predetermined value if the difference exceeds a predetermined value (for example, if it has decided to award planned points). The same applies to the planned points adjustment unit 203C.

[0140] The planned points determination unit 110C may notify that it has decided to award planned points when it has decided to award them (when it has decided to award planned points based on the fact that predicted personnel costs < base personnel costs - predetermined amount, or when it has decided to award planned points based on the fact that planned personnel costs < standard personnel costs). It may also notify the details of the planned points. The same applies to the planned points adjustment unit 203C.

[0141] The planned allowance determination unit 110D may notify the system that the difference between standard personnel costs and planned personnel costs has exceeded a predetermined value (for example, when it has been decided to grant a planned allowance). The same applies to the planned allowance adjustment unit 203D.

[0142] The planned allowance determination unit 110D may notify the system that it has decided to grant a planned allowance (for example, when it has decided to grant a planned allowance based on the fact that projected personnel costs < base personnel costs - predetermined amount, or when it has decided to grant a planned allowance based on the fact that planned personnel costs < standard personnel costs). It may also notify the system of the details of the planned allowance. The same applies to the planned allowance adjustment unit 203D.

[0143] (Notice regarding the return on investment) The reward unit 302 may also notify about the reward. For example, if the coupon reward unit 303 decides to grant a reward coupon, it may notify the target products / contents of the reward coupon (for example, output to the headquarters terminal 14 so that it can be displayed on the headquarters terminal 14, and output to the mobile terminal (not shown) used by employees so that it can be displayed on the said mobile terminal; the same applies hereinafter). The same applies if the point reward unit 304 decides to grant reward points, and if the allowance reward unit 305 decides to grant reward allowances. In lieu of or in addition to the notification by the reward unit 302 described above, if the evaluation unit 300 decides that it is necessary to return a portion of the store's profits, it may notify that it has decided that a reward is necessary (or that a reward will be given).

[0144] (Notification of planned price (price after change)) For products sold at a price different from the standard price (the price stored in the product master), customers and employees will be informed that the price differs from the standard price. Hereinafter, products sold at a price different from the standard price may be referred to as "price-variable products."

[0145] It has been explained that the registration and settlement device 20 may be a device that registers products based on the actions of a store employee and settles payments based on the actions of a store employee, a device that registers products based on the actions of a customer and settles payments based on the actions of a customer (a fully self-service device), a device that registers products based on the actions of a store employee and settles payments based on the actions of a customer (a face-to-face semi-self-service device), or a device that has multiple operating modes (fully self-service mode, face-to-face semi-self-service mode). However, for convenience, they may be distinguished as follows: A registration and settlement device 20 that registers products based on the actions of a store employee and settles payments based on the actions of a store employee will be referred to as registration and settlement device 20A. A fully self-service registration and settlement device 20 that registers products based on the actions of a customer and settles payments based on the actions of a customer will be referred to as registration and settlement device 20B. A face-to-face semi-self-service registration and settlement device 20 that registers products based on the actions of a store employee and settles payments based on the actions of a customer will be referred to as registration and settlement device 20C. A registration and payment device 20 having multiple operating modes (for example, a fully self-service mode, a face-to-face semi-self-service mode) is referred to as a registration and payment device 20D.

[0146] Let's look at an example of notification. For example, if you have implemented electronic shelf labels, you can provide information on price-sensitive products. Electronic shelf labels (ESLs) displayed for products sold at a price different from the standard price primarily serve to inform customers that the product's price is subject to change (for example, by marking it or displaying it in a different way than usual). In addition to the changed price, the ELS may also display the standard price and the difference (change amount) from the standard price. If ELS is not implemented, price tags (paper price tags) may be rewritten to address this issue.

[0147] When the registration and settlement device 20A registers a price-fluctuating product during the registration process, it may notify the store clerk that the price-fluctuating product has been registered along with the revised price on the clerk-side display unit (registration screen), and may also notify the customer that the price-fluctuating product has been registered along with the revised price on the customer-side display unit (customer confirmation screen). Furthermore, when the registration and settlement device 20A registers a price-fluctuating product, if the registered products include a price-fluctuating product, it may notify the store clerk that the product in question (the price-fluctuating product) is a price-fluctuating product on the clerk-side display unit (for example, by marking it or displaying it in a different way than usual), and may also notify the customer that the product in question is a price-fluctuating product on the customer-side display unit. The same applies to the registration and payment device 20C, the registration and payment device 20D (face-to-face semi-self-service mode), and the registration device 21.

[0148] If the registered payment device 20A includes price-variable items among the items to be paid for (registered items) during the payment process, it may inform the customer on the customer-side display unit (item list screen) that the item in question (price-variable item) is a price-variable item. The registered payment device 20A may also inform the store clerk, on behalf of or in addition to the customer, on the store clerk-side display unit (item list screen) that the item in question is a price-variable item during the payment process. The same applies to the registration and payment device 20C and the registration and payment device 20D (face-to-face semi-self-service mode).

[0149] When the registration and settlement device 20B registers a price-fluctuating product during the registration process, it may inform the customer on the display unit (registration screen) that a price-fluctuating product has been registered, along with the price after the change. Furthermore, when the registration and settlement device 20B registers a price-fluctuating product among the registered products during the registration process, it may inform the customer on the display unit that the product in question is a price-fluctuating product. The same applies to the registration and payment device 20D (full self-service mode) and the mobile terminal 30 (a terminal that registers products based on customer operations at the point of sale).

[0150] If the registered settlement device 20B includes price-fluctuating items among the items to be settled during the settlement process, it may inform the customer that the relevant items are price-fluctuating items on the display unit (product list screen). The same applies to the registration and payment device 20D (full self-service mode), payment device 22, and payment device 25.

[0151] At the end of the transaction (after the settlement process is completed), if the purchased goods include items with fluctuating prices, the registration and settlement device 20A may inform the customer on the receipt that the relevant items are items with fluctuating prices. In other words, the registration and settlement device 20A may issue a receipt that indicates that the items with fluctuating prices are items with fluctuating prices. The same applies to the registration and payment device 20B, registration and payment device 20C, registration and payment device 20D (full self-service mode, face-to-face semi-self-service mode), payment device 22, and payment device 25.

[0152] (Confirmation of purchase intent for items priced higher than the standard price) The price of a price-variable product (a product sold at a price different from the standard price) may be higher or lower than the standard price. However, for price-variable products where the price is higher than the standard price, it may be possible to confirm the purchase intention during the registration process. While the fact that a product is price-variable and the price after the change can be confirmed on electronic shelf labels or price tags, for price-variable products where the price is higher than the standard price, it may be possible to confirm the purchase intention once again when registering the product.

[0153] For example, when the registration and settlement device 20A scans the relevant product (a product with a price fluctuation higher than the standard price), it may display a purchase button and a non-purchase button on the customer-side display unit (customer confirmation screen) (for example, display a small screen with both buttons in front of the customer confirmation screen). If the customer presses the purchase confirmation button (i.e., scans and then presses the purchase button), the device may register the product. If the customer presses the non-purchase button (i.e., scans and then presses the non-purchase button), the device may not register the product. Alternatively, the registration and settlement device 20A may display both buttons on the staff display unit (registration screen) instead of displaying them on the customer-side display unit (the device may register the product if the customer presses the purchase confirmation button and not register the product if the staff presses the non-purchase button). The same applies to the registration and payment device 20C, the registration and payment device 20D (face-to-face semi-self-service mode), and the registration device 21.

[0154] When the registration and settlement device 20B scans the relevant product, it may display a purchase button and a non-purchase button on the display unit (registration screen) (for example, display a small screen with both buttons in front of the registration screen), and if the customer presses the purchase confirmation button, the product may be registered, and if the customer presses the non-purchase button, the product may not be registered. The same applies to the registration and payment device 20D (full self-service mode) and the mobile terminal 30. Furthermore, if the "Non-Purchase" button is pressed, a staff call process may be initiated (for example, the light on the signpost illuminates, a device operated by a staff member is used, or a notification is sent to a mobile terminal indicating that staff are needed). The same applies to the registration and payment device 20D (full self-service mode).

[0155] (Cancellation operation for items priced higher than the standard price) For products with fluctuating prices higher than the standard price, it may be possible to make it easy to cancel the listing after the product has been registered.

[0156] For example, if the registered products include products with price fluctuations higher than the standard price, the registration and settlement device 20A may accept cancellation operations for the relevant products (products with price fluctuations higher than the standard price) by the store clerk on the store clerk's display unit (registration screen) (cancellation operations specifying individual relevant products, or cancellation operations for all relevant products at once), or it may accept cancellation operations for the relevant products by the customer on the customer's display unit (customer confirmation screen) (cancellation operations specifying individual relevant products, or cancellation operations for all relevant products at once). The registration and settlement device 20A may also display the relevant products together (or display only the relevant products) to make it easier to confirm before cancellation. The same applies to the registration and payment device 20C, the registration and payment device 20D (face-to-face semi-self-service mode), and the registration device 21.

[0157] The registered payment device 20A may, during the payment process, accept cancellation requests from customers for the items subject to payment (registered items) if the items have a price fluctuation higher than the standard price (cancellation requests for individual items, or cancellation requests for all items at once) on the customer-side display unit (item list screen), or on the store clerk-side display unit (item list screen). The registered payment device 20A may also display the items together (or only the items) to facilitate confirmation before cancellation. The same applies to the registration and payment device 20C and the registration and payment device 20D (face-to-face semi-self-service mode).

[0158] For example, if the registered products include products with price fluctuations higher than the standard price, the registration and settlement device 20B may accept cancellation operations from the customer for the relevant products on the display unit (registration screen) (cancellation operations specifying individual relevant products, or cancellation operations for all relevant products at once). The registration and settlement device 20B may also display the relevant products together (or display only the relevant products) to make it easier for customers to confirm before cancellation. The same applies to the registration and payment device 20D (full self-service mode) and the mobile terminal 30.

[0159] The registered settlement device 20B may, during settlement processing, accept cancellation operations from the customer for the relevant products (registered products) if the products subject to settlement (registered products) include products with price fluctuations higher than the standard price, on the display unit (product list screen). These cancellation operations may include individual cancellation operations for the relevant products, or simultaneous cancellation operations for all relevant products. The registered settlement device 20B may also display the relevant products together (or display only the relevant products) to make it easier for customers to confirm before cancellation. The same applies to the registration and payment device 20D (full self-service mode), payment device 22, and payment device 25.

[0160] (Screen example) Figures 7 to 9 show example screens related to inputting and changing work shifts. Specifically, Figure 7 is an example of a work shift screen (work schedule submission screen). Figure 8 is an example of a work shift screen (work schedule change submission screen). Figure 9 is an example of displaying the scheduled price (price after change). Note that A to C are full-time employees, D to G are part-time employees, and H to K are temporary workers.

[0161] When "Schedule Input" is selected from the work shift screen (main work screen; not shown) on the headquarters terminal 14, it displays the work shift screen (work schedule reception screen) as shown in Figure 7. Through the work schedule reception screen in Figure 7, the headquarters terminal 14 accepts input of work schedules (scheduled workers, scheduled work hours) for each business day during the period from one month to one week before the business day.

[0162] As shown in Figure 7, the work schedule submission screen includes a work day specification area AR1 for specifying the work day, an employment category specification area AR2 for specifying the employment category, and a work schedule operation area AR3 for accepting input operations for work schedules (scheduled employees, scheduled work hours). In addition, the work schedule submission screen in Figure 7 has correction, back, and execute buttons.

[0163] Employees (for example, managers, or individual employees) operate the work schedule operation area AR3 to input their work schedule for the relevant business day (Month X, Day Y). In the example shown in Figure 7, the schedules for part-time and temporary workers are entered as follows: D (part-time) from 10am to 4pm, E (part-time) from 10am to 3pm, H (temporary) from 3pm to 7pm, and J (temporary) from 2pm to 6pm.

[0164] The input operation in the work schedule operation area AR3 only needs to be able to accept operations to specify employees who are scheduled to work. For example, the work schedule operation area AR3 can accept operations to specify a desired time (start time to end time), and the headquarters terminal 14 may, when a time is specified, display a pop-up screen (not shown) in which an employee can be selected, and when an employee is selected on the pop-up screen, the pop-up screen is cleared and the selected employee is assigned to the specified time. Note that the order may be employee selection → time specification, rather than time specification → employee selection. An employee selection button may be placed near the work schedule operation area AR3, and when the employee selection button is operated, the headquarters terminal 14 may display a pop-up screen (not shown) in which an employee can be selected, and when an employee is selected on the pop-up screen, the pop-up screen is cleared and the selected employee is temporarily stored (it may be displayed again), and then, when a time is specified in the work schedule operation area AR3, the selected employee (the temporarily stored employee) is assigned to the specified time. The same applies to the work schedule operation area AR4 (Figure 8).

[0165] The Correction button is used to correct work schedules during the work schedule application period (from one month to one week before a business day) on the work schedule application screen. After pressing the Correction button, employees operate the work schedule operation area AR3 to correct their work schedules.

[0166] Although the work schedule is finalized after the end of the acceptance period for the work schedule application screen (the period from one month to one week before the business day) (one week before the business day), modifications made after the work schedule has been finalized (specifically, during the acceptance period for changes to work shifts via the work schedule change application screen (one week to the day before the business day)) are referred to as "work schedule changes," while modifications made before the work schedule has been finalized (during the acceptance period for the work schedule application screen) are referred to as "work schedule corrections" for distinction. The work schedule application screen in Figure 7 has a correction button, but it is not necessary to have a correction button (that is, it may be possible to correct the work schedule in the work schedule operation area AR3 as appropriate).

[0167] The Execute button is used to confirm the actions taken in the work schedule operation area AR3. The Back button is used to return to the previous screen (work main screen).

[0168] The work shift determination unit 103 determines the work shift based on the information entered into the work shift screen (work schedule application screen). The work shift information, which shows the work shift determined by the work shift determination unit 103, is stored in the work shift information storage unit 104.

[0169] When "Schedule Change" is selected from the work shift screen (main work screen; not shown) on the headquarters terminal 14, it displays the work shift screen (work schedule change request screen) as shown in Figure 8. The headquarters terminal 14 accepts changes to the work schedule via the work schedule change request screen shown in Figure 8 for each business day, from one week before to the day before the business day.

[0170] As shown in Figure 8, the work schedule change request screen includes a work day specification area AR1 for specifying the work day, an employment category specification area AR2 for specifying the employment category, and a work schedule operation area AR4 for accepting work schedule change operations. In addition, the work schedule change request screen in Figure 8 has buttons for forecast details, price confirmation, target product, back, and execute.

[0171] An employee (for example, a manager, or individual employees) operates the work schedule operation area AR4 to change the work schedule for that business day (Month X, Day Y). In the example shown in Figure 8, H's (part-time) shift from 3 PM to 7 PM is deleted, E's (part-time) shift is changed from 10 AM to 3 PM to 10 AM to 5 PM, and F's (part-time) shift from 5 PM to 7 PM is added. In other words, H's shift from 3 PM to 5 PM is changed to E's, and H's shift from 5 PM to 7 PM is changed to F's. Message MS5 notifies the above changes (3 PM to 5 PM: H → E, 5 PM to 7 PM: H → F).

[0172] The forecast details button is used to view detailed forecast results. When the forecast details button is pressed, the headquarters terminal 14 displays the forecast results from the demand forecasting unit 101 (displayed in a pop-up window or by switching to a separate screen).

[0173] The price confirmation button is used to check the planned price (price after change) of the target product. When the price confirmation button is pressed, the headquarters terminal 14 displays a pop-up screen, such as the one shown in Figure 9, on top of the work schedule change request screen. The pop-up screen in Figure 9 displays the planned price of the target product. The headquarters terminal 14 may also switch to a different screen to display the planned price of the target product.

[0174] Furthermore, after the period for accepting changes to work shifts via the work schedule change request screen has ended (for example, before the start of business on a business day), the planned price adjustment unit 203A adjusts (re-determines) the planned price. Therefore, the planned price displayed by operating the price confirmation button mentioned above is a provisional planned price at the time of operation (Figure 3(B)).

[0175] The target product button is a button used to check or verify the target product. When the target product button is pressed, the headquarters terminal 14 displays a screen that allows the user to, for example, check, change, add, or delete the target product (displayed as a pop-up screen or by switching to a separate screen).

[0176] The Execute button is used to confirm the actions taken in the work schedule operation area AR4. The Back button is used to return to the previous screen (work main screen).

[0177] The work shift change unit 200 changes the work shift based on the information entered into the work shift screen (work schedule change request screen). The changes to the work shift made by the work shift change unit 200 are stored in the work shift information storage unit 104.

[0178] Furthermore, the screens shown in Figures 7 to 9 are web pages, and the headquarters terminal 14 may display the screens shown in Figures 7 to 9 using a browser. The screen information of these screens is stored in the work shift management server 12 (a server having the functions of a work shift determination unit 103, a work shift information storage unit 104, and a work shift change unit 200), and the work shift management server 12 may transmit the screen information of the corresponding screen to the headquarters terminal 14 in response to a request from the headquarters terminal 14.

[0179] Figure 10 shows an example of a screen when registering a product. Product aaa is not subject to the planned price (price after change), and its selling price is the standard price of 685 yen. Product eee is subject to the planned price (price after change) (specifically, it is a price-change product with a price higher than the standard price), and its selling price is the changed price of 395 yen (standard price is 380 yen).

[0180] During the registration process, the registration and payment device 20A reads the membership card of customer "○○" and, when scanning the barcode of product aaa as the first item, displays a registration screen as shown in Figure 10(A) on the employee's display unit and a customer confirmation screen as shown in Figure 10(B) on the customer's display unit.

[0181] For example, in the product area AR11 of the registration screen in Figure 10(A), information for product aaa (product name "aaa", sales price "¥685") is displayed as the most recently registered product. In the product details area AR12 of the registration screen in Figure 10(A), information for product aaa (product name "aaa", sales price "¥685") is displayed as a single product item. In the product details area AR22 of the customer confirmation screen in Figure 10(B), information for product aaa (product name "aaa", sales price "¥685") is displayed as a single product item.

[0182] When the barcode of product eee is scanned as the second item in the scenario shown in Figures 10(A) and 10(B), the registration and settlement device 20A displays a pop-up screen SG13 as shown in Figure 10(C) in front of the registration screen shown in Figure 10(A) on the employee's display unit, and displays a pop-up screen SG23 as shown in Figure 10(D) in front of the customer confirmation screen shown in Figure 10(B) on the customer's display unit.

[0183] The customer-facing pop-up screen SG23 displays buttons (purchase button, do not purchase button) to confirm the customer's intention to purchase price-varying product eee, which is priced higher than the standard price. The employee-facing pop-up screen SG13 also displays similar buttons (purchase button, do not purchase button).

[0184] If the customer presses the "Do Not Purchase" button on the pop-up screen SG23, the registration and payment device 20A simply clears the pop-up screen SG13 on the staff-side display and displays the registration screen shown in Figure 10(A), and the customer-side display simply clears the pop-up screen SG23 and displays the customer confirmation screen shown in Figure 10(B). In other words, the registration and payment device 20A does not register product eee if the customer presses the "Do Not Purchase" button on the pop-up screen SG23. The same applies if the customer presses the "Do Not Purchase" button on the pop-up screen SG13.

[0185] When the purchase button on the pop-up screen SG23 is pressed (by the customer), the registration and payment device 20A clears the pop-up screen SG13 on the staff-side display and displays the registration screen shown in Figure 10(E), and clears the pop-up screen SG23 on the customer-side display and displays the customer confirmation screen shown in Figure 10(F). In other words, when the purchase button on the pop-up screen SG23 is pressed, the registration and payment device 20A registers product eee. The same applies when the purchase button on the pop-up screen SG13 is pressed (by the staff).

[0186] In the registration screen of Figure 10(E), the relevant product area AR11 displays "(Price-Variable Product)" to indicate that product eee is a price-variable product. In the product details area AR12 of the registration screen of Figure 10(E), the revised price ("¥395") and the difference ("(+¥15)") are displayed for the two product eee items. In the product details area AR22 of the customer confirmation screen of Figure 10(F), the revised price ("¥395") and the difference ("(+¥15)") are displayed for the two product eee items. Note that the customer confirmation screen of Figure 10(F) may also display that product eee is a price-variable product.

[0187] (Decision-making system) The decision server 10 makes decisions on various matters (Figures 2 to 6). Therefore, the system that includes at least the decision server 10 within the headquarters system H (i.e., the system consisting of the decision server 10 alone, or the system consisting of the decision server 10 plus one or more other servers) may be referred to as the decision system. For example, a system that includes the planned price determination unit 110A (or the planned coupon determination unit 110B, or the planned point determination unit 110C, or the planned allowance determination unit 110D) may be referred to as the decision system. A system that includes the return unit 302 may also be referred to as the decision system. A system that includes the demand forecasting unit 101 and the planned price determination unit 110A may also be referred to as the decision system. The headquarters terminal 14 may also be included and referred to as the decision system.

[0188] Furthermore, since the decision system is a system that processes a wide range of store-related information, such as product information and coupon information, the decision system may also be referred to as the store information system or store information processing system. In addition, the decision system, store information system, or store information processing system may also include one or more devices on the headquarters system H side (decision server 10, etc.) as well as one or more devices on the store system S (registration and settlement device 20, etc.).

[0189] As described above, the embodiments allow for more favorable sales and other operations. For example, it can improve customer and employee satisfaction.

[0190] For example, according to the configuration shown in Figure 2, the price of the product (selling price) is controlled for each business day according to the expected busy / slow conditions (demand forecast) and the labor costs of employees scheduled to work (planned labor costs). (The price after the change is stored as the planned price in the special sale information storage unit 111.) This allows the product to be sold at a suitable price according to the busy / slow conditions and labor costs. This contributes, for example, to improving customer satisfaction. For example, according to the configuration in Figure 4 (Another Example 1), the provision of coupons to customers is controlled for each business day according to the expected busy / slow state and the labor costs of the employees scheduled to work (stored in the coupon storage unit 306 as planned coupons). This allows for the provision of coupons to customers appropriately according to the expected busy / slow state and planned labor costs. This contributes, for example, to improving customer satisfaction. According to the configuration in Figure 5 (Another Example 2), the awarding of points to customers is controlled for each business day according to the expected busy / slow periods and the labor costs of the employees scheduled to work (stored as planned points in the point storage unit 307). This allows for the appropriate awarding of points to customers according to the expected busy / slow periods and planned labor costs. This contributes, for example, to improving customer satisfaction. According to the configuration in Figure 6 (Another Example 3), the system controls the provision of allowances to employees scheduled to work according to the expected busy / slow conditions and the labor costs of the employees scheduled to work on each business day (by storing them as planned allowances in the allowance storage unit 308). This allows for the appropriate provision of allowances to employees on a given day according to the expected busy / slow conditions and planned labor costs. This contributes, for example, to improving employee and customer satisfaction. Furthermore, according to the configuration in Figure 2 (and similarly for the configurations in Figures 4 to 6), after business hours, an evaluation is conducted (evaluation unit 300), and if necessary, rewards are given to customers and employees (coupon rewards, point rewards, allowance rewards) (reward unit 302). This can, for example, further increase customer and employee satisfaction.

[0191] (Variations, etc.) The embodiments have been described above, but the configuration of the equipment, the data configuration, the processing flow, the display and output modes, etc., can be changed as appropriate, for example, as shown in (1) to (18) below. Furthermore, (1) to (18) below can be combined as appropriate.

[0192] (1) In the above embodiment, examples of providing coupons and points to customers were described, but the things that can be provided to customers are not limited to these. For example, cashback may be provided to customers (e.g., bank transfer, electronic money charge, etc.). Also, in the above embodiment, examples of providing allowances to employees were described, but the things that can be provided to employees are not limited to these. For example, since employees are also consumers, coupons and points may also be provided to employees.

[0193] (2) In the above embodiment, it was explained that work shifts may be determined considering the forecast results (dashed arrow Y in Figure 2), but as explained, it is not necessary to determine work shifts considering the forecast results. When work shifts are determined considering the forecast results, it is possible to balance them with the forecast results of the demand forecast to some extent at the stage of determining work shifts, but even when work shifts are not determined considering the forecast results, it is possible to balance them using planned prices, etc. (planned price, planned coupons, planned points, planned allowances).

[0194] (3) In the above embodiment, an example of adjusting planned prices, etc. in accordance with changes in work shifts has been described (planned price adjustment unit 203A, planned coupon adjustment unit 203B, planned point adjustment unit 203C, planned allowance adjustment unit 203D), but it is not necessary to adjust planned prices, etc. If adjustments are made to planned prices, etc., products can be sold at the planned price on the day of business, or coupons, points, and allowances can be given in accordance with the actual situation (labor costs based on the changed work shifts), but even if adjustments to planned prices, etc. are not made, compensation can be made after the end of business hours through reward coupons, reward points, and reward allowances (retroactive adjustments).

[0195] (4) In the above embodiment, an example of making a refund after closing time was described based on the actual sales amount, actual labor costs (initial planned labor costs if not adjusted, and adjusted planned labor costs if adjusted), and the refunded amount (amount already refunded based on the planned price, the converted amount of planned coupons already refunded, the converted amount of planned points already refunded, and the converted amount of planned allowances that have already been decided to be refunded). However, it is also possible to make a refund after closing time without calculating the amount already refunded. For example, although the accuracy will be rougher, the refund may be based on the amount of sales exceeding the standard sales (sales corresponding to actual labor costs), or the refund may be based on an amount obtained by multiplying the excess amount by an appropriate coefficient (for example, 0.8).

[0196] (5) In the above embodiment, an example of providing a return after business hours was described, but it is not necessary to provide a return after business hours. Even if a return is not provided after business hours, a return (a certain benefit to customers or employees) may already be provided through the planned price, etc.

[0197] (6) In the above embodiment, an example was described in which standard labor costs are obtained (specified) using the results of the demand forecast (forecasted sales, forecasted number of visitors), and the planned price etc. is determined based on the standard labor costs and the planned labor costs (determining the planned price, deciding on the provision of planned coupons, deciding on the provision of planned points, deciding on the provision of planned allowances). However, the planned price etc. may also be determined based on the results of the demand forecast and the planned labor costs. In other words, in the above embodiment, the planned price etc. is determined by comparing the standard labor costs obtained from the results of the demand forecast with the planned labor costs, but the planned price etc. may also be determined by directly comparing the results of the demand forecast with the planned labor costs.

[0198] (7) In the above embodiment, an example was described in which standard labor costs are obtained (specified) using the results of the demand forecast (predicted sales, predicted number of visitors), but standard labor costs may also be obtained without using the demand forecast. For example, standard labor cost information (or a formula or table for obtaining the standard labor costs for each day of the year) showing the standard labor costs for each day of the year may be stored, and the standard labor costs for each business day may be obtained (specified) by referring to the standard labor cost information, etc. In other words, in the above embodiment, an example was described in which the planned price, etc. is determined based on the demand forecast and planned labor costs, but the planned price, etc. may also be determined based on the planned labor costs without using the demand forecast.

[0199] (8) In the above embodiment, an example was described in which the estimated price, etc., is determined based on standard labor costs and estimated labor costs, but the estimated price, etc., may be determined without using standard labor costs. In other words, the estimated price, etc., may be determined using at least estimated labor costs.

[0200] For example, a table (or formula) showing the relationship between labor costs and profit amount (gross profit, operating profit, etc.) or profit margin (gross profit margin, operating profit margin, etc.) is prepared (for example, stored in the memory of the decision server 10). When a labor cost is input, the above table (or formula) outputs the profit amount or profit margin corresponding to that labor cost.

[0201] The planned price determination unit 110A uses the above table (or formula) to identify (obtain) the planned profit amount, etc. (planned profit amount or planned profit margin) corresponding to the planned personnel costs. The planned price determination unit 110A may determine a price higher than the standard price as the planned price if the planned profit amount, etc. is less than the first benchmark value (for example, the lower the planned profit amount, etc., the higher the planned price determined), or determine a price lower than the standard price as the planned price if the planned profit amount, etc. is greater than the second benchmark value (for example, the higher the planned profit amount, etc., the lower the planned price determined). Note that the second benchmark value ≥ the first benchmark value.

[0202] Furthermore, the planned coupon determination unit 110B uses the above table (or formula) to identify (obtain) the planned profit amount, etc., corresponding to the planned personnel costs. The planned coupon determination unit 110B may decide not to grant a planned coupon if the planned profit amount, etc., is less than the first threshold value, and may decide to grant a planned coupon if the planned profit amount, etc., is greater than the second threshold value.

[0203] Furthermore, the planned points determination unit 110C uses the above table (or formula) to identify (obtain) the planned profit amount, etc., corresponding to the planned personnel costs. The planned points determination unit 110C may decide not to award planned points if the planned profit amount, etc., is less than the first threshold value, and may decide to award planned points if the planned profit amount, etc., is greater than the second threshold value.

[0204] Furthermore, the planned allowance determination unit 110D uses the above table (or formula) to identify (obtain) the planned profit amount, etc., corresponding to the planned personnel costs. The planned allowance determination unit 110D may also decide not to grant a planned allowance if the planned profit rate is less than the first threshold value, and decide to grant a planned allowance if the planned profit rate exceeds the second threshold value.

[0205] (9) In the above embodiments, an example was described in which changes to work schedules are accepted from one week before to the day before each business day, but the period for accepting changes to work shifts is not limited to this. For example, changes to work shifts may be accepted during the time when work can be set, including during business hours on the business day (in the examples of Figures 7 and 8, from 8:00 to 20:00, including the business hours of 10:00 to 17:00).

[0206] If a work schedule is accepted during business hours and a change occurs in the price of a product (for example, if a product sold at the standard price becomes priced differently from the standard price, or if a product sold at a revised price becomes priced at the standard price (or another revised price)), the revised price may be reflected immediately (for example, it may be reflected whether the price has increased or decreased, or it may be reflected only if the price has decreased and not if it has increased, or it may be reflected if the price has increased but not if it has decreased).

[0207] For example, if full-time employee B, who is on duty at 3 PM (scheduled to work from 12 PM to 8 PM), leaves early due to illness, and part-time employee K is suddenly asked to work from 4 PM to 7 PM (closing time), the sales price may change between 3 PM and 4 PM, and further, the sales price may change between 4 PM and 7 PM. For example, if B requests to leave early at 2:30 PM, K will be arranged to work from 2:30 PM onwards, but the calculation of the price change (i.e., the change in schedule) may be done after B's request and before K's arrangement is completed, or after K's arrangement is completed.

[0208] Furthermore, even during business hours, there is still time remaining until closing time, so it is understood to be a "schedule," but since the situation can change moment by moment, it may also be considered a change in the current situation. In other words, for example, the selling price of a product may be changed according to the actual arrival / departure time. For example, if an employee scheduled to work does not arrive at the scheduled arrival time (for example, if they do not scan their ID card at the attendance management device), the price of a certain product may be increased from its original price, and if that employee arrives 30 minutes after the scheduled arrival time (for example, if they scan their ID card at the attendance management device), the price of that product may be returned to its original price.

[0209] (10) In the above embodiment, an example was described in which the price of one or more products is increased or decreased according to labor costs (work shifts), but the subtotal price may also be increased or decreased according to labor costs (work shifts). In other words, for example, when labor costs are relatively low (when the number of employees is relatively small or when there is a large proportion of employees with lower unit prices), the original subtotal price may be discounted instead of or in addition to lowering the price of one or more products, and when labor costs are relatively high (when the number of employees is relatively large or when there is a large proportion of employees with higher unit prices), an additional amount may be added to the original subtotal price instead of or in addition to raising the price of one or more products.

[0210] (11) In the above embodiment, an example of determining the planned price, etc. on a one-business-day basis was described, but the unit for determining the planned price, etc. does not have to be one business day. For example, the planned price, etc. may be determined on a half-day basis, a two-business-day basis, or a three-business-day basis. In other words, the planned price determination unit 110A may determine the planned price for a predetermined period. The planned coupon determination unit 110B may determine the granting of planned coupons for a predetermined period. The planned point determination unit 110C may determine the granting of planned points for a predetermined period. The planned allowance determination unit 110D may determine the granting of planned allowances for a predetermined period.

[0211] For example, the planned price determination unit 110A may determine the planned price for a half-day period using information on half-day work shifts (planned labor costs for a half-day period) and standard labor costs for a half-day period (or the results of a demand forecast), or using information on half-day work shifts and planned profit amounts for a half-day period. Alternatively, the planned price determination unit 110A may determine the planned price for a two-business-day period using information on two-business-day work shifts (planned labor costs for a two-business-day period) and standard labor costs for a two-business-day period (or the results of a demand forecast), or using information on two-business-day work shifts and planned profit amounts for a two-business-day period. The same applies to the planned coupon determination unit 110B, the planned point determination unit 110C, and the planned allowance determination unit 110D.

[0212] If the planned price for a predetermined period is determined, or if the provision of planned coupons (or planned points or planned allowances) for a predetermined period is determined, the evaluation unit 300 may evaluate for the predetermined period, and the reward unit 302 may provide rewards (determine the contents of the reward coupons, the contents of the reward points, or the contents of the reward allowances) for the predetermined period.

[0213] (12) In the above embodiment, an example was described in which the planned price, etc., is determined based on the work shifts of all employees (e.g., full-time employees, part-time employees, temporary employees, etc.). However, the planned price, etc., may be determined based on the work shifts of employees whose attendance is relatively fluid (part-time employees, temporary employees). In other words, the planned labor costs and standard labor costs may apply to employees of a specific employment category (e.g., part-time employees, temporary employees). Also, the employees to whom planned allowances and bonuses are paid may be employees of a specific employment category (e.g., part-time employees, temporary employees).

[0214] (13) In the above embodiment, employee information including employment categories (e.g., full-time employee, part-time employee, temporary worker, etc.) as data items has been described, but employee information may also include job categories (e.g., cashier, inventory management (inspection, stocking, ordering, etc.), customer service, etc.) as data items. In other words, in the above embodiment, an example of managing employment categories has been described, but job categories may be managed in place of or in addition to employment categories.

[0215] In a manner of managing work categories, planned prices, etc., may be determined based on the work shifts of employees in a specific work category. In other words, planned labor costs and standard labor costs may apply to employees in a specific work category. Furthermore, employees to whom planned allowances and bonuses are paid may also be employees in a specific work category.

[0216] (14) In the above embodiment, an example was described in which the decision server 10 comprises a personnel cost calculation unit 106 (planned personnel cost calculation unit 107, modified personnel cost calculation unit 201), a personnel cost storage unit 108 (planned personnel cost storage unit 109, modified personnel cost storage unit 202), a planned price determination unit 110A, a planned price adjustment unit 203A, an evaluation unit 300, a rebate unit 302 (coupon rebate unit 303, point rebate unit 304, allowance rebate unit 305), a planned coupon determination unit 110B, a planned coupon adjustment unit 203B, a planned point determination unit 110C, a planned point adjustment unit 203C, a planned allowance determination unit 110D, and a planned allowance adjustment unit 203D. However, some of the above components may be provided by other devices. In other words, each of the above components may be distributed across two or more devices instead of being contained in a single device (decision server 10).

[0217] (15) In the above embodiment, the decision server 10 was described as being included in the headquarters system H, but the location of the decision server 10 is not particularly limited. For example, the decision server 10 may be a cloud server installed in an IDC or the like. The same applies to the other servers. Also, the locations of each server do not have to be the same. For example, the decision server 10 and the demand forecasting server 11 may be installed in different locations.

[0218] (16) In the above embodiment, multiple servers have been described, but the functions of two or more servers may be implemented in a single server. For example, the decision server 10 and the demand forecasting server 11 may be implemented as the same server. Alternatively, all servers may be integrated into a single server. (17) In the above embodiment, the headquarters terminal 14 was described as a terminal capable of communicating with one or more servers, but the headquarters terminal 14 and one or more servers may be configured as an integral part of the system (one server may have the functions of the headquarters terminal 14, or the headquarters terminal 14 may have the functions of one server). For example, a work shift management server 12 (a server having the functions of a work shift determination unit 103, a work shift information storage unit 104, and a work shift change unit 200) and a headquarters terminal 14 (a terminal having the function of displaying a work shift screen, etc.) may be configured as an integral part of the system.

[0219] (18) In the above embodiment, the store system S and the headquarters system H were described as being applicable to supermarkets, convenience stores, drugstores, home centers, consumer electronics retailers, etc., but they can also be applied to various types of businesses such as hotels, inns, karaoke bars, restaurants, internet cafes, barber shops, nail salons, etc.

[0220] For example, in a restaurant, if there are too few kitchen staff, the service may be slow, and if there are too few service staff, the service may deteriorate. Therefore, in a restaurant where the time it takes to serve food is an issue, as related to (13) above, planned prices may be determined based on the kitchen staff. Similarly, in a restaurant where the deterioration of service is an issue, as related to (13) above, planned prices may be determined based on the service staff. In drugstores, home centers, electronics retailers, etc., planned prices may be determined based on the employees performing specific tasks related to solving the problem.

[0221] <Summary of Embodiments> [Technical field] This invention relates to a decision system. [Background technology] A system is known that determines how to display products based on sales forecasts (see, for example, Patent Document 1). [Prior art document] [Patent] [Patent Document 1] Japanese Unexamined Patent Publication No. 2004-199237 [Overview of the prefecture] [Problems the invention aims to solve] However, there is room for improvement regarding the sale of products. This invention has been made in view of these circumstances, and aims to provide a technology for more favorably selling products. [Means for solving the problem]

[0222] (1) One embodiment for solving the above-mentioned problems is a decision system comprising a labor cost calculation unit (e.g., labor cost calculation unit 106) that calculates the planned labor costs for a predetermined period of time (e.g., one business day, half a day, two business days, three business days, etc.) of a store, and a price determination unit (e.g., planned price determination unit 110A) that determines the planned price of goods for a predetermined period of time at the store using the planned labor costs for the predetermined period calculated by the labor cost calculation unit. According to the configuration of (1), products can be sold (or services can be provided) more effectively. For example, customer satisfaction can be improved.

[0223] (2) One embodiment for solving the above-mentioned problems is a decision system comprising a labor cost calculation unit (e.g., labor cost calculation unit 106) that calculates the planned labor costs for a predetermined period of time (e.g., one business day, half a day, two business days, three business days, etc.) of a store, and a benefit granting decision unit (e.g., planned coupon decision unit 110B, planned point decision unit 110C) that uses the planned labor costs for the predetermined period calculated by the labor cost calculation unit to decide on the granting of benefits (e.g., coupons, points, etc.) for the store during the predetermined period. According to the configuration of (2), products can be sold (or services can be provided) more effectively. For example, customer satisfaction can be improved.

[0224] (3) One embodiment for solving the above-mentioned problems is a decision system comprising a labor cost calculation unit (e.g., labor cost calculation unit 106) that calculates the planned labor costs for a predetermined period of time (e.g., one business day, half a day, two business days, three business days, etc.) of a store, and a bonus payment decision unit (e.g., planned bonus payment decision unit 110D) that uses the planned labor costs for the predetermined period calculated by the labor cost calculation unit to decide on the payment of bonuses to employees who come to work at the store during the predetermined period. According to the configuration of (3), products can be sold (or services can be provided) more effectively. For example, employee and customer satisfaction can be improved.

[0225] (4) The determination system described in (1) determines the planned price of goods for a specified period at the store based on the standard labor costs for a specified period at the store and the planned labor costs for a specified period calculated by the labor cost calculation unit. According to the configuration of (4), the planned price can be suitably determined using standard labor costs.

[0226] (5) The decision system described in (2) determines whether to grant benefits to the store during a specified period based on the standard labor costs for the store during a specified period and the planned labor costs for the specified period calculated by the labor cost calculation unit. According to the configuration of (5), the granting of benefits can be suitably determined using standard personnel costs.

[0227] (6) The decision system described in (3) determines the amount of allowances to be paid to employees who work at the store during a specified period, based on the standard labor costs for the store during a specified period and the planned labor costs for the specified period calculated by the labor cost calculation unit. According to the configuration of (6), it is possible to suitably determine the provision of allowances to employees using standard labor costs.

[0228] (7) The decision system described in (4) to (6), comprising a demand forecasting unit that forecasts the demand for the store for a specified period, and a standard labor cost acquisition unit that acquires standard labor costs using the forecast results from the demand forecasting unit. According to the configuration of (7), the accuracy of standard labor costs is improved, making it possible to more favorably determine planned prices, the granting of benefits, and the granting of allowances.

[0229] (8) The determination system described in (7), which includes a notification unit that notifies the system that the difference between the standard labor costs and the planned labor costs has exceeded a predetermined value when According to the configuration of (8), it is possible to recognize that the difference between standard labor costs and planned labor costs exceeds a predetermined value.

[0230] (9) The decision system described in (1) to (6) includes a display unit (e.g., headquarters terminal 14) that displays a work shift screen (e.g., Figures 7 and 8) that can accept operations to specify employees who are scheduled to come to work, and a work shift determination unit (e.g., work shift determination unit 103) that determines the work shifts of employees based on the information entered via the work shift screen, wherein the personnel cost calculation unit calculates the planned personnel costs for a predetermined period using the work shift information that shows the work shifts determined by the work shift determination unit. According to the configuration of (9), work shifts can be easily determined and planned personnel costs can be calculated.

[0231] Furthermore, the processing of each of the above-described devices (for example, the devices shown in Figure 1) may be performed by recording a program for realizing the functions of each device on a computer-readable recording medium, loading the program recorded on this recording medium into a computer system, and executing it. Here, "loading the program recorded on the recording medium into a computer system and executing it" includes installing the program into the computer system. Here, "computer system" includes hardware such as the OS and peripheral devices. Also, "computer system" may include multiple computer devices connected via a network including communication lines such as the Internet, WAN, LAN, and dedicated lines. Also, "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, CD-ROMs, and storage devices such as hard disks built into the computer system. Thus, the recording medium storing the program may also be a non-transient recording medium such as a CD-ROM. Also, the recording medium includes internal or external recording media that can be accessed from the distribution server for distributing the program. The program code stored on the distribution server's recording medium may be different from the program code in a format executable by the terminal device. In other words, the format in which the program is stored on the distribution server is irrelevant, as long as it can be downloaded from the distribution server and installed in an executable format on the terminal device. Furthermore, the program may be divided into multiple parts, each downloaded at a different time and then combined on the terminal device, and different distribution servers may distribute each of the divided programs. In addition, "computer-readable recording medium" includes volatile memory (RAM) within computer systems that act as servers or clients when a program is transmitted over a network, which retains the program for a certain period of time. Moreover, the program may be intended to implement only a part of the functions described above. Furthermore, the program may be a so-called differential file (differential program) that can implement the functions described above in combination with a program already recorded in the computer system. [Explanation of symbols]

[0232] 10...Decision Server, 11...Demand Forecasting Server, 12...Work Shift Management Server, 13A...Transaction Server, 13B...History Management Server, 13C...Product Management Server, 13D...Customer Management Server, 13E...Special Sale Management Server (Variable Price Management Server), 13F...Coupon Management Server, 13G...Employee Management Server, 13H...Allowance Management Server, 14...Head Office Terminal, 20...Registration and Settlement Device, 21...Registration Device, 22...Settlement Device

Claims

1. A labor cost calculation unit that calculates the planned labor costs for a store for a specified period, A price determination unit determines the planned price of goods for a predetermined period at the store using the planned labor costs for a predetermined period calculated by the labor cost calculation unit. A decision-making system equipped with the following features.

2. A labor cost calculation unit that calculates the planned labor costs for a store for a specified period, A benefit granting determination unit determines the granting of benefits to the store during a predetermined period, using the planned personnel costs for a predetermined period calculated by the aforementioned personnel cost calculation unit. A decision-making system equipped with the following features.

3. A labor cost calculation unit that calculates the planned labor costs for a store for a specified period, A Allowance Grant Decision Unit determines the granting of allowances to employees who work at the store during a specified period, using the planned personnel costs for a specified period calculated by the aforementioned personnel cost calculation unit. A decision-making system equipped with the following features.

4. The determination system according to claim 1, which determines the planned price of goods for a predetermined period at a store based on the standard labor costs for a predetermined period at the store and the planned labor costs for a predetermined period calculated by the labor cost calculation unit.

5. The decision system according to claim 2, which determines the provision of benefits to a store during a predetermined period based on the standard labor costs of the store during a predetermined period and the planned labor costs of the store during a predetermined period calculated by the labor cost calculation unit.

6. The decision system according to claim 3, which determines the provision of allowances to employees who work at the store during a predetermined period, based on the standard labor costs for the store during a predetermined period and the planned labor costs for the predetermined period calculated by the labor cost calculation unit.

7. A demand forecasting unit that predicts the demand for the store for a specified period, A standard labor cost acquisition unit that acquires standard labor costs using the forecast results from the aforementioned demand forecasting unit. A determination system according to any one of claims 4 to 6, comprising:

8. If the difference between the standard labor costs for a predetermined period obtained by the standard labor cost acquisition unit and the planned labor costs for a predetermined period calculated by the labor cost calculation unit exceeds a predetermined value, the notification unit will notify that the difference between the standard labor costs and the planned labor costs has exceeded a predetermined value. The determination system according to claim 7, comprising:

9. A display unit that shows a work shift screen that allows the user to specify employees scheduled to work, A work shift determination unit that determines the work shifts of employees based on the information entered via the work shift screen. Equipped with, The aforementioned personnel cost calculation unit, The decision system according to any one of claims 1 to 6, which calculates the planned labor costs for a predetermined period using work shift information indicating the work shifts determined by the work shift determination unit.

Images