Trading system, trading method, and trading program

Abstract

To reduce the load of demand work for royalty to an FC store and errors thereof when dealing trade is made between the FC store and its directly operated store.SOLUTION: A dealing trading system comprises: expected sale input means which inputs expected sale data including an expected sale number, an article, a sale amount, and a sale-completion flag indicative "sale in-completed" according to FC store-side operation on an expected sale input screen when the FC store sells the article to the directly operated store; sale purchase input means which refers to the expected sale data according to directly managed store-side operation on a sale purchase input screen to input purchase data including a purchase number, the article, and the sale amount, and updates the sale-completion flag of the expected sale data into "sale completed" to generate sale data; royalty calculation means which refers to a royalty setting master based upon the sale data to calculate a royalty; and demand data generation means which generates demand data to the FC store based upon the calculation result of the royalty.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a trading system, a trading method, and a trading program. [Background technology]

[0002] For example, in a company that operates multiple stores through a franchise (hereinafter sometimes referred to as "FC"), sales transactions occur between the headquarters and the FC stores, but sales transactions may also occur between directly managed stores and the FC stores. For example, Patent Document 1 is an example of a conventional FC system. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2018-55374 Summary of the Invention [Problem to be solved by the invention]

[0004] However, Patent Document 1 does not state anything about the case where a sales transaction occurs between a directly managed store and a franchise store.

[0005] The present invention has been made in consideration of the above, and aims to provide a trading system, a trading method, and a trading program that can reduce the burden and errors in claiming royalties from franchise stores when a trading transaction occurs between a franchise store and a directly managed store. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides a buying and selling transaction system that includes a control unit and calculates royalties when a franchised store sells goods to a directly managed store, the control unit being configured to be able to access a registered royalty setting master that associates product classifications with royalty rates, and that includes: a sales forecast input means that, when a franchised store sells goods to a directly managed store, inputs and stores in a memory area forecast sales data including a sales forecast number, product, sales amount, and a sold flag set to "unsold" in accordance with operations performed by the franchised store on a sales forecast input screen; a sales purchase input means that, in accordance with operations performed by the directly managed store on a sales purchase input screen, refers to the forecast sales data, inputs purchase data including a purchase number, product, and sales amount, and stores the purchase data in the memory area, updates the sold flag of the forecast sales data to "sold," and creates sales data including the sales number, product, and sales amount, and stores the sales data in the memory area; a royalty calculation means that refers to the royalty setting master based on the sales data and calculates royalties; and a billing data creation means that creates billing data for the franchised store based on the royalty calculation results.

[0007] Furthermore, according to one aspect of the present invention, the royalty setting master further registers an upper limit amount that specifies the upper limit of royalty generation and a lower limit amount that specifies the lower limit of royalty generation, and any portion of the sales amount that exceeds the upper limit amount is not subject to royalties, and if the sales amount is below the lower limit amount, it is also not subject to royalties.

[0008] According to another aspect of the present invention, the royalty setting master may be set for each franchise store.

[0009] Furthermore, according to one aspect of the present invention, the control unit may further be provided with an unrecorded purchase confirmation means that refers to the sales forecast data of franchise stores and the purchase data of directly managed stores stored in the memory area, and contacts the directly managed store if there are products that are planned to be purchased at the directly managed store but have not been recorded as purchased.

[0010] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention provides a buying and selling transaction method executed by an information processing device equipped with a control unit, wherein the control unit is configured to be able to access a registered royalty setting master that associates product classifications with royalty rates, and the method includes the following steps executed by the control unit: a sales forecast input process for, when a franchise store sells products to a directly managed store, inputting and storing in a memory area forecast sales data including the sales forecast number, product, sales amount, and a sold flag set to "unsold" in accordance with operations on the franchise store's sales forecast input screen; a sales purchase input process for, in accordance with operations on the directly managed store's sales forecast data, inputting and storing in the memory area purchase data including the purchase number, product, and sales amount, and updating the sold flag of the sales forecast data to "sold," creating and storing in the memory area sales data including the sales number, product, and sales amount; a royalty calculation process for calculating royalties by referring to the royalty setting master based on the sales data; and a billing data creation process for creating billing data for the franchise store based on the royalty calculation results.

