Product data processing device and program

Abstract

To provide a technology that enables information for determining delivery timing to be provided for a producer.SOLUTION: Provided is a commodity data processing device for selling a commodity delivered by a producer at a shop, including: input means to which commodity information indicating the commodity delivered by the producer is input; storage means for storing shipment time information indicating a time point when the commodity information is input by the input means and the commodity information on the delivered commodity in association with each other; acquisition means for acquiring information concerning sales of the commodity delivered by the producer; and display means for displaying the information concerning sales of the commodity delivered by the producer as acquired by the acquisition means, and displaying the shipment time information.SELECTED DRAWING: Figure 17

Description

[Technical field]

[0001] The present invention relates to a product data processing device and a program. [Background technology]

[0002] At farmer's markets, operators often sell products on behalf of producers, such as farmers. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2007-156952 A Summary of the Invention [Problem to be solved by the invention]

[0004] Each producer delivers their goods (e.g. agricultural products) to the farmer's shop, enters the products to be delivered, and then displays them. Since producers deliver their products at their own pace, they may miss the best selling times. Also, even if there are tools for production management, they may leave without realizing it.

[0005] The present invention has been made in view of the above circumstances, and has an object to provide a technique capable of providing producers with information for determining delivery timing. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems, one aspect of the present invention is a product data processing device for selling products delivered by producers in a store, and is characterized in that it has an input means for inputting product information indicating the products delivered by the producer, a storage means for linking and storing shipping time information indicating the time when the product information was input by the input means with the product information of the delivered products, an acquisition means for acquiring information regarding sales of the products delivered by the producer, and a display means for displaying the information regarding sales of the products delivered by the producer acquired by the acquisition means and displaying the shipping time information.

[0007] In order to solve the above-mentioned problems, one aspect of the present invention is a program that causes a computer to function as a product data processing device for selling products delivered by producers in a store, and is characterized in that it causes the computer to function as an input means for inputting product information indicating the products delivered by the producer, a storage means for linking and storing shipping time information indicating the time when the product information was input by the input means with the product information of the delivered products, an acquisition means for acquiring information regarding sales of the products delivered by the producer, and a display means for displaying the information regarding sales of the products delivered by the producer acquired by the acquisition means and displaying the shipping time information. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a conceptual diagram of a POS system network. [Diagram 2] FIG. 2 is a diagram showing an example of installation of a POS terminal 20. [Diagram 3] FIG. 1 is a diagram illustrating an example of the appearance of a POS terminal. [Figure 4] FIG. 2 is a diagram illustrating an example of the configuration of a POS terminal. [Diagram 5] FIG. 1 is a diagram illustrating an example of the appearance of a label printer. [Figure 6] FIG. 1 illustrates an example of the configuration of a label printer. [Figure 7]FIG. 2 is a diagram showing a configuration of a mobile terminal. [Figure 8] FIG. 13 is a diagram showing an example of a standby screen of the mobile terminal. [Figure 9] FIG. 13 is a diagram showing an example of a screen for a producer. [Figure 10] FIG. 13 is a diagram showing an example of a quantity input screen. [Figure 11] FIG. 13 is a diagram showing an example of a quantity input screen. [Figure 12] FIG. 13 illustrates a login screen. [Figure 13] FIG. 13 is a diagram showing an example of a disposal-related screen. [Figure 14] FIG. 13 is a diagram showing an example of a store sales screen. [Figure 15] FIG. 13 is a diagram showing an example of a store sales screen. [Figure 16] FIG. 13 illustrates a login screen. [Figure 17] FIG. 13 is a diagram showing an example of a producer sales screen. [Figure 18] FIG. 13 is a diagram showing an example of a producer sales screen. [Figure 19] 11 is a flowchart showing a transition of a display screen. [Figure 20] 11 is a flowchart showing a transition of a display screen. [Figure 21] FIG. 13 is a diagram showing an example of an email. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Fig. 1 is a conceptual diagram of a network including a POS (Point Of Sales) system 1. The POS system 1 shown in Fig. 1 includes a POS terminal 20, a management device 301, and a label printer 302. The POS terminal 20, the management device 301, and the label printer 302 are communicatively connected via an in-house network NWA such as a LAN (Local Area Network). The POS system 1 may include a plurality of POS terminals 20 and label printers 302.

[0010] The network NWA is connected to a wide area network NWB such as a wide area network (WAN). The producer terminal 303 is connected to the NWB. The producer terminal 303 is a terminal such as a smartphone owned by the producer.

[0011] The POS system 1 in this embodiment is installed in a direct sales outlet (hereinafter simply referred to as a "store") where products delivered by producers are sold on consignment. The management device 301 may be a stationary PC (Personal Computer), a portable PC, or a tablet, and multiple units may be installed in the store. The management device 301 is placed in a specific location in the store so that the producer can operate and view it at all times.

[0012] The management device 301 stores various information necessary for transactions, such as a product master. The product master is a file that stores product information such as product identification information for each product (a store-specific code or a JAN (Japanese Article Number) code, hereafter referred to as "product code"), product name, and sales price. In addition to the product master, the management device 301 also stores various information such as inventory status, sales history, and deposit and withdrawal records. Furthermore, the management device 301 generates product codes for products delivered by manufacturers, and registers the products to be delivered and their quantities.

[0013] The management device 301 sequentially acquires information related to sales from the POS terminal 20. In addition, the management device 301 acquires the final sales results of the POS terminal 20 through a closing operation of the POS terminal 20. The management device 301 provides information related to products stored as product master data to the label printer 302. The label printer 302 notifies the management device 301 of the printing results of price tags, which will be described later. Note that when a store has multiple POS terminals 20, instead of the management device 301, one POS terminal 20 may be made to execute the functions of the management device 301.

