Server and computer program

Abstract

To provide a server and a computer program for controlling a sales quantity by a supplier when selling a sales object through a seller such as a KOL.SOLUTION: In a supply management system in which a supply management server, a supplier terminal, a consumer terminal, and a KOL terminal are communicatively connected, the supply management server acquires a campaign setting unit that receives a setting of a new campaign, a sales target ID that specifies a sales target in a predetermined campaign period, and a total number of sellers to be employed in the campaign period from a terminal of a supplier via a network, the system includes a sales quantity allocation unit that registers the acquired sales target ID, the acquired total sales quantity, and the total number of sellers in a campaign information storage unit in association with each other, and determines the sales quantity of the sales target to be allocated to the adopted seller by referring to the campaign information storage unit, and an application result notification unit that transmits the determined sales quantity to the terminal of the seller determined to be adopted via a network.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present disclosure relates to a server and a computer program. [Background technology]

[0002] E-commerce is becoming more diverse in form. There are a wide variety of sales channels, including social networking sites, chat services, and live commerce. Live commerce is a new customer service and sales method that combines live streaming with e-commerce (EC). It can provide users with a shopping experience similar to that of a brick-and-mortar store, regardless of location (see Patent Document 1). As it is said that the Internet knows no borders, cross-border transactions are also becoming more common in e-commerce. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 7426637 Summary of the Invention [Problem to be solved by the invention]

[0004] There has been growing interest in transactions involving influential sellers such as KOLs. KOLs skillfully introduce the appeal, usability, advantages, and disadvantages of products on social media and live streams, and act as resellers or intermediaries for sales. In this sales format, product sales are heavily influenced by the popularity and mood of the KOLs, as well as changes in trends, making it difficult for product suppliers to accurately predict sales volumes. If a KOL goes viral, sales volume may skyrocket, and supply may be unable to keep up. If supply is not possible, apologies and refunds will be required, placing a greater burden on both the KOLs and suppliers. However, reducing the number of KOLs employed increases the likelihood that many products will remain unsold.

[0005] The present disclosure has been made in consideration of these issues, and its purpose is to provide technology that enables suppliers to control sales quantities when selling sales items through sellers such as KOLs. [Means for solving the problem]

[0006] One aspect of the present invention relates to a server that includes: means for acquiring, from a supplier terminal via a network, a sales object ID that identifies a sales object and a total number of sellers to be selected for a predetermined campaign period; means for registering the acquired sales object ID and the acquired total number of sellers in a storage means in association with each other; means for determining the sales quantity of the sales object to be allocated to the selected seller by referring to the storage means; and means for transmitting the determined sales quantity to the terminal of the selected seller via the network.

[0007] Another aspect of the present invention is a computer program that implements the following functions on a supplier terminal: displaying on a display a campaign setting screen for receiving input of a sales object ID that identifies a sales object and a total number of sellers to be employed during a predetermined campaign period; transmitting the sales object ID and the total number of sellers input on the campaign setting screen to a server via a network; receiving via the network an approval / denial request including information related to the application received by the server from a terminal of a seller who wishes to sell the sales object; and displaying on a display an approval screen that inquires whether to approve the application related to the approval / denial request.

[0008] Yet another aspect of the present invention is a computer program that implements the following functions: sending an application for an object for sale to a terminal of a seller who wishes to sell the object for sale to a server via a network; receiving, if the application is approved, from the server via the network a sales quantity of the object for sale allocated to the seller; and displaying the received sales quantity on a display in association with information about the object for sale.

[0009] In addition, any combination of the above components, or mutual substitution of the components or expressions of the present invention between devices, methods, systems, computer programs, recording media storing computer programs, etc., are also valid aspects of the present invention. [Effects of the Invention]

[0010] According to the present invention, it is possible to provide suitable control of sales volume. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a schematic diagram illustrating a configuration of a supply management system according to an embodiment of the present disclosure. [Figure 2] 2 is a block diagram showing the function and configuration of the supplier terminal of FIG. 1. FIG. [Figure 3] 2 is a block diagram showing the functions and configuration of the supply management server of FIG. 1. FIG. [Figure 4] 4 is a data structure diagram showing an example of a user information storage unit in FIG. 3. [Figure 5] 4 is a data structure diagram showing an example of a campaign information storage unit in FIG. 3. FIG. [Figure 6] 4 is a data structure diagram showing an example of an application information storage unit in FIG. 3. [Figure 7] 2 is a flowchart showing the flow of a series of processes in the supply management server of FIG. 1. [Figure 8] FIG. 10 is a representative screen diagram of a supplier home screen displayed on the display of the supplier's supplier terminal. [Figure 9] FIG. 10 is a representative screen diagram of a created campaign screen for a supplier, which is displayed on the display of the supplier's supplier terminal. [Figure 10] FIG. 10 is a representative screen diagram of a new campaign creation screen displayed on the display of the supplier's supplier terminal. [Figure 11] FIG. 10 is a diagram showing a representative screen of an application management screen displayed on the display of the supplier's supplier terminal. [Figure 12]FIG. 10 is a representative screen diagram of a collaboration display screen displayed on the display of the supplier's supplier terminal. [Figure 13] This is a representative screen diagram of the KOL home screen displayed on the display of the KOL's KOL terminal. [Figure 14] This is a representative screen diagram of the sales application screen displayed on the display of the KOL's KOL terminal. [Figure 15] This is a representative screen diagram of the application status screen displayed on the display of the KOL's KOL terminal. [Figure 16] This is a representative screen diagram of the collaboration status display screen displayed on the display of the KOL's KOL terminal. [Figure 17] This is a representative screen diagram of the approval notification screen displayed on the display of the KOL's KOL terminal. [Figure 18] 1 is a block diagram illustrating an example of a hardware configuration of an information processing device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, the same or equivalent components, parts, processes, and signals shown in each drawing will be denoted by the same reference numerals, and redundant explanations will be omitted where appropriate. In addition, some of the parts that are not important for the explanation will be omitted in each drawing.

