JP2019101827A - Multi-store management system, multi-store management device, multi-store management method, and program - Google Patents

Abstract

To provide a multi-store management system, a multi-store management device, a multi-store management method, and a program, capable of efficiently executing merchandise control, stock control, customer management, order reception management and the like across a plurality of stores.SOLUTION: A multi-store management system 10 comprises a plurality of malls 200 and a multi-store management device 100. The multi-store management device 100 includes: an information update unit 117, 127, 137, 147, or 157 which acquires at least one information of merchandise information, customer information, order reception information, payment information, or delivery information from a mall 200; an information conversion unit 115, 125, 135, 145, or 155 which converts the information acquired from the mall 200 according to prescribed conversion rules; and an information storage unit 111, 121, 131, 141, or 151 which stores the converted information.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a multi-store management system, a multi-store management apparatus, a multi-store management method, and a program, and more particularly to technology for efficiently performing product management, inventory management, customer management, order management and the like across multiple stores.

  In recent years, goods and services have come to be sold at stores established on computer networks such as the Internet (hereinafter referred to as "net shops"). The net shop, for example, participates as a shopkeeper in an EC (Electronic Commerce) platform provided by the mall operator, or builds a unique site using an EC framework supplied by a software vendor, or an exhibitor at an auction site. It can be realized in various forms such as participating as These platforms, frameworks, sites, etc. (hereinafter simply referred to as malls) generally provide functions for performing product management, order management, order management, deposit management, delivery management, customer management, etc. It is However, the specifications of those functions differ from one mall to another. Therefore, in the past, a business that sells in a plurality of malls needs to perform processing such as exhibition and order acceptance in a different method for each mall even if the same product is sold in a plurality of malls. there were. This is a very cumbersome task and has been a factor in increasing the cost of running multiple net shops.

  In this regard, Patent Document 1 discloses a system for selling products in a plurality of malls and processing order information generated in the plurality of malls. Specifically, the mall serving as an intermediary converts the product data it owns into a format that can be accepted by other malls, and transmits it to the other malls. In addition, the mall serving as the intermediary acquires order data held by other malls, converts the order data into a format acceptable to the processor for processing order data, and transfers the converted data to the processor for processing order data.

Patent No. 4225085

  However, in the system described in Patent Document 1, the product information is always synchronized in one direction from the intermediary mall to the other mall. Therefore, for example, the operation of registering a product already registered in another mall also in the mall of the intermediary role can not be performed, so the convenience is limited.

  Further, in the system described in Patent Document 1, processing such as delivery of products ordered from a plurality of malls is centrally performed at one site. However, nowadays, more complex delivery conditions are often applied, such as stocking products in a plurality of warehouses (including warehouses operated by the mall) and shipping from an optimal warehouse according to the content of the order received. . The system described in Patent Document 1 can not cope with such complicated delivery conditions.

  Further, in the system described in Patent Document 1, it is difficult to manage the purchase history and the like of the customer across a plurality of malls. The online shop may carry out sales promotion etc. simultaneously in a plurality of malls. For example, there are cases where the number of points purchased per customer is capped, or preferential treatment is given according to the customer's royalty, but the system described in Patent Document 1 has a function to sufficiently support such behavior on the store side. Not provided

  The present invention has been made to solve such problems, and is a multi-store management system capable of streamlining product management, inventory management, customer management, order management, etc. across multiple stores, multi-store management apparatus , And aims to provide a multi-store management method and program.

The multi-store management system according to the present invention is a multi-store management system including a plurality of malls and a multi-store management apparatus, wherein the multi-store management apparatus is configured to store merchandise information, customer information, order information from the mall. An information update unit for acquiring at least one of payment information and delivery information, an information conversion unit for converting the information acquired from the mall according to a predetermined conversion rule, and the information after conversion is stored. And an information storage unit.
In another multi-store management system according to the present invention, the information updating unit detects a change in the information in the mall and acquires the information from the mall.
In another multi-store management system according to the present invention, the information updating unit further acquires the information from the information storage unit, and the information conversion unit further determines the information acquired from the information storage unit. Converting according to the conversion rule, and the converted information is sent to the mall.
In another multi-store management system according to the present invention, the information updating unit detects a change in the information in the information storage unit, and acquires the information from the information storage unit.
In another multi-store management system according to the present invention, the information storage unit holds the product information including information on the locations of one or more warehouses in which the products are stocked.
In another multi-store management system according to the present invention, the information storage unit holds the customer information including information on the location of the customer who has ordered a product, and the location of the customer and the location of the warehouse The method further comprises an inventory allocation unit that selects the warehouse to which the goods related to the order are to be deposited based on a relationship.
In another multi-store management system according to the present invention, the information storage unit integrates and manages the customer information on the same customer using a plurality of the malls.
The multi-store management system according to claim 1.
The multi-store management apparatus according to the present invention includes an information updating unit that acquires at least one of product information, customer information, order information, payment information, and delivery information from a plurality of malls; The information processing apparatus may include an information conversion unit that converts the information according to a predetermined conversion rule, and an information storage unit that stores the converted information.
In the multi-store management method according to the present invention, the information update unit acquires at least one of product information, customer information, order information, payment information, and delivery information from a plurality of malls, and an information conversion unit. And converting the information acquired from the mall according to a predetermined conversion rule, and storing the information after conversion by the information storage unit.
A program according to the present invention is a program for causing a computer to execute the multi-store management method.

  According to the present invention, it is possible to provide a multi-store management system, a multi-store management apparatus, a multi-store management method, and a program that can streamline product management, inventory management, customer management, order management and the like across multiple stores.