[0014] The POS terminal 20 executes product registration processing and payment processing for the products registered by the registration processing in response to operations by store clerks in the store. Note that the POS system 1 may be provided with a ticket vending machine in addition to the POS terminal 20. The ticket vending machine is a device that executes product registration processing and payment processing in response to operations by customers, and issues tickets (e.g., meal tickets) to be exchanged for products.

[0015] The label printer 302 is a small, portable printing device. The label printer 302 prints price tags to be attached to products delivered by manufacturers. Product names and symbols (barcodes or two-dimensional symbols (two-dimensional codes)) are printed on the price tags.

[0016] Fig. 2 is a diagram showing an example of installation of a POS terminal 20 according to an embodiment of the present invention. Fig. 2(A) is a perspective view of the POS terminal 20, etc., as seen from the customer side. Fig. 2(B) is a perspective view of the POS terminal 20, etc., as seen from the store clerk side. As shown in Fig. 2(A), a counter is placed to the right of the POS terminal 20 as seen from the customer side.

[0017] Fig. 3 is a diagram showing an example of the appearance of the POS terminal 20. Fig. 3(A) is a perspective view of the POS terminal 20 as seen from the customer side. Fig. 3(B) is a perspective view of the POS terminal 20 as seen from the store clerk side. In Fig. 3, the same parts are given the same reference numerals.

[0018] An example of the configuration of the POS terminal 20 will be described below with reference to Fig. 4. The POS terminal 20 comprises a CPU 201, a ROM 202, a RAM 203, a hard disk 204, a customer display unit 205, a customer scanner unit 206, a card payment unit 208, a store clerk display unit 210, a key operation unit 211, a store clerk scanner unit 212, a printing unit 213, an audio output unit 214, and a communication unit 215. These can communicate with each other via a bus.

[0019] The CPU 201 is a central processing unit, and controls the operation of the POS terminal 20 by reading and executing programs stored in the ROM 202. The ROM 202 is a read-only memory, and stores various types of information used by the CPU 201, including programs.

[0020] The RAM 203 is a read / write memory and stores various information. For example, the RAM 203 stores information acquired from the outside (e.g., a product master acquired from the management device 301, etc.) and information generated in the process (e.g., registration information (registration data) generated in a registration process for registering products, settlement information generated in a settlement process for settling (paying) purchased products, etc.).

[0021] The hard disk 204 stores various information. For example, the hard disk 204 may store programs executed by the CPU 201 instead of the ROM 202. Also, instead of the RAM 203, the hard disk 204 may store information acquired from the outside and information generated during processing.

[0022] <Customer side display> The customer-side display unit 205 is a touch display for customers, which displays various information to customers and accepts various inputs from customers. The customer side scanner unit 206 is a scanner unit for customer use, and optically reads various information. For example, the customer-side scanner unit 206 optically reads bar codes (product codes, etc.) attached to products and codes (bar codes, two-dimensional codes, etc.) printed on receipts (registered trademarks). In addition to the above, the customer-side scanner unit 206 may also read codes (bar codes, two-dimensional codes, etc.) printed on gift certificates (gift certificates, coupons, and complimentary coupons) and various cards (e.g., membership cards, point cards, etc.).

[0023] Although the customer-side scanner unit 206 is used when a customer registers a product, the customer may register the product by other methods. For example, if a preset key (a button for ordering the product) corresponding to the product is displayed on the customer-side display unit 205, the customer may operate (press) the preset key to register the product.

[0024] The card payment unit 208 is a payment mechanism using various cards (credit cards, prepaid cards such as transportation cards, point cards, etc.). The card payment unit 208 includes a card recognition unit (reading unit), a display unit, and an operation unit. The card recognition unit magnetically or electrically reads information on various cards. The read information is used for payment (settlement) of the purchased items. The card recognition unit may recognize various cards not only when the recognized information is used for payment (settlement) of the purchased items (i.e., in the case of credit card payment, prepaid card payment, and the use (consumption) of points held on a point card), but also when the recognized information is not used for payment (settlement) of the purchased items (for example, when a special offer is given by presenting a credit card, when points are given to a point card, etc.). The card payment unit 208 of this embodiment includes a card recognition unit (reading unit), a display unit, and an operation unit, but the card payment unit 208 may include at least a card recognition unit. Further, the card recognition unit in this embodiment is compatible with contact cards (IC cards, magnetic cards), but may be compatible with non-contact cards (IC cards) instead of or in addition to contact cards.

[0025] The settlement unit 209 (cash settlement unit) is a cash settlement mechanism, and has an input port for banknotes and coins, an output port for banknotes and coins, etc., and calculates the amount inserted into the input port, calculates the change amount which is the difference between the input amount and the purchase amount, and outputs the change from the output port. The settlement unit 209 faces the customer and is operated by the customer. When banknotes or coins are inserted into the input port, they are detected by a sensor (detecting that they have been inserted, detecting the number of coins by denomination, etc.). The card settlement unit 208 and the settlement unit 209 form the settlement unit.

[0026] <Staff display section> The store clerk's display unit 210 is a touch display for the store clerk, which displays various information to the store clerk and receives various inputs from the store clerk. The key operation unit 211 is made up of various keys (hardware keys, buttons) and receives various inputs from the store clerk. The store clerk scanner unit 212 is a scanner unit for store clerks, and optically reads various information. For example, the store clerk scanner unit 212 optically reads barcodes attached to products and store clerk codes attached to store clerk nametags. In addition to the above, the store clerk scanner unit 212 may also read codes printed on gift certificates and various cards.

[0027] Although the store clerk's scanner unit 212 is used when the store clerk registers a product, the store clerk may register the product by other methods. For example, if a key corresponding to a product (e.g., a key corresponding to a sports newspaper, etc.) is arranged on the key operation unit 211, the store clerk may operate (press) that key to register the product. Also, if a preset key corresponding to a product is displayed on the store clerk's display unit 210, the store clerk may operate that preset key to register the product.