[0013] In a supply management system according to an embodiment, a supplier (also referred to as a supplier) that supplies products and / or services (hereinafter simply referred to as "sales items") to the market sets a campaign for the sales items. The campaign has a set period, during which the sales items are sold at a lower price than usual. For the campaign, the supplier sets the total sales volume of the sales items during the campaign period and the total number of KOLs (Key Opinion Leaders) to be employed during the campaign period. The supply management system enables the supplier to allocate a portion of the total sales volume of the sales items to the employed KOLs. The KOLs are expected to sell the sales items to end consumers within the allocated sales volume during the campaign period. This enables the supplier to more appropriately manage the sales of the sales items by the KOLs. The total sales volume of the sales items can be predetermined for each campaign, and KOLs can be employed within the total sales volume, thereby preventing unsold items and overselling. Furthermore, KOLs can improve sales efficiency by adjusting their sales activities according to the sales volume allocated to them.

[0014] A supplier may be a manufacturer of the product, a seller of the product, or a wholesaler or retailer of the product. A KOL is an example of a seller who sells the product to end consumers through e-commerce. A KOL may be a live commerce entity that sells the product through live streaming, or may be a seller who sells the product through a social networking service (SNS), a chat service, or a video streaming service. A seller may be, for example, an intermediary who mediates the sale of the product, such as a wholesaler, or may be a party that purchases the product from a supplier and sells it to end consumers.

[0015] FIG. 1 is a schematic diagram illustrating the configuration of a supply management system 2 according to an embodiment of the present disclosure. The supply management system 2 includes a supply management server 10, a first supplier terminal 40a used by a first supplier 4a, a second supplier terminal 40b used by a second supplier 4b, a third supplier terminal 40c used by a third supplier 4c, a first KOL terminal 60a used by a first KOL 6a, a second KOL terminal 60b used by a second KOL 6b, a third KOL terminal 60c used by a third KOL 6c, a first consumer terminal 80a used by a first consumer 8a, and a second consumer terminal 80b used by a second consumer 8b. The number of suppliers, KOLs, and consumers in FIG. 1 is merely an example, and there is no limit to these numbers. Hereinafter, suppliers 4a, 4b, 4c will be collectively referred to as suppliers 4, supplier terminals 40a, 40b, 40c will be collectively referred to as supplier terminals 40, KOLs 6a, 6b, 6c will be collectively referred to as KOL 6, KOL terminals 60a, 60b, 60c will be collectively referred to as KOL terminals 60, consumers 8a, 8b will be collectively referred to as consumers 8, and consumer terminals 80a, 80b will be collectively referred to as consumer terminals 80. Each terminal 40, 60, 80 and supply management server 10 is connected to a network 20 such as the Internet and configured to be able to communicate with each other.

[0016] In the supply management system 2, the supplier 4 inputs campaign information into the supplier terminal 40, and the campaign information thus input is registered in the supply management server 10. The KOL 6 obtains and views the campaign information from the supply management server 10 via the KOL terminal 60. When the KOL 6 wishes to sell a sales object related to the campaign, the KOL 6 sends a sales application to the supply management server 10 via the KOL terminal 60. The supply management server 10 presents the received sales application to the supplier 4 via the supplier terminal 40 and asks whether to approve or reject the application. The supply management server 10 notifies the KOL 6 of the approval or rejection result via the KOL terminal 60. If the sales application is approved, the KOL 6 sells the sales object to the consumer 8 through e-commerce. The sales form may be a form in which the supplier 4 mediates the sale of the sales object to the consumer 8, or a form in which the KOL 6 purchases the sales object from the supplier 4 and resells the purchased sales object to the consumer 8. When KOL 6 sells a product through live streaming, KOL 6 is the broadcaster of the live stream, and consumer 8 is the viewer of the live stream. Such a live commerce system may be realized, for example, by the technology described in Patent No. 7426637 or Patent No. 7288254. In this case, the campaign period may be associated with a live commerce event held on the live streaming platform. When supplier 4 is recruiting KOLs to sell products at a live commerce event held on the live streaming platform, the supply management system 2 according to this embodiment can be used.

[0017] The supply management server 10 may be configured with one or more information processing devices connected to the network NW. Each terminal may be a mobile terminal such as a smartphone, tablet terminal, laptop PC, recorder, portable game console, or wearable device, or may be a stationary device such as a desktop PC.

[0018] Figure 2 is a block diagram showing the functions and configuration of the supplier terminal 40 in Figure 1. The KOL terminal 60 and the consumer terminal 80 also have functions and configurations similar to those shown in Figure 2. Each block shown in Figure 2 and subsequent block diagrams can be realized in hardware terms by elements or mechanical devices such as a computer CPU, or in software terms by a computer program, etc., but the functional blocks shown here are realized by the cooperation of these. Therefore, those skilled in the art who have read this specification will understand that these functional blocks can be realized in various ways by combining hardware and software.

[0019] The supplier 4 downloads and installs a supply management application program (hereinafter referred to as the management app) according to this embodiment from a download site to the supplier terminal 40 via the network 20. Alternatively, the management app may be pre-installed on the supplier terminal 40. When the management app is executed by the supplier terminal 40, the supplier terminal 40 communicates with the supply management server 10 via the network 20 and realizes various functions. Hereinafter, functions realized by the supplier terminal 40 (its processor, such as a CPU) executing the management app will be described as functions of the supplier terminal 40. These functions are actually functions that the management app causes the supplier terminal 40 to realize. Note that in other embodiments, these functions may be realized by a computer program written in a programming language such as HTML (HyperText Markup Language), which is transmitted from the supply management server 10 to a web browser on the supplier terminal 40 via the network 20 and executed by the web browser.

[0020] The supplier terminal 40 includes a display control unit 400, a communication unit 402, and an input receiving unit 404. The display control unit 400 generates various screens and displays them on the display of the supplier terminal 40. The display control unit 400 updates the display content of the screen displayed on the display. The communication unit 402 communicates with the supply management server 10 via the network 20. The communication unit 402 generates various processing requests and signals and transmits them to the supply management server 10 via the network 20. The communication unit 402 receives requests and signals addressed to the supplier terminal 40 and transmitted by the supply management server 10 via the network 20. The communication unit 402 receives responses from the supply management server 10 to requests and signals transmitted by the communication unit 402 via the network 20. The input receiving unit 404 receives input from the supplier 4 via input means such as a mouse, keyboard, or touch panel.

[0021] Fig. 3 is a block diagram showing the functions and configuration of the supply management server 10 of Fig. 1. The supply management server 10 includes a campaign setting unit 102, an application receiving unit 104, an approval / rejection processing unit 106, a sales quantity allocation unit 108, an application result notification unit 110, an offer processing unit 112, a matching unit 114, a recommendation unit 116, a campaign management unit 118, a scoring unit 120, a user information storage unit 122, a campaign information storage unit 124, and an application information storage unit 126.