FIG. 2 is a block diagram showing a configuration example of a multi-store management system 10. It is a figure which shows an example of the goods information storage part 111. As shown in FIG. It is a figure which shows an example of the goods information input part 113. As shown in FIG. It is a figure which shows an example of the customer information storage part 121. As shown in FIG. FIG. 6 is a diagram showing an example of a customer information input unit 123. 5 is a diagram illustrating an example of an order information storage unit 131. FIG. FIG. 6 is a diagram showing an example of an order information input unit 133. It is a figure which shows an example of the payment information storage part 141. As shown in FIG. It is a figure which shows an example of the payment information input part 143. As shown in FIG. FIG. 6 is a diagram showing an example of a delivery information storage unit 151. It is a figure which shows an example of the delivery information input part 153. As shown in FIG. It is a flowchart which shows the expansion process example of goods information. It is a flowchart which shows the optimization process example of a delivery origin warehouse. It is a flowchart which shows the example of a customer's centralized management process. It is a flowchart which shows the example of an update process of order information.

  Hereinafter, specific embodiments to which the present invention is applied will be described in detail with reference to the drawings. First, the configuration of the multi-store management system 10 according to the embodiment of the present invention will be described using FIG. 1.

  The multi-store management system 10 includes a multi-store management apparatus 100, a plurality of malls 200, and a financial institution 300 as needed. The multi-store management apparatus 100, the mall 200, and the financial institution 300 are communicably connected via the network 400. The multi-store management apparatus 100, the mall 200, and the financial institution 300 are typically computers each having a central processing unit (CPU), a storage device, an input / output device and the like, and the CPU reads a program stored in the storage device. The predetermined function is realized by executing the The multi-store management apparatus 100, the mall 200, and the financial institution 300 need not necessarily be a single computer, and may be configured by a plurality of computers. For example, each processing unit of the multi-store management apparatus 100 and the mall 200 may realize its function in a distributed information processing environment.

  Each of the plurality of malls 200 sells products and the like of the online shop. Each mall 200 has a product DB 210, a customer DB 220, and an order DB 230. In addition, the mall 200 having the settlement function may have the deposit DB 240. The mall 200 having a shipping function may have a delivery DB 250.

  The mall 200 stores product information and stock information (hereinafter, product information and the like) of products sold in the mall 200 in the product DB 210. The product DB 210 stores, as product information, an ID of the product, a name, a photograph, a price, an explanation, attribute information (for example, a category of the product), and the like. Further, as stock information, the number of stocked products in the mall 200 is stored for each product ID. The names, locations, etc. of one or more warehouses where stock of each product is stored may be further stored as stock information.

  The mall 200 stores customer information and history information (hereinafter, customer information and the like) of a customer in the mall 200 in the customer DB 220. The customer DB 220 stores customer ID, name, address, contact address (for example, telephone number or e-mail address) as customer information. Further, as the history information, the customer purchase history, the request / complaint correspondence history, etc. are stored for each customer ID.

  The mall 200 stores the contents of the order received at the mall 200 in the order DB 230. The order reception DB 230 stores, as order reception information, an order reception ID, an order reception date and time, a product ID of an order reception product, the number of orders received, a customer ID of the orderer, and the like.

  The mall 200 stores, in the deposit DB 240, the status of deposit corresponding to the received order. The deposit DB 240 stores an order ID, a deposit amount, a deposit date and the like.

  The mall 200 stores the delivery status of the product in the delivery DB 250. The delivery DB 250 stores an order ID, a shipping date, and the like.

  The multi-store management device 100 is a device that performs cross-sectional information management for a plurality of malls 200. The multi-store management apparatus 100 includes a product management unit 110, a customer management unit 120, an order management unit 130, a deposit management unit 140, and a delivery management unit 150.

  The product management unit 110 manages sales products. The product management unit 110 includes a product information storage unit 111, a product information input unit 113, a product information conversion unit 115, and a product information update unit 117.

  The product information storage unit 111 is a database that centrally manages product information and inventory information of products that the online shop handles in a plurality of malls 200. An example of the product information storage unit 111 is shown in FIG. The product information storage unit 111 stores, for example, an ID of a product, a name, a photo, a price, an explanation, attribute information (for example, a category of the product), and the like as product information. Further, as stock information, the stock number, the distribution ratio of stock to the plurality of malls 200, the name of the warehouse where the stock is stored, the warehouse location, and the like are stored for each product ID. Here, the distribution ratio of stock is a numerical value indicating how much the stock number is allocated to each mall 200.

  In addition, when inventory is stored in a plurality of warehouses, a plurality of inventory information can be associated with one product ID. For example, as shown in FIG. 2, multiple records of inventory information including the same product ID may be created.

  The product information input unit 113 provides a function for registering product information and stock information (hereinafter, product information and the like) in the product information storage unit 111, and editing and searching product information and the like. The product information input unit 113 can receive registration or editing of product information and the like via a user interface as shown in FIG. 3. Alternatively, registration or editing may be performed by reading an external file or the like in which product information and the like are described and recording the described content in the product information storage unit 111.

  The product information conversion unit 115 converts the product information and the like stored in the product information storage unit 111 into a format that each mall 200 can handle, or converts the product information and the like stored in the product DB 210 of each mall 200 into a format that the product information storage unit 111 can handle. Convert to This is because the product information storage unit 111 and the product DB 210 have different types, sizes, names, and the like of data to be held. The product information conversion unit 115 eliminates the difference between the product information and the like by converting the product information and the like according to a predetermined conversion rule.

  When the distribution ratio of stock to each mall 200 is set in the product information storage unit 111, the number obtained by multiplying the distribution number of each mall 200 by the number of stocks is set as the number of stocks in the product DB 210 of each mall 200. Do.

  The product information updating unit 117 performs processing to synchronize part or all of the product information and the like in one direction or in both directions between the product information storage unit 111 and the product DB 210 of the mall 200. For example, the product information update unit 117 detects a change (typically, new registration, update, or deletion of product information, etc.) of product information and the like in one of the product information storage unit 111 or the product DB 210, and synchronizes with the other. Start processing Alternatively, the synchronization process may be triggered by an arbitrary event such as a user request.

  When the synchronization process is started, the product information update unit 117 reads out the product information etc. held by the synchronization source (the product information storage unit 111 or the product DB 210), and the product information conversion unit 115 has a format that the synchronization destination can handle. Convert. Various interfaces prepared by the mall 200 can be used to acquire product information and the like when the synchronization source is the product DB 210 and to transmit product information and the like when the synchronization destination is the product DB 210. For example, the product information update unit 117 calls a login API (Application Programming Interface) of the mall 200 and performs login authentication using an ID or the like previously given from the mall 200. After logging in, the product information etc. is acquired or updated using the product information etc. acquisition API for product DB 210 or the update API. It should be noted that for the mall 200 that does not have the API, other known techniques such as scraping are used, and even if login or acquisition of product information or the like is performed using the user interface provided by the mall 200. good.

  As a result, the multi-store management apparatus 100 can serve as a hub and expand the product information and the like of the product handled in one mall 200 to other malls 200.

  The customer management unit 120 manages customer information and purchase history. The customer management unit 120 includes a customer information storage unit 121, a customer information input unit 123, a customer information conversion unit 125, a customer information update unit 127, and a customer information integration unit 129.

  The customer information storage unit 121 is a database for storing customer information of the net shop. An example of the customer information storage unit 121 is shown in FIG. The customer information storage unit 121 stores a customer ID, a name, an address, a contact address (for example, a telephone number or an e-mail address) as the customer information. In addition, as the history information, the customer purchase history, the request / complaint correspondence history, the customer rank and the like are stored for each customer ID. The customer rank can be calculated and set by the customer information storage unit 121 using various known methods. For example, the customer rank can be calculated based on the cumulative number of purchases by the customer, the cumulative amount, and the like. Alternatively, any customer rank may be set by the user.

  The customer information input unit 123 provides functions for registering customer information and history information (hereinafter, customer information and the like) in the customer information storage unit 121 and editing and searching for product information and the like. The customer information input unit 123 can receive registration or editing of customer information and the like via a user interface as shown in FIG. Alternatively, registration or editing may be performed by reading an external file or the like in which customer information or the like is written and recording the written content in the customer information storage unit 121.

