JP4464017B2 - Store terminal and program - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
  The present invention relates to a store terminal and a program connected via a network to a computer system that manages and manages a net shop to which a user terminal is connected via a network.
[0002]
[Prior art]
In recent years, electronic commerce which performs two-way communication via the Internet between a net shop (virtual store) that sells various products via the Internet and a user terminal on the customer side that applies for purchases of products has become You can purchase the desired product freely from any user terminal at any time, and the payment for the purchased product can be automatically withdrawn from the bank account, so shopping equivalent to a virtual shopping street that is a collection of virtual stores Services for supporting online sales, such as malls, are becoming increasingly popular.
By the way, in a personal computer (store PC) as a sales management device installed in the store, the product information is stored and managed for each sale target product that is traded in the store, and the sales information is stored and managed. A sales management system (business application) is constructed that performs sales management such as updating sales information based on the contents of the ordered order and issuing various slips based on the sales information.
When a net shop is constructed using a store PC having such a system environment, a commercially available homepage creation support software is purchased or a professional contractor is requested to construct it.
[0003]
[Problems to be solved by the invention]
However, in order to build a net shop using commercially available homepage creation support software, in addition to assuming that you can fully use a PC, advanced knowledge about creating a homepage is required. It is difficult for store managers and store staff to build, and if you ask a specialist, the construction cost will be huge, so even if you want to sell online, you can easily achieve it. There wasn't.
In addition, in the present situation where many similar online shops are open in shopping malls, it is advantageous to have a large number of products desired by customers, easily find the desired products from them, and quickly purchase them. Therefore, in order to differentiate from other similar shops and promote sales, it is necessary to intensively publish the best-selling products in the product information page and to devise the arrangement state of the product information. It is difficult to request specialists each time even for difficult work, and it becomes impossible to quickly respond to the changing consumption trend.
[0004]
  The object of the present invention is to modify the content of the online shop product information storage means if the product to be corrected is a net sales target product when correcting the product information in the real shop product information storage means. It is possible to make corrections in conjunction with the correction of the storage means, and when deleting the product information in the product information storage means for the actual store, if the product to be deleted is a net sales target product, the deletion is prohibited.Is to be able to do it.
[0005]
[Means for Solving the Problems]
  The invention according to claim 1 is a store terminal connected via the network to a computer system for operating and managing a net shop to which a user terminal is connected via a network, and is an item to be sold that is traded in an actual store Product information storage means for real stores that stores and manages the product information every time, Product information storage means for net shops that stores and manages the product information for each product of a candidate product group to be exhibited in the online shop, A product group of candidate products to be exhibited on the net shop is arbitrarily selected and designated from the product information storage means for the actual store, and product information on each product is read from the product information storage means for the actual store and the product for the net shop is read. A registration unit for registering in the information storage unit, and a network arbitrarily selected from the product information storage unit for the net shop It is stored and managed in the product information storage means for the actual store according to a user operation, a transmission means for reading the product information of the sale target product, creating a product information page on which the product information is posted and transmitting it to the computer system Product informationCorrection or deletionWhen instructedProducts to be corrected or deletedDetermining means for determining whether the product is a product for sale on the Internet, and the determining meansProduct to be corrected isIf it is determined that the product is for sale online,Corresponding to the productProduct information stored and managed in the actual store product information storage meansAnd fix thisThe product information stored and managed in the product information storage means for the net shop corresponding to the product in conjunction withCorrectionUpdate means for performingThe product to be deleted isIf it is determined that the product is for sale online,Corresponding to the productProduct information stored and managed in the actual store product information storage meansDeleteAnd update control means for prohibiting.
[0006]
  Furthermore, a program for causing a computer to function as the main means shown in the invention of claim 1 is provided.2Described invention).