[0022] 4 is a data structure diagram showing an example of the user information storage unit 122 of FIG. 3. The user information storage unit 122 stores information about users registered in the supply management service provided by the supply management server 10. The user information storage unit 122 stores a user ID that identifies the user in the supply management service, information indicating whether the user is registered as a supplier or a KOL, product information of the supplier when the user is registered as a supplier, and the sales history, KOL score, and possible sales channels of the KOL when the user is registered as a KOL, in association with each other. The following describes a case where the object of sale is a product, but the technical idea of ​​this embodiment can also be applied when the object of sale is a service.

[0023] Product information is information registered by the supplier, and includes a product ID that identifies the product supplied by the supplier, the price of the product, and the number of products in stock. In the example of Figure 4, supplier "USR1" has 500 units of product "PRD_1" that costs 2000 yen in stock, and 1000 units of product "PRD_2" that costs 3000 yen in stock.

[0024] The sales history is information showing the sales performance of the KOL, and includes the product IDs of products sold by the KOL in the past and the number of units sold. In the example of Figure 4, KOL "SEL_4" has a track record of selling 100 units of product "PRD_2" and 50 units of product "PRD_5" in the past.

[0025] The KOL score is a numerical value that evaluates a KOL based on a set of criteria. Details will be explained later.

[0026] Possible sales channels are information registered by KOLs and indicate the e-commerce sales channels that they can use. In the example of Figure 4, KOL "SEL_4" can use two sales channels: live commerce using live streaming "LIVE_A" and sales using SNS "SNS_C."

[0027] The supply management server 10 is configured to allow a user to select whether to register as a supplier or as a KOL when registering with the supply management service for the first time. The supply management server 10 registers the selection result in the user information storage unit 122. The supply management server 10 is configured to allow suppliers to update product information at any time, and to allow KOLs to update possible sales channels at any time.

[0028] FIG. 5 is a data structure diagram showing an example of the campaign information storage unit 124 of FIG. 3. The campaign information storage unit 124 stores information about campaigns in the supply management service. The campaign information storage unit 124 stores a campaign ID identifying the campaign, a campaign organizer ID which is the user ID of the supplier hosting the campaign, the title of the campaign specified by the supplier, the period of the campaign specified by the supplier, the product ID of the product related to the campaign, the discount rate set for the product, the total sales quantity set for the product, the total number of KOLs set for the product, the hired KOL ID which is the user ID of the KOL hired to sell the product, the sales quantity assigned to the hired KOL, the sales channel of the hired KOL, the actual sales performance of the hired KOL, and the campaign status, in association with each other. The campaign status is "not started" if the campaign has not yet started, "in progress" if the campaign is within the campaign period, and "ended" if the campaign period has ended.

[0029] 5, the campaign information storage unit 124 stores the product IDs of multiple different products in association with a campaign period and the total sales quantity set for each of them. Two different products, "PRD_1" and "PRD_2," are associated with the campaign "CAN01." The product "PRD_1" is associated with a total sales quantity of "100," and the product "PRD_2" is associated with a total sales quantity of "80."

[0030] Fig. 6 is a data structure diagram showing an example of the application information storage unit 126 of Fig. 3. The application information storage unit 126 stores information on applications made by KOLs regarding the sale of products handled in campaigns. The application information storage unit 126 stores an application ID that identifies the application, an applicant ID that is the user ID of the KOL who made the application, the time the application was made, the campaign ID of the campaign that is the subject of the application, the product ID of the product that is the subject of the application, the desired sales quantity set by the KOL, and the sales channel to be used set by the KOL, in association with each other.

[0031] Returning to Figure 3, the campaign setting unit 102 enables a supplier to set up a campaign. The campaign setting unit 102 receives a new campaign creation request from the supplier's supplier terminal via the network 20, the new campaign creation request including a product ID that identifies the product related to the campaign, the total sales volume of the product during the campaign period, and the total number of KOLs to be employed during the campaign period. The campaign setting unit 102 associates the product ID, total sales volume, and total number of KOLs included in the received new campaign creation request and registers them in the campaign information storage unit 124.

[0032] The application receiving unit 104 receives an application via the network 20 from a KOL terminal of a KOL who wishes to sell a product related to a campaign registered in the campaign information storage unit 124. The application includes information specifying which KOL wishes to sell which product in which campaign, in what quantity, and through which sales channel. The application receiving unit 104 registers the information included in the received application in the application information storage unit 126. An application may be made for each product rather than for each campaign. In this case, the application may be for at least one of multiple different products handled in the campaign.

[0033] The approval / rejection processing unit 106 performs processing to determine whether to adopt the KOL related to the application received by the application receiving unit 104. In the case of automatic approval, the approval / rejection processing unit 106 refers to a policy set in advance by the supplier and determines whether to approve or reject the received application. The application information storage unit 126 updates the campaign information storage unit 124 and the application information storage unit 126 based on the result of the decision. For example, the policy may be a first-come-first-serve policy, in which applications are approved in the order in which they are submitted until a set total sales volume is reached for a certain product in a certain campaign. Alternatively, the policy may be to approve the application if the KOL score of the requesting KOL is equal to or greater than a predetermined threshold.

[0034] In the case of manual approval, the approval / rejection processing unit 106 receives an approval / rejection start request from the supplier's supplier terminal via the network 20. The approval / rejection processing unit 106 references the campaign information storage unit 124 and identifies a campaign whose campaign organizer ID is the supplier ID included in the received approval / rejection start request. The approval / rejection processing unit 106 references the application information storage unit 126 and identifies applications that have the campaign ID of the identified campaign as the application target campaign ID. The approval / rejection processing unit 106 generates an approval / rejection request including the user ID (applicant ID) of the KOL related to the identified application and the sales quantity of the application target product to be allocated to the KOL, and transmits it to the requesting supplier terminal via the network. The allocation of sales quantity to KOLs will be described later. The approval / rejection processing unit 106 receives an approval / rejection result signal indicating the result of approval or rejection of the approval / rejection request via the network from the supplier terminal to which the approval / rejection request was sent.

[0035] Upon receiving an application from a KOL, the approval / rejection processing unit 106 may generate an approval / rejection request for the application and transmit it to the supplier terminal of the corresponding supplier.