The customer information conversion unit 125 converts the customer information and the like stored in the customer information storage unit 121 into a format that each mall 200 can handle, or the format in which the customer information storage unit 121 can handle customer information and the like that the customer DB 220 of each mall 200 holds. Convert to This is because the customer information storage unit 121 and the customer DB 220 have different types, sizes, names, etc. of data to be held. The customer information conversion unit 125 eliminates these differences by converting the customer information and the like according to a predetermined conversion rule.
In the present embodiment, since the customer rank is data held only by the multi-store management apparatus 100, there is no need to perform conversion and synchronization.

  The customer information update unit 127 performs processing to synchronize part or all of the customer information and the like in one direction or in both directions between the customer information storage unit 121 and the customer DB 220 of the mall 200. For example, the customer information updating unit 127 detects a change in customer information etc. (typically, new registration, update, deletion etc. of customer information etc.) in one of the customer information storage unit 121 or the customer DB 220, and synchronizes with the other. Start processing Alternatively, the synchronization process may be triggered by an arbitrary event such as a user request.

  When the synchronization process is started, the customer information update unit 127 reads out the customer information etc. held by the synchronization source (the customer information storage unit 121 or the customer DB 220), and the customer information conversion unit 125 has a format that the synchronization destination can handle. Convert. Various interfaces prepared by the mall 200 can be used to acquire customer information and the like when the synchronization source is the customer DB 220 and to transmit customer information and the like when the synchronization destination is the customer DB 220. For example, the product information update unit 117 calls the login API of the mall 200, and performs login authentication using an ID or the like previously given from the mall 200. After login, the customer information etc. is acquired or updated using the customer information etc. acquisition API for the customer DB 220 or the update API. It should be noted that for the mall 200 not equipped with the API, other known techniques such as scraping are used, and acquisition or update of customer information etc. is carried out using the user interface provided by the mall 200. good.

  The customer information integration unit 129 performs a process of integrating a plurality of customer information and the like (records) included in the customer information storage unit 121 into one customer information and the like (record). For example, when a plurality of customer information and the like are designated by the customer ID, the customer information integration unit 129 sets one of the customer information and the like (hereinafter, integration destination information) and the other customer information and the like (hereinafter, integration source information) Add the contents of and delete the integration source information. In the integration destination information, the customer ID of the integration destination information is used. If the name, address, contact information, etc. differ between the integration destination information and the integration source information, only one of them can be left in the integration destination information according to a predetermined rule.

  As a result, customer information and the like of customers scattered in a plurality of malls 200 can be centrally managed in the multi-store management apparatus 100.

  The order management unit 130 manages orders, allocates stock, and the like. The order management unit 130 includes an order information storage unit 131, an order information input unit 133, an order information conversion unit 135, an order information update unit 137, and a stock allocation unit 139.

  The received order information storage unit 131 is a database for storing received order information of the net shop. An example of the order information storage unit 131 is shown in FIG. The order information storage unit 131 stores, as order information, an order ID, an order mall name, an order date and time, a product ID of an order item, the number of orders received, a customer ID of an orderer, and the like. Further, as provision information, the number of provisions and the warehouse name are stored for each order ID.

  The received order information input unit 133 provides functions for registering received order information in the received order information storage unit 131 and editing and searching for the received order information. The received order information input unit 133 can receive registration or editing of the received order information via the user interface as shown in FIG. Alternatively, registration or editing may be performed by reading an external file or the like in which order information is described and recording the described content in the order information input unit 133.

  The order information conversion unit 135 converts the order information stored in the order information storage unit 131 into a format that each mall 200 can handle, or converts the order information held by the order DB 230 of each mall 200 into a format that the order information conversion unit 135 can handle. Do. This is because the type, size, name, and the like of data to be held are different between the order information conversion unit 135 and the order reception DB 230. The order information conversion unit 135 eliminates these differences by converting the order information according to a predetermined conversion rule.

  The received order information updating unit 137 performs processing to synchronize part or all of the received order information in one direction or in both directions between the received order information storage unit 131 and the received order DB 230 of the mall 200. For example, the order information update unit 137 detects a change in order information in one of the order information storage unit 131 or the order DB 230 (typically, new registration, update, deletion of order information, etc.), and synchronization processing to the other is performed. Start. Alternatively, the synchronization process may be triggered by an arbitrary event such as a user request.

  When synchronization processing is started, the received order information update unit 137 reads out the received order information held by the synchronization source (the received order information storage unit 131 or the received order DB 230), and converts it into a format that can be handled by the synchronization destination by the received order information conversion unit 135. Do. Various interfaces prepared by the mall 200 can be used to acquire order information when the synchronization source is the order reception DB 230 and to transmit order information when the synchronization destination is the order reception DB 230. For example, the order information update unit 137 calls the login API of the mall 200, and performs login authentication using an ID or the like previously given from the mall 200. After login, the order information is acquired or updated using the order information acquisition API of the order DB 230 or the update API. Note that for the mall 200 that does not include the API, other known techniques such as scraping may be used, and acquisition or update of login and order information may be performed using a user interface provided by the mall 200. .

  The stock allocation unit 139 performs a process of allocating a product inventory when the order information in the order information storage unit 131 changes (newly registered, updated or deleted). The stock allocation unit 139 searches for stock information in the product information storage unit 111 using the product ID of the registered or updated order information as a key. If the number of stocks in the corresponding stock information is equal to or greater than the number of orders received in the order information, the number of orders is subtracted from the number in stock, and the number of orders is recorded in the number of provisions in the provision information. Further, the warehouse name included in the stock information is recorded in the warehouse name of the allocation information.

  When the distribution ratio is set in the stock information, the stock allocation unit 139 reads the above-mentioned number of stocks as a number obtained by multiplying the number of stocks by the distribution ratio of the order information to the mall name, and performs the same processing. On the other hand, if the number of stocks in the stock information is less than the number of orders received in the order information, an error is output. When the order information is deleted, the stock allocation unit 139 adds the number of orders received to the number of stocks and deletes the related allocation information.

  If a plurality of pieces of stock information exist, that is, if there are stocks in a plurality of warehouses, the stock allocation unit 139 can allocate goods from the warehouse closest to the orderer. The stock allocation unit 139 acquires the address of the customer from the customer information storage unit 121 using the customer ID of the order information as a key. A plurality of pieces of inventory information are acquired from the product information storage unit 111 using the product ID of the order information as a key. The stock allocation unit 139 compares the distances of the customer's address and the locations of the warehouses included in the plurality of inventory information with each other using known technology, and specifies the inventory information on the warehouse closest to the customer's address. . The stock allocation unit 139 executes the above-described allocation processing based on the identified stock information. If the number of stocks included in the specified stock information is insufficient for the number of orders received, then the allocation process may be performed from the warehouse closest to the customer's address. Alternatively, an error may simply be output.

  In addition, the stock allocation unit 139 may register history information in the customer information storage unit 121. The history information can include any item included in the order information in addition to the customer ID.

  As a result, the multi-store management apparatus 100 can be used as a hub to reflect inventory fluctuations due to an order received at one mall 200, and can be reflected in other malls 200 as well.

  The payment management unit 140 manages payment for the received order. The deposit management unit 140 includes a deposit information storage unit 141, a deposit information input unit 143, a deposit information conversion unit 145, a deposit information update unit 147, and a clear unit 149.

  The deposit information storage unit 141 is a database that centrally manages deposit information corresponding to the order information. An example of the payment information storage unit 141 is shown in FIG. The deposit information storage unit 141 stores, for example, an order ID, a deposit amount, a deposit date, etc., as deposit information.

  The clearing unit 149 acquires the deposit history from the financial institution 300, collates the deposit history and the order information, and records the result of the association in the deposit information storage unit 141. When the mall 200 has a payment function, the payment history may be acquired from the mall 200. The clearing unit 149 typically includes the deposit amount and depositor included in the acquired deposit history, the name associated with the order receipt amount calculated from the item ID of the order entry information and the number of orders received, If they match, the received order ID, deposit amount, and deposit date and time are registered in the deposit information storage unit 141 as deposit information.

  The deposit information input unit 143 provides functions for manually registering the deposit information in the deposit information storage unit 141 and editing and searching the deposit information. The deposit information input unit 143 can receive registration or editing of the deposit information through the user interface as shown in FIG. Alternatively, the registration or editing may be performed by reading an external file or the like in which the payment information is described and recording the described content in the payment information storage unit 141.

  The deposit information conversion unit 145 converts the deposit information stored in the deposit information storage unit 141 into a format that each mall 200 can handle, and converts the deposit information stored in the deposit DB 240 of each mall 200 into a format that the deposit information storage unit 141 can handle. . This is because the type, size, name, and the like of the data to be held are different between the payment information storage unit 141 and the payment DB 240. The deposit information conversion unit 145 eliminates these differences by converting deposit information according to a predetermined conversion rule.

  The payment information updating unit 147 performs processing to synchronize part or all of the payment information in one direction or in both directions between the payment information storage unit 141 and the deposit DB 240 of the mall 200. For example, the payment information updating unit 147 detects a change in payment information (typically, new registration, update, deletion of payment information, etc.) in one of the payment information storage unit 141 or the payment DB 240, and synchronizes the other. Start. Alternatively, the synchronization process may be triggered by an arbitrary event such as a user request.

  When the synchronization process is started, the payment information updating unit 147 reads out the payment information held by the synchronization source (the payment information storage unit 141 or the payment DB 240), and converts it into a format that can be handled by the synchronization destination by the payment information conversion unit 145. Do. Various interfaces prepared by the mall 200 can be used to acquire payment information when the synchronization source is the payment DB 240 and to transmit payment information when the synchronization destination is the payment DB 240. For example, the payment information update unit 147 calls the login API of the mall 200, and performs login authentication using an ID or the like previously given from the mall 200. After login, the deposit information is acquired or updated using the deposit information acquisition API or the update API of the deposit DB 240. Note that for the mall 200 that does not include the API, acquisition or update of login and payment information may be performed using a user interface provided by the mall 200 using other known techniques such as scraping. .

  As a result, it is possible to centrally manage payment management in a plurality of malls 200 in the multi-store management apparatus 100.

  The delivery management unit 150 manages delivery of goods, and the like. The delivery management unit 150 includes a delivery information storage unit 151, a delivery information input unit 153, a delivery information conversion unit 155, a delivery information update unit 157, and a shipping processing unit 159.

  The delivery information storage unit 151 is a database that centrally manages delivery information. An example of the delivery information storage unit 151 is shown in FIG. The delivery information storage unit 151 stores, for example, an order receipt ID, a shipping date, and the like as delivery information.

  The shipping processing unit 159 refers to the payment information storage unit 141, acquires the order reception ID in which the payment information is recorded, and records the received order ID in the delivery information storage unit 151 (when shipping is performed after payment). Alternatively, the shipping processing unit 159 refers to the received order information storage unit 131, acquires the received order ID in which the allocation information is recorded, and records the received order ID in the delivery information storage unit 151 (in the case of shipping without waiting for payment). Next, the shipping processing unit 159 outputs a shipping instruction for the received order ID recorded in the delivery information storage unit 151, and registers the shipping date and time. The aspect of the shipping instruction may be any known technique such as output of a shipping instruction slip, transmission of a shipping instruction message to a warehouse management system or a delivery company, and the like.

  The delivery information input unit 153 provides a function for manually registering delivery information in the delivery information storage unit 151 or editing and searching for delivery information. The delivery information input unit 153 can receive registration or editing of delivery information via a user interface as shown in FIG. Alternatively, the registration or editing may be performed by reading an external file or the like in which the delivery information is described and recording the described content in the delivery information storage unit 151.

  The delivery information conversion unit 155 converts the delivery information stored in the delivery information storage unit 151 into a format that each mall 200 can handle, or converts the delivery information held by the delivery DB 250 of each mall 200 into a format that the delivery information storage unit 151 can handle. Do. This is because the delivery information storage unit 151 and the delivery DB 250 have different types, sizes, names, and the like of data to be held. The delivery information conversion unit 155 eliminates these differences by converting the delivery information according to a predetermined conversion rule.

  The delivery information update unit 157 performs processing to synchronize part or all of the delivery information between the delivery information storage unit 151 and the delivery DB 250 of the mall 200 in one direction or in both directions. For example, the delivery information updating unit 157 detects a change in delivery information in one of the delivery information storage unit 151 or the delivery DB 250 (typically, new registration, update, deletion of delivery information, etc.), and synchronizes the other. Start. Alternatively, the synchronization process may be triggered by an arbitrary event such as a user request.

  When the synchronization process is started, the delivery information update unit 157 reads the delivery information held by the synchronization source (the delivery information storage unit 151 or the delivery DB 250), and converts the delivery information into a format that can be handled by the synchronization destination by the delivery information conversion unit 155. Do. For acquisition of delivery information when the synchronization source is the delivery DB 250 and transmission of delivery information when the synchronization destination is the delivery DB 250, various interfaces prepared by the mall 200 can be used. For example, the delivery information updating unit 157 calls the login API of the mall 200, and performs login authentication using an ID or the like previously given from the mall 200. After login, the delivery information is acquired or updated using the delivery information acquisition API or the update API of the delivery DB 250. Note that for the mall 200 that does not include the API, acquisition or update of login and delivery information may be performed using a user interface provided by the mall 200 using other known techniques such as scraping. .

  As a result, management of delivery in a plurality of malls 200 can be implemented centrally in the multi-store management apparatus 100.

