JP2023097833A - Program, portable fee-adjustment device, and system - Google Patents

Abstract

To provide a program, a portable fee-adjustment device, and a system that reduce the workload on delivery staff when products are delivered.SOLUTION: In a product sales system in which a cloud server, a registration device, and a mobile terminal device are communicably connected over a network, the mobile terminal device includes a product information acquisition unit 401, a display control unit 403, and a reception unit 404. The product information acquisition unit acquires product presentation information including a presentation item for selling each product. The display control unit displays a list of a plurality of display media each including the presentation item. The reception unit accepts in an alterable manner the presentation item to be displayed on each of the plurality of display media.SELECTED DRAWING: Figure 6

Description

The present invention relates to a program, a portable checkout device, and a system.

In recent years, various home delivery services have become popular. As a related technology, there is known a method of predicting the next order date based on the past order data of a business partner and sending an order promotion email before the predicted order date to prompt the next order ( For example, see Patent Document 1).

Japanese Patent Application Laid-Open No. 2007-328402

However, in the conventional technology, when the delivery staff delivers the product in the home delivery service, it may be difficult to grasp the purchased product and the price, which may impose a workload on the delivery staff.

SUMMARY OF THE INVENTION The present invention has been made in view of such circumstances, and an object of the present invention is to provide a technique for reducing the work load of delivery staff at the time of product delivery.

To solve the above-described problems, a program according to one aspect of the present invention includes product information acquisition means for acquiring product information registered by a registration device, and display control for selectively displaying the product information for each transaction. and a settlement means for performing settlement for each transaction based on the product information displayed by the display control means.

In order to solve the above-described problems, a portable payment device according to another aspect of the present invention includes product information acquisition means for acquiring product information registered by a registration device, and product information that can be selected for each transaction. A portable settlement apparatus comprising: display control means for displaying; and settlement means for performing settlement for each transaction based on the product information displayed by the display control means.

In order to solve the above-described problems, a system that is another aspect of the present invention is a system that includes a registration device and a portable settlement device, wherein the registration device registers product information, The portable settlement device includes product information acquisition means for acquiring product information registered by the registration device, display control means for selectively displaying the product information for each transaction, and the product displayed by the display control means. and settlement means for performing settlement for each transaction based on the information.

1 is an explanatory diagram showing a network configuration of a product sales system 1 according to an embodiment; FIG. 3 is an explanatory diagram showing an example of a product master 101; FIG. It is explanatory drawing which shows an example of member information DB102. 2 is a block diagram showing an example of a hardware configuration of a mobile terminal device 120; FIG. 4 is an explanatory diagram showing an example of information included in a code symbol 112 issued by a registration device 110; FIG. 2 is a functional block diagram showing an example of a functional configuration of a mobile terminal device 120; FIG. 3 is an explanatory diagram showing an example of a screen displayed on the mobile terminal device 120; FIG. 3 is an explanatory diagram showing an example of a screen displayed on the mobile terminal device 120; FIG. 3 is an explanatory diagram showing an example of a screen displayed on the mobile terminal device 120; FIG. 3 is an explanatory diagram showing an example of a screen displayed on the mobile terminal device 120; FIG. 4 is a sequence diagram showing the flow of processing in the product sales system 1; FIG. 6 is a flowchart showing an example of settlement processing performed by the mobile terminal device 120. FIG.

(embodiment)
(Network configuration of product sales system 1)
FIG. 1 is an explanatory diagram showing the network configuration of a product sales system 1 according to the embodiment. The merchandise sales system 1 (an example of the system) can be installed in various stores such as supermarkets, home centers, convenience stores, and various goods stores.

In FIG. 1 , the merchandise sales system 1 includes a cloud server 100 , a registration device 110 and a mobile terminal device 120 . Each device is communicably connected via a network 140 . Each device and each terminal is a computer device including a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a communication section, and the like.

In this embodiment, the cloud server 100 does not manage product information purchased by customers. The cloud server 100 includes a product master 101 (see FIG. 2), which will be described later, and a member information DB (database) 102 (see FIG. 3). When cloud server 100 receives a product code from registration device 110 , cloud server 100 transmits product information corresponding to the product code to registration device 110 . Also, when receiving a product code from the mobile terminal device 120 , the cloud server 100 transmits product information corresponding to the product code to the mobile terminal device 120 .

The registration device 110 is a POS (Point Of Sales) terminal device for registering products. The registration device 110 is arranged at the store 111 . The registration device 110 registers the product by scanning the product code attached to the product, for example. A product code is identification information that can uniquely identify a product. For example, the product code is a JAN (Japanese Article Number) code.

After reading the product code, the registration device 110 inquires of the cloud server 100 about the product information. The inquiry is to send the product code to the cloud server 100 and to request the cloud server 100 to send the product information. When the cloud server 100 receives an inquiry about product information, the cloud server 100 extracts product information corresponding to the product code from the product master 101 and transmits the extracted product information to the registration device 110 . Thereby, the registration device 110 acquires product information and registers the product.

Note that the product master 101 is not limited to being provided in the cloud server 100, and may be provided in the store controller when the store 111 is provided with a store controller. In this case, the registration device 110 may inquire of the store controller about product information. Also, the product master 101 may be provided in an external device different from the cloud server 100 . In this case, the registration device 110 may inquire of the external device about product information. Also, the product master 101 may be provided in the registration device 110 . In this case, the registration device 110 may refer to the product master 101 of its own device.

After completing the product registration, the registration device 110 generates a code symbol 112 including the product code and the registration date and time, and outputs the code symbol 112 . The code symbol 112 may be, for example, a two-dimensional code such as a QR code (registered trademark), or a barcode. The output mode of the code symbol 112 is, for example, a mode of printing on a sheet such as a paper medium, but is not limited to this, and may be a mode of display on a display.

The mobile terminal device 120 is an example of a portable settlement device. The mobile terminal device 120 is a portable computer device possessed by a delivery staff member riding in the delivery vehicle 122 . The mobile terminal device 120 is, for example, a smart phone, but may be a tablet terminal, a notebook computer, or a mobile phone. The mobile terminal device 120 has a camera and a scanner.