[0011] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention provides a sales transaction program to be executed by an information processing device having a control unit, the control unit being configured to be able to access a registered royalty setting master that associates product classifications with royalty rates, and the control unit is configured to execute the following sales transaction program: a sales forecast input process in which, when a franchise store sells products to a directly managed store, in accordance with operations on a sales forecast input screen by the franchise store, inputs and stores in a memory area forecast sales data including a sales forecast number, product, sales amount, and a sold flag set to "unsold"; a sales purchase input process in which, in accordance with operations on a sales purchase input screen by the directly managed store, references the forecast sales data, inputs and stores in the memory area purchase data including a purchase number, product, and sales amount, updates the sold flag of the forecast sales data to "sold," and creates and stores in the memory area sales data including the sales number, product, and sales amount; a royalty calculation process in which, based on the sales data, references the royalty setting master to calculate royalties; and a billing data creation process in which billing data for the franchise store is created based on the royalty calculation results. [Effects of the Invention]

[0012] According to the present invention, when a sales transaction occurs between a franchise store and a directly managed store, it is possible to reduce the burden and errors involved in billing royalties to the franchise store. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram illustrating a flow of a conventional sales transaction between a franchise store and a directly managed store. [Figure 2] FIG. 2 is a block diagram showing an example of a buying and selling transaction system according to this embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of the configuration of the royalty setting master. [Figure 4] FIG. 4 is a flowchart for explaining an outline of the overall processing of the buying and selling transaction system according to this embodiment. [Figure 5] FIG. 5 is a diagram for explaining a specific example of the processing of the control unit of the buying and selling transaction system according to this embodiment. [Figure 6] FIG. 6 is a diagram for explaining a specific example of the processing of the control unit of the buying and selling transaction system according to this embodiment. [Figure 7] FIG. 7 is a diagram for explaining a specific example of the processing of the control unit of the buying and selling transaction system according to this embodiment. [Figure 8] FIG. 8 is a diagram for explaining a specific example of the processing of the control unit of the buying and selling transaction system according to this embodiment. [Figure 9] FIG. 9 is a diagram for explaining a specific example of the processing of the control unit of the buying and selling transaction system according to this embodiment. [Figure 10] FIG. 10 is a diagram for explaining a specific example of the processing of the control unit of the buying and selling transaction system according to this embodiment. [Figure 11] FIG. 11 is a diagram for explaining a specific example of the processing of the control unit of the buying and selling transaction system according to this embodiment. [Figure 12] FIG. 12 is a diagram for explaining a specific example of the processing of the control unit of the buying and selling transaction system according to this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0014] An embodiment of a trading system, a trading method, and a trading program according to the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to the embodiment.

[0015] [1. Overview] For example, in a company that operates multiple stores through a franchise (hereinafter sometimes referred to as "FC"), sales transactions occur between the headquarters and the franchise stores, but sales transactions may also occur between directly managed stores and the franchise stores.

[0016] When franchise stores sell products to directly managed stores, they attach invoices to the products and ship them to the directly managed stores. Because directly managed stores and franchise stores record their purchases and sales separately, they need to compare the actual results. As a result, discrepancies in the comparison results occur due to missed invoice registrations and input errors in detailed information such as unit prices. This is because the more franchise stores and directly managed stores there are, the more diverse the combinations of directly managed stores and franchise stores become and the larger the amount of data becomes, which makes the comparison process more time-consuming and requires more individualized response.

[0017] Figure 1 is a diagram illustrating the flow of a conventional sales transaction between franchise stores and directly managed stores. In Figure 1, (1) the franchise store ships the product to the directly managed store with a voucher attached, and also enters the sales data and stores the sales data. (2) The directly managed store checks the product and voucher, enters the purchase data, and stores the purchase data. (3) The headquarters receives the purchase data from the directly managed store and the sales data from the franchise store, performs a cross-check with each store, and requests corrections to the voucher as necessary. (4) Royalties to the franchise store are calculated based on the directly managed store's purchase accounting. (5) Royalties are claimed from the directly managed store to the franchise store.

[0018] In this embodiment, when a sales transaction occurs between a directly managed store and a franchise store, instead of the directly managed store and the franchise store recording separate invoices, the purchasing side (directly managed store) records the invoice based on information registered from the selling side (franchise store), thereby reducing the burden and errors in the process of billing royalties to franchise stores.

[0019] According to this embodiment, discrepancies no longer occur during the reconciliation process, eliminating the need to check each store's performance. Furthermore, since the purchasing side does not need to input invoice information from scratch, there are no discrepancies between the product and the invoice. The reduced time spent on reconciliation improves operational efficiency, including royalty calculation. By setting upper and lower limits for the transaction amount, the higher the sales volume, the greater the range in which no royalties are generated, which increases the motivation of franchise stores to increase their sales. Royalties can be generated not only through transactions with the headquarters, but also between franchise stores and directly managed stores, eliminating the need for franchise stores to trade through the headquarters.

[0020] The buying and selling transaction system of this embodiment is widely applicable to the distribution and retail industry, franchised businesses, and the like.