Subsequently, some characteristic operations of the multi-store management system 10 will be described as an example.
<Example 1: Development of product information>
The first embodiment relates to processing for expanding product information held by one mall 200 (hereinafter, expansion source) into another mall 200 (hereinafter, expansion destination). An example of the operation of the multi-store management system 10 will be described using the flowchart of FIG. 12.
S101: A synchronization process of merchandise information and the like from the mall 200 at the deployment source to the multi-store management apparatus 100 is started. The product information update unit 117 of the multi-store management apparatus 100 acquires product information and the like from the product DB 210 of the mall 200 of the expansion source according to a method defined by the mall 200 of the expansion source according to the request by the user.
S102: The product information conversion unit 115 converts the product information and the like acquired in S101 into a format that the product information storage unit 111 of the multi-store management apparatus 100 can handle.
S103: The product information updating unit 117 stores the product information etc. converted in S102 in the product information storage unit 111.
S104: A synchronization process of merchandise information and the like from the multi-store management apparatus 100 to the mall 200 at the deployment destination is started. The product information update unit 117 detects a change in product information and the like in S103, and acquires product information and the like from the product information storage unit 111.
S105: The product information conversion unit 115 converts the product information and the like acquired in S104 into a format that can be handled by the product DB 210 of the mall 200 at the expansion destination.
S106: The product information update unit 117 transmits the product information and the like converted in S105 to the mall 200 of the expansion destination in a method defined by the mall 200 of the expansion destination.

  According to the present embodiment, product information and the like can be set in the multi-store management apparatus 100 by using the product information and the like already held by the mall 200 at the deployment source. Further, the multi-store management apparatus 100 serves as a hub, and product information and the like can be synchronized between the mall 200 of the expansion source and the mall 200 of the expansion destination. In other words, the multi-store management apparatus 100 can easily and automatically convert and hold the product information and the like stored in the exclusive format by the mall 200 in the multi-store management apparatus 100.

  The multi-store management apparatus 100 may synchronize only a part of the product information and the like held by the mall 200 with the product information storage unit 111. For example, information (less general) specific to the mall 200 can be excluded from synchronization. As a result, it is possible to hold only highly versatile product information in the multi-store management apparatus 100 and share it among a plurality of malls 200.