The mobile terminal device 120 reads the code symbol 112 output by the registration device 110 using a camera or scanner. When reading the code symbol 112 , the mobile terminal device 120 uses the product code included in the code symbol 112 to inquire of the cloud server 100 about product information. Thereby, the mobile terminal device 120 receives the product information corresponding to the product code. When the product master 101 is provided in the store controller, the mobile terminal device 120 may inquire of the store controller about product information.

The mobile terminal device 120 settles the account for the product registered by the registration device 110 at the delivery destination. The mobile terminal device 120 may have the functions of a printer 121 or may be connected to a printer 121 that is a separate device from the mobile terminal device 120 . The portable terminal device 120 causes the printer 121 to print a receipt when the payment is completed.

(Example of product master 101)
FIG. 2 is an explanatory diagram showing an example of the product master 101. As shown in FIG. In FIG. 2, the merchandise master 101 includes items of "merchandise code" and "merchandise information". A "merchandise code" is, for example, a JAN code and consists of a 13-digit code. A JAN code is a code that can specify a business and a product. Note that the "merchandise code" may include an in-store barcode. The in-store barcode is a uniquely numbered barcode used for product management within the store 111 .

"Product information" includes "product name", "unit price", and "tax rate". "Product name" is the name of the product. "Unit price" is the selling price per sales unit (for example, per piece) of the product. It should be noted that the products also include products sold by weight. In the case of products sold by weight, the “unit price” indicates, for example, the selling price per 100 g (grams). "Tax rate" is the consumption tax rate, and indicates either 8% or 10%, for example, depending on the type of product. In addition to the items shown in the figure, the item of "product information" may include, for example, the name of the place of origin, the manufacturing company (manufacturer), and the like.

(Example of member information DB 102)
FIG. 3 is an explanatory diagram showing an example of the member information DB 102. As shown in FIG. In FIG. 3, the member information DB 102 includes items of "membership number", "purchase history", and "privilege". The member information DB 102 is stored as member information by inputting information into the items of "membership number", "purchase history", and "privilege".

"Member number" is member identification information assigned to each member. "Purchase history" indicates the purchase history for each transaction of each member. "Privilege" is a privilege given to a member, such as the provision of points or a discount. A "privilege" is, for example, a point associated with each product included in the purchase history. Note that the "privilege" may be given for each transaction, like store visit points. Also, the "privilege" is not limited to points, but may be coupons, discount tickets, or the like.

Further, in this embodiment, the member information DB 102 does not store personal information such as member names and addresses. Therefore, there is no concern that personal information will be leaked in the merchandise sales system 1 . Therefore, customers can use the merchandise sales system 1 with peace of mind.

(Hardware Configuration of Mobile Terminal Device 120)
FIG. 4 is a block diagram showing an example of the hardware configuration of the mobile terminal device 120. As shown in FIG. 4, the mobile terminal device 120 includes a CPU 301, a memory 302, an input device 303, a communication I/F (interface) 304, a storage medium I/F 305, a display 306, a GPS unit 307, and a camera 308. , a scanner 309 , and a printer 121 . Also, the components 121 and 301 to 309 are connected by a bus 320, respectively.

The CPU 301 controls the entire mobile terminal device 120 . The memory 302 has, for example, ROM, RAM and flash ROM. For example, a flash ROM or ROM stores various programs. Various programs include a settlement processing program according to the present embodiment. The settlement processing program includes application software (hereinafter sometimes referred to as "application"). A settlement processing program (a settlement processing application) is pre-installed in the mobile terminal device 120 . A RAM is used as a work area for the CPU 301 . A program stored in the memory 302 is loaded into the CPU 301 to cause the CPU 301 to execute coded processing.

The input device 303 is a touch panel or operation buttons. Note that the input device 303 may include a keyboard, mouse, microphone, and the like.
Communication I/F 304 is connected to network 140 such as the Internet through a communication line, and is connected to other devices via network 140 . Also, the communication I/F 304 serves as an interface between the network 140 and the inside of the device itself, and controls input/output of data from other devices (for example, the cloud server 100, the registration device 110, etc.).

A storage medium I/F 305 controls reading and writing of data to a storage medium (not shown) such as a magnetic disk or an optical disk under the control of the CPU 301 .
Display 306 is an output device for displaying images. In addition to the display 306, a microphone may be included as an output device.

The GPS unit 307 has a function of receiving position information from GPS satellites and detecting the current position of the mobile terminal device 120 on map data. In addition, the mobile terminal device 120 includes various sensors (eg, a gyro sensor, an acceleration sensor, a distance sensor, etc.) not shown, and detects various states of the mobile terminal device 120 (eg, inclination of the mobile terminal device 120). have a function.

A camera 308 captures an image of a subject. Camera 308 captures moving images or still images. Camera 308 includes an in-camera provided on the display 306 side and an out-camera (rear camera) provided on the back side. In this embodiment, camera 308 reads code symbol 112 . When reading the code symbol 112 , the out-camera is used and the captured image is displayed on the display 306 . Note that the camera 308 may be capable of reading a product code (barcode) attached to the product instead of or in addition to reading the code symbol 112 .

A scanner 309 is provided at the upper end of the housing of the mobile terminal device 120 . As a reading method of the scanner 309, for example, a laser method, a CCD method, or the like can be adopted. The scanner 309 reads, for example, a product code (barcode) attached to the product. Note that the scanner 309 may be capable of reading the code symbol 112 instead of or in addition to reading the product code.

(Information included in code symbol 112 issued by registration device 110)
FIG. 5 is an explanatory diagram showing an example of information included in the code symbol 112 issued by the registration device 110. As shown in FIG. In FIG. 5, the information included in the code symbol 112 includes items of "transaction number", "product code", and "date and time of registration". "Transaction number" is identification information that identifies each transaction. A "merchandise code" is, for example, a JAN code. When purchasing multiple products, multiple product codes are associated with one transaction. When purchasing one product, one product code is associated with the position transaction. The “date and time of registration” is the date and time when the product was registered in each transaction. The "date and time of registration" may be, for example, the date and time when registration of all products in one transaction is completed (date and time for each transaction), or the date and time when each product in one transaction is registered (date and time for each product). date and time).