[0021] [2. Configuration] An example of the configuration of a buying and selling transaction system according to this embodiment will be described with reference to FIG. 2. FIG. 2 is a block diagram showing an example of a buying and selling transaction system according to this embodiment. The buying and selling transaction system according to this embodiment is introduced, for example, into the headquarters of a company that operates a franchise network. In the following, a company that operates a pawnbroking business will be described as an example, but the present invention is not limited to this.

[0022] The trading system 100 is a commercially available desktop personal computer. The trading system 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.

[0023] The trading system 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. The units included in the trading system 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0024] The communication interface unit 104 communicably connects the buying and selling transaction system 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of communicably connecting the buying and selling transaction system 100 with the server 200, the franchise store terminals 400... of multiple franchise stores, and the directly managed store terminals 500... of multiple directly managed stores, for example, the Internet or a LAN (Local Area Network).

[0025] The franchise store terminals 400 are terminals provided in a plurality of franchise stores (for example, the franchise store Shibuya, the franchise store Ikebukuro, the franchise store Ginza, the franchise store Nakano, etc.), and are configured to be capable of data communication with the buying and selling transaction system 100.

[0026] The directly managed store terminals 500 are terminals provided in a plurality of directly managed stores (for example, the directly managed Shinjuku store), and are configured to be capable of data communication with the buying and selling transaction system 100.

[0027] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that functions as a pointing device in cooperation with a mouse. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0028] The memory unit 106 (storage area) stores various databases, tables, files, etc. The memory unit 106 stores computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes. The memory unit 206 can be, for example, a memory device such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The memory unit 106 also includes a royalty setting master 106a, a franchise store table 106b, a directly managed store table 106c, etc. Figure 3 is a diagram showing an example of the configuration of the royalty setting master 106a.

[0029] As shown in FIG. 3, the royalty setting master 106a can be configured as a table that associates and registers franchise stores (franchise store codes and / or franchise store names), transaction types (e.g., sales, purchases), product categories, upper and lower limits, and royalty rates. "Transaction types" are purchases or sales. "Purchases" are transactions in which franchise stores purchase products from general customers. "Sales" are transactions that occur when franchise stores sell to general customers or directly managed stores. "Upper limit" is the maximum amount for which royalties are generated, and any portion of the transaction amount exceeding the upper limit is not subject to royalties. "Lower limit" is the minimum amount for which royalties are generated, and any transaction amount below the lower limit is not subject to royalties.

[0030] The franchise store table 106b is a file for storing projected sales data, sales data, purchase data, and the like for franchise stores.

[0031] The sales forecast data may include the slip number, transaction date, franchise store (shipping origin), customer (shipping destination), sales forecast number, product (product code and / or product name), sales quantity, sales amount, sold flag, etc. The sold flag is set to "0: not sold" when the sales forecast data is created, and is updated to "1: sold" when the purchase is recorded at a directly managed store.

[0032] Sales data may include slip number, transaction date (sales date), franchise store (shipping origin), customer (shipping destination), sales number, product, sales quantity, sales amount, etc.

[0033] The purchase data may include the franchise store, transaction date (purchase date), purchase number, product, purchase amount, etc.

[0034] The directly managed store table 106c is a table for storing purchase data, billing data, etc. of directly managed stores.

[0035] The purchase data may include directly managed store, transaction date (purchase date), supplier (franchise store), purchase number, product, purchase amount, etc.

[0036] The billing data may include the customer, billing number, billing amount, etc.

[0037] The control unit 102 is a CPU or the like that performs overall control of the buying and selling transaction system 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing based on these stored programs.

[0038] The control unit 102 is configured to be able to access the royalty setting master 106a, the franchise store table 106b, and the directly managed store table 106c stored in the storage unit 106. The royalty setting master 106a, the franchise store table 106b, and the directly managed store table 106c may be provided in another location (for example, the server 200) as long as the control unit 102 is able to access them.

[0039] In terms of functional concept, the control unit 102 comprises a sales forecast input unit 102a, a sales and purchase input unit 102b, a royalty calculation unit 102c, a billing data creation unit 102d, an unrecorded purchase confirmation unit 102e, a master maintenance unit 102f, and a screen display control unit 102g.

[0040] When a franchise store sells (ships) a product to a directly managed store, the sales forecast input unit 102a provides a sales forecast input screen in response to access from the franchise store terminal 400, and inputs sales forecast data including the sales forecast number, product, sales amount, and a sold flag set to "0: not sold" in response to operations of the franchise store terminal 400 on the sales forecast input screen, and stores the data in the franchise store table 106b.