<Example 2: Optimization of the shipping source warehouse>
The second embodiment relates to processing for shipping from an optimal warehouse when goods are stocked in a plurality of warehouses. An example of the operation of the multi-store management system 10 will be described using the flowchart of FIG. 13.
S201: A product is ordered by the customer at the mall 200. New order information on this order is registered in the order DB 230 of the mall 200.
S202: Synchronous processing of order reception information from the mall 200 to the multi-store management apparatus 100 is started. The received order information update unit 137 of the multi-store management apparatus 100 detects a change in the received order DB 230, and acquires the received order information newly registered in S201 according to a method defined by the mall 200.
S203: The received order information conversion unit 135 converts the received order information acquired in S202 into a format that can be handled by the received order information storage unit 131 of the multi-store management apparatus 100.
S204: The received order information update unit 137 stores the received order information converted in S203 in the received order information storage unit 131.
S205: The inventory allocation unit 139 detects a change in the order information storage unit 131, and searches inventory information of the product information storage unit 111 using the product ID of the order information registered in S204 as a key.
Here, if a plurality of inventory information are acquired, the inventory allocation unit 139 acquires the address of the customer from the customer information storage unit 121 using the customer ID of the order information as a key. Next, the inventory allocation unit 139 compares distances of the customer's address with the locations of the warehouses included in the plurality of inventory information, and specifies the inventory information on the warehouse with the shortest distance.
If the number of stocks in the specified stock information is equal to or greater than the number of orders received in the order information, the stock allocation unit 139 performs processing to reduce the number of orders received from the number in stock of the stock information. Further, provision information is created in the order information storage unit 131, and the order ID of the order information, the number of order receptions, the number of order receptions, and the warehouse name of the stock information are recorded as the order ID, the number of allocations, and the warehouse name.
S206: The shipping processing unit 159 refers to the received order information storage unit 131, acquires the received order ID of the allocation information created in S205, creates the delivery information in the delivery information storage unit 151, and registers the acquired received order ID (In this embodiment, shipping is performed without waiting for payment).
The shipping processing unit 159 outputs a shipping instruction based on the delivery information registered in the delivery information storage unit 151, and registers the shipping date and time in the delivery information. As a result, typically, the shipping instruction message is transmitted to the warehouse identified in S205, and shipping is performed.

  According to the present embodiment, the multi-store management apparatus 100 can hold information on a warehouse as stock information of goods, and can associate a plurality of stock information with one goods. This makes it possible to easily manage the product inventory distributed to a plurality of warehouses and to automatically ship from the inventory closest to the customer, thereby optimizing the delivery cost.