(Example of functional configuration of mobile terminal device 120)
FIG. 6 is a functional block diagram showing an example of the functional configuration of the mobile terminal device 120. As shown in FIG. The mobile terminal device 120 includes a product information acquisition unit 401, an input unit 402, a display control unit 403, a reception unit 404, a settlement unit 405, an identification information acquisition unit 406, a history output unit 407, and a privilege acquisition unit. 408 and a privilege output unit 409 . Each functional unit 401 to 409 is implemented by the CPU 301 included in the mobile terminal device 120 . That is, the functions of the functional units 401 to 409 are implemented by the CPU 301 executing the settlement processing program stored in the memory 302 .

The product information acquisition unit 401 acquires product information registered by the registration device 110 . The input unit 402 inputs identification information (product code) for identifying the product and the registration date and time when the identification information was input. The input unit inputs the product code and registration date/time information included in the code symbol 112 . However, the input unit 402 is not limited to inputting such information from the code symbol 112 . For example, the input unit 402 may input these pieces of information from the registration device 110 through communication. The communication may be communication via the network 140, or short-range wireless communication such as Bluetooth (registered trademark), NFC (Near Field Communication: registered trademark), or infrared communication. The product information acquisition unit 401 acquires product information corresponding to the product code input to the input unit 402 .

The product information acquisition unit 401 acquires product information for each transaction. Specifically, when one code symbol 112 is read by the camera 308, the mobile terminal device 120 acquires registered product information as one transaction. When the product information is read by the product information acquisition unit 401, the mobile terminal device 120 can display that the number of transactions has been increased by "1". The indication that "1" has been added to the number of transactions is, for example, the indication that "1" is added to the number shown in a transaction icon 722 (see FIG. 7B), which will be described later.

(About bargain items)
In the home delivery service, the registration date (order date) at which the product is registered (ordered) at the store 111 may differ from the home delivery date and time. In addition, the store 111 may prepare and sell bargain items on a daily basis. In the present embodiment, if the product is on sale at the registration date and time of the product, the product is targeted for sale. In other words, even if an item is on sale at the delivery date and time, it is not subject to sale if it is not on sale at the registration date and time. However, not limited to this, even if an item is not on sale at the registration date and time, it may be subject to sale if it is on sale at the home delivery date and time.

(About display control)
The display control unit 403 selectably displays product information for each transaction. Further, the display control unit 403 displays product information and registration date/time information.

Here, the functional configuration of the mobile terminal device 120 shown in FIG. 6 will be described with reference to screen examples displayed on the mobile terminal device 120 using FIGS. 7 to 10. FIG. Below, the screens displayed mainly at the delivery destination will be described.

7 to 10 are explanatory diagrams showing examples of screens displayed on the mobile terminal device 120. FIG. 7A shows a menu screen 710 displayed on the display 306 of the mobile terminal device 120. FIG. The menu screen 710 includes an employee column 701, an employee switching button 702, and various selection buttons 711-715.

The employee column 701 displays the name of the delivery staff member who has logged into the mobile terminal device 120 .
The employee switching button 702 is a button for accepting switching of the logged-in delivery staff.
The close button 711 is a button that accepts an operation for finalizing the results of sales and the like for a predetermined period (for example, the current day).
The registration button 712 is a button for accepting the start of general operations related to transactions including product registration.
The business button 713 is, for example, a button for accepting display of information related to various business such as purchase history.
The report button 714 is, for example, a button for receiving the display of messages and the like from the store 111 .
The setting button 715 is a button for receiving various setting changes of the payment processing application according to the present embodiment.
When the registration button 712 is selected on the menu screen 710, the screen transitions to the transaction details screen 720 shown in FIG. 7(B).

FIG. 7B shows a transaction details screen 720. FIG. Transaction details screen 720 includes an imaging area 721 and a transaction icon 722 .
The imaging area 721 is an area for reading various codes by imaging the product code (bar code) attached to the product or the membership code written on the membership card. It should be noted that the screen transition related to product registration will be described later with reference to FIG. 10 . The transaction details screen 720 is a screen that shows the details of one transaction, although no product is registered. For this reason, although the screen shown in FIG. 7B is referred to as the "transaction details screen 720" in the present embodiment, it can also be referred to as the "product registration screen" because it is a screen that allows product registration.

The transaction icon 722 indicates the current number of transactions, for example, the number of outstanding transactions (the number of delivery destinations). As shown, the trade icon 722 shows a "2", indicating that the current number of trades is "2". When the transaction icon 722 is pressed on the transaction details screen 720, the screen transitions to the transaction list screen 730 shown in FIG. 7(C).

FIG. 7C shows a transaction list screen 730. FIG. Transaction list screen 730 includes transaction information 731 (731a, 731b), each of which is a separate transaction.
The transaction information 731a indicates, for example, products purchased by a certain customer.
The transaction information 731b indicates, for example, products purchased by another customer. However, when the same customer orders products at different timings, the transaction information 731a and the transaction information 731b may be the same customer.
The transaction information 731 includes registration date and time information indicating the date and time when the product was registered. Also, the transaction information 731 includes the number of items purchased, the total amount, and some information on the product purchased by the customer. In the illustration, the registration date and time information included in the transaction information 731 displays only the time without the date, but the date and time may be displayed, or only the date without the time may be displayed. may be made. Moreover, the presence/absence of the date and the presence/absence of the time may be switchable according to user settings.

Each of the transaction information 731a and 731b is displayed so as to be selectable. That is, the display control unit 403 selectably displays product information for each transaction.
In the transaction list screen 730, it is possible to cancel a transaction by accepting a predetermined cancellation operation (for example, a swipe operation, an operation of a cancel button 1031d described later, etc.) for each transaction information 731 (for each transaction). . When the transaction cancellation operation is accepted, the transaction information 731 indicating the transaction is erased from the transaction list screen 730, and the number of transactions shown in the transaction icon 722 is displayed with "1" subtracted.

When the transaction information 731a is selected on the transaction list screen 730, the screen transitions to the transaction details screen 740 shown in FIG. 7(D).

FIG. 7D shows a transaction details screen 740. FIG. The transaction details screen 740 includes various product information 741 (741a to 741f) to be purchased, a total score column 742, a total amount column 743, and a subtotal button 744. Various product information 741 is displayed so as to be selectable by the operator. The various product information 741 includes quantity and price, respectively. If the product is on sale at the date and time when the product is registered, the price displayed in the price column is the price for the sale. The total score column 742 displays the total score of the product to be purchased. The total price column 743 displays the total price of the purchased product. The subtotal button 744 is a button for accepting the start of settlement processing.