[0028] The printing unit 213 prints and issues various media (receipts, etc.). The printing unit 213 can freely rotate to change its orientation (direction of the media issuing port) from the store clerk side to the customer side and from the customer side to the store clerk side. The orientation of the printing unit 213 may be changed manually or automatically (mechanically controlled, etc.). The correctness of the orientation of the printing unit 213 may be detected by a sensor or the like.

[0029] The audio output unit 214 outputs audio. For example, the audio output unit 214 outputs audio guidance, etc. The communication unit 215 transmits and receives information to and from other terminals (other devices: management device, etc.).

[0030] Fig. 5 is a diagram showing an example of the external appearance of label printer 302. As shown in Fig. 5, label printer 302 has an operation unit 11 that is operated by a user such as a producer, and a display unit 12 that displays various information to the user. Operation unit 11 is provided in case 2 (main body).

[0031] The label printer 302 is provided with a cutter unit (not shown) that cuts the label, and a paper feed unit 131 that issues the printed label.

[0032] An example of the configuration of the label printer 302 will be described with reference to Fig. 6. As shown in Fig. 6, the label printer 302 has a control unit 8 (CPU (Central Processing Unit)), flash memory 9, RAM 10, operation unit 11, display unit 12, communication unit 13, print control unit 14, print issuing unit 15, cutter drive unit 16, detection unit 105, and counter 17. Each component is connected by a communication line or the like.

[0033] The control unit 8 executes a program (control program) stored in the flash memory 9 or the like, and controls each component of the label printer 302. The flash memory 9 is a read-only memory that stores the control program, control data, and the like.

[0034] The RAM 10 has a work area for temporarily retrieving and processing data, including a dot expansion area for converting print data into dot data, a recall format area for retrieving and storing one piece of format data from a label format file, and a recall product area for retrieving and storing product data.

[0035] Furthermore, in this embodiment, the RAM 10 stores a label format file that sets the format for printing labels, a product file that sets various product data for label printing, and the like, and is backed up by a battery so that the product files and format files are retained even when the power is turned off.

[0036] The operation unit 11 is an input device for operating the label printer 302. For example, a touch panel configured integrally with the display unit 12 may be used as the operation unit 11. The display unit 12 is a display that displays various menu screens and data. The display unit 12 displays information related to the label printer 302 under the control of the control unit 8. Furthermore, under the control of the control unit 8, the display unit 12 performs a process of notifying the user to apply oil to the blade, for example, a process of displaying a cutter oil application message, when the number of cuts counted by the counter 17 exceeds a predetermined value.

[0037] The communication unit 13 performs data communication with the management device 301 and the like under the control of the control unit 8. The print control unit 14 controls the operation of the print issuing unit 15 under the control of the control unit 8. The print issuing unit 15 pulls out label paper from the label roll (roll paper) set in the roll paper mounting unit, and prints the above-mentioned symbols and the like.

[0038] More specifically, the printing issuing unit 15 pinches linerless label paper from a linerless label roll (not shown) between a thermal head and a platen roller driven by a stepping motor that constitute the printing unit 19, and pulls out the linerless label paper, while heating and printing on the surface (thermosensitive coloring surface) of the linerless label paper. The printing unit 19 may also print by applying ink to the linerless label paper.

[0039] Based on instructions from the control unit 8, the cutter driving unit 16 drives a cutter and the like arranged downstream in the transport direction from the printing unit 19 to cut the printed linerless label paper and produce sheet-like linerless labels (paper).

[0040] The control unit 8 executes a control program stored in a storage unit such as a flash memory 9 or a RAM 10, and controls the label printer as a computer, which performs the functions according to the present invention.

[0041] Fig. 7 is a diagram showing the configuration of a management device 301. The management device 301 is composed of a CPU 110, a ROM (Read Only Memory) 111, a RAM (Random Access Memory) 112, a display unit 113, a communication unit 114, a touch panel 115, and a scanner 117. The units shown in Fig. 7 are connected by a bus 119.

[0042] The CPU 110 controls the entire management device 301. The ROM 111 is a flash memory in which the programs and various data of the management device 301 are stored. The RAM 112 is where the programs are expanded and where temporary data is stored. The display unit 113 is composed of a liquid crystal display, an organic EL display, or the like. The communication unit 114 connects to the NWA via Wi-Fi (registered trademark). Note that the communication unit 114 may be capable of communication via 3G, 4G (LTE (Long Term Evolution)), 5G, Bluetooth (registered trademark), or the like.

[0043] The touch panel 115 is disposed over the display unit 113 and receives input from an operator. The scanner 117 is capable of reading symbols such as bar codes and two-dimensional codes. The symbols read by the scanner 117 are encoded by software.

[0044] The producer terminal 303 is composed of a CPU, ROM, RAM, a display unit, a communication unit, a touch panel, a microphone, a speaker, and a camera. The CPU controls the producer terminal 303 as a whole. The ROM is a flash memory in which the programs and various data of the producer terminal 303 are stored. The RAM is where the programs are expanded and where temporary data is stored. The display unit is composed of an LCD display or an organic EL display. The communication unit connects to the NWA via Wi-Fi (registered trademark). The communication unit 114 may be capable of communication via 3G, 4G (LTE (Long Term Evolution)), 5G, Bluetooth (registered trademark), or the like.

[0045] The touch panel is placed over the display unit and accepts input from the operator. The microphone receives voice input during a call, etc. The speaker outputs sounds such as a ringtone. The camera can read symbols such as barcodes and two-dimensional codes. The symbols read by the camera are encoded by software.

[0046] Next, the display screen of the management device 301 operated by the producer will be described. Prior to this description, an outline of the delivery procedure of the producer will be described. When the producer delivers a product, the producer prints a price tag from the label printer 302. The producer attaches the printed price tag to the product. After that, the producer performs a shipping operation. In this embodiment, the shipping operation means an operation of inputting product information using a screen for producer, which will be described later, before displaying the product in a store. A barcode is printed on the price tag. This barcode is an encoded product information indicating the product. The product information indicates at least the product name and the producer name, and in this embodiment, it is composed of a numerical value indicating the product name and a numerical value indicating the producer name. Since the product information can be obtained by reading the barcode, the management device 301 and the POS terminal 20 can specify, for example, Mr. XX's cabbage. Based on the above, the display screen of the management device 301 will be described below.

