Shopping assistance server, shopping assistance method, and recording medium

WO2025186918A8PCT designated stage Publication Date: 2025-10-02NEC CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2024/008401
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-03-06
Publication Date
2025-10-02

AI Technical Summary

Technical Problem

Existing shopping services face inefficiencies when customers request proxy shopping, as they often require manual intervention and multiple terminal operations for product delivery and billing, which can be burdensome for both agents and store employees.

Method used

A shopping support server that includes a request receiving unit to process information from vehicle drivers, a request sending unit to communicate with store staff, and a billing processing unit to automate the billing process, reducing the need for manual operations by agents and staff.

Benefits of technology

The system enhances the efficiency of proxy shopping services by automating the request and billing processes, thereby reducing the burden on agents and store employees while ensuring seamless product delivery and payment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2024008401_02102025_PF_FP_ABST
    Figure JP2024008401_02102025_PF_FP_ABST
Patent Text Reader

Abstract

A shopping assistance server according to the present disclosure comprises: a request reception means that receives, from a terminal used by a crew member of a vehicle that goes back and forth between the home of a member and a store to periodically transport the member, request information that identifies a requester who requests a proxy to shop in the store, and requested merchandise that the requester requests the purchase thereof; a request transmission means that transmits the request information to a terminal used by a staff member of the store; and an invoice processing means that processes an invoice for the price of the requested merchandise to the requester by using read information associated with the request information and read by a merchandise registration device of the store from a medium presented by the proxy.
Need to check novelty before this filing date? Find Prior Art

Description

Shopping support server, shopping support method and recording medium

[0001] The present disclosure relates to a shopping support server and the like.

[0002] There are services that transport customers who have difficulty going from their homes to stores and then returning their purchases from the store. For example, a shared vehicle operated by a service provider picks up a customer near their home at a designated time on a designated day of the week. The vehicle then transports the customer to the store. After the customer has completed their shopping at the store, they get back into the vehicle, which then transports the customer back to their home.

[0003] There are also shopping agent services. Patent Document 1 discloses a shopping agent service provision method in which, upon receiving a shopping agent request from a client terminal, shopping information is sent to a shopping agent terminal. In the method of Patent Document 1, the shopping agent terminal sends product delivery instructions to a transportation service provider terminal. This reduces the burden on the shopping agent to deliver the products.

[0004] Japanese Patent Application Laid-Open No. 2023-094909

[0005] In some cases, customers do not go to the store and do not ride in the vehicle of the business that regularly transports them to the store. If a customer who does not go to the store requests a proxy to do their shopping at the store, it would be efficient if the goods could be delivered to the customer using the business's vehicle.

[0006] One of the objects of the present disclosure is to provide a shopping support server or the like that supports the improvement of efficiency in proxy shopping.

[0007] In one aspect of the present disclosure, the shopping support server includes a request receiving means for receiving, from a terminal used by a driver of a vehicle that regularly transports members between the member's home and the store, request information specifying a requester who requests an agent to shop at the store and the requested product that the requester requests to purchase; a request sending means for sending the request information to a terminal used by a staff member of the store; and a billing processing means for processing a bill for the requested product from the requester using read information linked to the request information that is read from a medium presented by the agent by the store's product registration device.

[0008] A shopping assistance method in one aspect of the present disclosure receives request information from a terminal used by a driver of a vehicle that regularly transports a member between the member's home and a store, identifying a client who requests an agent to shop at the store and the requested product that the client requests to purchase, sends the request information to a terminal used by a store employee, and processes a bill for the requested product from the client using read information linked to the request information that is read from a medium presented by the agent by a product registration device in the store.

[0009] A program according to one aspect of the present disclosure causes a computer to execute a process of receiving, from a terminal used by a driver of a vehicle that regularly transports a member between the member's home and a store, request information specifying a requester requesting an agent to shop at the store and a requested product that the requester requests to purchase, transmitting the request information to a terminal used by a store staff member, and processing a bill for the requested product from the requester using read information linked to the request information that is read by a product registration device of the store from a medium presented by the agent. The program may be stored in a computer-readable non-transitory recording medium.

[0010] One example of the effect of the present disclosure is that it can help improve the efficiency of shopping proxy services.

[0011] FIG. 1 is an explanatory diagram showing an overview of an example of a service. FIG. 1 is an explanatory diagram showing an overview of an example of a service. FIG. 2 is an explanatory diagram showing an example of connection between a shopping support server and other devices. FIG. 3 is a block diagram showing an example of the configuration of a shopping support server. FIG. 4 is a flowchart showing an example of the operation of the shopping support server. FIG. 5 is a flowchart showing an example of the operation of each device. FIG. 6 is a diagram showing an example of the screen of a crew terminal. FIG. 7 is a diagram showing an example of a confirmation screen for request information. FIG. 8 is a block diagram showing an example of the configuration of a shopping support server. FIG. 9 is a flowchart showing an example of the operation of the shopping support server. FIG. 10 is a flowchart showing an example of the operation of each device. FIG. 11 is a block diagram showing an example of the hardware configuration of a computer.

[0012] The shopping support server according to the present disclosure can support the implementation of shopping proxy services at stores. In the shopping proxy services implemented according to the present disclosure, a vehicle of a transportation service is utilized to transport a member back and forth between their home and the store. The trip between their home and the store may include a trip between a bus stop near the member's home and the store. The shopping support server and transportation service are provided, for example, by a store. The shopping support server according to the present disclosure may be used when a client requests a member of a transportation service to purchase a requested product at a store. Alternatively, the shopping support server according to the present disclosure may be used when a client requests a store employee to do the shopping. The shopping support server may support both the case where a transportation service member performs shopping proxy services and the case where a store employee performs shopping proxy services. Examples of a person's behavior in each case are described below using FIGS. 1 and 2 .