(About change of product information 741)
The receiving unit 404 receives changes in the product information 741 displayed by the display control unit 403 for each transaction. Changes in product information 741 include price changes, quantity changes, tax rate changes, and product cancellations (deletion, cancellation). Specifically, when the product information 741f is selected on the transaction details screen 740, the screen transitions to a change acceptance screen 810 shown in FIG. 8(A).

FIG. 8A shows a change acceptance screen 810. FIG. Change acceptance screen 810 includes quantity change column 811 , price change column 812 , tax rate change column 813 , product cancel button 814 , and enter button 815 .
The quantity change column 811 is an area for accepting changes in the quantity of the product. Specifically, the quantity change column 811 includes a plus button for accepting the addition of "1" to the quantity and a minus button for accepting the subtraction of "1" from the quantity. When the plus button in the quantity change column 811 is pressed, the change reception screen 820 shown in FIG. 8B is displayed.
The price change column 812 is an area for accepting changes in the price of the product. For example, in the case of vegetables and fruits, some individuals may be damaged during delivery. In this case, the price of the product can be changed according to the judgment of the delivery staff.
The tax rate change column 813 is an area for accepting changes in the tax rate of the product.
The product cancellation button 814 is a button for accepting cancellation of registration of the product, that is, a button for accepting deletion or cancellation of the product.
The decision button 815 is a button for accepting a decision to register the product, which is displayed on the change acceptance screen 810 .

FIG. 8(B) shows the change acceptance screen 810 when "1" is added to the quantity of "chikuwa" shown in the quantity change column 811 on the change acceptance screen 810 of FIG. 8(A).

(Regarding settlement by settlement unit 405)
Here, the settlement unit 405 performs settlement for each transaction based on the product information displayed by the display control unit 403 . A specific description will be given below. For example, when the decision button 815 is selected on the change acceptance screen 820, the screen transitions to the transaction details screen 830 shown in FIG. 8(C).

FIG. 8C shows a transaction details screen 830. FIG. In the transaction details screen 830, the product information 741f has an increased quantity and price of "Chikuwa" compared to the transaction details screen 740 of FIG. 7(D), and the display mode is also different. Different display modes include different thicknesses and colors of the frames surrounding the product information 741f, different thicknesses and colors of the characters of the product information 741f, and different background colors of the product information 741f.

In addition, the total score column 742 and the total amount column 743 are also increased by adding 1 to "Chikuwa". When the subtotal button 744 is pressed on the transaction details screen 830, the screen transitions to the payment screen 840 shown in FIG. 8(D).

FIG. 8D shows a payment screen 840. FIG. The payment screen 840 includes an amount display field 841 , a numeric keypad 842 , an add payment button 843 and a confirmation button 844 .
The amount display column 841 includes a total amount column 841a, a shortfall amount column 841b, and a cash input column 841c.
The total amount column 841a indicates the total amount added by adding "1" to the quantity of "chikuwa".
The shortfall amount column 841b is a column for displaying the difference between the amount displayed in the total amount column 841a and the payment amount entered in the cash input column 841c.
The cash input field 841c is a field in which the amount of money input to the numeric keypad 842 is displayed.

The payment addition button 843 is a button for receiving a change or addition of payment type. Confirmation button 844 is a button for accepting completion of payment. When the payment addition button 843 is pressed on the payment screen 840, the screen transitions to the payment type selection screen 910 shown in FIG. 9(A).

FIG. 9A shows a payment type selection screen 910. FIG. A payment type selection screen 910 accepts selection of various payment types through a pop-up 911 . When, for example, "electronic money A" is selected from the payment types on the payment type selection screen 910, the screen transitions to a payment screen 920 shown in FIG. 9B.

In the payment screen 920 shown in FIG. 9B, an electronic money A column 841d is added to the amount display column 841 and displayed. Also, the cash entry field 841c shows that "1000 yen" has been entered using the numeric keypad 842. FIG. Also, the electronic money A column 841 d shows that “850 yen” has been input with the numeric keypad 842 . That is, it shows that 1000 yen is paid in cash and 850 yen is paid in electronic money A.

In addition, the shortfall amount column 841b indicates "0 yen". That is, the shortfall amount column 841b indicates that the difference between the amount displayed in the total amount column 841a and the payment amount entered in the cash input column 841c and the electronic money A column 841d is zero. When the confirm button 844 is selected on the payment screen 920, the payment is completed. I will add an example of a specific exchange in payment. For example, payment is made by handing over cash or reading electronic money or a credit card using a payment terminal brought by the delivery staff. Also, payment is made by code settlement, for example, by reading a QR code displayed on a customer terminal device owned by the customer with the mobile terminal device 120 .

In this way, the settlement unit 405 can settle each transaction based on the product information displayed by the display control unit 403 . It should be noted that after the payment is completed, it is possible to transition to the privilege screen 930 of FIG. 9(C).

(About obtaining a membership number)
The identification information acquisition unit 406 acquires a member number (member identification information) in settlement. The membership number may be obtained at the start of settlement, during settlement, or after completion of settlement. The identification information acquisition unit 406 acquires the membership number by reading the bar code (membership code) attached to the membership card. Note that the identification information acquisition unit 406 may acquire the membership number attached to the membership card by the delivery staff's operation input.

(Regarding purchase history output)
The history output unit 407 outputs the membership purchase history when the settlement unit 405 completes the settlement. The member purchase history includes product information (purchase history) for which payment has been completed, and the member number. Specifically, the history output unit 407 transmits the membership purchase history to the cloud server 100 . Thereby, the cloud server 100 updates the member information DB 102 . Specifically, cloud server 100 updates the purchase history corresponding to the membership number.

(Regarding the output of privilege information)
The privilege acquisition unit 408 acquires privilege information according to the member's purchase history. Specifically, the privilege acquisition unit 408 requests the cloud server 100 to send privilege information associated with the member number acquired by the identification information acquisition unit 406 . Thereby, the privilege acquisition unit 408 acquires the member information.