<Example 3: Central Management of Customers>
The third embodiment relates to the process of centrally managing the purchase history and the like of the same customer when the same customer uses a plurality of malls 200. An example of the operation of the multi-store management system 10 will be described using the flowchart of FIG. 14.
S301: A synchronization process of product information and the like from a plurality of malls 200 to the multi-store management apparatus 100 is performed. The customer information update unit 127 of the multi-store management apparatus 100 acquires customer information and the like from the customer DB 220 of the plurality of malls 200 in response to a request from the user or detecting a change in the customer DB 220.
S302: The customer information conversion unit 125 converts the customer information and the like acquired in S301 into a format that can be handled by the customer information storage unit 121 of the multi-store management apparatus 100.
S303: The customer information update unit 127 stores the customer information and the like converted in S302 in the customer information storage unit 121.
S304: The customer information input unit 123 extracts the same customer from the customer information storage unit 121 according to the user's instruction. For example, the user instructs the search function of the customer information input unit 123 to acquire customer information and the like having the same name and address.
S305: The customer information integration unit 129 integrates the plurality of customer information and the like extracted in S304 into one according to the user's instruction. Thereafter, the information on the customer is aggregated into the integrated customer information and the like.

  In addition, the processing according to steps S304 and S305 can be executed mainly by the multi-store management apparatus 100 without depending on the user's instruction and operation. That is, the multi-store management apparatus 100 can extract the same customer from the customer information storage unit 121 according to a predetermined standard in response to a predetermined trigger, and integrate the extracted customer information and the like.

  According to the present embodiment, customers existing in a plurality of malls 200 are managed by one customer ID in the multi-store management system 10. That is, the purchase histories of the same customer in the plurality of malls 200 and the request / complaint handling history are collected crosswise in the multi-store management system 10 and accumulated centrally. Therefore, for example, since the customer rank is calculated according to the purchase history in the plurality of malls 200, it is possible to more appropriately implement sales measures and the like according to the customer rank. In addition, even when the same customer purchases products for "one point only per person" at multiple malls 200, the net shop will be able to detect that and take an appropriate response. .