[0013] Using FIG. 1, an example of a person's behavior when a requester requests a member of a transportation service to shop for a requested product at a store will be described. Staff member S1 is a driver of a vehicle that transports members between their home and the store. The vehicle, for example, makes rounds between the homes of multiple members. Here, for example, the requester is a member who has signed up for regular transportation to the store and cancels their ride in the vehicle. Customer C1 is a requester who requests shopping assistance. Customer C2 is a member of the transportation service who receives transportation by vehicle. Customer C2 gets into the vehicle to shop at the store. Customer C1 may also be a member of the transportation service. In this case, customer C1 cancels their ride in the vehicle that came to pick them up and requests that the service assist them with their shopping. Customer C1 requests customer C2 to shop at the store. As shown in FIG. 1(i) at the time of pick-up, customer C1 may ask customer C2, for example, a friend who lives nearby, to shop for them. Customer C1 verbally informs staff member S1, who has come to pick up customer C1 or customer C2 in a vehicle, that they will be requesting that customer C2 do some shopping for them. Customer C1 verbally tells staff member S1 what products they would like to request staff member S1 to purchase. Staff member S1 operates a terminal to send information to the shopping support server. Customer C1 may request that customer C2 do their shopping for them directly over the phone or in person, or they may request this through staff member S1. Customer C1 may leave customer C2's card M1 with customer C2. Customer C1 may also hand customer C2 a shopping list with the products written on it. In this case, customer C2 may inform staff member S1 on behalf of customer C1 that they have been requested to do the shopping for them.

[0014] As shown in Figure 1 (ii) After Arrival at the Store, after the vehicle arrives at the store, customer C2 goes shopping at the store. Customer C2 may receive assistance from store staff S2 and S3 in purchasing the requested items. Staff S2 assists the customer in his / her shopping at the store. Staff S3 operates the product registration device. Customer C2 purchases the requested items using customer C1's card M1. After finishing his / her shopping at the store, customer C2 gets back into the vehicle and hands over the requested items to customer C1. In this way, shopping is carried out on behalf of the customer.

[0015] Using Figure 2, we will explain the actions of a person when a client requests a store employee to shop for a requested item at a store. Customer C1 is a member of a transportation service. As shown in Figure 2(i) at the time of pick-up, customer C1 verbally informs employee S1, the driver of the vehicle that has come to pick them up, that he or she is canceling the ride. As in Figure 1, customer C1 verbally tells employee S1 the item he or she would like to purchase. Employee S1 operates a terminal to send information to the shopping support server. As shown in Figure 2(ii) after arrival at the store, store employee S2 uses the information received by the terminal from the shopping support server to shop for customer C1. Store employee S2 hands over the requested item to employee S1. Employee S1 hands over the requested item to customer C1. Shopping can also be done on behalf of customer C1 in this way.

[0016] [First embodiment] An example of a connection between the shopping support server 100 and other devices in the present disclosure will be described with reference to Figure 3. The shopping support server 100 is connected to other devices via a communication network 50 by wire or wirelessly. The shopping support server 100 is connected to, for example, a crew terminal 10, a supporter terminal 20, a product registration device 30, and a database 40.

[0017] The crew terminal 10 is a terminal used by a crew member of a vehicle that regularly transports members between their homes and the store. In Figures 1 and 2, employee S1 uses the crew terminal 10. The crew terminal 10, for example, references the database 40 to display a list of members.

[0018] The crew terminal 10 generates request information that identifies the requester and the requested product. The requester is a customer who requests a proxy to shop at a store. In Figures 1 and 2, the requester is customer C1. In this embodiment, it is assumed that the requester is a member who uses the transportation service. The requested product is a product that the requester requests the proxy to purchase. The proxy purchases the requested product at the store for the requester. In Figures 1 and 2, the proxy is customer C2 or employee S2. The crew terminal 10 generates request information based on input operations by the crew.

[0019] The request information includes, for example, member information that identifies the requester. The member information is, for example, a member ID (identifier) ​​that uniquely identifies the member, such as a member number. The crew terminal 10 may accept input of member information by accepting an operation to select a member from a list of members to be transported by the vehicle.

[0020] The request information also includes product information that identifies the requested product. The product information is, for example, a product ID or product name that identifies the product. The crew terminal 10 may display products that the customer has previously purchased in a selectable manner. The crew terminal 10 may also search the database 40 for products sold in the store. The crew searches for products using the product name heard from the customer. The crew terminal 10 displays the search results in a selectable manner. The crew terminal 10 may also display products that the customer has previously purchased preferentially. The crew terminal 10 then accepts input of product information by accepting an operation to select a product.

[0021] The crew terminal 10 may also generate product information indicating characters entered from the keyboard. The product information may be part of a product name that is an abbreviation of the product name stored in the database 40. The product information may also be characters indicating the characteristics of the product, such as the general type of product. The product information may also be an image taken by the crew using a camera provided in the crew terminal 10. For example, the product information may be an image of a handwritten shopping note by a member. The crew terminal 10 may generate product information including characters recognized from the image of the shopping note using character recognition technology.

[0022] The request information may include information identifying the agent. When the requester requests a member of the transportation service to act on his / her behalf, the information identifying the agent includes member information. The crew terminal 10 may accept input of member information by accepting an operation to select a member from a list of members who will be transported by vehicle.

[0023] The supporter terminal 20 is a terminal used by store staff who support customers in the store. The staff can walk around the store with the customer and support the customer. For example, the staff may help the customer walk or carry their luggage. The staff may support a member of a transportation service who has been asked by a client to do shopping on their behalf. Alternatively, the staff may do shopping on the client's behalf. In Figures 1 and 2, staff member S2 uses the supporter terminal 20.

[0024] The types of the crew terminal 10 and the supporter terminal 20 are not particularly limited and may include smartphones, tablet-type terminals, and the like.

[0025] The product registration device 30 registers products purchased by customers. Furthermore, the product registration device 30 processes payment for the products. The product registration device 30 is, for example, a Point of Sales (POS) register connected to a POS server that manages sales at the store. The product registration device 30 transmits read information read from a medium presented by an agent to the shopping assistance server 100.

[0026] Each member may have a card that records member information. If the member of the transportation service is an agent, the agent may present the card received from the client as a medium. The member information may be recorded on the card using, for example, a barcode, a two-dimensional code, an IC (Integrated Circuit) chip, or a magnetic stripe. The card on which the member information is recorded may be a prepaid card. The product registration device 30 reads the member information recorded on the card via an IC tag reader, a code scanner, or a magnetic card reader. The product registration device 30 transmits the member information read from the card as read information.