[0036] The sales quantity allocation unit 108 determines the sales quantity of the product to be allocated to the selected KOL by referring to the campaign information storage unit 124. There are two ways to allocate the sales quantity: (1) automatically, and (2) by inquiring with the supplier and having the supplier specify it. In the case of (1) automatically, there are two ways: (1-A) by determining the sales quantity according to the parameters of the KOL who applied, and (1-B) by determining the sales quantity from the information set when the campaign was set up.

[0037] Regarding (1-B), when the campaign setting unit 102 accepts the setting of a new campaign, the sales quantity allocation unit 108 refers to the campaign information storage unit 124 to acquire the total sales quantity of each product and the total number of KOLs for the campaign. The sales quantity allocation unit 108 calculates the sales quantity per KOL to be employed by dividing the total sales quantity by the total number of KOLs. In the example of FIG. 5, the sales quantity per KOL for the product "PRD_3" in the campaign "CAN02" is calculated as "15" by dividing the total sales quantity "45" by the total number of KOLs "3". The sales quantity allocation unit 108 allocates the calculated sales quantity to KOLs whose applications to sell the corresponding product have been approved. In this case, the same sales quantity is allocated to KOLs selling the same product regardless of the KOL's characteristics. The approval / rejection processing unit 106 includes the calculated sales quantity in the approval / rejection request as the sales quantity to be allocated to the KOL who applied to sell the corresponding product. In this example, applications can be accepted both before and during the campaign, and if the number of KOLs recruited before the campaign starts is less than the total number of KOLs set in advance, applications will be accepted even during the campaign. If (1-B) is adopted, the KOL score may or may not be calculated.

[0038] Regarding (1-A), each time the sales quantity allocation unit 108 receives a product sales request from a KOL, it references the user information storage unit 122 and determines the sales quantity based on the parameters of the KOL who made the request. The sales quantity allocation unit 108 may determine the sales quantity based on at least one of the KOL's requested product, desired sales quantity, sales channel used, KOL score, sales history, and the organizer of the campaign for which the request is made. For example, the higher the KOL score, the larger the sales quantity allocated. Alternatively, if the KOL has a track record of selling the requested product in the past, a larger sales quantity may be allocated than if the KOL has not. Alternatively, the higher the matching score between the KOL and the organizer, the larger the sales quantity allocated. Alternatively, if the KOL is a live stream broadcaster, the higher the KOL's ranking in the live stream rankings, the larger the sales quantity may be allocated. The approval / rejection processing unit 106 includes the determined sales quantity in the approval / rejection request as the sales quantity to be allocated to the KOL who applied to sell the corresponding product. In this example, applications can be accepted both before and during the campaign, and if an application is accepted during a campaign, for example, the sales quantity may be determined based on the remaining period of the campaign.

[0039] Regarding (2), the sales quantity allocation unit 108 includes in the approval / rejection request the difference between the allocable amount of the applied-for product, i.e., the total sales quantity, and the sum of the allocated sales quantities of the KOLs employed so far, instead of the sales quantity of the applied-for product to be allocated to the KOL. When approving a KOL's sales application, the supplier specifies the sales quantity to be allocated to the KOL. The approval / rejection result signal includes the specified sales quantity.

[0040] Regarding (1) and (2), the sales volume allocation unit 108 may collectively determine the sales volumes for multiple KOLs who have been recruited up to a predetermined point in time before the start of the campaign.

[0041] The application result notification unit 110 transmits the sales quantity determined by the sales quantity allocation unit 108 to the KOL terminal of the KOL who has been selected via the network 20. If the approval / rejection result signal indicates approval, the application result notification unit 110 transmits an approval signal indicating that the application has been approved via the network 20 to the KOL terminal of the KOL related to the approved application. The application result notification unit 110 deletes information related to the approved application from the application information storage unit 126. The application result notification unit 110 registers the user ID of the approved KOL, the approved sales quantity, and the approved sales channel in the adopted KOL ID, allocated sales quantity, and sales channel of the corresponding product in the campaign information storage unit 124. If the approval / rejection result signal indicates rejection, the application result notification unit 110 transmits a rejection signal indicating that the application has been rejected via the network 20 to the KOL terminal of the KOL related to the rejected application. The application result notification unit 110 may delete information related to the rejected application from the application information storage unit 126 or may set a flag indicating rejection.

[0042] The matching unit 114 calculates a matching score between the product of the supplier and the registered KOL. The matching unit 114 calculates a matching score between the product and the registered KOL for the product registered by the supplier based on at least one of the KOL score, sales history, and possible sales channels.

[0043] The recommendation unit 116 generates KOL recommendations to the supplier and / or product recommendations to the KOL based on the calculated matching score. The recommendation unit 116 recommends KOLs to the supplier with higher priority for the KOL's matching score for the product specified by the supplier. For example, the KOLs may be listed in ascending order of matching score and presented to the supplier together with an allocated sales quantity set according to the matching score. When the recommendation unit 116 receives a recommendation request from a KOL, the higher the matching score between the KOL and the product, the higher the priority for recommending the product to the KOL. For example, the recommendation unit 116 may list products in ascending order of matching score and present them to the KOL.

[0044] The offer processing unit 112 transmits an offer including product information to the KOL terminal of the KOL selected by the supplier as the offer recipient via the network 20. When the offer processing unit 112 receives the supplier's selection of the KOL and the allocated sales quantity in response to the KOL's recommendation to the supplier, it transmits the offer to the KOL terminal of the selected KOL. The offer includes information about the supplier who made the offer, information about the campaign and product related to the offer, and the allocated sales quantity. When the offer processing unit 112 receives a signal indicating acceptance of the offer from the KOL terminal of the KOL, it registers the user ID of the KOL who accepted the offer, the offered allocated sales quantity, and the possible sales channel in the adopted KOL ID, allocated sales quantity, and sales channel of the product related to the offer in the campaign information storage unit 124, respectively.

[0045] The campaign management unit 118 performs processes related to campaign management, such as campaign start, progress, and collection of sales volume. When the start of a campaign period for a campaign arrives, the campaign management unit 118 changes the campaign status of the campaign in the campaign information storage unit 124 from not started to ongoing, and starts counting the actual sales volume for each KOL of each product associated with the campaign. The campaign management unit 118 obtains the actual sales volume of each KOL through self-reporting by the KOL or by linking data with a live streaming platform or social media. Such a data linking mechanism may be realized by known technology using an API (Application Programming Interface), etc. When the end of the campaign period arrives, the campaign management unit 118 changes the campaign status of the campaign in the campaign information storage unit 124 from ongoing to ended, and stops counting the actual sales volume for each KOL of each product associated with the campaign.