[0047] 8 is a diagram showing an example of the standby screen 400 of the management device 301. On the standby screen 400, a producer button 401, a disposal-related button 402, a store sales button 403, and a producer sales button 404 are provided.

[0048] The producer button 401 is a button that accepts operations by the producer. The disposal-related button 402 is a button that accepts operations by the store manager to dispose of products. In the following explanation, "manager" refers to the store manager. The store sales button 403 is a button that accepts operations to view information related to store sales. The producer sales button 404 is a button that accepts operations to view information related to store sales.

[0049] When the producer button 401 is pressed, the management device 301 displays a screen for the producer. Fig. 9 is a diagram showing an example of the screen for the producer 410. The screen for the producer 410 is provided with a ship button 411, a performance confirmation button 412, a take home button 413, a scan button 414, and a manual input button 415.

[0050] The Ship button 411 is a button for displaying a shipment screen in which product information indicating the product to be delivered by the producer is entered. The Take Home button 413 is a button for displaying a take home screen in which the producer abandons the sale of the product delivered by the producer and takes it home. In the following explanation, the abandonment of sale of the product delivered by the producer and taking it home by the producer is simply referred to as "take home". The Confirm Performance button 412 is a button for displaying a performance confirmation screen (not shown) that shows the history of the quantity shipped and the quantity taken home. The Scan button 414 is a button for accepting the reading of the price tag of the product to be shipped. The Manual Input button 415 is a button for accepting the manual input of numerical values ​​constituting the product information indicating the product to be shipped.

[0051] In a shipping operation, the producer first presses the shipping button 411. Next, the producer presses the scan button 414 or the manual input button 415. Fig. 9 shows the display state of the screen when the scan button 414 is pressed. Therefore, "Please scan the product barcode" is displayed on the screen. When the scan button 414 is pressed, the management device 301 waits for the scanner 117 to read the barcode.

[0052] 10 is a diagram showing an example of a quantity input screen 420 that is displayed when a barcode is read. The quantity input screen 420 is provided with a producer etc. display field 422, a back button 423, a quantity input area 424, and a confirm button 425. In addition, "Please enter the quantity to be shipped" is displayed.

[0053] The producer name in the producer etc. display field 422 displays the producer name shown in the product information. The product name in the producer etc. display field 422 displays the product name shown in the product information. The unit price in the producer etc. display field 422 displays the unit price linked to the product information. The unit price is linked to the product information in the product master.

[0054] The back button 423 is a button for displaying the producer screen 410 of FIG. 9 instead of the quantity input screen 420. The quantity input area 424 is an area for inputting the quantity to be delivered using the numeric keypad. The confirm button 425 is a button for confirming the shipment. When the confirm button 425 is pressed, the management device 301 displays a confirmation message and transmits shipping information indicating the product information and the quantity to the management device 301. Thereafter, the management device 301 displays the producer screen 410 of FIG. 9. The management device 301 registers the shipping information in a database (not shown). In addition, the management device 301 associates shipping time information indicating the time when the product information was input with the product information of the delivered product, and stores them in the ROM 111.

[0055] Next, take-out will be described. When taking out, the producer presses the take-out button 413 in FIG. 9. Next, the producer presses the scan button 414 or the manual input button 415. FIG. 9 shows the display state of the screen when the scan button 414 is pressed. Therefore, "Please scan the product barcode" is displayed on the screen. When the scan button 414 is pressed, the management device 301 starts the scanner 117 and waits for the barcode to be read.

[0056] 11 is a diagram showing an example of a quantity input screen 430 that is displayed when a barcode is read. The quantity input screen 430 is provided with a producer etc. display field 432, a back button 433, a quantity input area 434, and a confirm button 435. In addition, the message "Please enter the quantity to take home" is displayed.

[0057] The producer name in the producer etc. display field 432 displays the producer name shown in the product information. The product name in the producer etc. display field 432 displays the product name shown in the product information. The unit price in the producer etc. display field 432 displays the unit price linked to the product information. As described above, the unit price is linked to the product information in the product master.

[0058] The back button 433 is a button for displaying the producer screen 410 of FIG. 9 instead of the quantity input screen 430. The quantity input area 434 is an area for inputting the quantity to be delivered using the numeric keypad. The confirm button 435 is a button for confirming the take-out. When the confirm button 435 is pressed, the management device 301 displays a confirmation message and transmits take-out information indicating the product information and the quantity to the management device 301. Thereafter, the management device 301 displays the producer screen 410 of FIG. 9. The management device 301 registers the take-out information in a database (not shown).

[0059] Next, disposal will be described. When disposing of a product, the administrator presses the disposal-related button 402 in Fig. 8. Fig. 12 is a diagram showing a login screen 440 that is displayed when the disposal-related button 402 is pressed. The login screen 440 has a login ID input field 443, a password input field 444, a login button 441, and a cancel button 442 provided.

[0060] The login ID input field 443 is an input field for the login ID set by the administrator. The password input field 444 is an input field for the password set by the administrator. The login button 441 is a button that is pressed when logging in by inputting the login ID and password. The cancel button 442 is a button for canceling the login and displaying the standby screen 400 of FIG. 8 instead of the login screen 440. The login ID and password are input using a numeric keypad (not shown).

[0061] When the administrator presses login button 441, management device 301 transmits a login ID and password to management device 301, and when successful authentication is notified from management device 301, a disposal-related screen is displayed. On the other hand, when successful authentication is notified from management device 301, management device 301 displays that authentication has failed and waits for input of a login ID, etc.