[0027] If the agent is a store employee, the employee may present the supporter terminal 20 as a medium. For example, the employee may hold the supporter terminal 20 over an IC tag reader. Alternatively, the employee may hold the screen displayed on the supporter terminal 20 over a code scanner. The product registration device 30 reads the payment code from the supporter terminal 20 via the IC tag reader or code scanner. The payment code is a code linked to the request information and identifies the requester's payment method. The payment code may be a request ID that identifies the request information, or the requester's membership information. The payment method may be, for example, the requester's prepaid balance, credit card, or direct debit. The product registration device 30 transmits the read payment code as read information.

[0028] The database 40 manages information about members of a service that transports customers between their homes and stores. The managed member information includes, for example, member information, name, address, and the date and time of pickup by vehicle. The database 40 may also manage products sold at the store and customer purchase histories. The database 40 stores product IDs and product names of products sold at the store. The database 40 may also store product characteristics for each product. Product characteristics include, for example, product type, size, flavor, etc. The granularity of product type classification is determined as appropriate.

[0029] The database 40 may manage the balance of a customer's prepaid card. The database 40 may also manage the customer's payment method used for payments at stores, linked to the customer's membership information. For example, the database 40 may manage information on a bank account to which payment for merchandise is to be charged. This allows a customer to pay for merchandise at a store by bank transfer by presenting a card with their membership information recorded thereon.

[0030] A store operator may be in the business of delivering products to customers' homes on a regular basis. In such cases, the database 40 may manage payment methods used for paying for the regular product deliveries. Payment methods include credit cards and direct debit. The database 40 may be composed of multiple databases, each of which manages the various types of information described above.

[0031] An example of the configuration of shopping support server 100 in the present disclosure will be described using Fig. 4. Shopping support server 100 includes a request receiving unit 101, a request sending unit 102, and a billing processing unit 103. Shopping support server 100 may be realized by combining multiple devices or by a single device.

[0032] The request receiving unit 101 receives request information identifying the requester and the requested item from the crew terminal 10 used by the vehicle crew. The request information indicates the details of the shopping proxy request that the crew has obtained from the requester. The request information includes the member information of the requester and product information of the requested item. The request information received from the crew terminal 10 may also include information identifying the proxy.

[0033] The request sending unit 102 sends the request information received by the request receiving unit 101 to a terminal used by a store staff member. For example, the request sending unit 102 sends the request information to the supporter terminal 20, which is an example of a staff member's terminal. The request sending unit 102 also sends the request information to the product registration device 30, which is an example of a staff member's terminal. After the agent, who is a member of the transportation service, arrives at the store, the staff member using the supporter terminal 20 and the staff member operating the product registration device 30 can support the agent. The staff member using the supporter terminal 20 can also shop on behalf of the requester as a representative.

[0034] The billing processing unit 103 processes billing for the requested product to the client using the read information read from the medium presented by the agent in the store's product registration device 30. The agent performs procedures for purchasing the requested product on the client's behalf in the product registration device 30.

[0035] The product registration device 30 registers the requested products brought to it by the agent. The billing processing unit 103 receives information on the prices of the registered requested products from the product registration device 30. Using the received price information, the billing processing unit 103 processes the billing for the requested products registered in the product registration device 30. The billing processing unit 103 may add a fee for the shopping agent service to the price of the requested products and process the billing to the client. The product registration device 30 transmits the sales amount of the registered requested products to a POS server (not shown).

[0036] The read information is information linked to the request information accepted by the request accepting unit 101. The cases where the read information is member information and a payment code will be described below.

[0037] When the agent is a member of the transportation service, the billing processing unit 103 uses the read information read from the card that the agent has received from the client. The billing processing unit 103 receives information on the product price and the read member information from the product registration device 30. The billing processing unit 103 may process the billing using the balance of a prepaid card linked to the member information. The billing processing unit 103 may also process the billing using a payment method linked to the member information. For example, the billing processing unit 103 processes the billing using a payment method used to pay for regular product deliveries to the client's home. The billing processing unit 103 enables payment using a card presented by the agent, without the agent having to operate a terminal such as a smartphone for payment. This reduces the burden on the agent.

[0038] If the representative is a store employee, the billing processing unit 103 uses the read information read from the supporter terminal 20. The billing processing unit 103 receives information on the price of the product and the read information, which is the payment code, from the product registration device 30. The billing processing unit 103 processes the bill using the payment method specified by the payment code.

[0039] The configuration examples of each device have been described above. Below, an example of the operation of each device will be described.

[0040] First, an example of the operation of the shopping support server 100 will be described using the flowchart in Fig. 5. The shopping support server 100 can start the operation in Fig. 5 after the departure of a vehicle transporting a member between the member's home and the store.

[0041] In step S101, the request receiving unit 101 receives request information identifying the requester and the requested product from the driver terminal 10 used by the vehicle driver. In step S102, the request sending unit 102 transmits the request information received by the request receiving unit 101 to a terminal used by a store employee. In step S103, the billing processing unit 103 processes billing of the requester for the requested product using read information read from the medium presented by the agent in the store's product registration device 30. With this, the shopping support server 100 completes the operation of FIG. 5.

[0042] Next, an example of the operation of the shopping support server 100 and other devices will be described with reference to Figures 6 and 7. The steps of the shopping support server 100 correspond to the steps shown in Figure 5.

[0043] When a member of the transportation service handles shopping on behalf of a member, each device may perform the operation shown in FIG. 6. In step S11, the crew terminal 10 displays a list of members to be transported by vehicle. FIG. 8 is a diagram showing an example of a screen displayed by the crew terminal 10. The screen of FIG. 8 displays a list including the member information, member name, pickup date and time, and address of the members to be transported by vehicle. The crew drives the vehicle while looking at the list, and makes rounds to the members' homes.

[0044] The screen of FIG. 8 further includes a user interface for registering and displaying the usage status of the transportation service for that day. Usage status includes, for example, a status in which a member has used the service, a status in which the member has been delivered home and the transportation service has been completed, a status in which the service usage has been canceled, or a status in which the usage status is unknown until the member's home. By displaying the usage status, the crew terminal 10 can prevent the crew from forgetting to pick up the member and deliver them home. When an area for each member is selected, the crew terminal 10 may display a pop-up screen for selecting the usage status. A status in which a customer has used the service for that day may be displayed as "on board" as shown in FIG. 8. A status in which a customer has canceled the service for that day may be displayed as "not used" as shown in FIG. 8. A status in which the usage status is unknown may be displayed as "picking up" as shown in FIG. 8.