[0041] The sales and purchase input unit 102b provides a sales and purchase input screen in response to access from the directly managed store terminal 500, and in response to operation of the directly managed store terminal 500 on the sales and purchase input screen, references the projected sales data stored in the franchise store table 106b, inputs purchase data including the purchase number, product, and sales amount, and stores it in the franchise store table 106c, and also updates the sold flag of the referenced projected sales data to "1: Sold", creates sales data including the sales number, product, and sales amount, and stores it in the franchise store table 106b.

[0042] The royalty calculation unit 102c calculates royalties based on the sales data in the franchise store table 106b and by referring to the royalty setting master 106a.

[0043] The billing data creation unit 102d creates billing data for franchised stores based on the royalty calculation results and stores the data in the directly managed store table 106c.

[0044] The unrecorded purchase confirmation unit 102e refers to the sales forecast data in the franchise store table 106b and the purchase data in the directly managed store table 106c, and if there is a purchase planned at the directly managed store but there is a product (voucher) for which the purchase has not been recorded (for example, if the corresponding purchase data has not been created for a specified period after the sales forecast data was created), it contacts the directly managed store.

[0045] The master maintenance unit 102f performs settings such as inputting, adding, deleting, and editing data in the royalty setting master 106a in response to an operator's operation on a master maintenance screen (not shown) displayed on the monitor 114, for example.

[0046] The screen display control unit 102g controls the display of various screens (master maintenance screen, royalty calculation screen, etc.) displayed on the monitor 114 and the inputs therefor.

[0047] [3. Specific Examples] Specific examples of processing of the buying and selling transaction system 100 in this embodiment will be described with reference to Figures 2 to 12. First, an outline of the overall processing of the buying and selling transaction system 100 in this embodiment will be described with reference to Figure 4. Figure 4 is a diagram showing a flow for explaining an outline of the overall processing of the buying and selling transaction system 100 in this embodiment.

[0048] (3-1. Overall processing) Figure 4 shows the flow of sales transactions between franchise stores and directly managed stores. In Figure 4, (1) the franchise store ships merchandise to the directly managed store with an invoice attached, and also enters a sales forecast. The sales forecast input unit 102a executes a sales forecast input process (step S1). Specifically, in the sales forecast input process, the sales forecast input unit 102a provides a sales forecast input screen in response to access from the franchise store terminal 400, and enters sales forecast data including the invoice number, product, sales amount, and sales completion flag ("0: not yet sold") in response to input operations on the sales forecast input screen by the franchise store terminal 400, and stores the data in the franchise store table 106b.

[0049] (2) When the directly managed store receives the product, it performs a sales purchase entry based on the product's invoice number. The sales purchase entry unit 102b executes the sales purchase process (step S2). Specifically, in the sales entry process, the sales purchase entry unit 102b provides a sales purchase entry screen in response to access from the directly managed store terminal 500, and in response to input operations on the sales purchase entry screen from the directly managed store terminal 500, references (reads) the projected sales data stored in the franchise store table 106b using the invoice number as a key, inputs the purchase data including the purchase number, product, and sales amount, and stores it in the directly managed store table 106b. The sales purchase entry unit 102b also updates the sales completion flag of the referenced projected sales data to "1: Sold," and further generates sales data including the sales number, product, and amount based on the projected sales data and stores it in the franchise store table 106b.

[0050] (3) If a directly managed store has planned purchases but has not yet recorded the purchases, the headquarters (e.g., headquarters accounting) will contact the directly managed store. Specifically, the unrecorded purchases confirmation unit 102e, in response to operations by the headquarters accounting staff on the confirmation screen displayed on the monitor 114, refers to the planned sales data in the franchise store table 106b and the purchase data in the directly managed store table 106c, and if a directly managed store has planned purchases but has not yet recorded the purchases (slips) (e.g., if corresponding purchase data has not been created for a predetermined period after the planned sales data was created), will contact the directly managed store.

[0051] (4) Calculate royalties based on the purchases of directly managed stores. The royalty calculation unit 102c executes royalty calculation processing (step S3). Specifically, in the royalty calculation processing, the royalty calculation unit 102c calculates royalties based on the sales data in the franchise store table 106b, with reference to the royalty setting master 106a.

[0052] (5) Royalties are billed to franchised stores. The billing data creation unit 102d executes the billing data creation process (step S4). Specifically, in the billing data creation process, the billing data creation unit 102d creates billing data for franchised stores based on the royalty calculation results, stores the data in the directly managed store table 106c, and issues an invoice based on the billing data.