<Example 4: Update Order Information>
The fourth embodiment relates to processing when cancellation or change of an order occurs in the mall 200 after the order information is once taken from the mall 200 to the multi-store management system 10. An example of the operation of the multi-store management system 10 will be described using the flowchart of FIG.
S401: A product is ordered by the customer at the mall 200. New order information on this order is registered in the order DB 230 of the mall 200.
S402: Synchronous processing of order reception information from the mall 200 to the multi-store management apparatus 100 is started. The received order information update unit 137 of the multi-store management apparatus 100 detects a change in the received order DB 230, and acquires the received order information newly registered in S401 according to a method defined by the mall 200.
S403: The received order information conversion unit 135 converts the received order information acquired in S402 into a format that can be handled by the received order information storage unit 131 of the multi-store management apparatus 100.
S404: The received order information updating unit 137 stores the received order information converted in S403 in the received order information storage unit 131.

When the customer cancels the order at the mall 200, the processes of steps S405 to S407 are performed.
S405: The customer cancels the order at the mall 200. The order information on the order is deleted from the order DB 230 of the mall 200.
S406: Synchronous processing of order reception information from the mall 200 to the multi-store management apparatus 100 is started. The order information update unit 137 of the multi-store management apparatus 100 detects a change in the order DB 230, and acquires information (typically, an order ID) identifying the order information deleted in S405 by a method defined by the mall 200. .
S407: The received order information update unit 137 deletes the received order information specified in S406 from the received order information storage unit 131.