[0045] The crew terminal 10 may switch and register the usage status in response to pressing an area indicating the usage status. For example, when the crew arrives at a member's home, the crew presses a button labeled "Picking up" for the member. When the button is pressed, the crew terminal 10 may display a "Riding" button. Accordingly, the crew terminal 10 registers that the member is using the transportation service. When the crew arrives at the member's home, the member may verbally inform the member that they are canceling the ride. When the "Riding" button is pressed, the crew terminal 10 may display a "Not in Use" button. Accordingly, the crew terminal 10 registers that the customer is canceling their use of the transportation service. When the "Riding" button is pressed after a predetermined time has elapsed since the "Riding" button was displayed, the crew terminal 10 may display a "Complete" button. The predetermined time is determined as appropriate, taking into account the travel time between the member's home and the shopping time, such as 30 minutes.

[0046] In step S12, the crew terminal 10 generates request information. Step S12 is executed, for example, when the crew arrives in front of the requester's home. For example, the crew directly asks the requester about the product the requester requests to purchase. The crew terminal 10 accepts input of member information and product information through operation by the crew. The crew terminal 10 then generates request information including the input member information and product information. The crew terminal 10 transmits the generated request information to the shopping assistance server 100.

[0047] The crew terminal 10 may accept input of member information by accepting an operation to select a member from a list of members to be transported by vehicle. For example, in the screen of Fig. 8, the crew terminal 10 generates request information including the member information of the customer for whom the "Accept Requested Product" button was pressed.

[0048] When a member has registered that he / she will cancel his / her ride in a vehicle, the crew terminal 10 may activate a reception screen for the member's requested product. In the example of FIG. 8 , the crew terminal 10 may activate a "requested product reception" button. After step S11, the crew terminal 10 may notify the request reception unit 101 that the member has registered that he / she will cancel his / her ride in a vehicle. In response to the notification, the request reception unit 101 may activate a reception screen for the requested product on the crew terminal 10.

[0049] After the request information is sent, the crew terminal 10 may display that the request information for shopping assistance has been accepted. In the example of FIG. 8, the information of the customer with member ID "124" has been accepted. In FIG. 8, when the "Display details" button is pressed, the crew terminal 10 may display the request information. For example, the crew terminal 10 displays the request information as shown in FIG. 9.

[0050] In step S101, the request receiving unit 101 of the shopping support server 100 receives request information from the crew terminal 10. The request receiving unit 101 may notify the crew terminal 10 that the reception of the request information has been completed. Then, in step S102, the request sending unit 102 sends the request information to a terminal used by a store staff member. The example in FIG. 6 shows a case where the request sending unit 102 sends request information to the supporter terminal 20.

[0051] In step S21, the supporter terminal 20 displays the received request information. For example, the supporter terminal 20 displays the request information as shown in FIG. 9 . This display allows the store staff to support the customer who is the agent. When notified that a vehicle carrying the agent has arrived at the store, the supporter terminal 20 may output a notification of the request information linked to the agent. The store staff, upon confirming the notification, checks the request information displayed on the supporter terminal 20. For example, the crew terminal 10 notifies the supporter terminal 20 that the vehicle has arrived at the store based on the vehicle's location information and the crew's operation. For example, the store staff, while looking at the request information displayed on the supporter terminal 20, checks whether the agent has purchased the requested product. If the agent has forgotten or not heard about the requested product from the client, the store staff can inform the agent. The store staff may prepare the requested product for the agent. The staff may also patrol the store with the agent while looking at the supporter terminal 20. The agent goes to the product registration device 30 with the requested product.

[0052] In step S31, the product registration device 30 registers the product to be purchased. For example, the product registration device 30 registers the product identified by a barcode read by a scanner.

[0053] In step S32, the product registration device 30 reads the client's membership information from the card presented by the agent. Note that step S32 may be executed before step S31.

[0054] After steps S31 and S32, the product registration device 30 transmits a payment processing request to the shopping support server 100. The processing request includes, for example, information on the price of the registered product and the member information, which is the read information.

[0055] In response to receiving the processing request, the shopping support server 100 executes step S103. In step S103, the billing processor 103 processes the billing of the requester for the registered product using the member information included in the processing request. The billing processor 103 then transmits a notification of completion of the billing process to the product registration device 30.

[0056] The billing processing unit 103 may transmit information identifying the payment method used in association with the notification of completion of billing processing. The billing processing unit 103 may also transmit the scheduled date of debit from the account or the scheduled date of credit card billing in association with the completion notification. The billing processing unit 103 may also transmit the scheduled date of debit or the scheduled date of billing when the payment for regular delivery and the payment for merchandise purchased in a store are combined. In this case, the billing processing unit 103 may transmit the total amount of the confirmed payment for regular delivery and the payment for the merchandise purchased in the store.

[0057] For example, if the read information is membership information, the billing processing unit 103 determines to receive payment using a payment method linked to the membership information. For example, the billing processing unit 103 checks the prepaid balance, and if the balance is sufficient, the billing processing unit 103 executes payment using the balance. The billing processing unit 103 may also execute payment by account transfer or credit card. The billing processing unit 103 may execute payment using a payment method used to pay for regular delivery of goods to the client's home. For example, regular weekly deliveries may be paid for monthly in a lump sum. In this case, the billing processing unit 103 may process a bill by combining the payment for the regular delivery and the payment for the goods purchased at the store.

[0058] In step S33, the product registration device 30 issues a receipt. Information such as the purchased product, purchase price, purchase date and time, store name, store address, and store contact information may be printed on the receipt. The agent can then hand the receipt to the client along with the requested product and the card.

[0059] The product registration device 30 may issue a receipt based on information included in the billing completion notification received from the billing processor 103. That is, the billing processor 103 may control the content printed on the receipt. The product registration device 30 may issue a receipt on which the payment method is printed. The product registration device 30 may also print on the receipt the scheduled date of debit from the account or the scheduled date of credit card billing. The product registration device 30 may also print on the receipt the total amount of the confirmed payment for regular delivery and the payment for the products purchased at the store.