[0053] The following describes a case where a franchise store transacts with a general customer. When a franchise store sells to a general customer, the control unit 102 provides a sales input screen in response to access from the franchise store terminal 400, and inputs sales data including the sales number, product, and sales amount in response to input operations on the sales input screen by the franchise store terminal 400, and stores the data in the franchise store table 106b. When a franchise store purchases from a general customer, the control unit 102 provides a purchase input screen in response to access from the franchise store terminal 400, and inputs purchase data including the purchase number, product, and purchase amount in response to input operations on the purchase input screen by the franchise store terminal 400, and stores the data in the franchise store table 106b.

[0054] (3-2. Sample data) 5 to 8 are diagrams showing sample data for explaining a specific example of the processing by the control unit 102 of the buying and selling transaction system 100 according to this embodiment. A specific example of the processing by the control unit 102 of the buying and selling transaction system 100 according to this embodiment will be explained with reference to FIGS.

[0055] (S1: Sales forecast input processing) The sales forecast input process will be described in detail with reference to Figure 5. In response to access from the franchise store terminal 400, the sales forecast input unit 102a provides a sales forecast input screen, and in response to input operations on the sales forecast input screen by the franchise store terminal 400, inputs sales forecast data including the slip number, product, sales amount, and sold flag (0: not sold), and stores the data in the franchise store table 106b.

[0056] 5(A) is a diagram showing an example of a display of a sales forecast input screen. The sales forecast input screen has a header area for specifying (inputting) the slip number, transaction date, franchise store (shipping origin), shipping destination (directly managed store), etc., a details area for specifying the sales category, product / product name, sales quantity, sales amount, etc., and a registration button (not shown).

[0057] When the registration button is pressed, the sales forecast data corresponding to the input contents on the sales forecast input screen is registered in the franchise store table 106b.

[0058] In the example shown in the figure, the header section contains the slip number "Y0000000001," the sender "FC001: FC Shibuya Store," the transaction date "2022 / 6 / 30," and the destination "Choku01: Directly Managed Shinjuku Store." In the details area, the first line contains the sales category "Sales," the product "Shouhin01: Luxury Watch," the sales quantity "1," and the sales amount "400,000." The second line contains the sales category "Sales," the product "Shouhin02: Brand Bag A," the sales quantity "1," and the sales amount "150,000." When the registration button (not shown) is pressed, the expected sales data shown in Figure 5(B) is registered.

[0059] Figure 5(B) is a diagram showing an example of part of the forecast sales data. In the example shown in the figure, the first line contains the customer (shipping destination) "Choku01: Directly Managed Shinjuku Store," the forecast sales number "U10000001," the product "luxury watch," the sales quantity "1," the sales amount "400,000," and the sold flag "0." The forecast sales number is assigned at the time of registration. Note that Figure 5(B) omits data such as the sender (franchise store), invoice number, and transaction date, but these data are also registered as forecast sales data.

[0060] (S2: Sales and purchase input processing) A specific example of the sales and purchase input process will be described with reference to Figure 6. In response to access from the directly managed store terminal 500, the sales and purchase input unit 102b provides a sales and purchase input screen, and in response to input operations on the sales and purchase input screen from the directly managed store terminal 500, references the projected sales data stored in the franchise store table 106b using the slip number as a key, inputs purchase data including the purchase number, product, and sales amount, and stores the data in the franchise store table 106c. The sales and purchase input unit 102b also updates the sold flag of the referenced projected sales data to "1," and further generates sales data including the sales number, product, and sales amount based on the projected sales data, and stores the data in the franchise store table 106b.

[0061] 6 is a diagram showing an example of the sales and purchase input screen. The sales and purchase input screen has a header area for specifying the slip number, transaction date, sender (FC store), and destination (direct store), a details area for specifying the purchase category, product name, purchase quantity, purchase amount, etc., and a registration button (not shown).

[0062] On the sales and purchase input screen, when the slip number in the header area is specified, the slip number is used as a key to read and display the sales forecast data from the franchise store table 106b. The operator can edit and modify the displayed data.

[0063] When the registration button is pressed, purchase data corresponding to the input contents on the sales purchase input screen is registered in the directly managed store table 106c.

[0064] In the example shown in Figure 6(A), the slip number "Y0000000001" is specified, and using the slip number "Y0000000001" as a key, the projected sales data shown in Figure 5(B) from the franchise store table 106b is read and displayed.