[0020]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, an embodiment of the present invention will be described with reference to FIGS.
FIG. 1 is a block diagram showing the overall configuration of the sales management network system in this embodiment.
This sales management network system (wide area communication system) has a shopping mall site 1 as a core, and the shopping mall site 1 is installed in an actual store (actual store) that is a member user (net store). A system environment in which a store terminal 2 is connected via a network (Internet) 3 and a user terminal (product purchaser terminal) 4 which is a general customer of a shopping mall is connected via the network 3 It has become.
The shopping mall site 1 is a computer system for operating and managing a virtual shopping street (shopping mall) that is a collection of net shops (virtual stores).
[0021]
The store terminal 2 has a product information page (HTML HTML page) with content arbitrarily selected from a group of products to be sold in an actual store for products to be sold online (net shop products) to be displayed on the shopping mall site 1. Web page) is created and uploaded to the shopping mall site 1, or sales information and customer information etc. at the actual store side are updated based on the order information of the net sales ordered for the product at the shopping mall site 1 side. Therefore, the present invention is a sales management device capable of easily linking a net shop construction and a net sales management with an existing sales management system without changing an existing sales management system to be described later.
[0022]
In this embodiment, for example, data digitized (packetized) between the shopping mall site 1, the store terminal 2, and the product purchaser terminal 4 by the HTTP protocol using the TCP / IP communication protocol. In addition, data processing is performed in cooperation with each other while recognizing necessary processing contents from data including coded control information. The shopping mall site 1 has a database server function, a Web server function, a mail server function, and the like, and the store terminal 2 and the product purchaser terminal 4 have a Web browser function.
[0023]
FIG. 2 is a block diagram for explaining a basic system outline of the store terminal 2.
The store terminal 2 is a personal computer (store PC) installed in the store. The store terminal 2 stores and manages the product information for each sale target product that is traded in the store, as well as sales information and An existing sales management system 21 that stores and manages customer information and performs various types of sales management based on keyed order information (slip data) is constructed. In other words, the sales management system 21 is a normal business application that operates and manages various master files, files for slip processing, etc., and performs a series of business operations such as order business, deposit management, billing business, and shipping business. It has general sales management processing functions such as data input, slip issuance, data management, and data utilization.
On the sales management system 21 side, as the basic data file, a plurality of product MT (master) files F1 for each product genre, which will be described later, a slip details / slip total file F2, a customer master file F3, a delivery master file F4 is provided. Note that the master file is a concept for a transaction file, but in this embodiment, it simply indicates a basic file and may be used in a transactional manner (for example, a customer master file F3). The delivery destination master file F4) is referred to as a master file (hereinafter the same).
[0024]
In addition to the existing sales management system 21 described above, the store terminal 2 is additionally configured with a net shop construction / operation system 22 unique to this embodiment.
This network shop construction / operation system 22 is used to construct a network shop and manage online sales, so that the store terminal 2 equipped with this system 22 also functions as a “PC for a net shop shopkeeper”. Become.
The net shop construction / operation system 22 is roughly divided into a net shop construction AP (application) 22a and a net sales input AP 22b, and cooperates with the existing sales management system 21. Note that the linkage with the sales management system 21 includes “product master linkage” and “order transaction linkage”.
[0025]
“Product Master Linkage” means that the product master file F1 on the sales management system 21 side is referred to, and information on each product for display on the net shop is generated and uploaded to the shopping mall site 1. The consistency between the product and the product in the product master file F1 is maintained.
“Order transaction linkage” means that various business processes are performed by acquiring order information (order transaction) on the net shop side and inputting it as order information to the sales management system 21. A series of operations such as billing operations, customer management, and shipping operations are processed according to order information of online sales.
[0026]
When a net shop is newly constructed, the operator arbitrarily defines the configuration of the product guide page by activating the net shop construction AP 22a, and arbitrarily sets the product information to be posted in the product guide page and its arrangement state. To the shopping mall site 1 by uploading various file groups F storing the product information page configuration (HTML) and product information (including product images) to be posted in the product guide page to the shopping mall site 1 The construction information is constructed in the store-specific storage area E.
Here, the net shop construction AP 22a is roughly divided into a net shop definition module M1, a net merchandise registration module M2, and a net merchandise display module M3. The net shop definition module M1 is a module for arbitrarily defining the structure of the net shop, that is, the page design and the like for each of a plurality of product guide pages.
[0027]
The online merchandise registration module M2 is selected when a merchandise that is a candidate for listing as net sales is arbitrarily selected from various merchandise stored in the merchandise master file F1 on the sales management system 21 side. This is a module for registering information about products in the linked product master file F5. The linked product master file F5 is a product master file for online sales that stores and manages product groups that are candidates for online sales.
The online product display module M3 can select an arbitrary product from the exhibition candidate group registered in the linked product master file F5 as a target product for online sales, and information on the selected product is displayed on the product guide page. This is a module that can arbitrarily set the display state for placement inside.
[0028]
The net sales input AP 22b configuring the net shop construction / operation system 22 includes a net order information acquisition module M5 and a net order input module M6.
The net order information acquisition module M5 receives and acquires the net sales order information read from the order information file OF corresponding to the net shop where the product is ordered on the shopping mall site 1 side, and the linked sales details file F6 It is a module for accumulating in Note that the order information for online sales includes information on ordered products, information on the orderer, and information on delivery destinations (delivery destinations), which are collectively referred to as order information.
[0029]
The linked sales statement file F6 is used to temporarily store and hold the contents of the order information file OF on the shopping mall site 1, and the net order input module M6 stores the contents of the linked sales details file F6 (order information for net sales) as 1. Read in units of slips and store them in the slip details / slip total file F2, extract information on the orderer and store it in the customer master file F3, update the sales performance by customer, and information on the delivery destination Is extracted and stored in the delivery destination master file F4, and at the same time, the sales results for each customer and each delivery destination are updated.
[0030]
FIG. 3 is a diagram for explaining the operation concept of the net shop definition module M1, the net merchandise registration module M2, and the net merchandise display module M3 constituting the net shop construction AP 22a.
When the net shop definition module M1 is activated, the store terminal 2 defines the structure of the net shop such as the number of Web pages, the page type and the maximum number of products posted on each page, and the shop structure definition file F11. Or the design (page components such as background images and buttons and their layout) is defined for each page and stored in the HTML file F12.
The HTML file F12 is a file created in a hypertext markup language, and includes a plurality of pages corresponding to the number of pages in the shop structure definition.
FIG. 32B shows a shop structure definition screen for inputting and setting data stored in the shop structure definition file F11, and details thereof will be described later.
[0031]
When the online product registration module M2 is activated, the store terminal 2 displays a list of a plurality of product master files F1 associated with product genres provided on the sales management system 21 side. When the product master file F1 of the desired product genre is arbitrarily selected and specified, the contents of the selected product master file F1 are displayed in a list, and when any product is selected and specified from this product list, Information about the product is registered in the linked product master file F5. That is, when the selected product master file F1 is used as a source and a product that is a candidate for online sales is arbitrarily selected from various products in the product master file F1, the selected product information Information necessary for online sales is taken out and registered in the linked product master file F5, and unique information inputted for online sales is registered in the linked product master file F5.
[0032]
In this case, the product master file F1 and the linked product master file F5 are associated by a product code or the like. Even if a product is not registered in the product master file F1, that is, a new product that is not handled in an actual store, it can be registered in the linked product master file F5 as a candidate for online sales. If registered, it is additionally registered in the product master file F1 to maintain consistency between the product master file F1 and the linked product master file F5.
[0033]
Further, as a means for maintaining consistency between the product master file F1 and the linked product master file F5, when the content of the product master file F1 is corrected, the product designated as the correction target is the shopping mall site 1 side. It is determined whether the product is a product that has been sent to the Internet (a product that is being sold online). If the product is being sold online, a correction warning message is displayed.
In this case, on the condition that a correction execution instruction is received, the contents of the linked product master file F5 corresponding to the product are updated in conjunction with the update of the product master file F1. Furthermore, even when the contents of the product master file F1 are deleted, if the product designated as the deletion target is a product currently on the Internet, it is prohibited to delete the content of the product master file F1 corresponding to the product. A message to be displayed is displayed.
[0034]
FIG. 4A shows the record structure of the product master file F1, and each product record includes “product code”, “product name”, “product classification”, “JAN code”, “sales price”, and the like. It has various items.
FIG. 4B shows the record structure of the linked product master file F5. Each product record includes “product code”, “product name”,..., “Sales price”, “image number”, It has various items such as “Product Description” and “Delivery Fee”. The “product code”, “product name”,..., “Sales price” are information acquired from the product master file F1, but “image number”, “product description”, “delivery fee”, etc. This is information specific to the net product that does not exist in the product master file F1. In addition, the name of the product master file F1 linked to the linked product master file F5 is added as the “source master name”.
[0035]
Further, the store terminal 2 activates the image selection module M21 according to the online product registration module M2, and displays the contents of the image candidate file F7 as a list. The image candidate file F7 is a file that stores and manages a product image captured in advance for each of various products in a one product file format corresponding to the image number. When an arbitrary product image is selected and specified from the image list, the store terminal 2 stores the selected image number in the linked product master file F5 as information related to the product.
[0036]
When the online merchandise display module M3 is activated, the store terminal 2 displays a list of the contents of the shop structure definition file F11. FIG. 37 shows an example of a net product display <page list> screen displaying the contents of the shop structure definition file F11, and details thereof will be described later.
Then, when an arbitrary page is selected from the page list, the store terminal 2 accesses the product display definition file F31, and displays and outputs the definition content corresponding to the selected page (initially undefined).
FIG. 5 is a diagram showing the configuration of the product display definition file F31, which defines products to be arranged in the pages corresponding to a plurality of pages and their arrangement order. The definition content corresponding to each page is “page “No.”, “product code (1)”, “product code (2)”,... Are stored. FIG. 38 exemplifies a display product registration screen corresponding to the selection page, and details thereof will be described later.
[0037]
Further, the store terminal 2 accesses the linked product master file F5 according to the online product display module M3 and displays a product list screen. FIG. 39 exemplifies a product list screen of the linked product master file F5, and details thereof will be described later.
When an arbitrary product is selected as a net display target from the product list, the product code is arranged in the selection page of the product display definition file F31. When an operation (arrangement operation) for arbitrarily changing the display arrangement order is performed after an operation (arrangement operation) for arbitrarily selecting the net display target product is performed, according to the net product display module M3. The store terminal 2 performs an editing process for rearranging the contents of the selection page of the product display definition file F31 in the designated order. Then, the online merchandise display module M3 activates the page generation module M31.
[0038]
According to the page generation module M31, the store terminal 2 refers to the contents of the linked product master file F5, the image candidate file F7, and the product display definition file F31, and pages the net image file F32, the net product master file F33, and the HTML file F12. Create each. That is, the content of the product display definition file F31 is analyzed for each page, and the product information read from the linked product master file F5 according to the definition content is set in the net product master file F33, and an image corresponding to the product is displayed. The contents are read from the image candidate file F7 and set in the net image file F32, and the contents of the shop structure definition file F11 and the product display definition file F31 are set in the HTML file F12 for each page.
FIG. 4C shows that the product information (net product record) read from the linked product master file F5 is set in the net product master file F33 as it is.
[0039]
FIG. 6 is a diagram showing how various types of information obtained by building a net shop are uploaded to the shopping mall site 1 side.
That is, the upload module M4 is a module for associating the net image file F32, net product master file F33, and HTML file F12 generated by the page generation module M31 and uploading them to the shopping mall site 1. In this case, the shopping mall site 1 sets the net shop construction information transmitted from each store terminal 2 in the store-specific storage area E. In addition to the order information file OF, the shopping mall site 1 is provided with a store management table T described later.
[0040]
FIG. 7 is a diagram showing the contents of the store-specific storage area E that stores and manages the net shop construction information for each store on the shopping mall site 1 side. This store-specific storage area E is configured to store and manage the HTML file F12, the net product master file F33, and the net image file F32 corresponding to the identification information (store number) for each net shop. The shopping mall site 1 reads the contents of the store-specific storage area E corresponding to the net shop accessed from the product purchaser terminal 4, creates a product information page for the customer, and sends it to the requesting product purchaser terminal 4 To do.
[0041]
FIG. 8A shows the contents of the store management table T provided on the shopping mall site 1 side, and “access information of shop store PC for calling the store terminal 2 corresponding to“ store number ”. Is stored and managed. That is, in correspondence with the “store number” for identifying the store terminal (shop store PC) 2 that is a member of the shopping mall, as the “shop store PC access information”, the phone number of the store terminal 2 and the like When the shopping mall site 1 sends the order record in the order information file OF corresponding to the store to the store terminal 2, the “shop store PC access information” is stored from the store management table T. Is read out.
[0042]
FIG. 8B shows the record structure of the order information file OF. The order record includes “product code”, “product name”, “quantity”, “price”, “total amount”, “orderer”. It consists of items such as “name”, “address”, “phone number”, “mail address”, “member ID”, “delivery name”, “delivery address”, “delivery address”. "Product code", "Product name", "Quantity", "Price", and "Total price" indicate information related to product orders, such as "Orderer name", "Address", "Phone number", "Email address" ”And“ Membership ID ”indicate information related to the purchaser (customer) of online sales, and“ Destination name ”,“ Destination address ”, and“ Destination phone number ”are those for requesting delivery of the ordered product to a third party. Indicates information about the delivery address. Here, every time an order is received from the product purchaser terminal 4, the shopping mall site 1 inquires the purchaser about the order contents, and stores the order record created thereby in the order information file OF. Yes.
[0043]
FIG. 9 shows a list of various files provided on the sales management system 21 side and various files provided on the net shop construction / operation system 22 side.
The slip detail / slip total file F2 stores and manages slip detail records including items similar to the items of the order information file OF described above (see FIG. 8B) and slip total records totaled for each order. It is a file. Here, according to the net sales input AP 22b, the store terminal 2 acquires the net sales order information for each slip from the linked sales detail file F6 and stores it in the slip details / slip total file F2. Thereafter, in accordance with the sales management system 21, the store terminal 2 creates a delivery note, a transfer request form, a delivery slip, a daily order detail report, etc. based on the contents of the slip details / slip total file F2, and prints out the slip issuing process. And various slip management processes.
[0044]
FIG. 9 shows the above-mentioned linked product master file F5, image candidate file F7, shop structure definition file F11, product display definition file F31, HTML file on the net shop construction AP 22a side in the net shop construction / operation system 22. F12 is provided, and an Internet merchandise master file F33, an Internet image file F32, and an HTML file F12 are provided as various files uploaded to the shopping mall site 1. Further, it is shown that a linked customer master file F8 and a linked delivery destination master file F9 are provided on the net sales input AP 22b side in addition to the linked sales description file F6 described above.
[0045]
FIG. 10A shows the record structure of the customer master file F3, and FIG. 10B shows the record structure of the linked customer master file F8.
The customer master file F3 includes, for each customer, items "customer code", "customer name", "address", "phone number", ... "cumulative sales amount", and "customer rank". The customer record is stored and managed. “Cumulative sales amount” is a sales result for each customer, and “customer rank” indicates a rank divided according to the sales result.
[0046]
Here, according to the online sales input AP 22b, the store terminal 2 acquires online sales order information for each slip from the linked sales detail file F6, and whether the customer information has been registered in the customer master file F3. If registered, only the relevant “cumulative sales amount” in the customer master file F3 is updated. If not registered, the online sales order information obtained from the linked sales detail file F6 is updated. Information about the customer is extracted from the information and registered in the customer master file F3, and the “cumulative sales amount” in the customer master file F3 is updated.
[0047]
The linked customer master file F8 is for online sales that stores and manages linked customer records having items of "customer code", "email address", and "cumulative sales points" for each customer using online sales. Customer master. In accordance with the online sales input AP 22b, the store terminal 2 extracts information on the customer from the online sales order information acquired from the linked sales description file F6, and registers it in the linked customer master file F8 under certain conditions. The relevant “cumulative sales points” are updated.
[0048]
FIG. 11A shows the record configuration of the delivery destination master file F4, and FIG. 11B shows the record configuration of the linked delivery destination master file F9.
The delivery destination master file F4 stores and manages delivery destination records having items of “customer code”, “delivery destination code”, “delivery destination name”, “delivery destination address”, “delivery destination telephone number”, and “delivery destination accumulated amount”. The “delivery destination cumulative amount” is, for example, the sales results up to the present time that A company sends to B company when A company, the customer, requests delivery of products to B company, which is the delivery destination. It is.
[0049]
Here, according to the net sales input AP 22b, the store terminal 2 acquires the net sales order information for each slip from the linked sales detail file F6, and the customer code and the destination code extracted from the order information are the destination master file F4. If it is registered, only the relevant “cumulative sales amount” in the delivery destination master file F4 is updated. If not registered, it is acquired from the linked sales details file F6. Information on the customer code and delivery destination is extracted from the order information of online sales and registered in the delivery destination master file F4, and the corresponding “cumulative sales amount” in the delivery destination master file F4 is updated.
[0050]
The linked delivery destination master file F9 corresponds to the customer and delivery destination when the customer using the online sales requests delivery of the ordered product to a third party. This is a delivery destination master for online sales that stores and manages delivery destination codes and delivery destination names. In accordance with the online sales input AP 22b, the store terminal 2 extracts information on the delivery destination from the online sales order information acquired from the linked sales description file F6, and registers it in the linked delivery destination master file F9 under certain conditions. .
[0051]
FIG. 12 is a block diagram showing basic components of the store terminal 2.
The CPU 201 is a central processing unit that controls the overall operation of the store terminal 2 according to the operating system and various application software in the storage device 202. The storage device 202 stores the above-described various files in addition to the operating system and various application software, and includes a magnetic, optical, semiconductor memory, and the drive system thereof. The recording device 202 is not limited to a fixed memory such as a hard disk, but may be configured to be able to mount a removable storage medium such as a CD-RO or a DVD. Programs and data in the storage device 202 are loaded into a RAM (for example, static RAM) 203 as needed, or data in the RAM 23 is saved in the storage device. Further, the CPU 201 can directly access and use programs / data of other electronic devices via the communication device 24, and can receive and download from other electronic devices via the communication device 204.
On the other hand, a communication device 204, an input device 205, a display device 206, and a printing device 207, which are input / output peripheral devices, are connected to the CPU 201 via a bus line, and the CPU 201 controls their operations according to an input / output program. To do.
[0052]
Next, the operation algorithm of the sales management network system in this embodiment will be described with reference to the flowcharts shown in FIGS. Here, each function described in these flowcharts is stored in the form of a readable program code, and operations according to the program code are sequentially executed. It is also possible to sequentially execute operations according to the program code transmitted via the transmission medium. That is, in addition to the recording medium, an operation specific to this embodiment can be executed using a program / data supplied externally via a transmission medium.
[0053]
13 to 24 are flowcharts showing the operation of the store terminal 2 in response to the activation of the net shop construction AP 22a constituting the net shop construction / operation system 22. 13 to FIG. 17 are a series of flowcharts showing the operation when a new net shop is constructed, and FIG. 18 to FIG. 24 are newly constructed net shops. FIG. 18 and FIG. 19 show the change of the linked product master, and FIG. 20 and FIG. 21 show the display definition change (during online sales). FIG. 22 to FIG. 24 are flowcharts showing operations according to the change of the product master file F1.
FIG. 25 and FIG. 26 are flowcharts showing operations on the shopping mall site 1 side in response to access from the product purchaser terminal 4.
27 to 29 are flowcharts showing the operation of the store terminal 2 in accordance with the online sales input AP 22b constituting the online shop construction / operation system 22.
30 and 31 are flowcharts illustrating the operation of the store terminal 2 in accordance with the sales management system 21.
[0054]
First, with reference to FIG. 13 to FIG. 17, an operation when a net shop is newly constructed will be described.
In this case, when activation of the net shop construction AP 22a is designated, the CPU 201 displays and outputs the top page screen (step A1). This top page screen has menu items of “1: create new net shop” and “change net shop”, and when one of the menu items is selected (step A2), the selection item is discriminated. (Step A3).
[0055]
If the menu item “1: New net shop creation” is selected, the net shop definition module M1 is activated, and a work procedure screen showing a series of work procedures is displayed and output (step A4).
FIG. 32A shows this work procedure screen, which includes “1: Shop structure definition”, “2: Net product registration”, “3: Net product display”, “4: Site upload”. "Is displayed in a list, and a" Start "button is arranged. The following processing is sequentially executed according to this work procedure.
[0056]
When the operator confirms the contents of the work procedure screen and operates the “start” button (step A5), the shop structure definition screen is displayed (step A6).
FIG. 32 (B) shows this shop structure definition screen. In this shop structure definition screen, definition items of “page type”, “selection”, “page title”, and “maximum number of products” are provided for each page. Have. This “page type” item corresponds to the first page, the second page, etc., “cover”, “shop introduction”, “product list (1)”, “product list (2)”, Are displayed in a fixed sequence in advance, and the “page type” is selected and specified by entering “check” in the “select” item position corresponding to the “page type”. . “Maximum number of products” indicates the maximum number of products to be arranged in the selected page.
[0057]
In this shop structure definition screen, “Check” is entered in the item position of “Select” and a necessary page is arbitrarily selected (Step A7), then “Page Title”, “Maximum Product” corresponding to the selected page When “number” is input and set (step A8), the contents of the shop structure definition screen are stored in the shop structure definition file F11 (step A9). Thereafter, for each page selected as described above, when the page design (background components, title images, page components such as buttons, and their layout) is set and input (step A10), the set page design is Then, it is stored in the HTML file F12 corresponding to each page (step A11).
[0058]
In this way, by arbitrarily selecting and specifying the page type prepared in advance, the shop structure consisting of a plurality of pages is arbitrarily set, and the basic configuration content of each page is arbitrarily set to perform HTML. When the file F12 is generated, the online merchandise registration module M2 is activated.
Then, the process proceeds to step A12 in FIG. 14, and various product master files F1 prepared for each product genre are accessed, and the master list menu is displayed and output. When an arbitrary product master is selected and designated from the master list menu (step A13), after the process of storing the name of the selected master as the source file name of the linked product master file F5 is performed (step A14), a new item master is created. An online merchandise registration screen is displayed (step A15).
[0059]
FIG. 33 shows a base screen for this new net product registration.
This new net product registration screen is a registration screen for registering the data input in the screen as an exhibition candidate in the linked product master file F5. Each item of “product code”, “product name”, “product name 2”, “tax-excluded tax category”, etc. in this registration base screen is a product that is not stored in the product master file F1. This item data is newly registered for the product master file F1 when registered in F5. In addition to the above-mentioned “product code” and “product name”, the items “sales price”, “product description”, “remarks 1”, etc. are item data registered in the linked product master file F5. is there.
[0060]
The registration base screen is provided with an image display area to which a product image is pasted, and various function buttons are arranged. Among these function buttons, the “processing category” button (upper right in the figure) selects and designates the processing of “add”, “correct”, and “delete” when changing the contents of the linked product master file F5. Is. The various buttons arranged in the button menu provided at the bottom of the screen are not shown.
[0061]
In a state where such a new net product registration screen is displayed, the next step A16 determines whether or not reading from the selection master. That is, whether to read information from the product master file F1 selected in step A13 and register it in the linked product master file F5, or to register products not stored in the selected master in the linked product master file F5. To determine.
If it is specified that information is read from the selected master and registered in the linked product master file F5, the source file name stored in step A14 is acquired, and the product master specified by the source file name is acquired. The file F1 is accessed and the product list screen is displayed and output (step A17).
[0062]
FIG. 34 is a diagram showing a product list screen of the selection master (product master file F1).
This product list screen displays a list of “product name” and “product code” for each product corresponding to the serial number, and when a product as a candidate for online exhibition is arbitrarily selected and designated (step A18). , The product information corresponding to the selected product is read from the product master file F1, and necessary item data (product code, product name, price) is extracted from the product information in the new net product registration screen of FIG. Is copied and displayed at the corresponding item position (step A19).
[0063]
On the other hand, when registering a product that is not stored in the selection master in the linked product master file F5 (step A16), data (product code, product name, price) of necessary items in the new net product registration screen of FIG. ) (Step A20), a new product registration screen corresponding to the product master file F1 specified by the source file name is displayed and output (step A21). This new product registration screen corresponding to the source master is a registration screen for registering each item of the product record constituting the product master file F1, although not shown, and the item data input in the above-mentioned new net product registration screen Is copied and displayed at the corresponding item position in the registration screen (step A22). Then, manually input data of other necessary items in the registration screen corresponding to the source master (step A23).
In this way, a product record is generated based on each item data input on the registration screen corresponding to the source master, and this product record is additionally registered in the product master file F1 specified by the source file name (step A24). Then, the new net product registration screen is displayed again (step A25).
[0064]
Next, the online merchandise registration module M2 activates the image selection module M21 and displays a list of the contents of the image candidate file F7 (step A26 in FIG. 15). FIG. 35 shows this image list screen, and in this screen, product images captured in advance corresponding to various products are listed. When an arbitrary product image is selected and specified from the image list, the image number selected from the image candidate file F7 is acquired and sent to the net product registration module M2 under the control of the image selection module M21. The image number is stored in the linked product master file F5 as information related to the product (step A27). Further, the selected image is pasted in the image display area in the new net product registration screen of FIG. 33 (step A28).
[0065]
In this state, when data of other necessary items (product description, etc.) is input in the new net product registration screen, the input data is displayed at the corresponding item position in the registration screen (step A29). Here, when all the necessary item data has been input and a confirmation operation has been performed (step A30), a product record is generated based on the data in the new net product registration screen, and this generated record is stored in the linked product master file F5. (Step A31). In the next step A32, it is determined whether or not there is an instruction to end the registration process, and the process returns to step A15 in FIG. 14 until there is an end instruction.
[0066]
Here, when an instruction to end registration is received (step A32), the online merchandise registration module M2 activates the online merchandise display module M3. Then, the process proceeds to step A33 in FIG. 16, and the store terminal 2 reads the contents of the shop structure definition file F11 in accordance with the net product display module M3 and displays the net product display <page list> according to the contents of this structure definition ( Step A34).
FIG. 37 shows this net product display <page list> screen. In this list screen, for each page defining the shop structure, a series of “page number”, “page type”, “selection” ”,“ Page Title ”, and“ Maximum Number of Products ”are displayed in a list.
[0067]
When an arbitrary page is selected and designated in the net product display <page list> screen (step A35), the corresponding page in the product display definition file F31 is accessed based on the selected page, and based on the definition content of the page. A display product registration screen corresponding to the selected page is displayed and output (step A36), and a product list screen in the linked product master file F5 is displayed and output (step A37).
FIG. 38 shows the display product registration screen corresponding to this selection page. In this registration screen, the “page number” is displayed and various product information arranged in the selection page is displayed. They are displayed in order of display. That is, “number”, “product name”, and “product code” indicating the display order for each product are displayed in a list, but when the net shop is newly constructed, data is stored in the product display definition file F31. Since there is no information on the product on the registration screen, it remains blank.
[0068]
FIG. 39 shows the product list screen of the linked product master file F5. This product list screen displays a list of “product name” and “product code” for each product corresponding to the serial number. When any product is selected and designated as a display target (step A38), product information corresponding to the selected product is read from the linked product master file F5 and additionally displayed in the display product registration screen corresponding to the selected page. (Step A39).
Here, the first selected product is displayed at the top position (the position indicated by the display number “1”) in the display product registration screen. When such a display target selection operation is sequentially performed for each product, information regarding the product is sequentially arranged and displayed in the display product registration screen according to the selected order.
[0069]
When all the display target products are selected (step A40), the display state change instruction set this time is received (step A41). If there is a change instruction, the product arrangement in the display product registration screen is changed to the change operation. Accordingly, a process of changing in the designated order is performed (step A42). In this case, if you specify the name of the product to be changed and its placement position in the display product registration screen, and perform the change operation to reposition the specified product at the specified location, the contents of the display product registration screen will be as specified. Are changed in the order of arrangement. When the end of change is instructed (step A43), the product codes in the display product registration screen are read in the order and stored in the product display definition file F31 corresponding to the page (step A44).
Then, it is checked whether processing for all pages has been completed (step A45). If there is an unprocessed page, the next unprocessed page is selected, and then a step is performed to display the net product display <page list> screen. Returning to this description, the product display definition file F31 shown in FIG. 5 is generated as a result of repeating the above operation for all pages.
[0070]
Thus, when the product display definition file F31 for all pages is generated, the online product display module M3 activates the page generation module M31. Then, the process proceeds to step A46 in FIG. 17, and one page from the top of each page of the product display definition file F31 is designated.
Then, the “product code” is sequentially read from the product display definition file F31 corresponding to the designated page, the linked product master file F5 is accessed based on this “product code”, and information (net product record) related to the product is linked. Obtained from the product master file F5 and stored in the net product master file F33 (step A47).
[0071]
Next, the image candidate file F7 is accessed based on the “image number” in the net product record acquired from the linked product master file F5, and the corresponding product image is read out and stored in the net image file F32 (step A48). Such storage processing of net products and net images is performed for all products in the designated page (steps A47 to A49).
When the storage process for one page is completed (step A49), the HTML file F12 is accessed based on the designated page, the HTML page corresponding to the designated page is read (step A50), and the product display definition is defined in the HTML page. An HTML page including the product display definition is created by pasting each product code in the order of the product display definition set in the corresponding page of the file F31, and this is stored again in the HTML file F12 (step) A51).
[0072]
When the processing for generating the net product master file F33, the net image file F32, and the HTML file F12 corresponding to the designated page is completed in this way, the generation processing for all pages defined in the product display definition file F31 is completed. (Step A52). Since the generation processing for the first page is now complete, the process returns to step A46, and after specifying the second page, the net product master file F33 corresponding to the second page. Then, processing for generating the net image file F32 and the HTML file F12 is executed (steps A47 to A51).
[0073]
As a result, when the generation processing for all pages is completed (step A52), the page generation module M31 activates the upload module M4. Then, the net product master file F33, net image file F32, and HTML file F12 for all pages are uploaded to the shopping mall site 1 as net shop construction information (step A53).
The shopping mall site 1 sets the net shop construction information transmitted from the store terminal 2 in the store-specific storage area E, thereby constructing a net shop corresponding to the store.
[0074]
After the net shop is constructed in this way, when “change net shop” in the top page screen described above is selected (steps A1 to A3 in FIG. 13), the process proceeds to the net shop change process ( 18 to 24).
First, when the menu item “Change net shop” is selected, the online merchandise registration module M2 is activated. Then, the change menu screen is displayed and output (step A60 in FIG. 18).
FIG. 40A shows the change menu screen. The menu screen includes menu items of “linked product master change”, “display definition change”, “product master change”, and “end”. Is displayed.
[0075]
“Linked product master change” is a menu item for instructing processing to change the net product record stored as an exhibition candidate in the linked product master file F5. “Display definition change” is a product display definition file. F31 is a menu item for instructing processing to change a product record stored as a product being sold online in the F31, and “change product master” changes the product record stored in the product master file F1. This is a menu item for instructing processing. “End” is an item for instructing the end of the change process.
When an arbitrary menu item is selected from such a change menu screen (step A61), the selection item is determined (step A62).
[0076]
Now, when the menu item is selected to execute “linked product master change” (steps A61 and A62), the linked product master file F5 is accessed (step A63), and the change processing category is selected. It will be in the state which can be received (step A64).
Here, when an arbitrary category is selected from “add”, “modify”, and “delete” as the change processing category, the selected category is determined (step A65).
Here, when a new product is added to the linked product master file F5, “add” is selected as the change processing category. Then, the online product registration screen of FIG. 33 is displayed (step A66), and the product master file F1 designated by the source file name is accessed to display and output the product list screen of FIG. 34 (step A67).
[0077]
When a product to be added as an online exhibition candidate is arbitrarily selected and designated from the product list screen (step A68), product information corresponding to the selected product is read from the product master file F1, and necessary item data is stored therein. Extracted and copied and displayed at the corresponding item position in the new net product registration screen (step A69).
Next, the image selection module M21 is activated by the online merchandise registration module M2. Then, the image candidate file F7 is accessed, and an image list screen as shown in FIG. 35 is displayed (step A70).
When the product image to be added is selected and specified from the image list screen, the selected image number is acquired (step A71). The selected image is the image in the net product registration screen of FIG. Affixed to the display area (step A72).
[0078]
Next, when data of other necessary items (such as a product description) is input into the online product registration screen, the input data is displayed at the corresponding item position in the registration screen (step A73). Here, when all the necessary item data has been input and a confirmation operation has been performed (step A74), a product record is generated based on the data in the online product registration screen, and this generated record is transferred to the linked product master file F5. Additional registration is performed (step A75). In the next step A76, it is determined whether or not there is an additional end instruction, and the process returns to step A66 until there is an end instruction, and the above-described operation is repeated thereafter.
[0079]
Further, when changing the product information in the linked product master file F5, “modify” is selected as the change processing category (step A77 in FIG. 19). Then, a product list in the linked product master file F5 as shown in FIG. 39 is displayed (step A78). When the product to be corrected is selected from the product list screen (step A79), the net product record corresponding to the product is read, and the content of the product record is displayed and output in the net product registration screen (step A80). .
When an operation for correcting the item or product image is performed in the online product registration screen corresponding to the selected product, the corresponding data in the registration screen is corrected accordingly (step A81).
When the data correction of the selected product is completed (step A82), the corresponding net product record in the linked product master file F5 is accessed based on the product, and the corresponding data in the net product record is based on the correction data. It is updated (step A83). Then, in the next step A84, it is determined whether or not there is an end instruction, and the process returns to step A78 until there is an end instruction, and the above operation is repeated thereafter.
[0080]
When “delete” is selected and designated as the change processing category (step A77 in FIG. 19), a product list in the linked product master file F5 is displayed (step A85). When a product to be deleted is selected from the product list screen (step A86), the product display definition file F31 is accessed based on the selected product, and the “product code” of the product is searched. The presence or absence is determined (steps A87 and A88). That is, it is determined whether or not the product selected as the deletion target is a product currently on sale on the Internet. Here, if the “product code” of the corresponding product is stored in the product display definition file F31, the product selected for deletion is a product currently being sold online, so that the operator can be notified of this fact. A deletion warning message is displayed and output (step A89).
[0081]
After receiving this warning message, if a deletion execution request is received (step A90), the corresponding product code in the product display definition file F31 is deleted, and the product is removed from the target products for online sales. At the same time (step A91), the corresponding product record in the linked product master file F5 is deleted (step A92). Note that when the execution of deletion is canceled after the warning message, the deletion processing of steps A90 and A91 described above is not executed. Then, in the next step A93, it is determined whether or not there is a deletion end instruction, and the process returns to step A85 until there is an end instruction, and the above operation is repeated thereafter.
In the case where the termination is instructed during the “addition”, “modification”, and “deletion” processing of the linked product master file F5 as described above (steps A76, A84, A93), FIG. Returning to step A60, the change menu screen is displayed again.
[0082]
Next, an operation for changing a product being sold online (display definition change) will be described with reference to FIGS. 20 and 21. FIG.
In this case, when the menu item “display definition change” is selected from the change menu screen shown in FIG. 40A, the net product display module M3 is activated. As a result, the process proceeds to step A100 in FIG. 20, the contents of the shop structure definition file F11 are read (step A101), and the net product display <page list> is displayed according to the contents of the structure definition (step A102). When a page to be changed is selected and specified in the net product display <page list> screen (step A103), the corresponding page in the product display definition file F31 is accessed based on the selected page, and based on the definition content of the page. Then, a product registration screen (see FIG. 38) corresponding to the selected page is displayed and output (step A104).
[0083]
Then, the selection of the process category is accepted (step A105), and it is determined which of “add”, “move”, “delete”, “other page”, and “end” is selected as the process category (step A106).
Now, when adding a new product as a product being sold online, when “add” is selected as the processing category, the linked product master file F5 is read (step A107), and the product list screen (see FIG. 39). ) Is displayed and output (step A108). When a product to be added is selected from the product list screen (step A109), information related to the selected product is additionally inserted into the display product registration screen of FIG. 38 (step A110). Then, in the next step A111, it is determined whether or not there is an addition end instruction, and the process returns to step A108 until there is an end instruction. Thereafter, the above operation is repeated, and then added to the display product registration screen in response to this end instruction The registered product code is additionally registered in the product display definition file F31 corresponding to the page (step A112). Thereafter, the process returns to step A105, and the processing section can be selected.
[0084]
Further, when changing the display order of the products being sold online, “move” is selected as the processing category (step A113 in FIG. 21). Here, when a product name order changing operation is performed, the contents of the display product registration screen are changed in the arrangement order as specified (step A114). Such change processing is repeated until the end of movement is instructed. Here, when the end of movement is instructed (step A115), the contents of the product display definition file F31 corresponding to the page are updated in the order of the changed product names (step A116), and then the processing category selectable state is set. (Step A105 in FIG. 20).
[0085]
Further, when a product currently sold on the Internet is excluded from the target, “delete” is selected as the processing category (step A117 in FIG. 21). Then, when a product to be deleted is selected from the display product registration screen (step A118), the corresponding product code in the product display definition file F31 is deleted, and the product is removed from the products for sale online ( Step A119). Such deletion processing is repeated until the end of deletion is instructed. Here, when the end of deletion is instructed (step A120), the processing section can be selected (step A105 in FIG. 20).
[0086]
After the change processing for one page is performed in this way, the above-described display definition change processing can be executed for each page until “end display definition” is selected (step A121 in FIG. 21). Therefore, the process returns to step A102 in FIG. 20 to display the online merchandise display screen, and then accepts selection of the next change target page. Thereafter, the above-described changing operation is repeated for each selected page.
Here, when the end of “display definition change” is selected (step A121 in FIG. 21), the above-described processes in FIG. 17 are sequentially executed.
[0087]
That is, one page of the product display definition file F31 is designated (step A46), the net product record of the corresponding product is obtained from the linked product master file F5 from the product display definition file F31 corresponding to the designated page, and the net product master file. In addition to being stored in F33 (step A47), the corresponding product image is read from the image candidate file F7 based on the “image number” in the net product record acquired from the linked product master file F5 and stored in the net image file F32 ( Step A48).
When the storage process for one page is completed, an HTML page to which each product code is pasted according to the order of the product display definition is created, and this is stored again in the HTML file F12 (step A51). Thereafter, when the generation processing for all the pages is completed, the net product master file F33, the net image file F32, and the HTML file F12 are uploaded to the shopping mall site 1 (step A53).
[0088]
Next, with reference to FIGS. 22-24, the operation | movement in the case of changing the content of the goods master file F1 is demonstrated.
When the item “product master” is selected from the change menu screen described above (step A121 in FIG. 22), the online product registration module M2 is activated. Then, various product master files F1 prepared for each product genre are accessed, and the master list menu is displayed and output (step A122). When an arbitrary product master is selected and designated from the master list menu (step A123), the selected product master file F1 is accessed (step A124), and the selection of the processing category can be accepted. (Step A125).
Here, when an arbitrary category is selected from “add”, “modify”, and “delete” as the process category, the selected category is determined (step A126).
[0089]
Here, when adding a new product to the product master file F1, “add” is selected as the processing category. Then, a new product registration screen for product master is displayed and output (step A127). In this state, after inputting necessary item data in the new product registration screen (step A128) and performing an input confirmation operation (step A129), a product record is created based on the input data in the new product registration screen. The generated record is additionally registered as new product information in the product master file F1 (step A130). The process of adding and registering other new products is repeated until the process is instructed (steps A127 to A131).
[0090]
In addition, when “modify” is selected and specified as the processing category in order to correct the product information registered in the product master file F1, each product in the product master file F1 is listed (step A132 in FIG. 23). It is displayed (step A133). When the product to be corrected is selected from the product list screen (step A134), the product display definition file F31 is accessed based on the selected product, the “product code” of the product is searched, and the presence or absence of the product is present. Is discriminated (steps A135 and A136). That is, it is determined whether the product selected as the correction target is a product currently being sold on the Internet. Here, if the “product code” of the corresponding product is stored in the product display definition file F31, the product selected as the correction target is a product currently being sold online, so that the operator is notified of this fact. A correction warning message is displayed and output (step A137).
[0091]
After displaying this warning message, a correction execution request is accepted (step A138). If there is no execution request, the process proceeds to step A145 to cancel the correction process for the selected product, but the correction execution request is received. In the case where the corresponding product code is not stored in the product display definition file F31 (when the product code is not on the Internet), a product registration screen corresponding to the selected product is displayed and output (step A139). Of the product data displayed in the product registration screen, when an item to be corrected is specified and the data is corrected (step A140), the corresponding in the product master file F1 is based on the product code. The record is searched, and the content of the product record is updated based on the correction data (step A141).
[0092]
Then, in order to update the contents of the linked product master file F5 in conjunction with the correction of the product master file F1, the linked product master file F5 is searched based on the product code to determine whether the corresponding product code exists. (Steps A142, A143) If there is no corresponding code, the process proceeds to Step A145. If there is a corresponding product code, the contents of the net product record in the linked product master file F5 are updated based on the correction data (Step S142). A144). In this case, if the product selected as the correction target is a product being sold on the net, a process of updating the contents of the corresponding net product record in the net product master file F33 based on the correction data is also performed. Then, the process proceeds to step A145, where it is determined whether or not an instruction to end the process has been issued.
[0093]
In addition, when “Delete” is selected and specified as a processing category in order to delete the product information registered in the product master file F1, each product in the product master file F1 is listed (step A150 in FIG. 24). It is displayed (step A151). When a product to be deleted is selected from the product list screen (step A152), the product display definition file F31 is accessed based on the selected product, the “product code” of the product is searched, and the presence or absence of the product is present. Is discriminated (steps A152 and A153). Here, if the “product code” of the corresponding product is stored in the product display definition file F31, the product selected as the deletion target is a product currently being sold on the Internet, and therefore deletion of product information is prohibited. The deletion prohibition message shown is displayed and output (step A159).
[0094]
On the other hand, if the product selected for deletion is not a product currently on sale on the Internet (step A153), the corresponding record in the product master file F1 is searched based on the product code, and the product record is deleted (step A154). . Then, in order to delete the corresponding product record in the linked product master file F5 in conjunction with the deletion of the product master file F1, the linked product master file F5 is searched based on the product code, and there is a corresponding product code. (Step A155, A156) If there is no corresponding code, the process proceeds to Step A150. If there is a corresponding product code, the corresponding net product record in the linked product master file F5 is deleted (Step A157). . Then, the process proceeds to step A158, where it is determined whether the process end is instructed. The process returns to step A150 until the end instruction is given, and the above operation is repeated thereafter.
[0095]
If an instruction to end processing is given during the processing of “add”, “modify”, and “delete” for the product master file F1 (steps A131, A145, A158), the process returns to step A60 in FIG. The changed menu screen is redisplayed.
When the “end” menu item is selected in the change menu screen, this is detected in step A121 in FIG. 22, and the operation is terminated at this point in accordance with the net shop construction AP 22a.
[0096]
Next, an operation when the product purchaser terminal 4 accesses the shopping mall site 1 will be described with reference to FIGS. 25 and 26. FIG.
In response to the access from the product purchaser terminal 4, the shopping mall site 1 transmits a top page on which information for each net shop is posted to the requesting terminal (step B1), and then the user selects a desired net shop. A request is waited (step B2). Here, when a selection request is received from the product purchaser terminal 4, the HTML file F12, the net image file F32, and the net product master file F33 set corresponding to the net shop are referred to, and the corresponding net shop is supported. A process for creating a product information page is performed. FIG. 36 shows a product guidance page creation processing state. FIG. 36A shows a specific example of a product guide page created based on the HTML file F12, the net image file F32, and the net product master file F33. (B) is a diagram showing the contents of one page constituting the HTML file F12.
[0097]
First, the shopping mall site 1 accesses the HTML file F12 associated with the selected net shop, specifies the head HTML page (step B3), and is set in the specified HTML page. The online product master file F33 is accessed based on each product code, and an “image number” corresponding to each product code is acquired (step B4). The net image file F32 is accessed based on each “image number” acquired from the net product master file F33 in this way, the corresponding product image is read (step B5), and each product code is specified in the designated HTML page. A product image is pasted to the corresponding position (step B6).
[0098]
Furthermore, the online product master file F33 is accessed based on each product code set in the designated HTML page, and “product name”, “price”, and “product description” are read from each product code (step B7). In the designated HTML page, a product guide page is created with the contents pasted with the “product name”, “price”, and “product description” at the corresponding position of each product code (step 8). As a result, the product information page is a list of each product image in addition to its “page title”, and the page content with “product name”, “price”, and “product description” placed below each image. Thus, the product information page created in this way is transmitted to the product purchaser terminal 4 that is the request source (step B9).
[0099]
After transmitting the product information page, the shopping mall site 1 waits for a request from the product purchaser terminal 4 (step B10 in FIG. 26). Here, when a request from the product purchaser terminal 4 is received, it is determined whether the request is another page request (step B11) or a product selection request for purchasing a product (step B13).
If another page request is accepted (step B11), the requested page is designated (step B12), and then the process returns to step B4 in FIG. 25, and the HTML page corresponding to the requested page from the HTML file F12. Is specified, and a product guide page is created based on the HTML page.
[0100]
When a product to be purchased is selected (step B13), the online product master file F33 is accessed based on the product code of the selected product, and “product name” and “price” are acquired from the product record. Then, an order page in which the “product name” and “price” are inserted is created and transmitted to the requesting product purchaser terminal 4 (step B16).
FIG. 40B shows the order page screen. In this order page screen, the selected “net shop name”, “product name”, and “price” are displayed. As input items for input, “quantity”, “orderer name”, “address”, “phone number”, “mail address”, “destination name”, “destination address”, and so on are provided.
[0101]
When the product purchaser terminal 4 that has received this order page fills in the data of necessary items in the order page screen and returns it to the shopping mall site 1, the shopping mall site 1 returns from the product purchaser terminal 4. Is received (step B17), and the order record is stored in the order information file OF (step B18). After that, the system waits for a request from the product purchaser terminal 4 (step B10).
[0102]
If an end request is received (step B13), the order information file OF is accessed to check whether there is order information. If there is order information (step B14), all the order information is stored in each network. The information is read for each shop and transmitted to the corresponding store terminal (shop exhibitor PC) 2 (step B15).
In this case, when the order information from the shopping mall site 1 is received on the store terminal 2 side, the net order information acquisition module M5 is activated and the received order information is stored in the linked sales details file F6.
[0103]
FIG. 27 is a flowchart showing the operation when the net sales input AP 22b is activated in response to a request from the operator on the store terminal 2 side.
First, the store terminal 2 accesses the linked sales detail file F6, reads data for one record from the head (step C1), and performs customer registration processing based on this linked sales detail record (step C2).
In this customer registration process, a new customer (customer) through online sales is registered in the linked customer master file F8 for online sales, and registered in the customer master file F3 on the sales management system 21 side. In addition, the consistency between the customer master file F3 and the linked customer master file F8 is maintained.
[0104]
FIG. 28 is a flowchart detailing the customer registration process.
First, the store terminal 2 acquires “email address” from the record read from the linked sales details file F6 according to the net sales input AP 22b, and the corresponding record in the linked customer master file F8 based on this “mail address”. The contents are checked, and it is checked whether or not the customer having the corresponding “mail address” has already been registered (step D1). In other words, by searching the linked customer master file F8 using “mail address”, which is data unique to online sales, as a key, and determining whether the same “mail address” is registered, It is discriminated whether the customer has been used even once.
[0105]
As a result, if the same “e-mail address” is not registered in the linked customer master file F8 (step D2), the record is read from the linked sales description file F6 because it is the first customer for online sales this time. "Customer name" and "telephone number" are acquired from the inside, and the corresponding record contents in the customer master file F3 on the sales management system 21 side are checked based on the "customer name" and "telephone number" It is checked whether or not the customer having the “customer name” and “phone number” has been registered (step D3). That is, the customer master file F3 is searched using the “customer name” and “telephone number” that can specify the customer as keys, and it is determined whether the same “customer name” and “telephone number” are registered. By doing so, it is determined whether the customer has already used actual store sales or online sales even once (existing customer).
[0106]
Here, if it is not registered (step D4), since it is a new customer who has never used actual store sales or online sales, the process proceeds to step D5 to generate a “new customer code”. Then, the generated “customer code” and the “mail address” acquired from the linked sales detail record are additionally registered as a new record in the linked customer master file F8 (step D6), and this “customer code” The corresponding information (including the customer name, address, etc., including the mail address) acquired from the linked sales statement record is additionally registered as a new record in the customer master file F3 (step D7).
[0107]
If the same “e-mail address” has already been registered in the linked customer master file F8 (step D2), it is an existing customer who has used online sales. The corresponding “customer code” is read from the master file F8. Then, the customer master file F3 on the sales management system 21 side is searched based on this “customer code”, and “address”, “telephone number”, “mail address” are read out from this customer record and linked. “Address”, “telephone number”, and “mail address” are read out from the sales detail record, and these are correlated and displayed (step D11).
[0108]
In other words, “address”, “telephone number”, and “e-mail address” of customer information are data that may be changed. By displaying it, the operator is inquired whether there is a need to correct or update the registered contents. When an update request is received (step D12), the corresponding record contents in the customer master file F3 are corrected and updated based on the “address”, “phone number”, and “mail address” of the linked sales detail record. Is performed (step D13).
[0109]
If the same “customer name” and “telephone number” are registered in the customer master file F3 (step D4), the customer is an existing customer, but this is the first customer who has used online sales. Therefore, the process proceeds to step D9, and the “customer code” is read from the customer master file F3. Then, this “customer code” and the “mail address” of the linked sales detail record are additionally registered as a new record in the linked customer master file F8 (step D10). Thereafter, the above-mentioned “address”, “phone number”, and “mail address” are compared and displayed (step D11). When an update request is received (step D12), the contents of the corresponding record in the customer master file F3 are displayed. Is corrected and updated (step D13).
[0110]
When such customer registration processing is completed, the process proceeds to step C3 in FIG. 27, where the “total amount” is acquired from the linked sales detail record, and the customer master file F3 based on the “product code” of the linked sales detail record. To update the “total amount” acquired from the linked sales detail record to “cumulative sales amount” in the corresponding record of the customer master file F3. Further, an update process of adding “1” to “sales accumulated points” in the corresponding record of the linked customer master file F8 is performed (step C4).
Thereafter, a destination registration process is performed (step C5). This delivery destination registration process registers the delivery destination information in the linked delivery destination master file F9 for online sales when it is specified that the product purchased by the customer by online sales should be delivered to a third party. Registration processing for registration in the delivery destination master file F4 on the sales management system 21 side is performed, and consistency between the delivery destination master file F4 and the linked delivery destination master file F9 is maintained.
[0111]
FIG. 29 is a flowchart detailing the destination registration process.
Since this delivery destination registration process is basically the same as the customer registration process shown in FIG. 27 described above, the following description will focus on the characteristic part of this delivery destination registration process.
First, the “customer code” obtained in the above-mentioned customer registration processing step is acquired, and this “customer code” and a “destination name” obtained from the linked sales detail record are paired. Then, it is checked whether or not the “customer code” and “destination name” have been registered in the linked delivery destination master file F9 (steps E1, E2).
[0112]
If the “customer code” and “destination name” are not registered in the linked delivery destination master file F9 (step E2), the current delivery destination designated by the existing customer is the first delivery destination for online sales. Therefore, the process proceeds to step E3, and it is checked whether the “customer code” and the “delivery name” and “phone number” in the linked sales detail record are registered in the delivery master file F4 (steps E3 and E4). . Here, if the same “customer code”, “destination name”, and “telephone number” have already been registered in the delivery destination master file F4, the existing customer has requested delivery of the product in the past ( This is a case where the delivery of the product is requested again to the existing delivery destination), but if it is not registered, it is a delivery request to a new delivery destination that has not been requested to deliver the product in the past.
[0113]
If it is a new delivery destination, a “new delivery destination code” is generated (step E5). Then, the “customer code”, “new delivery destination code”, and “delivery destination name” acquired from the linked sales detail record are additionally registered as new records in the linked delivery destination master file F9 (step E6). The “destination code”, “new delivery destination code” and the corresponding information (customer name, customer address, etc.) acquired from the linked sales details are additionally registered as new records in the delivery destination master file F4 (step E7).
[0114]
If an existing customer who used online sales has requested delivery of the product to the existing delivery destination that has requested delivery of the product in the past (step E2), the linked delivery destination The corresponding “destination code” is read from the master file F9 (step E8). Then, the “address” and “phone number” in the delivery destination master file F4 corresponding to the “customer code” and “delivery destination code” are compared with the “address” and “phone number” in the linked sales detail record. Later (step E11), when an update request is received from the operator (step E12), the corresponding record in the delivery destination master file F4 is corrected and updated based on the “address” and “phone number” in the linked sales detail record. (Step E13).
[0115]
On the other hand, if the same “customer code”, “delivery name”, and “telephone number” are already registered in the delivery destination master file F4 (step E4), the existing customer has requested delivery of the product in the past. Since this is the case of a delivery request by online sales for the first time with respect to a certain existing delivery destination, the process proceeds to step E9, and the corresponding “delivery destination code” is read from the delivery destination master file F4. Then, the “customer code”, “shipping destination code” and “shipping destination name” in the linked sales detail record are additionally registered as new records in the linked shipping destination master file F9 (step E10). Thereafter, the above-mentioned “address” and “phone number” are compared and displayed (step E11). When an update request is received (step E12), the contents of the corresponding record in the delivery destination master file F4 are corrected and updated (step S12). Step E13).
[0116]
When such a delivery destination registration process is completed, the process proceeds to step C6 in FIG. 27, where “total amount” is acquired from the linked sales detail record and the delivery destination master file F4 is accessed based on the “product code” of the linked sales detail record. Then, the “total amount” acquired from the linked sales detail record is added and updated to the “accumulated amount by destination” in the corresponding record of the destination master file F4. Further, a slip record corresponding to the slip detail / slip total file F2 is created based on the contents of the linked sales detail record (step C7), and this slip record is additionally registered in the slip detail / slip total file F2 (step C8).
When the processing for one record is completed in this way, it is determined whether or not there is an unprocessed record in the linked sales detail file F6 (step C9), and if there is an unprocessed record, the process returns to step C1 and unprocessed. The record is read, and the above operation is repeated thereafter.
[0117]
FIG. 30 is a flowchart showing the operation of the store terminal 2 that is started to be executed in response to the activation of the sales management system 21 in the actual store sales ordering operation.
First, the store terminal 2 reads out the sales slip form according to the sales management system 21 and displays and outputs it (step F1), and the slip data (product code, quantity, customer code, delivery address code, etc.) relating to the sales product is stored. When input (step F2), a slip record is created based on the input slip data (step F3) and additionally registered in the slip details / slip total file F2 (step F4).
[0118]
Here, the designated state of the designated slip immediate processing / batch processing is discriminated (step F5), and when the slip immediate processing is designated, various slips for ordering work based on the created slip record. A process for printing (delivery form, transfer request form, home delivery slip, etc.) is performed (step F6), and various slip management processes for other business are performed based on this slip record (step F7).
Then, the “customer code” is acquired from the created slip record, the customer master file F3 is searched based on this “customer code”, the corresponding customer record is read (step F8), and the slip record The “total amount” acquired from the inside is added to the “cumulative sales amount” in the customer record to update the “cumulative sales amount” (step F9).
[0119]
Next, when the “delivery destination code” is included in the slip record (step F10), the “customer code” and “delivery destination code” are acquired from the slip record, and the “customer code” and “delivery destination” are acquired. The delivery destination master file F4 is searched based on the “code”, the corresponding delivery destination record is read (step F11), and the “total amount” acquired from the slip record is added to the “accumulated amount by delivery destination” in the delivery destination record. Then, the “cumulative amount by destination” is updated (step F12).
When batch processing is specified in step F5 described above, processing for updating the “cumulative sales amount” in the customer master file F3 is performed (steps F8 and F9). If the “destination code” is included in the slip record (step F10), processing for updating the “accumulated amount by destination” in the destination master file F4 is performed (steps F11 and F12).
[0120]
FIG. 31 shows the operation of the store terminal 2 when the sales management system 21 is started and started when a batch processing request from the operator is received or a slip processing request is received from the net order input module M6. It is a flowchart.
First, the slip details / slip total file F2 is accessed to read an unprocessed slip record (step G1), and various slips for ordering are printed based on the slip record (step G2). Based on the above, various business form slip management processes are executed (step G3).
Then, it is checked whether or not there is an unprocessed slip record in the slip description / slip total file F2 (step G4). If there is, the process returns to step G1 to perform slip printing / management processing based on the unprocessed record (step S4). G2, G3).
[0121]
As described above, in the store terminal 2 in this embodiment, in addition to the existing sales management system 21, the net shop construction / operation system 22 is constructed. When a product to be sold online is arbitrarily selected and specified from the product master file F1 for storing and managing product information, a product information page containing information on the selected product is created and the shopping mall site 1 side In addition, the order information of the net sales where the product was ordered at the net shop side is received, and the contents of the slip details / slip total file F2 are updated based on the order information. Without changing the sales management system 21 for the store, the network shop construction and operation system 22 can be easily made to the sales management system 21. It can be mobile, whereby it is possible to easily add the net sold as new sales unit.
[0122]
In this case, the net shop construction AP 22a is roughly divided into a net shop definition module M1, a net merchandise registration module M2, and a net merchandise display module M3. When a net shop is newly constructed, the work procedure is displayed on the screen. By sequentially starting the online shop definition module M1, the online product registration module M2, and the online product display module M3, the shop structure definition screen, online product registration screen, product master list screen, image list screen, display product registration screen, interlocking A series of work contents are guided while displaying the product list screen, and the net image file F32, the net product master file F33, and the HTML file F12 generated by this series of operations are uploaded to the shopping mall site 1 side as HTML web pages. Because it is loaded, it is possible to efficiently perform a series of operations associated with new construction, and even users who cannot fully use PCs or users who do not have knowledge of Web pages (low skill users) are unique to the store. It is possible to easily construct a net shop. In this case, by dividing the series of work into three stages, a person in charge with a necessary minimum skill can share the work for each stage.
[0123]
In addition to arbitrarily setting and specifying the page type prepared in advance, the page structure consisting of a plurality of product guide pages can be arbitrarily set, and the basic configuration content of the product guide page can be set arbitrarily. As a result, it is possible to obtain a product guide page with a store-specific design and configuration and to set a page structure composed of a plurality of product guide pages by arbitrarily selecting and specifying a page type prepared in advance. Therefore, the setting work can be easily performed.
[0124]
In addition, since each product arbitrarily selected from the product master file F1 on the sales management system 21 side is registered in the linked product master file F5 as an exhibition candidate for listing in the net shop, The sales target product can be directly used as a target product for online sales, and if such a linked product master file F5 is prepared in advance, it can be selected from the product candidate group in the linked product master file F5. By simply selecting and specifying a product, it is possible to prepare a product guide page with information on the product. In this case, since the exhibition candidate group in the linked product master file F5 is consistent with the product in the product master file F1, it is possible to prevent an accident such as the absence of a product ordered through online sales or a difference in product content. Is possible. Note that it is not necessary to change the record configuration of the product master file F1 by providing the linked product master file F5 separately from the product master file F1 on the sales management system 21 side.
[0125]
When the contents of the net shop are arbitrarily changed after the net shop is newly constructed, the net merchandise registration module M2 and the net merchandise display module M3 can be activated individually. For example, a new net shop is constructed. Even if it is a general store manager or store clerk who does not have special expertise, it is possible to easily replace the net product and change the display state thereafter.
[0126]
That is, even a general store manager or a store clerk can arbitrarily change the online sales product candidate group in the linked product master file F5 by independently starting the online product registration module M2, By starting the online product display module M3 independently, it is possible to arbitrarily select and specify a product to be sold online from a group of product candidates in the linked product master file F5 prepared in advance. Can be prepared in advance, and the merchandise display state can be arbitrarily set. For example, the merchandise display state can be appropriately changed according to consumption trends, sales promotions, and the like. In this way, even if a low-skill user can easily change the product or change the display state, it is possible to perform the work frequently, and keep the assortment and display state in the best condition at all times. And the opportunity to sell is not missed due to timing delays.
[0127]
Further, when an instruction to update the product master file F1 on the sales management system 21 side is given, if the product to be updated is a product currently on sale on the Internet, the product is handled in conjunction with the update of the product master file F1. Since the contents of the linked product master file F5 to be updated are updated, it is possible to always maintain the consistency between the product master file F1 and the linked product master file F5.
Further, when the product master file F1 is updated, if the product to be updated is a product being sold online, the update of the linked product master file F5 is prohibited, so that the product master file F1 and the product being sold online It is possible to always maintain the consistency of
[0128]
Since the linked product master file F5 is created based on the product master arbitrarily selected and specified from the product master file F1 prepared for each product genre, for example, a plurality of types of product genres are mixed. The linked product master file F5 can be created more easily and reliably than finding a product belonging to a desired product genre from such product masters and selecting it as a candidate for online exhibition.
When registering a candidate product for sale in the linked product master file F5, if the product to be registered is a new product that does not exist in the product master file F1, the product master is based on the input information about the new product. Since a product record for file F1 is created and this product record is additionally registered in product master file F1, consistency between product master file F1 and linked product master file F5 can be maintained, and the same data is duplicated. Therefore, it is not necessary to input, and the input operation can be performed efficiently.
[0129]
If you specify any product in the linked product master file F5 and change the information about that product, display a warning message for the change, and then change the information on that product on the condition that you received the change execution request. Since the contents of the corresponding linked product master file F5 are changed, it is possible to prevent the contents of the linked product master file F5 from being inadvertently changed.
When changing the contents of the linked product master file F5, if the product specified as the change target is a product being sold online, the change to that product is suppressed. The product in the product master file F5 can be matched.
[0130]
On the other hand, it is transmitted from the shopping mall site 1 to the sales management system 21 which stores the order information (slip data) input by the commercial transaction at the actual store in the slip details / slip total file F2 and executes various slip processes. Since the online sales order information can be stored in the slip statement / slip total file F2 and various slip processing can be executed, there is no burden of manually inputting the online sales order information, and there is a posting mistake, etc. In addition, it is possible to reliably process orders for online sales, and without changing the existing sales management system 21, in addition to the original ordering work, various bill processing such as billing work and payment management Internet sales order information can be linked to the sales management system 21, and management of online sales can be reflected in daily operations. To become.
[0131]
In the above-described embodiment, when a net shop is newly constructed, after displaying the work procedure on the screen, the net shop definition module M1, the net merchandise registration module M2, and the net merchandise display module M3 are sequentially activated. The work procedure is not limited to this. For example, the online product registration may be performed first prior to the online shop definition.
In addition, when the online shop is changed, the online product registration module M2 and the online product display module M3 can be activated individually. Furthermore, the online shop definition module M1 can also be activated individually to change the structure of the online shop. You may make it do.
When a background image, a title image, and a button image are set in each page by the net shop definition module M1, an arbitrary image may be selected and set from candidate images prepared in advance.
[0132]
Further, for each product arbitrarily selected as an online listing candidate from the product master file F1, the “product code”, “product name”, “sale price”, etc. are read from the product master file F1 and linked product master file F5. However, by registering only “product code” without registering items such as “product name” and “sales price” in the linked product master file F5, the product master file F1 and the linked product master are registered. The file F5 may be associated. In this case, at the time of online product display, the product master file F1 and the linked product master file F5 may be accessed to obtain the data of necessary items from the product master file F1.
[0133]
In order to match the product master file F1 and the linked product master file F5, not only when a new net shop is constructed, but also when a linked product master file F5 is changed, linked products not registered in the product master file F1 are linked. In the case of additional registration in the product master file F5, after displaying and outputting a message notifying that effect, information on this new product is provided subject to a request from the operator who has obtained the consent of the store manager, the manager, etc. You may make it additionally register to the goods master file F1.
Further, the process for matching the product master file F1 and the linked product master file F5 may be performed by batch processing under the supervision of a responsible person or the like.
[0134]
Furthermore, the present invention is not limited to the file management system that manages the various files described above, and can of course be applied to a database management system that manages them in a database. In this case, since it is not necessary to change the sales management system 21 and the net shop construction / operation system 22 in accordance with a change in the data structure, for example, addition or deletion of fields, a flexible response is possible.
[0135]
In addition, the sales management device as the store terminal 2 is not limited to the stand-alone type, and is a distributed device that transmits and receives data via a wired transmission line such as a communication line or a cable or a wireless transmission line such as radio waves, microwaves, and infrared rays. Type computer system. In this case, a store PC incorporating the sales management system 21 and a store PC incorporating the net shop construction / operation system 22 are provided, and data is transmitted to and received from each store PC so that they are linked. Also good.
Here, when applied to a client / server system, the net shop construction / operation system 22 may be incorporated in the server computer.
[0136]
The actual store is not limited to a small private store such as a stationery store or a fresh fish store, but may be a large-scale corporate store such as a discount shop, convenience store, supermarket, etc. It may be a store that performs.
In addition, the products handled by actual stores are not limited to tangible products, but may also be sold as intangible products such as music content, image content, and document content. It may be.
[0137]
On the other hand, a recording medium (for example, a CD-ROM, a floppy disk, a RAM card, etc.) on which a program code for executing each of the above-described units is recorded may be provided to the computer.
That is, a recording medium having a computer-readable program code, and a function for arbitrarily setting a configuration of a product guide page for the net shop side performing electronic commerce via the network to present to the customer; For each target product to be traded in a physical store, arbitrarily select and specify a product group of candidates for listing in the online store from the product master for the physical store that stores and manages the product information, and each A function for registering information related to products in the product master for the net shop, and a product for posting in the product information page of the set arbitrary configuration arbitrarily from the candidate product group in the product master for the net shop Sends a product information page with information about the selected and designated function and information about the selected and designated product to the online shop. It is also possible to provide the ability to.
[0138]
A computer-readable recording medium having a program code, which performs electronic commerce via a network from a merchandise master for a real store that stores and manages product information for each sale target product that is traded in a real store A product group as a candidate for listing to be sent to the online shop is arbitrarily selected and designated, and a function for registering information related to each product in the online product master and an optional product master for the online shop are selected. A function for creating a product information page containing information on products and sending it to the net shop side, and when updating the contents of the product master for the actual store, the product designated as the update target is the net shop A function to determine whether the product is on the online sales page posted on the product information page sent to When it is determined that the product is currently on sale, a function is provided to update the contents of the product master for the net shop corresponding to the product in conjunction with the update of the product master for the actual store. You may do it.
[0139]
A computer-readable recording medium having a program code, which performs electronic commerce via a network from a merchandise master for a real store that stores and manages product information for each sale target product that is traded in a real store A product group as a candidate for listing to be sent to the online shop is arbitrarily selected and designated, and a function for registering information related to each product in the online product master and an optional product master for the online shop are selected. A function for creating a product information page on which information related to a product is created and transmitting it to the net shop side, and when an update of the product master for the actual store is instructed, the product designated as the update target is the net A function to determine whether the product is being sold online that is posted on the product information page sent to the shop, If it Tsu is a trade in bets sales is determined, it may provide a function of inhibiting updates to the product master for the real shop for that product.
[0140]
【The invention's effect】
  According to the present invention, when correction of the product information stored and managed in the actual store product information storage means is instructed, if the correction target product is a net sales target product, the actual store product information storage means In conjunction with the correction, the contents of the net shop product information storage means corresponding to the product are corrected, and when deletion of the product information stored and managed in the actual store product information storage means is instructed, If the product to be deleted is a product to be sold online, the product information storage means for the actual store and the net shop are prohibited by prohibiting deletion of the product information stored and managed in the product information storage means for the actual store corresponding to the product. It is possible to always maintain consistency with the product information storage means.