[0060] When a store employee is shopping on behalf of a customer, each device may perform the operations shown in Figure 7. The operations of each device when a store employee is shopping on behalf of a customer are basically the same as the operations of each device when a shipping service member is shopping on behalf of a customer. Therefore, a description of the similar operations will be omitted.

[0061] In step S21, the agent collects the requested items while looking at the supporter terminal 20. Then, the agent goes to the item registration device 30 with the requested items.

[0062] After step S21, in step S22, the supporter terminal 20 displays a payment code to be used for payment. The payment code may be displayed on the supporter terminal 20 as a barcode or a two-dimensional code. The supporter terminal 20 may receive a payment code generated by the shopping support server 100. The supporter terminal 20 may generate a payment code based on the received request information. For example, the supporter terminal 20 generates a payment code that encodes the member information included in the request information.

[0063] After step S31, in step S32-2, the merchandise registration device 30 reads the payment code from the supporter terminal 20 presented by the agent. Note that step S32-2 may be executed before step S31.

[0064] After step S31 and step S32-2, the product registration device 30 transmits a payment processing request to the shopping support server 100. The processing request includes, for example, information on the price of the registered product and the payment code, which is the read information.

[0065] In response to receiving the processing request, the shopping support server 100 executes step S103. In step S103, the billing processor 103 processes billing for the registered product to the client using the payment code included in the processing request. The billing processor 103 then transmits a notification of completion of billing to the product registration device 30.

[0066] For example, if the payment code is a request ID that identifies the request information, the billing processing unit 103 identifies the request information identified by the payment code from the request information accepted by the request accepting unit 101. The billing processing unit 103 references the database 40 and identifies the payment method linked to the membership information of the requester included in the identified request information. The billing processing unit 103 processes the billing using the identified payment method. Similarly, if the payment code is the membership information of the requester, the billing processing unit 103 references the database 40, identifies the payment method linked to the membership information of the requester, and processes the billing.

[0067] In step S33, the product registration device 30 issues a receipt. The agent hands the requested product and the receipt to the vehicle driver. The driver then hands the requested product and the receipt to the requester.

[0068] According to one embodiment, the request receiving unit 101 receives request information identifying the requester and the requested product from the driver terminal 10 used by the driver of the vehicle that regularly transports the member to the store. The request sending unit 102 sends the request information to a terminal used by the store staff. The billing processing unit 103 processes billing for the requested product to the requester using read information read from a medium presented by the agent in the store's product registration device 30. Therefore, the shopping support server 100 enables the agent to deliver the requested product purchased on the product registration device 30 for the requester to the requester using the vehicle that transports the member. Therefore, the shopping support server 100 can support the efficiency of shopping proxy services.

[0069] According to one embodiment, a vehicle driver operates a terminal for the requester, and the terminal transmits request information to the shopping support server 100. This reduces the amount of terminal operation by the requester, thereby reducing the burden on the requester. In one embodiment, the agent is a member of a service that provides regular transport to the store. The request transmission unit 102 transmits the request information to a terminal used by a store employee. This allows the shopping support server 100 to reduce the amount of terminal operation by the agent, potentially reducing the burden on the agent.

[0070] Second Embodiment An example of the configuration of a shopping support server 200 according to the present disclosure will be described using Fig. 10. The shopping support server 200 differs from the shopping support server 100 according to the first embodiment in that it includes a registration acceptance unit 104, a determination unit 105, and a notification unit 106. Regarding the configuration of the shopping support server 200, a description of the configuration that is the same as that of the shopping support server 100 according to the first embodiment will be omitted.

[0071] The registration reception unit 104 receives registered product information that identifies registered products registered in the product registration device 30. The registration reception unit 104 receives the registered product information from the product registration device 30. The registered product information includes a product ID.

[0072] The determination unit 105 determines whether the requested product has been registered using the registered product information and the request information linked to the read information. The determination unit 105 uses the registered product information received in association with the read information read by the product registration device 30. The requested product may not be registered, for example, when the requested product is not included in the registered products or when a product other than the requested product is included in the registered products.

[0073] If the product information included in the request information is a product ID, the determination unit 105 compares the product ID in the registered product information with the product ID included in the request information linked to the read information. Based on the comparison result, the determination unit 105 can determine whether the requested product has been registered. Furthermore, the product information included in the request information may be part of a product name or a general description of the product type. In this case, the determination unit 105 determines that the requested product has been registered if the product name included in the request information partially matches the product name of the registered product recorded in the database 40. The determination unit 105 may also determine whether the product features identified by the product ID of the registered product match the features identified by the product information included in the request information. The determination unit 105 may refer to the product features recorded in the database 40 to determine whether the product features match. If the features do not match, the determination unit 105 determines that the requested product has not been registered. If the features match, the determination unit 105 determines that the requested product has been registered.

[0074] If the requested product is not included in the registered products, the determination unit 105 may determine whether the requested product is in stock. The determination unit 105 refers to the database 40 that manages inventory information and determines whether the product is in stock at the store.

[0075] The notification unit 106 notifies the registered product based on the result of the determination. The notification unit 106 notifies the store staff terminal, either the supporter terminal 20 or the product registration device 30, of the registered product. If it is determined that the requested product is not registered, the notification unit 106 may notify of a mismatch between the requested product and the registered product. As a notification of a mismatch, for example, the notification unit 106 may notify that the requested product is not included in the registered products, or that a product other than the requested product is included in the registered products. If the requested product is in stock, the notification unit 106 may notify that the requested product is not included in the registered products. If the requested product is out of stock, the notification unit 106 may cancel the notification. If it is determined that the requested product is registered, the notification unit 106 may notify that the requested product matches the registered product. This allows the agent to confirm that the requested product has been purchased.

[0076] The notification unit 106 may further notify the crew terminal 10 about the registered products based on the determination result, similar to the notification to the staff terminal. For example, the notification unit 106 may notify the crew terminal 10 that the requested product is not included in the registered products, or that a product other than the requested product is included in the registered products. Furthermore, if the requested product is out of stock, the notification unit 106 may notify the crew terminal 10 that the requested product is not included in the registered products because the requested product is out of stock. This allows the crew to inform the requester that the requested product was not purchased due to a lack of inventory. Furthermore, if it is determined that the requested product has been registered, the notification unit 106 may notify that the requested product matches the registered product. This allows the crew to inform the requester that the requested product has been purchased.