[0062] 13 is a diagram showing an example of a disposal-related screen 450. On the disposal-related screen 450, a disposal button 451, a disposal history button 452, a scan button 454, a manual input button 455, and a back button 453 are provided.

[0063] The discard button 451 is a button for displaying a discard screen for discarding delivered products. The discard history button 452 is a button for displaying a discard history screen that displays the discarded products and their quantities. The scan button 454 is a button for accepting reading of the price tag of the product to be discarded. The manual input button 455 is a button for accepting manual input of numerical values ​​constituting product information indicating the product to be discarded. The back button 423 is a button for displaying the standby screen 400 of FIG. 8 instead of the discard-related screen 450.

[0064] When discarding, the manager first presses the discard button 451. Next, the producer presses the scan button 454 or the manual input button 455. Fig. 13 shows the display state of the screen when the scan button 454 is pressed. Therefore, "Please scan the product barcode" is displayed on the screen. When the scan button 454 is pressed, the management device 301 waits for the scanner 117 to read the barcode.

[0065] 14 is a diagram showing an example of a quantity input screen 460 that is displayed when a barcode is read. The quantity input screen 460 is provided with a producer etc. display field 462, a back button 463, a quantity input area 464, and a confirm button 465. In addition, "Please enter the quantity to be discarded" is displayed.

[0066] The producer name in the producer etc. display field 462 displays the producer name shown in the product information. The product name in the producer etc. display field 462 displays the product name shown in the product information. The unit price in the producer etc. display field 462 displays the unit price linked to the product information. As described above, the unit price is linked to the product information in the product master.

[0067] The back button 463 is a button for displaying the disposal-related screen 450 of FIG. 13 instead of the quantity input screen 460. The quantity input area 464 is an area for inputting the quantity to be disposed of with the numeric keypad. The confirm button 465 is a button for confirming the disposal. When the confirm button 465 is pressed, the management device 301 displays a confirmation message and transmits disposal information indicating the product information and the quantity to the management device 301. Thereafter, the management device 301 displays the disposal-related screen 450 of FIG. 13. The management device 301 registers the disposal information in a database (not shown).

[0068] Next, a case where the store sales button 403 is pressed on the standby screen 400 will be described. When the producer presses the store sales button 403, the management device 301 displays a store sales screen. FIG. 15(A) is a diagram showing an example of a store sales screen 470. The store sales screen 470 is provided with a graph area 471, a back button 472, a number of customers button 473, a store sales number button 474, a display period setting field 475, a display button 476, and a producer sales confirmation button 477.

[0069] Graph area 471 is an area that displays a graph showing sales results in a chronological order. Store sales figures (store sales in FIG. 15(A)) and number of customers are used as examples of sales results, so the vertical axis indicates store sales figures or number of customers, and the horizontal axis indicates time (in one-hour increments from 9:00 to 19:00). Back button 472 is a button for displaying standby screen 400 of FIG. 8 instead of store sales screen 470. Producer sales confirmation button 477 is a button for displaying the producer sales screen.

[0070] Customer count button 473 is a button for displaying a graph showing the number of customers who made transactions at the store in graph area 471. Store sales number button 474 is a button for displaying a graph showing the sales of the entire store in graph area 471. Since the graph showing the sales of the entire store is displayed on store sales screen 470 in Fig. 15, store sales number button 474 is not selectable.

[0071] The display period setting field 475 is a field for setting the period to be tabulated for display as a graph. The producer can set three periods, days, weeks, and months, using the radio buttons. When the producer presses the display button 476 after setting the period using the radio buttons, the management device 301 tabulates the store sales figures or number of customers for the set period and displays a graph showing the tabulation results in the graph area 471.

[0072] In the case of FIG. 15(A), a day is set as the period. In this case, the producer can set the target day. In FIG. 15(B), a week is set as the period. A specific week is set according to the target day. The week from Sunday to Saturday, which includes the target day, is set as the period. In FIG. 15(C), a month is set as the period. A specific month is set according to the target month. Furthermore, the day of the week can also be set. The day of the week can be set to any one of Monday to Sunday, or all (the entire month). For example, if Friday is set, the sum or average for each hour of all Fridays of the target month is displayed. If all is set, the sum or average for each hour of all days of the target month is displayed.

[0073] As shown in graph area 471, store sales figures, which are one type of sales performance, are displayed in chronological order without using numerical values. Although the numerical values ​​of store sales figures are not displayed, the length of each graph is proportional to the numerical value. For example, if the height of bar graph A is twice the height of bar graph B, then the numerical value of bar graph A is twice the numerical value of bar graph B. This allows the producer to grasp trends, even though he does not know the numerical values ​​of store sales figures and number of customers.

[0074] Next, a case will be described where the producer sales button 404 is pressed on the standby screen 400, and where the producer sales confirmation button 477 is pressed on the store sales screen 470. When the producer presses the producer sales button 404 or the producer sales confirmation button 477, the management device 301 displays a login screen.

[0075] 16 is a diagram showing a login screen 480. The login screen 480 is provided with a producer code input field 483, a password input field 484, and a login button 481.

[0076] The producer code input field 483 is an input field for the producer code set for the producer. The password input field 484 is an input field for the password set for the producer. The producer code and password are input using the numeric keypad. The login button 481 is a button that is pressed when logging in by inputting the producer code and password.

[0077] When the producer presses the login button 481 and authentication is successful, the management device 301 displays a producer sales screen. On the other hand, if authentication is unsuccessful, the management device 301 displays a message indicating that authentication has failed and waits for input of a login ID, etc.

[0078] 17 is a diagram showing an example of a producer sales screen 490. The producer sales screen 490 is provided with a graph area 500, a back button 491, a display period setting field 492, a search button 493, a scan button 494, a display button 495, a store sales confirmation button 496, a category field 497, and a product field 498. On the producer sales screen, the store sales number and the producer sales number indicate the number of products sold.