[0046] The scoring unit 120 calculates a KOL score for each KOL. The KOL score is a value that quantifies the sales power of a KOL. The scoring unit 120 may calculate the KOL score for each KOL based on the sales history of the KOL. Alternatively, the scoring unit 120 may update the KOL score for each KOL employed in a campaign after the campaign ends based on the allocated sales volume and the actual sales volume. The scoring unit 120 may update the KOL score so that the smaller the difference between the allocated sales volume and the actual sales volume, the greater the increment in the KOL score. In the example of FIG. 5, for the campaign "CAN02," the KOL score for KOL "SEL_12" is calculated to be +10, the KOL score for KOL "SEL_10" is calculated to be -10, and the KOL score for KOL "SEL_11" is calculated to be -3. For KOL "SEL_10," the actual sales volume is greater than the allocated sales volume, meaning that KOL "SEL_10" has sold more, but a penalty is still imposed on the score. This type of system makes it easier to control sales volume.

[0047] 7 is a flowchart showing the flow of a series of processes in the supply management server 10. The supply management server 10 receives a new campaign creation request from the supplier terminal of the supplier (S202). The supply management server 10 registers the campaign information included in the new campaign creation request received in step S202 in the campaign information storage unit 124 (S204). The supply management server 10 transmits the campaign information to the KOL terminal of the KOL (S206). The supply management server 10 receives an application for sales of the product included in the campaign information transmitted in step S206 from the KOL terminal of the KOL (S208). The supply management server 10 registers the received sales application in the application information storage unit 126 (S210).

[0048] The supply management server 10 inquires of the supplier's supplier terminal whether or not to approve the sales application registered in step S210 (S212). If the supplier rejects the application (rejection in S212), the supply management server 10 transmits a rejection signal to the KOL terminal of the KOL who submitted the rejected application (S214). If the supplier approves the application (approval in S212), the supply management server 10 registers the approved application in the campaign information storage unit 124 (S216) and transmits an approval signal to the KOL terminal of the KOL who submitted the approved application (S218).

[0049] The campaign begins when the start of the campaign period of the campaign arrives (S220). The supply management server 10 updates the actual sales volume of KOLs who have submitted approved applications during the campaign period (S222). The supply management server 10 determines whether the end of the campaign has arrived (S224). If it has not arrived (N in S224), the process returns to step S222. If the campaign has ended (Y in S224), the supply management server 10 updates the KOL score based on the difference between the allocated sales volume and the actual sales volume (S226).

[0050] 8 is a representative screen diagram of a supplier home screen 600 displayed on the display of the supplier's supplier terminal. When a user logs in, the supplier management server 10 refers to the user information storage unit 122 to determine whether the user is registered as a supplier or a KOL. If the user is registered as a supplier, the supplier management server 10 transmits information for displaying the supplier home screen 600 to the supplier terminal, and the display control unit of the supplier terminal generates the supplier home screen 600 based on the information and displays it on the display. The supplier home screen 600 has a collaboration object 602 with a KOL, an application object 604 from a KOL, and a your campaign object 606.

[0051] When the input acceptance unit of the supplier terminal accepts the specification of your campaign object 606, the communication unit generates a campaign information request including the supplier's user ID and sends it to the supply management server 10 via the network. When the supply management server 10 receives the campaign information request, it acquires campaign information registered in association with the user ID included in the campaign information request from the campaign information storage unit 124 and returns the acquired campaign information to the supplier terminal via the network. The display control unit of the supplier terminal generates a created campaign screen 610 for the supplier based on the received campaign information and displays it on the display.

[0052] FIG. 9 is a representative screen diagram of a supplier-created campaign screen 610 displayed on the display of the supplier's supplier terminal. The supplier-created campaign screen 610 includes campaign information display areas 612 and 614 that display information about campaigns previously created by the supplier, and a new creation button 616. The campaign information display areas 612 and 614 display the campaign status, campaign title, campaign period, information about the products handled in the campaign, the number of KOLs already employed for the campaign, and the number of KOLs currently applying to sell products for the campaign. The number of KOLs currently applying in the campaign information display areas 612 and 614 is calculated by referring to the application information storage unit 126.

[0053] When the input receiving unit of the supplier terminal receives the designation of the Create New button 616, the display control unit generates a create new campaign screen 620 and displays it on the display. Fig. 10 is a representative screen diagram of the create new campaign screen 620 displayed on the display of the supplier's supplier terminal. The create new campaign screen 620 has a title input area 622 for receiving input of the title of the campaign, a period input area 624 for receiving input of the campaign period, a product information input area 626 for receiving input of information about products related to the campaign, a create button 628, and an add product button 629. The product information input area 626 has a product ID input area 626a that accepts input of the product ID of the product that is the subject of the campaign, an area that displays the cost price of the product, a discount rate input area 626b that accepts input of the discount rate to be set for the product, an area that displays the selling price of the product (cost price x discount rate), a total sales quantity input area 626c that accepts input of the total sales quantity of the product in the campaign, and a total number of KOLs input area 626d that accepts input of the total number of KOLs to be hired to sell the product in the campaign.

[0054] The supplier enters the necessary information in the title input area 622, period input area 624, and product information input area 626, and selects the create button 628. When the input acceptance unit of the supplier terminal accepts the selection of the create button 628, the communication unit generates a new campaign creation request including the information entered in the title input area 622, period input area 624, and product information input area 626, and transmits the request to the supply management server 10. The campaign setting unit 102 receives this new campaign creation request, and generates and registers the campaign as described above.

[0055] When the input receiving unit of the supplier terminal receives the designation of the application object 604 from the KOL on the supplier home screen 600 of Figure 8, the communication unit generates an approval / rejection start request including the supplier's supplier ID and transmits it to the supply management server 10 via the network. When the supply management server 10 receives the approval / rejection start request, it generates a corresponding approval / rejection request as described above and returns it to the supplier terminal. The display control unit of the supplier terminal generates an application management screen 630 based on the application information included in the received approval / rejection request and displays it on the display.