The privilege output unit 409 outputs privilege information acquired by the privilege acquisition unit 408 . The output mode of privilege information is an output mode by display on the display 306 or an output mode by printing on a sheet. When the privilege information is printed, the privilege information may be printed on the receipt, or the privilege information may be printed on a sheet different from the receipt. Moreover, the output mode of privilege information may also include the output mode by sound.

FIG. 9C shows a privilege screen 930 as a display example of privilege information. A privilege screen 930 displays a member number 931 , a privilege 932 , and a confirmation button 933 . The privilege 932 indicates points given for each purchased product. The award 932 may indicate the total points awarded this time. This point may be a point that can be used regardless of the product to be purchased at the next purchase, or a point that can be used only for the product when the same product is purchased next time. Also, the points may be points that can be used at the time of this payment. When the confirmation button 933 is selected on the privilege screen 930, the screen transitions to the receipt issue screen 940 shown in FIG. 9(D).

FIG. 9(D) shows a receipt issue screen 940 . The receipt issue screen 940 is a screen for accepting whether or not to issue a receipt. When the "Yes" button 941 is selected on the receipt issue screen 940, the printer 121 issues a receipt. If the "No" button 942 is selected on the receipt issue screen 940, no receipt will be issued. Therefore, receipts can be issued according to the customer's request.

(Regarding product registration)
The reception unit 404 can receive registration of new products.
On the transaction details screen 720 shown in FIG. 10A, when the scanner 309 is turned on and the product code 1021 is read by the scanner 309 as shown in FIG. The product information is queried, and the product corresponding to the product code 1021 is newly registered. If the new registration is registration (addition) within the same transaction, product information 741 shown in the transaction details screen 740 (see FIG. 7D) is newly added and displayed. On the other hand, if the new registration is the registration of a new transaction, the number of transactions indicated by the transaction icon 722 is displayed with "1" added. That is, when the product code is read by the scanner 309, the product information acquisition unit 401 may acquire one product information within the same transaction, or acquire one product information in a new transaction. be.

When the operator flicks the screen on the transaction details screen 720 shown in FIG. 10(A), the screen transitions to the selection screen 1030 shown in FIG. 10(C). The transaction details screen 720 of FIG. 7B, the transaction details screen 740 of FIG. 7D, and the transaction details screen 830 of FIG. 8C are also transitioned to the selection screen 1030 shown in FIG. Is possible.

FIG. 10C shows a selection screen 1030. FIG. The selection screen 1030 displays various selection buttons 1031 (1031a to 1031e). The selection button 1031a is a button for accepting a transition to a code input screen 1040 (FIG. 10(D)) for accepting manual entry of a product code. The selection button 1031b is a button for accepting a transition from a product category (vegetables, meat, alcoholic beverages, etc.) to a category registration screen (not shown) for accepting product registration. Note that the classification registration screen is a screen that allows the product to be specified by hierarchically transitioning the screen, for example, in the order of large category→small category→product.

The selection button 1031c is a button for turning on the camera 308 and changing to a screen for accepting reading of the code symbol 112 . The cancel button 1031d is a button for accepting a transaction reset (cancellation). In the transaction details screen 740 of FIG. 7(D) and the transaction details screen 830 of FIG. 8(C) in which product information is registered, it is possible to accept the cancellation of the transaction, but even one product information is registered. Transaction cancellation is not accepted from the transaction details screen 720 (product registration screen) shown in FIGS. 7B and 10A. The selection button 1031e is a button for accepting transition to the menu screen 710 (FIG. 7A).

Selection screen 1030 may display a selection button for accepting registration using a preset key. In the registration using the preset key, the preset key corresponding to the product is displayed, and the product can be registered by pressing the preset key.

FIG. 10D shows a code input screen 1040. FIG. The code input screen 1040 is a screen for accepting manual input of product codes. When a product code is entered on the code input screen 1040, a product corresponding to the product code is newly registered.

(Regarding registration of goods in a separate transaction)
It should be noted that the reception unit 404 can receive registration of products in another transaction different from the current transaction. For example, the reception unit 404 can receive registration of the next product at the delivery destination.

(Regarding the flow of processing in the product sales system 1)
FIG. 11 is a sequence diagram showing the flow of processing in the merchandise sales system 1. As shown in FIG. In FIG. 11, the registration device 110 reads the product code to acquire the product code (step S1101). For example, a store clerk receives a telephone order and causes a registration device to read the item ordered by the telephone, thereby reading the item code. In step S1101, the product code is acquired by reading the product code, but it is also possible to acquire the product code by accepting the operation of the preset key corresponding to the product. Then, the registration device 110 makes an inquiry about product information to the cloud server 100 (step S1102). This inquiry is specifically a request to acquire product information corresponding to the product code.

In response to the inquiry, the mobile terminal device 120 receives product information from the cloud server 100 and registers the product (step S1103). When the registration of the product for one transaction is completed, the registration device 110 issues the code symbol 112 including the product code and the date and time of registration (step S1104), and the series of processing ends.

On the other hand, the portable terminal device 120 reads the code symbol 112 according to the operation of the store clerk at the store 111 (step S1105). Then, the mobile terminal device 120 makes an inquiry about product information to the cloud server 100 (step S1106). This inquiry is specifically a request to acquire product information corresponding to the product code decoded from the code symbol 112 . Next, the mobile terminal device 120 receives product information from the cloud server 100 by inquiry (step S1107).

Then, the mobile terminal device 120 displays the acquired product information (step S1108). Next, the portable terminal device 120 performs settlement processing (see FIG. 12) at the delivery destination (step S1109), and ends the series of processing.

Note that the code symbol 112 includes the product code and the date and time of registration, but the code symbol 112 is not limited to this. For example, it is possible to issue a transaction number (including a provisional number) when the registration device 110 registers the product. In this case, code symbol 112 may include the transaction number. Also, in this case, the mobile terminal device 120 may display the transaction number on the transaction list screen 730 shown in FIG. 7C by reading the code symbol 112 .

In addition, the operation of the registration device 110 by the store clerk differs between a normal shopper's transaction at the store 111 and a home delivery service transaction. Specifically, in the case of normal shopper transactions, the store clerk operates the subtotal button after registering the product. On the other hand, in the case of a home delivery service transaction, the store clerk issues the code symbol 112 after registering the product. The issue operation of the code symbol 112 is, for example, pressing a code symbol issue button displayed on the display of the registration device 110 .