[0079] The back button 491 is a button for displaying the standby screen 400 in Fig. 8 or the store sales screen 470 in Fig. 15(A) instead of the producer sales screen 490. The display period setting field 492 is a field for setting the period for tallying up data for display as a graph. As with the store sales screen 470, the producer can set three periods of days, weeks, and months using radio buttons.

[0080] On the producer sales screen, it is possible to display a graph of store sales numbers and producer sales numbers by narrowing down to a certain category or type of product. Producer sales numbers are the number of products delivered by a producer that have been sold.

[0081] When the graph is displayed by narrowing down to a category, the category is displayed in a category column 497. Examples of categories include vegetables and fruits. When the graph is displayed by narrowing down to a product, the product name is displayed in a product column 498. The category can be set using a pull-down menu.

[0082] For example, if the category is vegetables and only cucumbers and cabbages, which belong to vegetables, are sold, and 3 cucumbers and 4 cabbages are sold, the number of units sold for the vegetable category will be 3 + 4 = 7. On the other hand, if the product name displayed as a graph is cabbage, the number of units sold will be 4 cabbages.

[0083] The search button 493 is a button for searching for products to be displayed as a graph. When the search button 493 is pressed, a screen (not shown) for searching for products is displayed. The scan button 494 is a button for identifying products to be displayed as a graph by scanning the price tags of the products. This allows the producer to easily input products to be displayed as graphs without searching for the products. When the scan button 494 is pressed, the management device 301 waits for the scanner 117 to read the barcode. When the producer sets a period with the radio buttons, inputs a category or type of product, and presses the display button 495, the management device 301 tallies up the store sales figures for the set period, and displays a graph showing the tallied results in the graph area 500.

[0084] Next, the graph area 500 will be described. In the graph area, a bar graph indicates the store sales number, and a line graph indicates the producer sales number. The store sales number is an example of store sales performance regarding sales of the same type of product delivered by the producer that was sold at the store. Also, the vertical bar 501 indicates the time when the product information indicating the product delivered by the producer was input. In other words, it indicates the timing of shipping (delivery). Furthermore, the shipment number 503 displayed under the vertical bar indicates the shipment number at that time. Therefore, the producer sales screen 490 of FIG. 17 shows that 25 products were shipped around 11:00 (10:30 to 11:30). Also, the vertical bar displayed around 12:00 (11:30 to 12:30) similarly indicates the timing of shipping. The producer sales screen 490 of FIG. 17 shows that the products were shipped twice, around 11:00 and 12:00. Note that even if multiple shipments are made in the same time period, for example, twice around 11:00, only one vertical bar is displayed for that time period. Furthermore, the number of shipments 503 displayed below the vertical bar indicates the total number of shipments made in that time period. For example, if three shipments are made in the same time period, the number of shipments 503 indicates the total number of shipments for the three shipments.

[0085] Furthermore, a scale 502 for a line graph is displayed on the vertical axis. This scale indicates the number of sales of the producer. The number of sales of the producer for each hour of the day is also displayed. This allows the user to see, for example, that the producer sold two items at 10 o'clock and four items at 12 o'clock. Note that it is also possible to display only one of the scale and the number of sales of the producer for each hour of the day.

[0086] In this way, the management device 301 displays the producer's sales results in chronological order, as well as shipping time information. The management device 301 also displays the store sales results and the shipping time information on the same screen. The producer sales screen displays store sales figures, allowing producers to understand the time periods when products are likely to be sold at the store. This allows producers to determine that they should ship products before the time periods when they are likely to be sold. Thus, by displaying the producer sales screen, the management device 301 can provide producers with information for determining the timing of delivery.

[0087] Also, on the producer sales screen, store sales figures are displayed in chronological order without using numerical values. Similarly, although numerical values ​​are not displayed, the length of each graph is proportional to the numerical value. This allows producers to grasp trends, even though they do not know the values ​​of store sales figures. In this way, on the producer sales screen, the management device 301 displays producer sales results in chronological order using numerical values, and displays store sales results in chronological order without using numerical values.

[0088] In the example of Fig. 17, the store sales number and the producer sales number are the number of items sold, but they may be the sales amount of the items. In this way, more detailed sales results of the store can be provided to the producer.

[0089] FIG. 18 is a diagram showing the producer sales screen 510 when the month is set in the display period setting field 492. In FIG. 18, January 2021 is set as the target month, and Sunday is also set. FIG. 18 also shows the total for each time on Sunday. Note that the scale on the vertical axis is displayed in a pattern that does not display the scale.

[0090] Generally, store sales vary depending on the day of the week. Therefore, by displaying the sales figures for each day of the week, it is possible to provide producers with information to determine the timing of deliveries for each day of the week.

[0091] 19 and 20 are flowcharts showing the transition of the display screen performed by the management device 301. Processing other than the transition of the display screen is omitted.

[0092] 19, the management device 301 displays the standby screen 400 (step S101). The management device 301 determines whether or not the producer button 401 has been pressed (step S102). If the producer button 401 has been pressed (step S102: YES), the management device 301 displays the producer screen 410 (step S103).

[0093] The management device 301 judges whether the shipping button 411 is pressed (step S104). If the shipping button 411 is pressed (step S104: YES), the management device 301 displays the quantity input screen 420 (step S105), and after inputting the quantity, etc., returns to step S101.

[0094] In step S104, the management device 301 judges whether the take home button 413 has been pressed without pressing the ship button 411 (step S106). If the take home button 413 has been pressed (step S106: YES), the management device 301 displays the quantity input screen 430 (step S107), and after inputting the quantity, etc., returns to step S101.

[0095] In step S106, the management device 301 determines whether the result confirmation button 412 has been pressed without pressing the take home button 413 (step S108). If the result confirmation button 412 has been pressed (step S108: YES), the management device 301 displays a result confirmation screen (not shown) (step S109) and returns to step S101. If the result confirmation button 412 has not been pressed (step S108: NO), the management device 301 returns to step S103.