[0065] FIG. 6(B) shows an example of purchase data to be registered. The first line contains the supplier "FC001: FC Shibuya Store," purchase number "S10000001," product "luxury watch," and purchase amount "400,000." When the purchase data is registered, the sales flag in the sales forecast data is updated to "1: Sold," as shown in FIG. 6(D). Furthermore, sales data such as that shown in FIG. 6(C) is generated based on the sales forecast data and stored in the franchise store table 106b. In the example sales data shown in FIG. 6(C), the first line contains the customer (shipping destination) "Choku01: Directly Managed Shinjuku Store," sales number "E10000001," product "luxury watch," and sales amount "400,000." While data such as the sender (franchise store) and transaction date (sales date) are omitted from FIG. 6(C), these data are also registered as sales data.

[0066] (Purchases from general customers of franchise stores) A case where a franchise store purchases from a general customer will be described with reference to Figure 7. When a franchise store purchases from a general customer, the control unit 102 provides a purchase input screen in response to access from the franchise store terminal 400, and inputs purchase data including the purchase number, product, and purchase amount in response to input operations on the purchase input screen by the franchise store terminal 400, and stores the data in the franchise store table 106b.

[0067] FIG. 7(A) is a diagram showing an example of the purchase input screen. The purchase input screen has a header area for specifying the transaction date, franchise store, customer, etc., a details area for specifying the purchase category, product, purchase quantity, purchase amount, etc., and a register button (not shown). When data is entered in the header area and details area and the register button (not shown) is pressed, purchase data corresponding to the input on the screen is created and registered in the franchise store table 106b. FIG. 7(B) is a diagram showing an example of the purchase data to be registered. Note that data such as franchise store and transaction date are omitted in FIG. 7(B), but this data is also registered as purchase data.

[0068] (S3: Royalty calculation process) A specific example of royalty calculation processing will be described with reference to Figures 8 to 10. For example, the royalty calculation unit 102c extracts sales data and purchase data from the franchise store table 106b for the target year and month and franchise store specified by an operator's operation on the royalty calculation screen displayed on the monitor 114, and calculates royalties based on the extracted sales data and purchase data by referring to the royalty setting master 106a.

[0069] FIG. 8 is a diagram showing an example of the royalty calculation screen. The royalty calculation screen displays the target year and month, a target flag for specifying the target franchise store from a list of franchise stores, and an execute button (not shown). When the operator checks the target flag for the target year and month and the target franchise store and presses the execute button, sales data and purchase data for the target year and month and the target franchise store are extracted from franchise store table 106b and royalties are calculated. In the example shown in the figure, the target year and month "2022 / 6" and franchise store "FC001: FC Shibuya Store" have been selected. The following describes the case where royalty calculation is performed for franchise store "FC001: Shibuya Store" for the target year and month "2022 / 6."

[0070] A specific example of royalty calculation will be described with reference to Figures 9 and 10. Figure 9 shows sales data and purchase data for the franchise store "FC001: Shibuya Store" and example data in the royalty setting master 106a. The royalty setting master 106a has fields for the franchise store (franchise store code and / or franchise store name), transaction type (e.g., sale, purchase), product category, upper limit, lower limit, and royalty rate. The "transaction type" is purchase or sale. "Purchase" is the business in which a franchise store purchases products from a general customer. "Sales" is the business that occurs when a franchise store sells to a general customer or a directly managed store. The "upper limit" is the maximum amount for which royalties are generated, and no royalties are collected if the transaction amount exceeds the upper limit. The "lower limit" is the minimum amount for which royalties are generated, and no royalties are collected if the transaction amount is below the lower limit.

[0071] In the example shown in the figure, the first line contains the franchise store "FC001: FC Shibuya Store," the transaction type "sales," the product category "watches," the upper limit amount "300,000," the lower limit amount "50,000," and the royalty rate "2.7."

[0072] The second line shows the franchise store "FC001: FC Shibuya store", transaction type "sales", product category "bags", upper limit amount "500,000", lower limit amount "200,000", and royalty rate "3.2".

[0073] The third line shows the franchise store "FC001: FC Shibuya store", transaction type "sales", product category "bags", upper limit amount "1,000,000", lower limit amount "200,000", and royalty rate "5.0".

[0074] FIG. 10 shows an example of royalty calculation when using sales data and purchase data of the franchise store "FC001: Shibuya store" and the royalty setting master 106a.

[0075] In Figure 10(1), we will explain the case where the amount exceeds the upper limit. The first line of the sales data for franchise store "FC001: FC Shibuya Store" in Figure 9 lists the product "luxury watches" and the sales amount as "400,000." Using the franchise store "FC001: FC Shibuya Store," transaction type "sales" (since this is sales data, the transaction type is "sales"), and product category "watches" (the product category of luxury watches is "watches") as keys, the upper limit amount of "300,000," the lower limit amount of "50,000," and the royalty rate of "2.7" are obtained from the royalty setting master 106a (first line). Of the sales amount of "400,000," only the upper limit amount of "300,000" is eligible for royalties, and the amount of "100,000," which exceeds the upper limit amount of "300,000," is not eligible for royalties. The royalty amount is calculated as follows: royalty amount "30,000" out of sales amount "400,000" x royalty rate "2.7%" = 8,100.