Further, the registration device 110 may also print the date and time of registration on the sheet on which the code symbols 112 are printed. This sheet is attached to a basket, a bag, or the like in which the products at the delivery destination are stored. As a result, the delivery staff can confirm and distinguish the registration date and time for each product to be delivered (for each transaction), so that it is possible to prevent the wrong product to be delivered.

(An example of settlement processing performed by the mobile terminal device 120)
FIG. 12 is a flow chart showing an example of settlement processing performed by the mobile terminal device 120 . In FIG. 12, the mobile terminal device 120 determines whether or not the display start of the transaction list screen 730 (see FIG. 7C) has been accepted (step S1201). Specifically, accepting the start of display of the transaction list screen 730 means, for example, pressing the transaction icon 722 on the transaction detail screen 720 (see FIG. 7B).

The mobile terminal device 120 waits until accepting the start of display of the transaction list screen 730 (step S1201: NO). Upon receiving the start of displaying the transaction list screen 730 (step S1201: YES), the mobile terminal device 120 displays the transaction list screen 730 (see FIG. 7C) (step S1202). Then, the mobile terminal device 120 accepts selection of one transaction on the transaction list screen 730 (step S1203).

Next, the mobile terminal device 120 determines whether or not a change in the product information 741 (registered content) has been received (step S1204). If the change of the product information 741 is not accepted (step S1204: NO), the mobile terminal device 120 proceeds to step S1206. When the change of the product information 741 is accepted (step S1204: YES), the mobile terminal device 120 updates the product information 741 (step S1205).

Then, the mobile terminal device 120 determines whether or not the payment has been completed (step S1206). Completion of payment means, for example, pressing the confirm button 844 (see FIG. 8(D)). If payment has not been completed (step S1206: NO), the mobile terminal device 120 returns to step S1204. If payment has been completed (step S1206: YES), the mobile terminal device 120 determines whether the customer is a member (step S1207). If the customer is not a member (step S1207: NO), specifically, if the member number is not acquired during the settlement process, the mobile terminal device 120 proceeds to step S1210.

If the customer is a member (step S1207: YES), specifically, if the member number is acquired during the settlement process, the mobile terminal device 120 transmits the membership purchase history to the cloud server 100 (step S1208). ). Then, the mobile terminal device 120 receives privilege information from the cloud server 100 and outputs the received privilege information (step S1209). Next, the mobile terminal device 120 causes the printer 121 to issue a receipt (step S1210).

Then, the mobile terminal device 120 transmits a settlement completion notice indicating that the settlement has been completed to the cloud server 100 (step S1211), and ends the series of processes. When the cloud server 100 receives the settlement completion notice, it stores that the settlement of the transaction has been completed. Note that the cloud server 100 may transmit to the registration device 110 that the settlement of the transaction has been completed upon receiving the settlement completion notification. The registration device 110 may output to a display or the like that the transaction has been settled.

As described above, the mobile terminal device 120 according to the present embodiment selectably displays product information registered by the registration device for each transaction, and settles each transaction based on the displayed product information. to As a result, when the delivery staff deliver the product in the home delivery service, the purchased product and the price can be easily grasped for each transaction, so that the settlement can be easily and accurately performed. Therefore, it is possible to reduce the workload of the delivery staff when delivering the product.

Further, the mobile terminal device 120 according to the present embodiment accepts changes in the displayed product information for each transaction. As a result, the delivery staff at the delivery destination can change the product or discount the price according to the customer's request. Therefore, it is possible to flexibly respond to the customer's request at the delivery destination, thereby improving the convenience of the home delivery service.

In addition, the mobile terminal device 120 according to the present embodiment accepts registration of new products. As a result, at the delivery destination, the customer can purchase products that the customer did not plan to purchase, and the delivery staff can sell the products brought in separately. Therefore, the convenience of the home delivery service can be improved.

In addition, the mobile terminal device 120 according to the present embodiment inputs a product code and registration date/time information when the product code was input. This makes it possible to simplify the information obtained from the registration device 110 (for example, the information of the code symbols 112). In addition, the mobile terminal device 120 displays product information corresponding to the product code and registration date/time information for each transaction. This allows the delivery staff to easily grasp the registration date and time of the product for each transaction. Therefore, it is possible to easily confirm that there is no error in the delivery date and that there is no error in the bargain item corresponding to the registration date and time.

In addition, the mobile terminal device 120 according to the present embodiment outputs a membership purchase history including the membership number obtained at the time of payment and product information. Thereby, in the home delivery service, it is possible to appropriately output the membership purchase history when the payment is normally completed. Therefore, it is possible to appropriately give benefits to the member.

Also, the mobile terminal device 120 according to the present embodiment outputs privilege information according to the membership purchase history. Thereby, in the home delivery service, when the payment is completed, the customer can be notified of the privilege information. Therefore, since the customer can be urged to purchase the product next time, it is possible to arouse the customer's willingness to purchase.

Further, in the product sales system 1, the cloud server 100 does not manage products purchased by customers. Therefore, according to the product sales system 1, the configuration can be relatively simple, and the cost for managing product information in the cloud server 100 can be suppressed.

In addition, since the merchandise sales system 1 does not use personal information, even a seeming customer can use the home delivery service. Therefore, it is possible to make it easier for customers who do not want to present their personal information to use the home delivery service, thereby contributing to the spread of the home delivery service.

(Modification of embodiment)
Modifications of the embodiment will be described below. In addition, in the following modified examples, the description of the contents described in the above-described embodiment will be omitted as appropriate.

(Modification 1)
First, Modification 1 of the embodiment will be described. In the above-described embodiment, the product sales system 1 does not use personal information such as the customer's name and address. In Modified Example 1, a merchandise sales system 1 that uses personal information such as customer names and addresses will be described.

In Modified Example 1, the code symbol 112 issued by the registration device 11 is made to include personal information. Personal information includes name, address, date of birth, telephone number, gender, and the like. For example, the clerk may ask the customer for personal information when receiving an order, and the clerk may operate and input the personal information into the registration device 110 when registering the product. Further, registration device 110 may store personal information input in the past as a history, and acquire personal information from the history. It is also possible to include personal information in member information. In this case, the store clerk inputs the customer's name and the like obtained when receiving the order into the registration device 11 . Thereby, the registration device 110 may obtain personal information from the member information specified based on the name or the like.