[0056] FIG. 11 is a representative screen diagram of an application management screen 630 displayed on the display of a supplier's supplier terminal. The application management screen 630 includes an application information display area 632 that displays application information for a product that is the subject of a campaign created by the supplier. The application information display area 632 is generated for each application. The application information display area 632 includes an applicant ID identifying the KOL who submitted the application, the title of the campaign related to the application, the application time (the time the application was submitted or received), the product ID of the product the KOL wishes to sell (i.e., the product subject to the application), the desired sales quantity specified by the KOL, the sales channel specified by the KOL, an allocation sales quantity input area 634 that accepts input of the supplier's allocation sales quantity, an approve button 636, and a reject button 638. The application management screen 630 also functions as an approval screen that inquires whether to approve the application included in the received approval / rejection request. In other embodiments, application management and approval may be implemented on separate screens.

[0057] In an example where the sales quota is calculated by a server, the sales quota calculated by the system may be displayed in an unchangeable form in place of the sales quota input field 634. Alternatively, the sales quota calculated by the server may be pre-filled and entered into the sales quota input field 634. In the application information display field second from the top in FIG. 11, since the available allocation for product "PRD_2" is 0 at the time the application management screen 630 is displayed, the sales quota input field is pre-filled with "none" and cannot be entered, and the approve button is grayed out and cannot be selected. In this way, the application information display field 632 is configured so that if there is no sales quantity of a product to be allocated to a KOL, the application for that product can only be rejected.

[0058] 11, the supplier inputs the necessary information into the quota sales quantity input area 634 for each application information display area 632 displayed on the application management screen 630, and selects either the approve button 636 or the reject button 638. When the input acceptance unit of the supplier terminal accepts the selection of the approve button 636 or the reject button 638, the communication unit generates an approval / rejection result signal indicating approval including the quota sales quantity input into the quota sales quantity input area 634 if the approve button 636 is selected, or generates an approval / rejection result signal indicating rejection if the reject button 638 is selected. The communication unit transmits the generated approval / rejection result signal to the supply management server 10.

[0059] When the input receiving unit of the supplier terminal receives the designation of the collaboration object 602 with a KOL on the supplier home screen 600 of Figure 8, the communication unit generates a collaboration information request including the supplier's supplier ID and transmits it to the supply management server 10 via the network. Upon receiving the collaboration information request, the supply management server 10 obtains information on the campaign registered in association with the supplier ID included in the collaboration information request and information on the KOL selected in the campaign from the campaign information storage unit 124 and returns it to the supplier terminal via the network. The display control unit of the supplier terminal generates a collaboration display screen 640 based on the received information and displays it on the display.

[0060] 12 is a representative screen diagram of a collaboration display screen 640 displayed on the display of the supplier's supplier terminal. The collaboration display screen 640 has a collaboration item display area 642 that displays information about KOLs selected in a campaign created by the supplier. The collaboration item display area 642 displays, in association with each other, the KOL ID of the KOL selected in the campaign, the campaign title of the campaign, the campaign status, the product ID of the product sold by the KOL, the KOL's allocated sales quantity, and the KOL's actual sales quantity.

[0061] FIG. 13 is a representative screen diagram of a KOL home screen 700 displayed on the display of a KOL terminal of a KOL. When a user logs in, the supply management server 10 refers to the user information storage unit 122 to determine whether the user is registered as a supplier or a KOL. If the user is registered as a KOL, the supply management server 10 transmits information for displaying the KOL home screen 700 to the KOL terminal via the network. The display control unit of the KOL terminal generates the KOL home screen 700 based on the received information and displays it on the display. The KOL home screen 700 includes a campaign search area 702, a currently collaborating object 704, and an application-in-progress object 706. The campaign search area 702 includes a search key receiving area for receiving input of a search key and a recommendation information display area for displaying recommendation information generated for the KOL by the recommendation unit 116. In its initial state, the recommendation information display area displays information about campaigns generated by suppliers with high matching scores with the KOL. The campaign information includes the supplier ID of the supplier who created the campaign, the title of the campaign, and the campaign period. When the KOL enters a desired word in the search key reception area, the communication unit transmits the word to the supply management server 10. The supply management server 10 searches for suppliers and / or campaigns using the received word as a key and transmits the search results to the KOL terminal. The display control unit of the KOL terminal updates the campaign information displayed in the recommendation information display area based on the received search results.

[0062] When the input acceptance unit of the KOL terminal accepts the designation of a campaign to be displayed in the campaign search area 702, the communication unit generates a campaign details request including the campaign ID of the designated campaign and transmits it to the supply management server 10 via the network. When the supply management server 10 receives the campaign details request, it obtains information about the campaign identified by the campaign ID included in the campaign details request from the campaign information storage unit 124 and returns it to the KOL terminal via the network. The display control unit of the KOL terminal generates a sales application screen 710 based on the received campaign information and displays it on the display.

[0063] FIG. 14 is a representative screen diagram of a sales application screen 710 displayed on the display of a KOL's KOL terminal. The sales application screen 710 displays information about the campaign specified in the campaign search area 702 of the KOL home screen 700 of FIG. 13, and has a campaign information display area 712 that accepts applications to sell products related to the campaign. The campaign information display area 712 displays the campaign status, campaign title, campaign period, and information about the products related to the campaign. In association with the display of each product related to the campaign, a desired sales quantity input area 716 that accepts input of the desired sales quantity of the product and a sales channel input area 718 that accepts input of the sales channel to be used are displayed. If you do not wish to sell a certain product, enter 0 in the desired sales quantity input area 716.

[0064] The KOL enters the necessary information in the desired sales quantity input area 716 and the sales channel input area 718, and selects the sales application button 714. When the input acceptance unit of the KOL terminal accepts the selection of the sales application button 714, the communication unit generates an application including the information entered in the desired sales quantity input area 716 and the sales channel input area 718, and transmits it to the supply management server 10. The application acceptance unit 104 receives this application and registers it in the application information storage unit 126 as described above.

[0065] When the input acceptance unit of the KOL terminal accepts the designation of the pending application object 706 on the KOL home screen 700 of Figure 13, the communication unit generates an pending application information request including the KOL's KOLID and transmits it to the supply management server 10 via the network. When the supply management server 10 receives the pending application information request, it obtains application information registered in association with the KOLID included in the received pending application information request from the application information storage unit 126 and returns it to the KOL terminal via the network. The display control unit of the KOL terminal generates an application status screen 720 based on the received application information and displays it on the display.