[0077] An example of the operation of the shopping support server 200 will be described using Figure 11. The operation up to step S202 is the same as the operation up to step S102 in Figure 5. In step S201, the request receiving unit 101 receives request information identifying the requester and the requested product from the crew terminal 10 used by the vehicle crew. In step S202, the request sending unit 102 sends the request information received by the request receiving unit 101 to a terminal used by a store staff member.

[0078] In step S203 , the registration receiving unit 104 receives registered product information that identifies the registered product registered in the product registration device 30 .

[0079] In step S204, the determination unit 105 determines whether the requested product has been registered, using the registered product information and the request information linked to the read information.

[0080] If the requested product is not registered (step S204: No), the shopping support server 200 executes step S206. In step S206, the notification unit 106 notifies the user that the requested product does not match the registered product. After step S206, the registered product may be added to the product registration device 30. Therefore, the registration acceptance unit 104 may execute step S203 again and accept registered product information from the product registration device 30.

[0081] If the requested product has been registered (step S204: Yes), the shopping support server 200 executes step S205. In step S205, the billing processing unit 103 processes billing of the client for the requested product using the read information read from the medium presented by the agent at the store's product registration device 30.

[0082] With the above, the shopping support server 200 ends the operation of FIG.

[0083] If the requested product is not registered in step S204, the determination unit 105 may determine whether the requested product is in stock. If it is determined that the requested product is out of stock, the shopping support server 200 executes step S205. If it is determined that the requested product is in stock, the shopping support server 200 executes step S206.

[0084] 12, an example of the operation of the shopping support server 200 and the product registration device 30 will be described. Each step of the shopping support server 200 corresponds to each step shown in FIG.

[0085] In step S31, the product registration device 30 registers the product to be purchased. In step S32, the product registration device 30 reads member information from the card presented by the customer. Note that step S32 may be executed before step S31. For example, the product registration device 30 may read member information while registering multiple products. The product registration device 30 transmits registered product information of registered products to the shopping support server 200. The product registration device 30 may transmit registered product information of added products each time a product is additionally registered. The product registration device 30 also transmits member information as read information to the shopping support server 200. The product registration device 30 associates the registered product information of the customer with the read information of the card presented by the customer and transmits them. For example, the product registration device 30 may associate the registered product information with the read information using a payment ID that identifies the payment process for each customer. After steps S31 and S32, the product registration device 30 transmits a payment processing request to the shopping support server 100.

[0086] In step S203, the registration receiving unit 104 receives registered product information that identifies the registered product registered in the product registration device 30. In step S204, the determination unit 105 determines whether the requested product has been registered, using the registered product information and the request information linked to the read information.

[0087] If it is determined that the requested product is not registered, the shopping support server 200 executes step S206. In the example of FIG. 12 , the notification unit 106 notifies the product registration device 30 of a mismatch between the requested product and the registered product. In step S34, the product registration device 30 displays a notification of the mismatch on the display. After step S34, the product registration device 30 may transmit registered product information for the additional product. In this case, the shopping support server 200 executes step S203. Alternatively, after step S34, the product registration device 30 may transmit a payment processing request even though the requested product and the registered product do not match. In this case, the shopping support server 200 executes step S205.

[0088] If it is determined that the requested product has been registered, the shopping support server 200 executes step S205. In step S205, the billing processor 103 processes the billing of the requested product to the client using the read information read from the medium presented by the agent at the store's product registration device 30. The billing processor 103 sends a notification of completion of the billing process to the product registration device 30. In step S33, the product registration device 30 issues a receipt.

[0089] This concludes the explanation using FIG.

[0090] According to one embodiment, the registration acceptance unit 104 accepts registered product information that identifies registered products registered in the product registration device 30. The determination unit 105 determines whether the requested product has been registered using the registered product information and the request information linked to the read information. The notification unit 106 then notifies the user about the registered product based on the result of the determination. Therefore, the shopping support server 200 can prevent the agent from failing to purchase the requested product or purchasing a product different from the requested product. Therefore, the shopping support server 200 can support the agent in shopping as requested.

[0091] [Modifications] The above-described embodiments can be modified in various ways, and modifications will be described below.

[0092] <Modification 1> When the shopping support server 200 according to the second embodiment is configured as follows, the agent can present his / her own card as a medium at the product registration device 30. This eliminates the need for the client to hand over the card to the agent.

[0093] The request receiving unit 101 receives request information that links the member information of the requester with the member information of the agent who is a member of the transportation service.

[0094] The product registration device 30 reads the agent's membership information recorded on the card via an IC tag reader, a code scanner, or a magnetic card reader, and then transmits the agent's membership information as read information.

[0095] The determination unit 105 compares the product information included in the request information linked to the agent's membership information with the registered product information. Based on the comparison result, the determination unit 105 can determine whether the requested product has been registered.

[0096] The billing processing unit 103 receives product price information and the read member information from the product registration device 30. The billing processing unit 103 processes the billing based on the result of the determination by the determination unit 105. For registered products with product information included in the request information linked to the agent's member information, the billing processing unit 103 processes the billing using the payment method linked to the requester's member information. For example, the billing processing unit 103 processes the billing using the requester's prepaid balance, credit card, or bank account. The billing processing unit 103 may process the billing to the requester by adding a fee to be paid to the agent. For registered products with product information not included in the request information, the billing processing unit 103 processes the billing using the payment method linked to the agent's member information. For example, the billing processing unit 103 processes the billing using the agent's prepaid balance, credit card, or bank account. The agent may be provided with a discount equivalent to the fee for shopping on behalf of the agent. Therefore, the billing processing unit 103 may process the billing to the agent by subtracting the fee.

[0097] If the read information is the agent's membership information, the product registration device 30 may issue a receipt for the requester and a receipt for the agent, respectively. The product registration device 30 prints registered products included in the requested products on the requester's receipt. The requester's name and the requester's payment method may also be printed on the requester's receipt. The product registration device 30 prints registered products not included in the requested products on the agent's receipt.

[0098] <Modification 2> The shopping support server 100, 200 according to one modification may include a billing processor 103 as needed. If the billing processor 103 is not used, for example, the agent may pay for the requested product in cash. The client can settle the amount by handing over cash to the agent.