Further, in Modification 1, it is possible to include the customer's personal information in the transaction information 731 of the transaction list screen 730 shown in FIG. 7(C). Specifically, the transaction information 731 can display the customer's name and address.

According to Modification 1, the delivery staff can deliver the product after confirming the address, name, product, and the like. As a result, it is possible to prevent the product from being mixed up. Therefore, it is possible to reduce the workload of the delivery staff when delivering the product.

(Modification 2)
Next, Modification 2 of the embodiment will be described. In the above-described embodiment, the merchandise sales system 1 has been described in which an order for merchandise is received at the store 111 by telephone and the store clerk registers the merchandise in the registration device 11 . In Modified Example 2, a merchandise sales system 1 in which merchandise is ordered from a store 111 using a terminal device owned by a customer (hereinafter referred to as a "customer terminal device") will be described.

In Modification 2, the customer terminal device is connected to the cloud server 100 via the network 140 . The customer terminal device is a smart phone, a tablet terminal, a personal computer, a mobile phone, or the like. A predetermined application is installed in the customer terminal device. The customer terminal device displays a screen for accepting an order when a predetermined application is started. Upon receiving the order, the customer terminal device transmits order information to the cloud server 100 . When the cloud server 100 receives the order information from the customer terminal device, the cloud server 100 transmits the order information to the registration device 110 . When the registration device 110 receives the order information from the cloud server 100, the registration device 110 registers the product and issues the code symbol 112 based on the order information.

It should be noted that personal information is not included in the order information. Therefore, the code symbol 112 does not contain personal information. However, if personal information such as name and phone number is registered when registering a predetermined application, it is possible to obtain personal information, so the personal information may be included in the order information. In this case, the code symbol 112 may include personal information.

According to Modification 2, the customer himself/herself can place an order for the product using the customer terminal device. Therefore, it is possible to reduce the work load of the store clerk at the time of product delivery. In addition, since the store clerk does not need to perform the product registration operation at the store 111, the workload associated with the registration of the store clerk can be reduced.

(Modification 3)
Next, Modification 3 of the embodiment will be described. In Modified Example 3, a merchandise sales system 1 that performs settlement using the customer's address information and the GPS function of the mobile terminal device 120 will be described.

In Modified Example 3, the registration device 110 acquires address information indicating the delivery destination for each transaction. The address information may be acquired by an operation input by the store clerk, or may be acquired from the member information when the member information includes the address information. Further, the registration device 110 may store the address information input in the past as a history, and acquire the address information from the history.

The registration device 110 issues a code symbol 112 containing address information. The mobile terminal device 120 can obtain the address information for each transaction by reading the code symbol 112 . For example, the customer's address information can be included in the transaction information 731 of the transaction list screen 730 shown in FIG. 7(C).

Portable terminal device 120 compares (hereinafter referred to as “position comparison”) whether or not the address information of the delivery destination and the information on the current position obtained by GPS unit 307 match, and notifies about the position comparison. may be performed. Specifically, for example, when the transaction information 731 is selected at the delivery destination, the mobile terminal device 120 compares the position indicated by the address information with the current position obtained by the GPS unit 307 . As a result of the position comparison, if they match, the fact may be notified, and if they are different, the fact may be notified.

Also, the mobile terminal device 120 may control whether or not the payment can be made using the result of the position comparison. Specifically, the mobile terminal device 120 may allow settlement when the position comparison result indicates a match, and may disable settlement when the position comparison result indicates a difference. Further, the mobile terminal device 120 may notify that the settlement is possible when the settlement is possible, and notify that the settlement is impossible when the settlement is impossible.

Also, the mobile terminal device 120 may have a route search function. If there are multiple delivery destinations, the mobile terminal device 120 may search for a suitable route in order of delivery and display the route on the display 306 . Note that the position comparison function may be switched on/off. In this way, even when the product is delivered to the customer at a place different from the delivery destination, it is possible not to control the notification related to the position comparison and control the settlement related to the position comparison.

According to Modified Example 3, the delivery staff can perform notification and settlement based on the comparison result of the position comparison, so that it is possible to suppress the misunderstanding of the product at the time of delivery. Therefore, it is possible to reduce the workload of the delivery staff when delivering the product.

A summary of the embodiments will be described below.
[Title of the invention] Program, portable payment device, and system [Technical field]
The present invention relates to a program, a portable checkout device, and a system.
[Background technology]
Conventionally, various home delivery services have spread. As a related technology, there is known a method of predicting the next order date based on the past order data of the supplier and sending an order promotion e-mail by e-mail before the predicted order date to encourage the next order. (See Patent Document 1, for example).
[Prior art documents]
[Patent Literature]
[Patent Document 1] JP-A-2007-328402 [Summary of the Invention]
[Problems to be solved by the invention]
However, with the conventional technology, there is a problem that when the delivery staff pays the bill, it may not be possible to easily pay the bill, which may impose a workload on the delivery staff.
SUMMARY OF THE INVENTION The present invention has been made in view of such circumstances, and an object of the present invention is to provide a technique for reducing the work load of the delivery staff for settlement.

[Means to solve the problem]
(1) In order to solve the above-described problems, a program according to one aspect of the present invention includes product information acquisition means for acquiring product information registered by a registration device, and display of the product information in a selectable manner for each transaction. and a settlement means for performing settlement for each transaction based on the product information displayed by the display control means. .
According to the above configuration, when the delivery staff deliver the product in the home delivery service, the purchased product and the price can be easily grasped for each transaction, so that the settlement can be easily and accurately performed. Therefore, it is possible to reduce the workload of the delivery staff when delivering the product.

(2) In the configuration of (1) above, the portable settlement device may include reception means for receiving changes in the product information displayed by the display control means for each transaction.
According to the above configuration, at the delivery destination, the delivery staff can change the product or discount the price according to the customer's request. Therefore, it is possible to flexibly respond to the customer's request at the delivery destination, thereby improving the convenience of the home delivery service.

(3) In the configuration of (2) above, the accepting means may accept a new product registration.
According to the above configuration, at the delivery destination, the customer can purchase a product that the customer did not plan to purchase, and the delivery staff can sell the product brought in separately. Therefore, the convenience of the home delivery service can be improved.