When the content is changed by the customer in the mall 200, the processes of steps S408 to S411 are performed.
S408: The order details are changed by the customer at the mall 200. For example, a change in the number of orders received. The order information is updated in the order DB 230 of the mall 200.
S409: Synchronous processing of order reception information from the mall 200 to the multi-store management apparatus 100 is started. The received order information update unit 137 of the multi-store management apparatus 100 detects a change in the received order DB 230, and acquires the received order information updated in S408 in a method defined by the mall 200.
S410: The received order information conversion unit 135 converts the received order information acquired in S409 into a format that can be handled by the received order information storage unit 131 of the multi-store management apparatus 100.
S411: The received order information update unit 137 updates the contents of the received order information storage unit 131 with the received order information converted in S410.

  According to the present embodiment, even when the contents of the received order are changed by the customer after the received order, the multi-store management device 100 can easily grasp the change without delay.

  The present invention is not limited to the above embodiment, and can be appropriately modified without departing from the scope of the present invention. For example, the present invention may be realized by hardware, or may be realized by a CPU executing a computer program. In this case, the computer program may be stored in various types of temporary or non-transitory computer readable media and supplied to the computer.

10 multi-store management system 100 multi-store management apparatus 110 product management unit 111 product information storage unit 113 product information input unit 115 product information conversion unit 117 product information update unit 120 customer management unit 121 customer information storage unit 123 customer information input unit 125 customer Information conversion unit 127 Customer information update unit 129 Customer information integration unit 130 Order management unit 131 Order reception information storage unit 133 Order reception information input unit 135 Order information conversion unit 137 Order information update unit 139 Inventory allocation unit 140 Payment management unit 141 Payment information storage unit 143 deposit information input part 145 deposit information conversion part 147 deposit information update part 149 clear part 150 delivery management part 151 delivery information storage part 153 delivery information input part 155 delivery information conversion part 157 delivery information update part 159 shipping processing part 200 mall 210 Product DB
220 customer DB
230 Order Received DB
240 Deposit DB
250 Shipping DB
300 financial institution 400 network

Claims (10)

A multi-store management system including a plurality of malls and a multi-store management device,
The multi-store management device
An information updating unit that acquires at least one of product information, customer information, order information, payment information, and delivery information from the mall;
An information conversion unit that converts the information acquired from the mall according to a predetermined conversion rule;
And an information storage unit for storing the converted information. The multi-store management system according to claim 1, wherein the information updating unit detects a change in the information in the mall and acquires the information from the mall. The information updating unit further acquires the information from the information storage unit;
The information conversion unit further converts the information acquired from the information storage unit according to a predetermined conversion rule,
The multi-store management system according to claim 1, wherein the converted information is transmitted to the mall. The multi-store management system according to claim 3, wherein the information updating unit detects a change in the information in the information storage unit and acquires the information from the information storage unit. The multi-store management system according to claim 1, wherein the information storage unit holds the product information including information on the locations of one or more warehouses in which the product is stocked. The information storage unit holds the customer information including information on the location of the customer who has ordered a product,
6. The multi-store management according to claim 5, further comprising an inventory allocation unit that selects the warehouse to which the goods related to the order are placed based on the relationship between the location of the customer and the location of the warehouse. system. The multi-store management system according to claim 1, wherein the information storage unit integrates and manages the customer information related to the same customer who uses a plurality of the malls. An information updating unit that acquires at least one of product information, customer information, order information, payment information, and delivery information from a plurality of malls;
An information conversion unit that converts the information acquired from the mall according to a predetermined conversion rule;
And an information storage unit for storing the converted information. The information updating unit acquires at least one of product information, customer information, order information, payment information, and delivery information from a plurality of malls;
The information conversion unit converts the information acquired from the mall according to a predetermined conversion rule;
And a step of storing the converted information by the information storage unit.   A program for causing a computer to execute the multi-store management method according to claim 9.

Images