[Brief description of the drawings]
FIG. 1 is a block diagram showing the overall configuration of a sales management network system.
FIG. 2 is a block diagram for explaining a basic system outline of the store terminal 2;
FIG. 3 is a diagram for explaining an operation concept of an online shop definition module M1, an online product registration module M2, and an online product display module M3 constituting the online shop construction AP 22a.
4A is a diagram showing a record configuration of a product master file F1, and FIG. 4B is a diagram showing a record configuration of a linked product master file F5.
FIG. 5 is a diagram showing a configuration of a product display definition file F31.
FIG. 6 is a diagram showing how various types of information obtained by building a net shop are uploaded to the shopping mall site 1 side.
FIG. 7 is a view showing the contents of a store-specific storage area E for storing and managing net shop construction information for each store on the shopping mall site 1 side.
8A is a diagram showing the contents of a store management table T provided on the shopping mall site 1 side, and FIG. 8B is a diagram showing the record structure of the order information file OF.
FIG. 9 is a diagram showing a list of various files provided on the sales management system 21 side and various files provided on the net shop construction / operation system 22 side.
10A is a diagram showing a record configuration of a customer master file F3, and FIG. 10B is a diagram showing a record configuration of a linked customer master file F8.
11A is a view showing a record configuration of a delivery destination master file F4, and FIG. 11B is a view showing a record configuration of a linked delivery destination master file F9.
FIG. 12 is a block diagram showing basic components of the store terminal 2;
FIG. 13 is a flowchart showing the operation of the store terminal 2 in response to the activation of the net shop construction AP 22a constituting the net shop construction / operation system 22.
FIG. 14 is a flowchart showing the operation at the time of building a net shop, following FIG. 13;
FIG. 15 is a flowchart illustrating the operation at the time of building a net shop, following FIG. 14;
FIG. 16 is a flowchart illustrating the operation at the time of building a net shop, following FIG. 15;
FIG. 17 is a flowchart showing the operation at the time of building a net shop, following FIG. 16;
FIG. 18 is a flowchart illustrating an operation at the time of building a net shop, following FIG. 13;
FIG. 19 is a flowchart illustrating an operation at the time of building a net shop, following FIG. 18;
FIG. 20 is a flowchart illustrating an operation at the time of building a net shop, following FIG. 18;
FIG. 21 is a flowchart illustrating an operation at the time of building a net shop, following FIG. 20;
FIG. 22 is a flowchart illustrating an operation at the time of building a net shop, following FIG. 20;
FIG. 23 is a flowchart illustrating an operation at the time of building a net shop, following FIG. 22;
FIG. 24 is a flowchart illustrating an operation at the time of building a net shop, following FIG. 23;
FIG. 25 is a flowchart showing the operation on the shopping mall site 1 side in response to access from the product purchaser terminal 4;
FIG. 26 is a flowchart showing the operation on the shopping mall site 1 side, following FIG. 25;
FIG. 27 is a flowchart showing the operation of the store terminal 2 in response to an online sales input AP 22b constituting the online shop construction / operation system 22.
FIG. 28 is a flowchart detailing a customer registration process shown in FIG. 27;
FIG. 29 is a flowchart detailing the destination registration process shown in FIG. 27;
30 is a flowchart showing the operation of the store terminal 2 in accordance with the sales management system 21. FIG.
FIG. 31 is a flowchart showing the operation of the store terminal 2 when a slip batch process is performed in accordance with the sales management system 21;
32A is a diagram showing a work procedure screen, and FIG. 32B is a diagram showing a shop structure definition screen.
FIG. 33 is a diagram showing a base screen for new net product registration.
FIG. 34 is a diagram showing a product list screen of a selection master (product master file F1).
FIG. 35 is a diagram showing an image list screen.
36A and 36B show a product guide page creation process state, where FIG. 36A shows a specific example of the created product guide page, and FIG. 36B shows the contents of one page constituting the HTML file F12. FIG.
FIG. 37 is a diagram showing an online product display <page list> screen.
FIG. 38 is a diagram showing a display product registration screen corresponding to a selection page.
FIG. 39 is a diagram showing a product list screen of a linked product master file F5.
40A is a diagram showing a change menu screen, and FIG. 40B is a diagram showing the contents of an order page.
[Explanation of symbols]
1 Shopping mall site
2 store terminals
3 network
4 Product purchaser terminal
21 Sales management system
22 Net shop construction and operation system
F1 product master file
F2 slip details and slip total file
F5 linked product master file
F6 linked sales details file
F11 Shop structure definition file
F12 HTML file
F31 Product display definition file
F32 net image file
F33 Net product master file
M1 online shop definition module
M2 online product registration module
M3 online merchandise display module
M4 upload module
M5 online order information acquisition module