[0066] FIG. 15 is a representative screen diagram of an application status screen 720 displayed on the display of a KOL's KOL terminal. The application status screen 720 includes an application information display area 722 that displays information about the application submitted by the KOL. The application information display area 722 is generated for each application. The application information display area 722 displays the title of the campaign related to the product for which the KOL has applied to sell, the period of the campaign, the status of the campaign, the product ID of the product, the desired sales quantity specified by the KOL, the status of the application, and a withdrawal button. When the withdrawal button is pressed, the communication unit generates a withdrawal request including an application ID that identifies the application corresponding to the pressed withdrawal button and transmits the request to the supply management server 10 via the network. Upon receiving the withdrawal request, the supply management server 10 either deletes the application identified by the application ID included in the withdrawal request from the application information storage unit 126 or sets a flag indicating withdrawal. The withdrawn application is no longer included in the approval / rejection request.

[0067] When the input acceptance unit of the KOL terminal accepts the designation of the collaborating object 704 on the KOL home screen 700 of Figure 13, the communication unit generates a collaboration information request including the KOL's KOLID and transmits it to the supply management server 10 via the network. When the supply management server 10 receives the collaboration information request, it acquires campaign information registered in association with the KOLID included in the received collaboration information request from the campaign information storage unit 124 and returns it to the KOL terminal via the network. The display control unit of the KOL terminal generates a collaboration status display screen 730 based on the received campaign information and displays it on the display.

[0068] FIG. 16 is a representative screen diagram of a collaboration status display screen 730 displayed on the display of a KOL's KOL terminal. The collaboration status display screen 730 has a collaboration information display area that displays information about products for which the KOL has been approved to sell. A collaboration information display area is created for each product. The collaboration information display area displays the title of a campaign related to a product that the supplier has approved the KOL to sell, the period of the campaign, the status of the campaign, the product ID of the product, the sales quantity allocated to the KOL, and the actual sales quantity.

[0069] FIG. 17 is a representative screen diagram of an approval notification screen 740 displayed on the display of the KOL terminal of the KOL. When the display control unit of the KOL terminal receives an approval signal from the supply management server 10, it generates an approval notification screen 740 including the allocated sales quantity included in the approval signal and displays it on the display. If the application sent from the KOL terminal is approved by the supplier, an approval signal including a notice that the application has been approved and the approved allocated sales quantity is generated by the supply management server 10 and transmitted via the network to the KOL terminal of the KOL who made the application. The KOL terminal receives the approval signal. The approval notification screen 740 displays the allocated sales quantity included in the received approval signal in association with information about the approved product.

[0070] In the above-described embodiments, examples of the storage unit are a hard disk and a semiconductor memory. Furthermore, based on the description in this specification, it will be understood by those skilled in the art that each unit can be realized by a CPU (not shown), an installed application program module, a system program module, a semiconductor memory that temporarily stores the contents of data read from a hard disk, or the like.

[0071] The supply management system 2 according to this embodiment allows suppliers to more appropriately manage sales of sales targets by KOLs. The total sales quantity of sales targets is predetermined for each campaign, and KOLs can be employed within the range of this total sales quantity, thereby preventing unsold items and overselling. Furthermore, KOLs can improve sales efficiency by adjusting their sales activities according to the sales quantity allocated to them. In particular, in the case of cross-border sales, it is even more difficult for suppliers to estimate how much a KOL can sell because the countries are different. In such cases, the system according to this embodiment specifies the total sales quantity in advance and determines the sales quantity to be allocated to each KOL, making it easier and more accurate to control the sales quantity.

[0072] The hardware configuration of an information processing device according to this embodiment will be described with reference to Fig. 18. Fig. 18 is a block diagram showing an example of the hardware configuration of an information processing device according to this embodiment. The illustrated information processing device 900 can realize, for example, the supply management server 10 and each terminal according to this embodiment.

[0073] The information processing device 900 includes a CPU 901, a read-only memory (ROM) 902, and a random-access memory (RAM) 903. The information processing device 900 may also include a host bus 907, a bridge 909, an external bus 911, an interface 913, an input device 915, an output device 917, a storage device 919, a drive 921, a connection port 925, and a communication device 929. The information processing device 900 also includes an imaging device (not shown) such as a camera. The CPU 901 is an example of a hardware configuration for realizing functions realized by the components described herein. The functions described herein may be realized by circuits programmed to realize the described functions. Circuits programmed to realize the functions described herein include a central processing unit (CPU), a digital signal processor (DSP), a general-purpose processor, an application-specific processor, an integrated circuit, an application-specific integrated circuit (ASIC), and / or a combination thereof. In this specification, a unit that achieves a specific function may be realized as a circuit programmed to achieve that function.

[0074] The CPU 901 functions as an arithmetic processing unit and control unit, and controls all or part of the operations within the information processing device 900 in accordance with various programs recorded in the ROM 902, RAM 903, storage device 919, or removable recording medium 923. For example, the CPU 901 controls all of the operations of the functional units included in the server 10 and the user terminals 20 and 30 in this embodiment. The ROM 902 stores programs and calculation parameters used by the CPU 901. The RAM 903 temporarily stores programs used in the execution of the CPU 901, as well as parameters that change as appropriate during the execution. The CPU 901, ROM 902, and RAM 903 are interconnected by a host bus 907, which is an internal bus such as a CPU bus. The host bus 907 is further connected to an external bus 911, such as a PCI (Peripheral Component Interconnect / Interface) bus, via a bridge 909.

[0075] The input device 915 may be, for example, a device operated by a user, such as a mouse, keyboard, touch panel, button, switch, or lever, or may be a device that converts physical quantities into electrical signals, such as a sound sensor such as a microphone, an acceleration sensor, a tilt sensor, an infrared sensor, a depth sensor, a temperature sensor, or a humidity sensor. The input device 915 may be, for example, a remote control device that uses infrared or other radio waves, or an externally connected device 927 such as a mobile phone that supports operation of the information processing device 900. The input device 915 includes an input control circuit that generates an input signal based on information input by the user or a sensed physical quantity and outputs the signal to the CPU 901. The user operates the input device 915 to input various data to the information processing device 900 or to instruct processing operations.