[0096] In the above step S102, if the producer button 401 has not been pressed (step S102: NO), the management device 301 proceeds to step S201 in Fig. 20. In Fig. 20, the management device 301 determines whether or not the discard-related button 402 has been pressed (step S201). If the discard-related button 402 has been pressed (step S201: YES), the management device 301 displays the login screen 440 (step S202). Here, it is assumed that the authentication has been successful.

[0097] The management device 301 displays the disposal-related screen 450 (step S203). The management device 301 determines whether the disposal button 451 is pressed (step S204). If the disposal button 451 is pressed (step S204: YES), the management device 301 displays the quantity input screen 460 (step S205), and after inputting the quantity, etc., returns to step S101.

[0098] If the discard button 451 has not been pressed (step S204: NO), the management device 301 determines whether or not the discard history button 452 has been pressed (step S206). If the discard history button 452 has been pressed (step S206: YES), the management device 301 displays a discard history screen (not shown) (step S207) and returns to step S101. If the discard history button 452 has not been pressed (step S206: NO), the management device 301 returns to step S203.

[0099] In the above step S201, if the disposal related button 402 has not been pressed (step S201: NO), the management device 301 judges whether or not the store sales button 403 has been pressed (step S208). If the store sales button 403 has been pressed (step S208: YES), the management device 301 displays the store sales screen 470 (step S209). The management device 301 judges whether or not the producer sales confirmation button 477 has been pressed (step S210). If the producer sales confirmation button 477 has been pressed (step S210: YES), the process proceeds to step S212. If the producer sales confirmation button 477 has not been pressed (step S210: NO), the management device 301 returns to step S101.

[0100] In the above step S208, if the store sales button 403 has not been pressed (step S210: NO), the management device 301 judges whether or not the producer sales button 404 has been pressed (step S211). If the producer sales button 404 has not been pressed (step S211: NO), the management device 301 returns to step S101.

[0101] If the producer sales button 404 is pressed (step S211: YES), the management device 301 displays the login screen 480 (step S212). Here, it is assumed that the authentication is successful. The management device 301 displays the producer sales screen 490 (step S213). The management device 301 determines whether or not the store sales confirmation button 496 is pressed (step S214). If the store sales confirmation button 496 is pressed (step S214: YES), the process proceeds to step S209. If the store sales confirmation button 496 is not pressed (step S214: NO), the management device 301 returns to step S101.

[0102] So far, we have explained the flow for producers to use the management device 301, but in a system in which the management device 301 exchanges data by connecting to another management server (cloud) via the Internet, the same operations can be performed by accessing the management server using a mobile terminal or tablet owned by the producer instead of the management device 301.

[0103] Next, an explanation will be given of emails sent from the management device 301 to the producer terminal 303. Fig. 21 is a diagram showing an example of an email sent to the producer terminal 303. The email is sent at predetermined time intervals or when an event (such as when the stock quantity becomes 0) occurs.

[0104] In FIG. 21, the email 520 has a flash report section 521 and a replenishment section 522. The flash report section 521 lists the product name, number of items, sales amount, and total amount sold. The contents listed here may be, for example, the contents sold since the previous email was sent, or the contents sold since the store opened. The replenishment section 522 lists the products for which replenishment is recommended and the remaining number when the number of products falls below a set number (which can be set for each product). In this way, the producer can immediately grasp the products that have been sold and the products that need replenishment by using the producer terminal 303 even when not at the store. Therefore, the management device 301 and the POS system 1 can also provide the producer with information for determining the delivery timing.

[0105] Incidentally, by providing a web server function in the management device 301 or by providing a web server, the producer may be able to use the producer terminal 303 to view information viewable by the producer on the management device 301, such as the above-mentioned store sales screen, regarding the above-mentioned breaking news and replenishment. Furthermore, information and functions for displaying the information viewable by the producer on the management device 301 on the producer terminal 303 may be provided in a cloud, and the producer terminal 303 may communicate with the cloud to enable the producer terminal 303 to view the information viewable by the producer on the management device 301.

[0106] According to this embodiment, the producer can view the products that he / she has shipped individually on the producer sales screen and can also understand the time of shipment. Based on the time of shipment and the store sales, the producer can later determine when it would have been better to ship the products.

[0107] AI can also be used to tell the best time to ship. For example, in the case of the producer sales screen in Figure 17, sales suddenly increased at 11 o'clock, so a notification could be made that it would have been better to ship at 10 o'clock, or the display style of the bar graph for 11 o'clock could be changed. One example of changing the display style is to change the display style of the bar graph with the highest sales.

[0108] The embodiments will be summarized below. [Name of invention] Product data processing device and program [Technical field]

[0109] The present invention relates to a product data processing device and a program. [Background technology]

[0110] At farmer's markets, operators often sell products on behalf of producers, such as farmers. [Prior art document] [Patent documents]

[0111] [Patent Document 1] JP 2007-156952 A [Summary of the Invention] [Problem to be solved by the invention]

[0112] Producers deliver their products (e.g. agricultural products) to the farmer's market, enter the products to be delivered, and then display them. Producers deliver their products at their own pace, so they may miss the best selling times. Even if there are tools for production management, they may leave without realizing it.

[0113] The present invention has been made in view of the above circumstances, and has an object to provide a technique capable of providing producers with information for determining delivery timing. [Means for solving the problem] (1) In order to solve the above-mentioned problems, a product data processing device which is one aspect of the present invention is a product data processing device for selling products delivered by a producer in a store, and is characterized in having an input means for inputting product information indicating the products delivered by the producer, a storage means for linking and storing shipping time information indicating the time when the product information was input by the input means with the product information of the delivered products, an acquisition means for acquiring information regarding sales of the products delivered by the producer, and a display means for displaying the information regarding sales of the products delivered by the producer acquired by the acquisition means and displaying the shipping time information. According to the above configuration, it is possible to provide the producer with information for determining the timing of delivery.