Claims (2)

A store terminal connected via a network to a computer system that operates and manages a net shop to which a user terminal is connected via a network,
Product information storage means for the actual store that stores and manages the product information for each sale target product that is traded in the actual store,
Product information storage means for a net shop for storing and managing the product information for each product of a candidate product group to be exhibited in the net shop;
The product group of the candidate for exhibition to be exhibited in the online shop is arbitrarily selected and designated from the product information storage means for the actual store, and the product information relating to each product is read from the product information storage means for the actual store and is used for the network shop. Registration means for registering in the product information storage means;
Transmission means for reading product information of an item for sale on the Internet arbitrarily selected from the product information storage means for the net shop, creating a product guide page on which the product information is posted, and transmitting it to the computer system;
In accordance with a user operation, wherein if the modification or deletion of real shop for product information product information stored and managed in the storage means is instructed, or goods or the deleted items to be modified is the net sales Shipping Discriminating means for discriminating;
When it is determined by the determining means that the product to be corrected is the net sales target product, the product information stored and managed in the product information storage means for the actual store corresponding to the product is corrected, and this and updating means for modifying the product information that is stored and managed in the product information storage means net shop in conjunction with the modified corresponding to the product,
Update that prohibits deletion of product information stored and managed in the product information storage unit for the actual store corresponding to the product when the determination unit determines that the product to be deleted is the product for sale on the Internet Control means;
A store terminal characterized by comprising: Computer
Product information storage means for the actual store that stores and manages the product information for each sale target product that is traded in the actual store,
Product information storage means for a net shop for storing and managing the product information for each product of a candidate product group to be exhibited in the net shop,
A product group of candidate products to be exhibited in the online shop is arbitrarily selected and specified from the product information storage unit for the actual store, and product information relating to each product is read from the product information storage unit for the actual store and Registration means for registering in the product information storage means;
Transmission means for reading product information of an item for sale on the Internet arbitrarily selected from the product information storage means for the net shop, creating a product guide page on which the product information is posted, and transmitting it to the computer system;
If correction or deletion of the product information stored and managed in the actual store product information storage means is instructed in response to a user operation, whether the correction target product or the deletion target product is the net sales target product Discriminating means for discriminating,
When it is determined that the product to be corrected is the net sales target product by the determining unit, the product information stored and managed in the product information storage unit for the actual store corresponding to the product is corrected, and this updating means in conjunction with the corrected correcting the commodity information stored management in the product information storage means for said net shop corresponding to the product,
Update that prohibits deletion of product information stored and managed in the product information storage unit for the actual store corresponding to the product when the determination unit determines that the product to be deleted is the product to be sold online Control means,
Program to function as.

Images