[0076] The output device 917 is configured by a device that can notify the user of acquired information visually or audibly. The output device 917 can be, for example, a display such as an LCD, PDP, or OELD, an audio output device such as a speaker or headphones, or a printer. The output device 917 outputs the results obtained by processing by the information processing device 900 as video such as text or images, or as sound such as audio.

[0077] The storage device 919 is a data storage device configured as an example of a storage unit of the information processing device 900. The storage device 919 is configured, for example, by a magnetic storage device such as a hard disk drive (HDD), a semiconductor storage device, an optical storage device, or a magneto-optical storage device. The storage device 919 stores programs and various data executed by the CPU 901, as well as various data acquired from the outside.

[0078] The drive 921 is a reader / writer for a removable recording medium 923 such as a magnetic disk, optical disk, magneto-optical disk, or semiconductor memory, and is built into or externally attached to the information processing device 900. The drive 921 reads information recorded on the attached removable recording medium 923 and outputs it to the RAM 903. The drive 921 also writes information to the attached removable recording medium 923.

[0079] The connection port 925 is a port for directly connecting a device to the information processing device 900. The connection port 925 can be, for example, a Universal Serial Bus (USB) port, an IEEE 1394 port, or a Small Computer System Interface (SCSI) port. The connection port 925 can also be an RS-232C port, an optical audio terminal, or a High-Definition Multimedia Interface (HDMI) (registered trademark) port. By connecting an external device 927 to the connection port 925, various types of data can be exchanged between the information processing device 900 and the external device 927.

[0080] The communication device 929 is, for example, a communication interface configured with a communication device for connecting to a network NW. The communication device 929 can be, for example, a communication card for a wired or wireless LAN (Local Area Network), Bluetooth (registered trademark), or WUSB (Wireless USB). The communication device 929 may also be a router for optical communication, a router for ADSL (Asymmetric Digital Subscriber Line), or a modem for various communications. The communication device 929 transmits and receives signals, for example, between the Internet and other communication devices using a predetermined protocol such as TCP / IP. The communication network NW connected to the communication device 929 is a network connected by wire or wirelessly, such as the Internet, a home LAN, infrared communication, radio wave communication, or satellite communication. The communication device 929 also functions as a communication unit.

[0081] An imaging device (not shown) such as a camera is a device that captures real space and generates a captured image using an imaging element such as a CCD (Charge Coupled Device) or a CMOS (Complementary Metal Oxide Semiconductor), and various components such as a lens for controlling the formation of a subject image on the imaging element. The imaging device may capture still images or moving images.

[0082] The above describes the configuration and operation of the supply management system 2 according to the embodiment. This embodiment is an example, and it will be understood by those skilled in the art that various modifications are possible in the combination of each component and each process, and that such modifications are also within the scope of the present disclosure.

[0083] In the embodiment, the case where the supplier specifies the total sales quantity of the product during the campaign period has been described, but this is not limited thereto, and the supplier does not have to specify such a total sales quantity. In this case, the sales quota may be calculated based on the inventory quantity of the product registered in the user information storage unit 122. For example, if the inventory quantity of a certain product is 500 and the total number of sellers of the product in a certain campaign is 10, the sales quota of each seller to be adopted may be calculated as 500 / 10=50.

[0084] In the processing procedures described in this specification, particularly in processing procedures described using flow diagrams and flowcharts, it is possible to omit some of the processes (steps) that make up the processing procedures, to add processes that are not explicitly stated as processes that make up the processing procedures, and / or to change the order of the processes, and processing procedures in which such omissions, additions, or changes in order have been made are also included within the scope of this disclosure as long as they do not deviate from the intent of this disclosure.

Claims

1. A means for acquiring, via a network from a supplier terminal, a sales object ID that identifies a sales object and the total number of sellers to be employed during a predetermined campaign period; a means for registering the acquired sales object ID and the acquired total number of sellers in a storage means in association with each other; a means for determining the sales quantity of the sales object to be allocated to the selected seller by referring to the holding means; and means for transmitting the determined sales quantity via the network to the terminal of the seller who has been selected.

2. means for receiving an application from a terminal of a seller who wishes to sell the object for sale via the network; The server according to claim 1 , further comprising: a means for performing a process for determining whether or not to employ the seller related to the received application.

3. The means for performing the processing includes: means for transmitting an approval or denial request to the supplier terminal via the network, the approval or denial request including information on the seller pertaining to the application and the sales quantity of the sales object to be allocated to the seller; The server according to claim 2, further comprising: means for transmitting information indicating that the application has been rejected via the network to the terminal of the seller related to the application if the result of the approval / denial request for approval / denial is a rejection.

4. the storage means stores sales object IDs of a plurality of different sales objects in association with the campaign period; The server according to claim 2 , wherein the application is an application relating to at least one of the plurality of different sales objects.

5. The server according to claim 1, further comprising means for transmitting an offer including information about the sale target via the network to a terminal of a seller of the sale target selected by the supplier.

6. A means for calculating a matching score between the sales object and a registered seller; The server of claim 1 , further comprising: means for generating recommendations of sellers to the suppliers and / or recommendations of the items for sale to the sellers based on the calculated matching scores.

7. The server of claim 1 , wherein the campaign period is associated with a live commerce event held on a live streaming platform.

8. 2. The server according to claim 1, wherein said determining means determines the sales quantity of said sales objects to be allocated to each employed seller based on the total sales quantity of said sales objects and said total number of sellers.

9. On the supplier's terminal, a function of displaying on a display a campaign setting screen for receiving input of a sales target ID that identifies a sales target and the total number of sellers to be employed during a predetermined campaign period; a function of transmitting the sales target ID and the total number of sellers inputted on the campaign setting screen to a server via a network; a function of receiving, via the network, an approval / denial request including information related to the application received by the server from a terminal of a seller who wishes to sell the item for sale; A computer program for realizing a function of displaying on the display an approval screen inquiring whether or not to approve the application related to the approval / rejection request.

10. The computer program according to claim 9 , wherein the approval screen is configured to only allow rejection of the application related to the approval / rejection request if there is no sales quantity of the sales item to be allocated to the seller.

11. On the terminal of the seller who wants to sell the item, a function of transmitting the application for the object for sale to a server via a network; a function of receiving, if the application is approved, the sales quantity of the object for sale allocated to the seller from the server via the network; a computer program for realizing a function of displaying the received sales quantity on a display in association with information on the sales item;

Images