[0076] In Figure 10 (2), we will explain the case where the amount falls below the minimum amount. The second line of the sales data for the franchise store "FC001: FC Shibuya Store" in Figure 9 lists the product "Brand Bag A" and the sales amount as "150,000." Using the franchise store "FC001: FC Shibuya Store," transaction type "sales," and product category "bag" (the product category of Brand Bag A is "bag") as keys, the upper limit amount of "500,000," the lower limit amount of "20,000," and the royalty rate of "3.2" are retrieved from the royalty setting master 106a (second line). The sales amount of "150,000" is below the lower limit amount of "200,000," so it is not eligible for royalties. Therefore, the royalty amount is calculated as follows: sales amount "150,000" x royalty rate "none" = 0.

[0077] In Figure 10 (3), we will explain the case where the amount falls between the upper and lower limits. The first line of the purchase data for franchise store "FC001: FC Shibuya Store" in Figure 9 lists the product "Brand Bag A" and the sales amount as "900,000." Using the franchise store "FC001: FC Shibuya Store," transaction type "Purchase" (since this is purchase data, the transaction type is "Purchase"), and product category "Bag" as keys, the upper limit amount of "1,000,000," the lower limit amount of "20,000," and the royalty rate of "5.0" are retrieved from the royalty setting master 106a (third line). The purchase amount of "900,000" is between the upper limit amount of "1,000,000" and the upper limit amount of "200,000," so it is eligible for royalties. The royalty amount is purchase amount "900,000" x royalty rate "5.0%" = 45,000.

[0078] (S4: Billing data creation process) A specific example of the billing data creation process will be described with reference to Figures 11 and 12. The billing data creation unit 102d creates billing data for franchised stores of directly managed stores based on the royalty calculation results, stores the data in the directly managed store table 106c, and issues an invoice based on the billing data.

[0079] 11(A) is a diagram showing an example of royalty calculation results (sales data). The first line shows customer "FC001", sales number "E10000011", product "royalty", and sales amount "8,100", and the second line shows customer "FC001", sales number "E10000012", product "royalty", and sales amount "45,000".

[0080] 11B shows an example of billing data. The first line contains the customer "FC001," the billing number "SEQ10001," and the billing amount "53,100 (=8,100 + 45,000)."

[0081] Figure 12 is a diagram showing an example of an invoice. The example invoice shown in Figure 12 includes a header section with the customer (FC store) and billing source (headquarters), the billing amount, and billing details (date, product, amount).

[0082] As described above, according to this embodiment, there is provided a registered royalty setting master 106a that associates product classifications with royalty rates, a sales forecast input unit 102a that, when a franchise store sells a product to a directly managed store, inputs sales forecast data including the sales forecast number, product, sales amount, and a sold flag set to "unsold" in response to operations on the sales forecast input screen on the franchise store side, and stores the input data in the franchise store table 106b, and a sales data input unit 102b that, in response to operations on the sales purchase input screen on the directly managed store side, refers to the sales forecast data, inputs purchase data including the purchase number, product, and sales amount, and stores the input data in the directly managed store table 106c. The system is equipped with a sales and purchase input unit 102b that updates the sold flag of the sales forecast data to "sold" and creates sales data including the sales number, product, and sales amount and stores it in the franchise store table 106b, a royalty calculation unit 102c that calculates royalties based on the sales data by referring to the royalty setting master 106a, and a billing data creation unit 102d that creates billing data for franchise stores based on the royalty calculation results, so that when a sales transaction occurs between a franchise store and a directly managed store, it is possible to reduce the burden and errors in the work of billing royalties to franchise stores.

[0083] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of SDGs Goals 8 and 9.

[0084] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0085] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.

[0086] 5. Other Embodiments The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0087] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0088] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings can be changed as desired unless otherwise specified.

[0089] Furthermore, with regard to the buying and selling transaction system 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0090] For example, all or any part of the processing functions of the trading system 100, particularly the processing functions performed by the control unit 102, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing an information processing device to execute the processes described in this embodiment, and is mechanically read by the trading system 100 as needed. That is, a computer program for providing instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). The computer program is executed by being loaded into RAM, and constitutes the control unit 102 in cooperation with the CPU.

[0091] This computer program may also be stored in an application program server connected to the trading system 100 via any network, and all or part of it may be downloaded as needed.

[0092] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) disc.