[0114] (2) In the configuration of (1) above, the acquisition means acquires store sales records regarding sales of the same type of product delivered by the producer and sold at the store, and the display means displays the acquired store sales records and the shipping time information on the same screen. According to the above configuration, since it is possible to compare with the store's sales record on the same screen, the producer can grasp the time periods when the products are most likely to sell at the store. Therefore, the producer can determine that it is best to ship the products before the time periods when the products are most likely to sell. Therefore, by displaying the producer sales screen, the management device 301 can provide the producer with information for determining the timing of delivery.

[0115] (3) In the configuration of (2) above, the acquisition means further acquires producer sales results regarding the sales of goods delivered by the producer and sold at the store, and when displaying the acquired producer sales results, the display means displays the producer sales results in chronological order using numerical values, and when displaying the acquired store sales results, the display means displays the store sales results in chronological order. According to the above configuration, it is possible to provide more detailed information about the sales record of the store to the producer.

[0116] (4) In the configuration of (3) above, the producer sales record is information indicating the sales amount of the goods delivered by the producer or information indicating the number of goods delivered by the producer, and the store sales record is information indicating the sales amount of the goods sold at the store or information indicating the number of goods sold at the store. According to the above configuration, the producer can check the sales amount and the number of items sold.

[0117] (5) In order to solve the above-mentioned problems, a program which is one aspect of the present invention is a program that causes a computer to function as a product data processing device for selling products delivered by producers in a store, and is characterized in that it causes the computer to function as an input means for inputting product information indicating the products delivered by the producer, a storage means for linking and storing shipping time information indicating the time when the product information was input by the input means with the product information of the delivered products, an acquisition means for acquiring information regarding sales of the products delivered by the producer, and a display means for displaying the information regarding sales of the products delivered by the producer acquired by the acquisition means and displaying the shipping time information. According to the above configuration, it is possible to provide the producer with information for determining the timing of delivery.

[0118] In relation to the above, the POS terminal device 20 may function as a so-called thin client specialized in the input / output interface portion with respect to product registration and settlement. In other words, the POS terminal device 20 may accept various inputs (operation by an operator, detection by a device such as a scanner), transmit input information (operation information, scan information, etc.) to the cloud server Sv, receive the processing results of the cloud server Sv based on the input information (update screen information, device control information, etc.), and perform various outputs (display on a display unit, control of a device).

[0119] The program for implementing the management device 301 described above may be recorded in a computer-readable recording medium, and the program may be read into a computer system and executed. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. The term "computer-readable recording medium" refers to portable media such as a flexible disk, an optical magnetic disk, a ROM, and a CD-ROM, and a storage device such as a hard disk built into a computer system. The term "computer-readable recording medium" also refers to a storage device that holds a program for a certain period of time, such as a volatile memory (RAM) inside a computer system that becomes a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. The program may be transmitted from a computer system that stores the program in a storage device to another computer system via a transmission medium or by a transmission wave in the transmission medium. The "transmission medium" that transmits the program refers to a medium that has a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may also be for implementing a part of the above-mentioned functions. Furthermore, the above-mentioned functions may be realized in combination with a program already recorded in the computer system, that is, a so-called differential file (differential program).

[0120] Although the embodiment of the present invention has been described in detail above with reference to the drawings, the specific configuration is not limited to the embodiment, and the present invention also includes designs that do not deviate from the gist of the present invention. [Explanation of symbols]

[0121] 1. POS system 2. Case 3…Cover body 8...Control section 9. Flash memory 11...Operation unit 12...Display section 13…Communications Department 14...Print control unit 15…Printing and Issuing Department 16…Cutter drive unit 17…Counter 19...Printing section 20…POS terminal 100…Management device 301 105…Detection unit 131...Paper passing section 133…Cutter cover 201...CPU 202...ROM 203...RAM 204...Hard disk 205…Customer side display section 206…Customer side scanner section 208…Card payment department 209…Payment Department 210...Staff side display section 211...Key operation section 212…Clerk side scanner 213…Printing Department 214...Audio output unit 215…Communications Department 301…Management device 302...Label printer 303…Producer terminal

Claims

1. A product data processing device for selling products delivered by manufacturers in a store, comprising: an input means for inputting product information indicating products delivered by the manufacturer; a storage means for storing shipping time information indicating the time when the product information was input by the input means and the product information of the delivered product in association with each other; An acquisition means for acquiring information regarding sales of the products delivered by the producer; a display means for displaying information regarding sales of the products delivered by the producer acquired by the acquisition means and displaying the shipping time information; A product data processing device comprising:

2. The acquiring means acquires store sales results regarding sales of the same type of product delivered by the producer and sold in the store, The display means includes: The product data processing device according to claim 1 , wherein the acquired store sales record and the acquired shipping time information are displayed on the same screen.

3. The acquiring means further acquires a producer sales record regarding sales of the products delivered by the producer and sold at the store; The display means includes: When displaying the acquired sales record of the producer, the sales record of the producer is displayed in chronological order using numerical values; The product data processing device according to claim 2 , wherein, when the acquired store sales results are displayed, the store sales results are displayed in chronological order.

4. A product data processing device as described in claim 3, wherein the producer sales record is information indicating the sales proceeds of products delivered by the producer or information indicating the number of products sold by the producer, and the store sales record is information indicating the sales proceeds of products sold at the store or information indicating the number of products sold at the store.

5. A program that causes a computer to function as a product data processing device for selling products delivered by manufacturers in a store, The computer, an input means for inputting product information indicating the product to be delivered by the manufacturer; a storage means for storing shipping time information indicating the time when the product information was input by the input means and the product information of the delivered product in association with each other; An acquisition means for acquiring information regarding sales of the goods delivered by the producer; a display means for displaying information related to sales of the products delivered by the producer, which information has been acquired by the acquisition means, and for displaying the shipping time information; A program characterized by causing the program to function as a

Images