[0099] In the above embodiments, the billing processor 103 processes billing using read information linked to request information. However, the billing processor 103 may process billing using read information that is not linked to request information. For example, a requester may leave a prepaid card that is not linked to membership information with an agent. The billing processor 103 processes billing based on the balance of such a prepaid card.

[0100] <Modification 3> In each of the above embodiments, the case where the requester is a member of a transportation service that receives regular transportation to the store has been described. However, the request receiving unit 101 may also receive request information from a customer who is not a member of the transportation service. In this case, the request receiving unit 101 may, for example, receive request information that includes customer information that identifies the customer of the store. Furthermore, instead of a card that records member information, a card that records customer information may be used.

[0101] [Hardware Configuration] In each of the above-described embodiments, each component of the shopping support server 100, 200 represents a functional block. Some or all of the components of the shopping support server 100, 200 may be realized by any combination of a computer 500 and a program.

[0102] Fig. 13 is a block diagram showing an example of the hardware configuration of a computer 500. Referring to Fig. 13, the computer 500 includes, for example, a processor 501, a read only memory (ROM) 502, a random access memory (RAM) 503, a program 504, a storage device 505, a drive device 507, a communication interface 508, an input device 509, an output device 510, an input / output interface 511, and a bus 512.

[0103] The processor 501 controls the entire computer 500. The processor 501 may be, for example, a CPU (Central Processing Unit). The number of processors 501 is not particularly limited, and there may be one or more processors 501.

[0104] The program 504 includes instructions for implementing each function of the shopping support servers 100, 200. The program 504 is stored in advance in the ROM 502, the RAM 503, and the storage device 505. The processor 501 executes the instructions included in the program 504 to implement each function of the shopping support servers 100, 200. The RAM 503 may also store data to be processed in each function of the shopping support servers 100, 200.

[0105] The drive device 507 reads and writes data from and to the recording medium 506. The communication interface 508 provides an interface with a communication network. The input device 509 is, for example, a mouse or keyboard, and accepts information input from an administrator or the like. The output device 510 is, for example, a display, and outputs (displays) information to an administrator or the like. The input / output interface 511 provides an interface with peripheral devices. The bus 512 connects these hardware components. The program 504 may be supplied to the processor 501 via a communication network, or may be stored in advance on the recording medium 506, read by the drive device 507, and supplied to the processor 501.

[0106] It should be noted that the hardware configuration shown in FIG. 13 is an example, and other components may be added, or some components may not be included.

[0107] There are various variations in the method of realizing the shopping support servers 100 and 200. For example, the shopping support servers 100 and 200 may be realized by any combination of different computers and programs for each component. Furthermore, multiple components included in the shopping support servers 100 and 200 may be realized by any combination of a single computer and program.

[0108] Furthermore, at least a portion of the shopping support servers 100 and 200 may be provided in a software as a service (SaaS) format. That is, at least a portion of the functions for realizing the shopping support servers 100 and 200 may be executed by software that is executed via a network.

[0109] Although the present disclosure has been described above with reference to the embodiments, the present disclosure is not limited to the above embodiments. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present disclosure within the scope of the present disclosure. Furthermore, the configurations in the respective embodiments can be combined with each other without departing from the scope of the present disclosure.

[0110] Some or all of the above embodiments may be described as, but are not limited to, the following supplementary notes.

[0111] [Supplementary Note 1] A shopping support server comprising: a request receiving means for receiving, from a terminal used by a driver of a vehicle that regularly transports members between the member's home and a store, request information specifying a requester who requests a proxy to shop at the store and a requested product that the requester requests to purchase; a request sending means for sending the request information to a terminal used by a staff member of the store; and a billing processing means for processing a bill for the requested product from the requester using read information linked to the request information that is read from a medium presented by the proxy by a product registration device of the store.

[0112] [Supplementary Note 2] The shopping support server according to Supplementary Note 1, wherein the requester is a member who has signed up for regular transportation to the store and who cancels his / her ride in the vehicle.

[0113] [Supplementary Note 3] The shopping support server according to Supplementary Note 1 or 2, wherein the agent is a member who rides in the vehicle.

[0114] [Supplementary Note 4] The shopping support server according to Supplementary Note 3, wherein the staff member is a staff member who supports the agent.

[0115] [Supplementary Note 5] The shopping support server according to any one of Supplementary Notes 1 to 4, wherein the read information is membership information of the client read from a card entrusted to the agent by the client.

[0116] [Supplementary Note 6] The shopping support server according to Supplementary Note 5, wherein the billing processing means processes billing based on a prepaid balance linked to the member information.

[0117] [Supplementary Note 7] The shopping support server described in any one of Supplementary Notes 1 to 6, wherein the agent is the staff member of the store, and the request sending means sends the request information to a terminal of the staff member who shops for the requester.

[0118] [Supplementary Note 8] The shopping support server according to Supplementary Note 7, wherein the read information is a code displayed on the staff member's terminal.

[0119] [Supplementary Note 9] The shopping support server according to any one of Supplementary Notes 1 to 8, wherein the billing processing means processes billing using a payment method used for paying for regular delivery of goods to the client's home.

[0120] [Supplementary Note 10] The shopping support server described in any one of Supplementary Notes 1 to 9 further comprises: a registration receiving means for receiving registered product information that identifies registered products registered in the product registration device; a determination means for determining whether the requested product has been registered using the registered product information and the request information linked to the read information; and a notification means for notifying the staff member's terminal about the registered product based on the result of the determination.

[0121] [Supplementary Note 11] The shopping support server according to Supplementary Note 10, wherein the notification means notifies the terminal of the driver about the registered product.

[0122] [Supplementary Note 12] The shopping support server according to Supplementary Note 10 or 11, wherein the notification means notifies the user of a mismatch between the requested product and the registered product.

[0123] [Appendix 13] The request receiving means receives the request information linking the membership information of the requester with the membership information of the agent who is a member riding in the vehicle, and the read information is the membership information of the agent recorded on a card. A shopping support server described in any one of Appendices 10 to 12.

[0124] [Supplementary Note 14] The shopping support server according to Supplementary Note 13, wherein the billing processing means processes billing of the agent for the registered products that are not included in the requested products.

[0125] [Supplementary Note 15] The shopping support server according to Supplementary Note 13 or 14, wherein the billing processing means issues a receipt for the requested product and receipts for the registered products other than the requested product.