[0093] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single program, but also includes programs that are distributed as multiple modules or libraries, or programs that achieve their functions by cooperating with other programs, such as an OS. Note that the specific configurations and reading procedures for reading a recording medium in each device shown in the embodiments, as well as the installation procedures after reading, can use well-known configurations and procedures.

[0094] The various databases stored in the memory unit 106 are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

[0095] The trading system 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The trading system 100 may be realized by installing software (including programs or data) that causes the information processing device to perform the processing described in this embodiment.

[0096] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or function additions. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Explanation of symbols]

[0097] 100 Trading System 102 Control section 102a Sales forecast input section 102b Sales and Purchase Input Department 102c Royalty Calculation Department 102d Billing Data Creation Department 102e Unaccounted Purchases Confirmation Department 102f Master Maintenance Department 102g Screen display control unit 104 Communication interface unit 106 Storage section 106a Royalty Setting Master 106b FC store table 106c Direct Store Table 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network 400 FC store terminal 500 Direct store terminals

Claims

1. A buying and selling transaction system including a control unit, which calculates royalties when a franchise store sells a product to a directly managed store, The control unit It is configured to be able to access royalty setting master that associates product classification with royalty rate and registers it. a sales forecast input means for inputting sales forecast data including a sales forecast number, product, sales amount, and a sales flag indicating "unsold" in response to operations on the sales forecast input screen by the franchise store when the franchise store sells products to directly managed stores, and storing the data in a storage area; a sales and purchase input means for inputting purchase data including purchase numbers, products, and sales amounts, referring to the sales forecast data, in response to operations on the sales and purchase input screen by the directly managed store, and storing the input data in the storage area, updating the sold flag of the sales forecast data to "sold", and creating sales data including sales numbers, products, and sales amounts, and storing the sales data in the storage area; royalty calculation means for calculating royalties based on the sales data and by referring to the royalty setting master; a billing data creation means for creating billing data for franchised stores based on the royalty calculation results; A buying and selling transaction system comprising:

2. In the royalty setting master, an upper limit amount specifying an upper limit of royalty generation and a lower limit amount specifying a lower limit of royalty generation are further registered in association with each other, 2. The buying and selling transaction system according to claim 1, wherein any portion of the sales amount that exceeds the upper limit amount is not subject to royalties, and any portion of the sales amount that is below the lower limit amount is not subject to royalties.

3. 3. The buying and selling transaction system according to claim 1, wherein the royalty setting master is set for each franchise store.

4. The control unit further The buying and selling transaction system according to claim 1, further comprising an unrecorded purchase confirmation means for contacting a directly managed store when there is a product that is planned to be purchased at the directly managed store but has not been recorded as purchased, by referring to the sales forecast data of franchise stores and the purchase data of directly managed stores stored in the memory area.

5. A buying and selling transaction method executed by an information processing device having a control unit, The control unit It is configured to be able to access royalty setting master that associates product classification with royalty rate and registers it. Executed in the control unit: a sales forecast input step of inputting sales forecast data including a sales forecast number, product, sales amount, and a sales flag indicating "unsold" in response to operations on the sales forecast input screen by the franchise store when the franchise store sells a product to a directly managed store, and storing the input data in a storage area; a sales and purchase input process for inputting purchase data including purchase numbers, items, and sales amounts with reference to the sales forecast data in response to operations by the directly managed store on the sales and purchase input screen, storing the input data in the storage area, updating the sold flag of the sales forecast data to "sold," and creating sales data including sales numbers, items, and sales amounts, and storing the sales data in the storage area; a royalty calculation step of calculating royalties by referring to the royalty setting master based on the sales data; a billing data creation step of creating billing data for the franchised store based on the royalty calculation result; A buying and selling transaction method comprising:

6. A trading program to be executed by an information processing device having a control unit, The control unit It is configured to be able to access royalty setting master that associates product classification with royalty rate and registers it. In the control unit, a sales forecast input step of inputting sales forecast data including a sales forecast number, product, sales amount, and a sales flag indicating "unsold" in response to operations on the sales forecast input screen by the franchise store when the franchise store sells a product to a directly managed store, and storing the input data in a storage area; a sales and purchase input process for inputting purchase data including purchase numbers, items, and sales amounts with reference to the sales forecast data in response to operations by the directly managed store on the sales and purchase input screen, storing the input data in the storage area, updating the sold flag of the sales forecast data to "sold," and creating sales data including sales numbers, items, and sales amounts, and storing the sales data in the storage area; a royalty calculation step of calculating royalties by referring to the royalty setting master based on the sales data; a billing data creation step of creating billing data for the franchised store based on the royalty calculation result; A trading program for executing the above.

Images