(4) In any one of the configurations (1) to (3) above, the portable payment device inputs identification information for identifying a product and registration date/time information indicating the date/time when the identification information was input. An input means is provided, wherein the product information acquisition means acquires the product information corresponding to the identification information, and the display control means displays the product information and the registration date/time information for each transaction. good too.
According to the above configuration, information obtained from the registration device 110 (for example, information of the code symbol 112) can be simplified. Also, the delivery staff can easily grasp the registration date and time of the product for each transaction. Therefore, it is possible to easily confirm that there is no error in the delivery date and that there is no error in the bargain item corresponding to the registration date and time.

(5) In any one of the configurations (1) to (4) above, the portable checkout device includes identification information acquisition means for acquiring member identification information that identifies a customer who is a member in the checkout; A history output means for outputting a member purchase history including the product information for which payment has been completed and the member identification information may be provided.
According to the above configuration, it is possible to appropriately output the membership purchase history when the payment is normally completed in the home delivery service. Therefore, it is possible to appropriately give benefits to the member.

(6) In the configuration of (5) above, the portable payment device includes privilege acquisition means for acquiring privilege information according to the membership purchase history, and privilege output means for outputting the privilege information. You may do so.
According to the above configuration, in the home delivery service, it is possible to notify the customer of privilege information when payment is completed. Therefore, since the customer can be urged to purchase the product next time, it is possible to arouse the customer's willingness to purchase.

(7) In order to solve the above-described problems, a portable payment device according to another aspect of the present invention includes product information acquisition means for acquiring product information registered by a registration device, and the product information for each transaction. The portable settlement device is characterized by comprising display control means for selectably displaying, and settlement means for performing settlement for each transaction based on the product information displayed by the display control means.
According to the above configuration, when the delivery staff deliver the product in the home delivery service, the purchased product and the price can be easily grasped for each transaction, so that the settlement can be easily and accurately performed. Therefore, it is possible to reduce the workload of the delivery staff when delivering the product.

(8) In order to solve the above problems, a system according to another aspect of the present invention is a system comprising a registration device and a portable settlement device, wherein the registration device registers product information. , the portable settlement device includes product information acquisition means for acquiring product information registered by the registration device, display control means for selectively displaying the product information for each transaction, and display control means for displaying the product information. and settlement means for performing settlement for each transaction based on the product information.
According to the above configuration, when the delivery staff deliver the product in the home delivery service, the purchased product and the price can be easily grasped for each transaction, so that the settlement can be easily and accurately performed. Therefore, it is possible to reduce the workload of the delivery staff when delivering the product.

It should be noted that all or part of each function (input/output, storage, processing (including judgment)) of the portable terminal device 120 described above is realized by another device different from the device described as the execution subject of the function. may

Specifically, in the above description, the configuration in which the mobile terminal device 120 includes the functional units 401 to 409 has been described. All or part of the functional units 401 to 409 may be provided in another computer device. For example, all or part of the functional units 401 to 409 may be provided in the cloud server 100, may be provided in the registration device 110, or may be provided in a computer device other than these. good too. Further, the number of computers provided with the functional units 401 to 409 may be plural or may be one.

In relation to the above, the mobile terminal device 120 may function as a so-called thin client that specializes in the input/output interface portion regarding the display of product information that can be selected for each transaction. That is, the mobile terminal device 120 receives various inputs (operator's operation, detection by a device such as a scanner), transmits input information (operation information, etc.) to the cloud server 100, and the cloud server 100 based on the input information. (update screen information, device control information, etc.) may be received and various outputs (display on the display unit, device control) may be performed.

A program for realizing the product sales system 1 and the portable terminal device 120 described above may be recorded in a computer-readable recording medium, and the program may be read and executed by a computer system. It should be noted that the "computer system" referred to here includes hardware such as an OS and peripheral devices. The term "computer-readable recording medium" refers to portable media such as flexible discs, magneto-optical discs, ROMs and CD-ROMs, and storage devices such as hard discs incorporated in computer systems. In addition, "computer-readable recording medium" means a volatile memory (RAM) inside a computer system that acts as a server or client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. , includes those that hold the program for a certain period of time. Further, the above program may be transmitted from a computer system storing this program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in a transmission medium. Here, the "transmission medium" for transmitting the program refers to a medium having 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. Further, the program may be for realizing part of the functions described above. Further, it may be a so-called difference file (difference program) that can realize the above-described functions in combination with a program already recorded in the computer system.

1 Product sales system 100 Cloud server 101 Product master 102 Member information DB 110 Registration device 112 Code symbol 120 Portable terminal device 121 Printer 301 CPU 302 Memory 306... Display, 308... Camera, 309... Scanner, 401... Merchandise information acquisition unit, 402... Input unit, 403... Display control unit, 404... Reception unit, 405... Checkout unit, 406... Identification information acquisition unit, 407... History Output unit 408 Privilege acquisition unit 409 Privilege output unit

Claims (6)

product information acquisition means for acquiring product information registered by the registration device;
display control means for selectively displaying the product information for each transaction;
settlement means for performing settlement for each transaction based on the product information displayed by the display control means;
A program characterized by causing a computer to function as a portable settlement device. The portable payment device is
receiving means for receiving, for each transaction, a change in the product information displayed by the display control means;
2. The program according to claim 1, comprising: The reception means receives registration of a new product,
3. The program according to claim 2, characterized by: The portable payment device is
An input means for inputting identification information for identifying a product and registration date and time information indicating the date and time when the identification information was input,
The product information acquisition means acquires the product information corresponding to the identification information,
The display control means displays the product information and the registration date/time information for each transaction.
4. The program according to any one of claims 1 to 3, characterized by: product information acquisition means for acquiring product information registered by the registration device;
display control means for selectively displaying the product information for each transaction;
settlement means for performing settlement for each transaction based on the product information displayed by the display control means;
A portable settlement device comprising: A system comprising a registration device and a portable settlement device,
The registration device registers product information,
The portable payment device is
product information acquisition means for acquiring product information registered by the registration device;
display control means for selectively displaying the product information for each transaction;
settlement means for performing settlement for each transaction based on the product information displayed by the display control means;
A system characterized by comprising:

Images