[0126] [Appendix 16] The shopping support server described in any one of Appendices 1 to 15, wherein the request receiving means displays a list of members who have applied for regular transportation to the store on the driver's terminal so that requesters who do not ride in the vehicle can be registered.

[0127] [Supplementary Note 17] The shopping support server described in any one of Supplementary Notes 1 to 16, wherein the request receiving means activates a reception screen for the requested product on the driver's terminal when the requester registers that he or she will cancel his or her ride in the vehicle.

[0128] [Supplementary Note 18] The shopping support server described in any one of Supplementary Notes 1 to 17, wherein the billing processing means issues a receipt including a scheduled payment date for the regular delivery when the payment for the regular delivery of goods and the payment for the goods purchased at the store are combined.

[0129] [Supplementary Note 19] A shopping support method comprising: receiving, from a terminal used by a driver of a vehicle that regularly transports a member between the member's home and a store, request information specifying a requester who requests an agent to shop at the store and a requested product that the requester requests to purchase; transmitting the request information to a terminal used by a staff member of the store; and processing a bill for the requested product from the requester using read information linked to the request information that is read by a product registration device of the store from a medium presented by the agent.

[0130] [Supplementary Note 20] A recording medium that non-temporarily records a program that causes a computer to execute the following processes: receive, from a terminal used by a driver of a vehicle that regularly transports members between the member's home and a store, request information that identifies a client who requests a proxy to shop at the store and a requested product that the client requests to purchase; transmit the request information to a terminal used by a staff member of the store; and process a billing of the requested product from the client using read information linked to the request information that is read from a medium presented by the proxy by a product registration device of the store.

[0131] Some or all of the configurations described in Supplementary Notes 2-18, which are dependent on Supplementary Note 1, may also be dependent on Supplementary Notes 19-20 in the same dependency relationship as Supplementary Notes 2-18. Not limited to Supplementary Notes 1, 19-20, but also to various hardware, software, various recording devices for recording software, or systems, some or all of the configurations described as Supplements may be made dependent on each other within the scope of the above-mentioned embodiments.

[0132] C1, C2 Customer S1, S2, S3 Staff M1 Card 10 Crew terminal 20 Supporter terminal 30 Product registration device 40 Database 50 Communication network 100, 200 Shopping support server 101 Request reception unit 102 Request transmission unit 103 Billing processing unit 104 Registration reception unit 105 Determination unit 106 Notification unit

Claims

1. A shopping support server comprising: a request receiving means for receiving, from a terminal used by a driver of a vehicle that regularly transports members between the member's home and a store, request information specifying a requester requesting a proxy to shop at the store and the requested product that the requester requests to purchase; a request sending means for sending the request information to a terminal used by a staff member of the store; and a billing processing means for processing a bill for the requested product from the requester using read information linked to the request information that is read from a medium presented by the proxy by a product registration device of the store.

2. The shopping support server according to claim 1, wherein the requester is a member who has signed up for regular transportation to the store and who is canceling his / her ride in the vehicle.

3. The shopping support server according to claim 1 or 2, wherein the agent is a member who rides in the vehicle.

4. The shopping support server according to claim 3, wherein the staff member is a staff member who supports the agent.

5. A shopping support server according to any one of claims 1 to 4, wherein the read information is the client's membership information read from a card entrusted to the agent by the client.

6. The shopping support server according to claim 5, wherein the billing processing means processes billing based on a prepaid balance linked to the member information.

7. A shopping support server as described in any one of claims 1 to 6, wherein the agent is an employee of the store, and the request sending means sends the request information to a terminal of the employee who shops for the requester.

8. The shopping support server according to claim 7, wherein the read information is a code displayed on the staff member's terminal.

9. The shopping support server according to any one of claims 1 to 8, wherein the billing processing means processes billing by a payment method used for paying for regular delivery of goods to the client's home.

10. A shopping support server as described in any one of claims 1 to 9, further comprising: a registration acceptance means for accepting registered product information that identifies registered products registered in the product registration device; a determination means for determining whether the requested product has been registered using the registered product information and the request information linked to the read information; and a notification means for notifying the staff member's terminal about the registered product based on the result of the determination.

11. The shopping support server according to claim 10, wherein the notification means notifies the driver's terminal of the registered product.

12. The shopping support server according to claim 10 or 11, wherein the notification means notifies of a discrepancy between the requested product and the registered product.

13. A shopping support server as described in any one of claims 10 to 12, wherein the request receiving means receives the request information linking the membership information of the requester with the membership information of the agent who is a member riding in the vehicle, and the read information is the membership information of the agent recorded on a card.

14. The shopping support server according to claim 13, wherein the billing processing means processes billing of the agent for the registered products that are not included in the requested products.

15. The shopping support server according to claim 13 or 14, wherein the billing processing means issues a receipt for the requested product and a receipt for the registered products other than the requested product.

16. A shopping support server as claimed in any one of claims 1 to 15, wherein the request receiving means displays on the driver's terminal a list of members who have applied for regular transportation to the store, allowing requesters who do not ride in the vehicle to be registered.

17. A shopping support server as claimed in any one of claims 1 to 16, wherein the request acceptance means activates an acceptance screen for the requested product on the driver's terminal when the requester registers that he or she will cancel his or her ride in the vehicle.

18. A shopping support server as claimed in any one of claims 1 to 17, wherein the billing processing means issues a receipt including the scheduled payment date for the regular delivery when the payment for regular delivery of goods and the payment for goods purchased at the store are combined.

19. A shopping support method comprising: receiving, from a terminal used by a driver of a vehicle that regularly transports a member between the member's home and a store, request information specifying a requester who requests an agent to shop at the store and the requested product that the requester requests to purchase; transmitting the request information to a terminal used by a staff member of the store; and processing a bill for the requested product from the requester using read information linked to the request information that is read by the store's product registration device from a medium presented by the agent.

20. A recording medium that non-temporarily records a program that causes a computer to execute the following processes: receive, from a terminal used by a driver of a vehicle that regularly transports members between the member's home and the store, request information that identifies a client requesting a proxy to shop at the store and the requested product that the client requests to purchase; send the request information to a terminal used by a staff member of the store; and process a bill for the requested product from the client using read information linked to the request information that is read from a medium presented by the proxy by the store's product registration device.