JP2019028547A - Reservation management apparatus, reservation management method, and program - Google Patents

Abstract

To facilitate management of reservations accepted by a plurality of Web sites.SOLUTION: A reservation management apparatus 10 includes a login processing unit 12, a shop management screen generation unit 13, and a display processing unit 14. The login processing unit 12 accesses a plurality of Web server devices and collects reservation information indicating reservations accepted by each of Web sites managed by each of the Web server devices. The shop management screen generation unit 13 generates a shop management screen including the collected reservation information. The display processing unit displays the generated shop management screen on a shop terminal.SELECTED DRAWING: Figure 2

Description

  The present invention relates to a reservation management apparatus, a reservation management method, and a program.

  In recent years, it is known to connect a user terminal used by a user to the Internet and make a reservation for a store (or facility) such as a restaurant via a Web site, for example.

  In this case, the user accesses a Web server device that manages the above-described Web site from user terminals such as a personal computer (PC), a smartphone, and a tablet terminal, and inputs information necessary for the reservation, thereby making a reservation for the store. It can be carried out.

  On the other hand, a store terminal (personal computer or the like) is installed at a store reserved via the website, and employees of the store can make reservations (information) received at the website via the store terminal. Can be confirmed.

Japanese Patent Laid-Open No. 2017-084241

  By the way, the websites that can accept reservations for the above-described stores are diversified, and there are various websites.

  In this case, in order for the store to acquire many reservations, it is necessary to receive reservations via a plurality of Web sites.

  However, since the reservation management screen is different for each Web site, it is necessary to sequentially check the management screen of each Web site when checking the reservation status, which is troublesome.

  For example, when a reservation is received via the website A, it may be necessary to update the status of a seat or table that can be reserved on the website B. Even in this case, store employees and the like need to perform an update operation on the management screen of the website B.

  Therefore, the problem to be solved by the present invention is to provide a reservation management apparatus, a reservation management method, and a program capable of facilitating management of reservations accepted at a plurality of Web sites.

  According to one aspect of the present invention, the first and second server devices that manage each of the different first and second Web sites for receiving a reservation for a store and the store terminal provided in the store communicate with each other. A reservation management device that can be connected is provided. The reservation management apparatus includes a collection unit, a generation unit, and a display processing unit. The collection means accesses the first and second server devices, and receives reservations accepted by the first and second Web sites managed by the first and second server devices, respectively. The first reservation information shown is collected. The generation unit generates a store management screen including the collected first reservation information. The display processing means displays the generated store management screen on the store terminal.

  The present invention makes it easy to manage reservations accepted at a plurality of Web sites.

The figure which shows an example of a structure of the network system containing the reservation management apparatus which concerns on embodiment of this invention. The block diagram which mainly shows a function structure of a reservation management apparatus. The flowchart which shows an example of the process sequence of the reservation management apparatus at the time of starting cooperation with a reservation management apparatus and a Web server apparatus. The figure which shows an example of a login information registration screen. The figure which shows an example of the data structure of the seat information stored in the storage part. The figure which shows an example of the data structure of the reservation information stored in the storage part. The figure which shows an example of the shop management screen displayed on the shop terminal. The flowchart which shows an example of the process sequence of the reservation management apparatus when a user makes a new reservation with respect to a handling store via a website. The flowchart which shows an example of the process sequence of the reservation management apparatus when the user changes the content of the reservation to the object store received on the website. The flowchart which shows an example of the process sequence of the reservation management apparatus when a user cancels the reservation received at the target store via a Web site. The flowchart which shows an example of the process sequence of the reservation management apparatus in case registration of a new reservation is performed by the shop terminal side. The figure which shows an example of a reservation registration screen. The flowchart which shows an example of the process sequence of the reservation management apparatus in case a reservation change is performed by the shop terminal side. The flowchart which shows an example of the process sequence of the reservation management apparatus in case cancellation of a reservation is performed by the shop terminal side. The flowchart which shows an example of the process sequence of the reservation management apparatus when a user makes a request reservation with respect to an object store via a website. The flowchart which shows an example of the process sequence of the reservation management apparatus when a request reservation is accepted. The figure which shows an example of a request reservation confirmation screen. The flowchart which shows an example of the process sequence of the reservation management apparatus when a request reservation is refused. The flowchart which shows an example of the process sequence of the reservation management apparatus at the time of adjusting vacant seat information. The figure for demonstrating specifically the case where it is necessary to adjust vacant seat information, and the case where it is not necessary to adjust vacant seat information.

Embodiments of the present invention will be described below with reference to the drawings.
FIG. 1 shows an example of the configuration of a network system (reservation management system) including a reservation management apparatus according to the present embodiment. The reservation management apparatus according to the present embodiment is used to realize collective management (Web reservation management) of reservations to stores such as restaurants, which are performed via a plurality of Web sites.

  As shown in FIG. 1, the reservation management apparatus 10 includes a computer (server computer) 10a and a storage device 10b. The computer 10a includes a processor such as a CPU, for example. The storage device 10b includes, for example, a hard disk drive (HDD), a solid state drive (SSD), a read only memory (ROM), or a random access memory (RAM).

  The reservation management apparatus 10 is communicably connected to a plurality of Web server apparatuses via a network such as the Internet. In FIG. 1, only the web server devices 20a and 20b are shown as a plurality of web server devices for the sake of convenience, but the reservation management device 10 may be communicably connected to three or more web server devices.

  The web server devices 20a and 20b manage websites for accepting reservations for stores, and provide users with services (hereinafter referred to as web reservation services) that accept reservations for various stores via the websites. . Note that the Web server devices 20a and 20b manage different Web sites.

  The reservation management apparatus 10 can communicate with a store terminal 30 installed in a store that can be reserved via each of the Web sites managed by the Web server devices 20a and 20b via a network such as the Internet. Connected.

  The store terminal 30 is a terminal for displaying a store management screen for the employees of the store to confirm the status of the Web reservation for the store where the store terminal 30 is provided. For example, a personal computer (PC) Including smartphones and tablet computers.

  In FIG. 1, only one store terminal 30 is shown for convenience, but the reservation management apparatus 10 passes through various Web sites including Web sites managed by the Web server devices 20 a and 20 b described above. Are connected so as to be communicable with store terminals installed in each of a plurality of stores that can be reserved.

  In the following description, it is assumed that the store where the store terminal 30 is installed can be reserved via two Web sites managed by each of the Web server devices 20a and 20b. In this case, for convenience, the Web site managed by the Web server device 20a is the Web site A, the Web site managed by the Web server device 20b is the Web site B, and the store where the store terminal 30 is installed is targeted. This is called a store.

  FIG. 2 is a block diagram mainly showing a functional configuration of the reservation management apparatus 10 shown in FIG. As shown in FIG. 2, the reservation management apparatus 10 includes a storage unit 11, a login processing unit 12, a store management screen generation unit 13, a display processing unit 14, and a mail analysis unit 15.

  In the present embodiment, the storage unit 11 is stored in, for example, the storage device 10b described above. In the present embodiment, the login processing unit 12, the store management screen generation unit 13, the display processing unit 14, and the mail analysis unit 15 execute, for example, a program stored in the storage device 10b by the computer 10a illustrated in FIG. (Ie, software). This program may be stored in advance in a computer-readable storage medium and distributed, or may be downloaded to the reservation management apparatus 10 via a network. Each of these units 12 to 15 may be realized by hardware (for example, an IC or the like).

  The storage unit 11 stores information for logging in to each of the Web sites A and B managed by the Web server devices 20a and 20b (hereinafter referred to as login information). This login information includes a login ID and a password.

  The login processing unit 12 acquires login information stored in the storage unit 11. The login processing unit 12 accesses the Web server devices 20a and 20b and logs in to the Web sites A and B using the acquired login information sequentially. As a result, the login processing unit 12 collects reservation information indicating a reservation for the target store accepted on the website A. In addition, the login processing unit 12 collects reservation information indicating reservations (contents) to the target store accepted at the website B. The reservation information collected by the login processing unit 12 is stored in the storage unit 11.

  The store management screen generation unit 13 generates a store management screen including reservation information stored in the storage unit 11. The store management screen is a screen for confirming the reservation status (Web reservation status) for the target store by the employees of the target store as described above.

  The display processing unit 14 displays the store management screen on the store terminal 30 by transmitting the store management screen (data) generated by the store management screen generating unit 13 to the store terminal 30.

  Here, a user who uses the Web reservation service can make a new reservation, change a reservation, cancel a reservation, and the like for the target store via Web sites A and B. Thereby, for example, when a new reservation for the target store is accepted at the Web site A, the Web server device 20a that manages the Web site A transmits an email to the email address of the user registered in advance. Similarly, when a change in reservation and a cancellation of the reservation are accepted on the Web site A, an email for notifying that is transmitted. Here, the Web site A (Web server device 20a) has been described, but the same applies to the Web site B (Web server device 20b).

  The mail analysis unit 15 analyzes the mail transmitted by the web server devices 20a and 20b. Based on the analysis result, the mail analysis unit 15 identifies a website that has accepted a new reservation, a change in reservation, or a cancellation of the reservation.

  In this case, the login processing unit 12 uses the login information stored in the storage unit 11 to log in to the Web site specified by the mail analysis unit 15. The login processing unit 12 acquires information indicating a new reservation, a reservation change, or a reservation cancellation for the target store accepted by the logged-in Web site. Here, the information acquired by the login processing unit 12 is used for updating vacant seat information on other websites and updating a store management screen, which will be described later.

  Hereinafter, the operation of the reservation management apparatus 10 according to the present embodiment will be described. As described above, the reservation to the target store can be accepted at the Web sites A and B. In this case, different login information issued from each of the websites A and B is assigned to the target store. The login information is information for logging in to the websites A and B. The login information includes a login ID and a password, but the login ID and password may be specified on the target store side.

  Here, in order for the target store to use the Web reservation management by the reservation management apparatus 10 according to the present embodiment, login information for logging in to the Web sites A and B assigned to the target store (hereinafter simply referred to as “reservation information”). It is necessary to register the login information of the Web site) and start the cooperation between the reservation management apparatus 10 and the Web server apparatuses 20a and 20b.

  First, an example of a processing procedure of the reservation management apparatus 10 when starting cooperation between the reservation management apparatus 10 and the Web server apparatuses 20a and 20b will be described with reference to a flowchart of FIG.

  In this case, the display processing unit 14 included in the reservation management apparatus 10 displays a screen for registering login information of each Web site (hereinafter referred to as a login information registration screen) on the store terminal 30 (step S1).

  Here, FIG. 4 shows an example of a login information registration screen. On the login information registration screen shown in FIG. 4, login information of a plurality of websites including websites A and B can be registered.

  As shown in FIG. 4, the login information registration screen 100 includes a login ID column 101 and a password column 102 for each Web site.

  As described above, since the target store has the login information of the websites A and B, the employees of the target store log in to the login ID column 101 and the password column 102 corresponding to the website A. The ID and password are input, and the login ID and password of Web site B are input to the login ID column 101 and password column 102 corresponding to Web site B.

  It should be noted that reservations to the target store can be accepted at other websites other than websites A and B, and if there is login information of the other websites, the other websites. The login information is also registered on the login information registration screen 100.

  As described above, when the input to the login information registration screen 100 is completed, the login information (here, the login information of the websites A and B) input on the login information registration screen 100 is reserved from the store terminal 30. Sent to device 10.

  Returning to FIG. 3, the reservation management apparatus 10 receives the login information transmitted from the store terminal 30 (step S2). The login information received by the reservation management apparatus 10 is stored in the storage unit 11.

  Next, the login processing unit 12 performs the following steps S <b> 3 to S <b> 5 for each login information stored in the storage unit 11. Here, the login information of the website A will be mainly described.

  In this case, the login processing unit 12 logs in to the website A using the login information of the website A (step S3).

  Here, in the Web site A (the Web server device 20a that manages the Web site A), the seat information indicating the seat (table) of the target store for which the presence or absence of reservation is managed in the Web site A, the seat indicated by the seat information Among them, reservation information indicating reservations that have already been received on the website A, vacant seat information that indicates seats that can be reserved at the present time (that is, vacant seats), and the like are held.

  The login processing unit 12 acquires seat information and reservation information held in the Web site A logged in in step S3 (step S4).

  The seat information and reservation information acquired in step S4 are stored in the storage unit 11 (step S5).

Although the login information of the website A has been described here, the same processing is executed for the login information of the website B, and the storage unit 11 stores the seat information and reservation information held in the website B. Is done.

  Here, FIG. 5 shows an example of the data structure of the seat information stored in the storage unit 11. Here, the seat information acquired from the website A will be described.

  As shown in FIG. 5, the seat information includes the seat type and the number of people that can be used in association with the seat ID.

  The seat ID is identification information for identifying a seat of a target store whose presence or absence of reservation is managed on the website A (that is, a seat assigned to the website A).

  The seat type indicates the seat type identified by the seat ID associated with the seat type, and includes, for example, a table, a parlor, a round table, and the like.

  The available number of people indicates the number of people (maximum number and minimum number of people) who can use the seat (table, parlor, round table, etc.) identified by the seat ID associated with the available number of people.

  In the example illustrated in FIG. 5, the seat information acquired from the website A includes seat information 111a and 111b.

  The seat information 111a includes the seat type “table 1” and the available number of people “4” in association with the seat ID “1”. According to the seat information 111a, the presence / absence of reservation is managed on the website A identified by the seat ID “1” (that is, the seat assigned to the website A) is the seat of “table 1”. It is shown that the number of people who can use the table is four.

  The seat information 111b includes a seat type “table 2” and an available number of people “8” in association with the seat ID “2”. According to the seat information 111b, the seat whose presence or absence of reservation is managed on the Web site A identified by the seat ID “2” is the seat of “table 2”, and the number of people who can use the table is 8. It has been shown.

  Although only the seat information 111a and 111b has been described here, all the seat information acquired from the website A is stored in the storage unit 11.

  In addition, although the seat information acquired from the website B is also stored in the storage unit 11, the data structure of the seat information is the same as the data structure described in FIG. To do.

  It should be noted that at least a part of the seats of the target store where the presence / absence of reservation is managed on the website A and the seats of the target store where presence / absence of the reservation is managed on the website B may overlap. Different seats may be assigned to the Web sites A and B so as not to be.

  The seats of the target stores where the presence / absence of reservations on the website A are managed in advance on the website A. Similarly, the seats of the target stores whose presence / absence of reservation is managed on the website B are set in advance on the website B. In addition, the seat of the target store where the presence or absence of reservation is managed on the websites A and B can be changed by, for example, an employee of the target store who operates the store terminal 30.

  FIG. 6 shows an example of the data structure of the reservation information stored in the storage unit 11. Here, reservation information acquired from the website A will be described.

  As shown in FIG. 6, the reservation information includes a name, an e-mail address, a use date and time, the number of people, and a seat ID in association with the reservation ID.

  The reservation ID is identification information assigned to a reservation received on the website A.

  The name is the name of the user who made the reservation identified by the reservation ID associated with the name.

  The email address is the email address of the user who made the reservation identified by the reservation ID associated with the email address.

  The use date and time is the use start date and time of the target store designated by the user in the reservation identified by the reservation ID associated with the use date and time (that is, the planned date and time of entering the target store).

  The number of people is the number of users of the target store designated by the user in the reservation identified by the reservation ID associated with the number of people.

  The seat ID is identification information for identifying the seat of the target store specified by the user in the reservation identified by the reservation ID associated with the seat ID (that is, the reserved seat).

  In the example shown in FIG. 6, the reservation information acquired from the website A includes reservation information 112a and 112b.

  In the reservation information 112a, the name “XXX”, the mail address “Mail address 1”, the use date “5/27 19:00”, the number of people “4”, and the seat ID “1” are associated with the reservation ID “1”. 1 ”is included. According to this reservation information 112a, a reservation that uses four seats identified by the seat ID “1” of the target store from 19:00 on May 27 is made by a user whose name is “XXX”. It has been shown that. Further, it is indicated that the mail address of this user is “mail address 1”.

  The reservation information 112b is associated with the reservation ID “2”, the name “xxxx”, the mail address “mail address 2”, the use date “5/27 19:30”, the number of people “6”, and the seat ID “6”. 2 ”is included. According to this reservation information 112b, a user who uses the seat identified by the seat ID “2” of the target store with 6 people from 19:30 on May 27th, whose name is “xxxx” It has been shown that Further, it is indicated that the mail address of this user is “mail address 2”.

  Although only the reservation information 112a and 112b has been described here, the storage unit 11 stores all the reservation information acquired from the website A.

  In FIG. 6, the reservation information has been described as including a reservation ID, name, e-mail address, use date / time, number of people, and seat ID, but the reservation information may include other information. Specifically, the reservation information may include a telephone number, a course (cooking) designated by the user at the time of reservation, or information about the user (such as age and gender).

  In addition, although the reservation information acquired from the website B is also stored in the storage unit 11, the data structure of the reservation information is the same as the data structure described with reference to FIG. To do.

  In addition, according to the seat information described in FIG. 5 and the reservation information described in FIG. 6, it is possible to grasp the reserved seat and the use date and time of the seat among the seats prepared in the target store. Can do.

  Returning to FIG. 3 again, the store management screen generation unit 13 generates a store management screen for displaying the reservation status for the target store based on the seat information and reservation information stored in the storage unit 11 (step S6). ). In this case, the store management screen generation unit 13 generates a time table for each seat prepared in the target store based on the seat information (seat information acquired from each of the websites A and B). The store management screen generation unit 13 generates a store management screen by associating reservations indicated by reservation information (reservation information acquired from each of the websites A and B) with the generated time table. .

  The display processing unit 14 transmits the store management screen (data) to the store terminal 30 in order to display the store management screen generated in step S6 on the store terminal 30 (step S7). Thereby, the store management screen is displayed on the store terminal 30.

  Here, FIG. 7 shows an example of a store management screen displayed on the store terminal 30. As shown in FIG. 7, the store management screen 200 includes a date display area 201, a seat information display area 202, a reservation information display area 203, and the like.

  In the date display area 201, for example, the current date is displayed. In this case, the reservation status on the current date (that is, today) can be confirmed on the store management screen 200.

  In the seat information display area 202, a list of seats prepared in the target store (here, store X) is displayed.

  In the reservation information display area 203, whether or not there is a reservation for each of the seats prepared in the target store (that is, the seat displayed in the seat information display area 202) is displayed on the date displayed in the date display area 201. Displayed in association with each time zone.

  In the example shown in FIG. 7, it is shown that the seats of “Table 1” among the seats prepared in the target store are reserved by 4 persons from 19:00. In addition, among the seats prepared in the target store, the seat of “Table 2” has been reserved by 6 persons from 19:30. In addition, among the seats prepared in the target store, the seats of “Table 3” are not currently reserved. In addition, among the seats prepared in the target store, the seat of “tatami room 1” is shown to be reserved for 10 persons from 20:00. The request reservation will be described later.

  Here, among reservations (information) displayed in the reservation information display area 203, reservations surrounded by a solid line and hatched are already entered by the user (including the group) who made the reservation. Indicates that it has been completed. On the other hand, among the reservations displayed in the reservation information display area 203, reservations surrounded by a solid line and not hatched are not yet entered by the user (including the group) who made the reservation. Indicates. It should be noted that the employee of the target store can input whether or not the user who made the reservation displayed on the store management screen 200 has entered the store by operating the store terminal 30.

  In addition, in the store management screen 200, as shown in FIG. 7, information on reservation routes (for example, Web sites A and B) for each reservation displayed in the reservation information display area 203 is also added. . According to this, for example, it is possible to easily grasp the status of reservation accepted at the websites A and B (that is, the effect of using the websites A and B, etc.). The reservation route information can be added to the reservation information and stored in the storage unit 11 according to the reservation information acquisition destination (Web sites A and B, etc.).

  In addition, in the store management screen 200 shown in FIG. 7, the reservation status from 19:00 to 21:00 on May 27 (Saturday) is displayed. By scrolling, it is possible to display the reservation status in other time zones. For example, when the date display area 201 is specified on the store management screen 200, a calendar is displayed, and reservation information on the date specified in the calendar can be displayed.

  By confirming the store management screen 200 described above, employees of the target store can collectively manage and grasp reservations accepted at each of a plurality of websites (for example, websites A and B). It becomes.

  Here, the user using the Web reservation service may make a new reservation for the target store via the Web site A, for example, using a user terminal (personal computer, smartphone, tablet computer, etc.) possessed by the user. it can.

  Hereinafter, with reference to the flowchart of FIG. 8, for example, a processing procedure of the reservation management apparatus 10 when the user makes a new reservation to the target store via the website A will be described. Here, it is assumed that the store terminal 30 is in a state in which the store management screen is displayed by executing the process shown in FIG.

  As described above, when the user makes a new reservation to the target store via the website A, information indicating the contents of the new reservation (hereinafter referred to as new reservation information) is held in the website A. A mail for notifying that the new reservation has been accepted (hereinafter referred to as a reservation completion mail) is transmitted from the Web server device 20a to the user. Note that the new reservation information includes, for example, a name, an e-mail address, a use date and time, the number of people, a seat ID, and the like in association with the reservation ID, similarly to the reservation information described in FIG. In addition, the reservation completion mail includes information indicating a Web reservation service (here, Web site A) that has received a reservation for the target store. A mail address included in the new reservation information is used to transmit the reservation completion mail from the Web server device 20a to the user.

  In the Web server device 20a, it is assumed that the email address of the reservation management device 10 is registered as the transmission destination of the email (for example, the reservation completion email) from the Web server device 20a. According to this, the mail from the Web server device 20a is also transmitted to the reservation management device 10 in addition to the user. Here, only the mail transmitted from the Web server apparatus 20a has been described, but the same applies to the mail transmitted from the Web server apparatus 20b.

  As described above, when the reservation completion mail is transmitted from the Web server device 20a, the reservation management apparatus 10 receives the reservation completion mail (step S11).

  The mail analysis unit 15 analyzes the reservation completion mail received in step S11. According to this, the mail analysis part 15 specifies the Web site (here, Web site A) on which the user has made a reservation from information indicating the Web reservation service included in the reservation completion mail (step S12).

  Next, the login processing unit 12 acquires the login information of the website A specified in step S12 from the storage unit 11, and logs in to the website A using the login information (step S13). Note that the process (login process) in step S13 may be executed by a crawler, an API, or the like. Hereinafter, the process of logging in to the websites A and B is the same.

  Here, as described above, the Web site A holds new reservation information indicating the contents of the new reservation. For this reason, the login processing unit 12 acquires new reservation information held in the Web site A logged in in step S13 (step S14).

The new reservation information acquired in step S14 is stored in the storage unit 11 (step S15). In addition, when the new reservation information acquired in step S14 is different from the format of the reservation information stored in the storage unit 11 (that is, the format that can be displayed on the store management screen), the new reservation information is appropriately processed. It may be edited. The same applies to various types of information stored in the storage unit 11 described below.
When the process of step S15 is executed, the processes of steps S16 and S17 described below and the processes of steps S18 and S19 are executed in parallel.
In this case, the store management screen generation unit 13 generates a store management screen based on the new reservation information (and the seat information and other reservation information) stored in the storage unit 11 (step S16).
When the process of step S16 is executed, the display processing unit 14 transmits the store management screen (data) to the store terminal 30 in order to display the store management screen generated in the step S16 on the store terminal 30. (Step S17). Thereby, the store management screen displayed on the store terminal 30 is updated to a store management screen reflecting the new reservation information.

  On the other hand, the login processing unit 12 acquires login information of a Web site (here, Web site B) different from the Web site A specified in step S12 from the storage unit 11, and uses the login information to acquire a Web site. Login to site B (step S18).

  The login processing unit 12 updates the vacant seat information (inventory information) held in the Web site B logged in in step S18 based on the new reservation information acquired in step S14 (step S19).

  Here, the vacant seat information held in the Web site B refers to information indicating a vacant seat that has not yet been reserved among the seats of the target store whose presence or absence of reservation is managed in the Web site B as described above. The seats indicated by the vacant seat information (vacant seats) do not include seats that have already been reserved and seats that cannot be reserved.

In the process of step S19, for example, the seat identified by the seat ID included in the new reservation information (hereinafter referred to as a new reserved seat on the website A) is indicated by the seat information held on the website B ( That is, it is determined whether the seat is assigned to the website B. In other words, it is determined whether or not the newly reserved seat of the website A is managed for the website B as well.
In addition, when the same seat is managed (assigned) in the website A and the website B, the same seat managed in the website A and the website B is linked in advance so as to be associated with each other. It is possible to set it.

  When the new reserved seat of the Web site A is not managed by the Web site B, it is not necessary to update the vacant seat information held in the Web site B according to the new reserved information (new reservation indicated by). In this case, the process of step S19 is omitted.

  On the other hand, when the new reserved seat is managed on the website B, the login processing unit 12 assumes that a reservation having the same content as the content of the new reservation information has been accepted also on the website B. The seat availability information is updated so that reservations cannot be made.

  According to the processing in step S19, the website B (another reservation seat) is reserved so that a duplicate reservation is not made via the website B for a seat for which a new reservation is accepted on the website A (new reserved seat). It is possible to automatically update the vacant seat information of the Web site.

  Here, for example, when a new reservation is accepted at the website A, the vacant seat information is updated so that a new reserved seat cannot be reserved even at the website B. In the case of a single seat (table, parlor, etc.), it is possible to accept different reservations if the time zone is different. For this reason, vacant seat information is managed in consideration of the concept of time.

  Specifically, it is assumed that the user uses a store for a predetermined time (hereinafter referred to as a use period) from the use date and time included in the new reservation information indicating the new reservation. Note that the usage period (stay period) may be a predetermined period, may be set by an employee of the target store via the store terminal 30, or the course (cooking) in the new reservation. May be set according to the course.

  In this case, when the usage period starting from the usage date and time included in the new booking information (hereinafter referred to as the usage period for the new booking) is excluded from the time zones in which the websites A and B can accept the booking, If there is time (vacant time) that can accept a reservation that is assumed to use the store for the length of the usage period, even if it is a newly reserved seat, it is possible to make a reservation in that empty time Update the seat availability information. On the other hand, when the use period by the new reservation is excluded and there is no vacant time for accepting another reservation, the vacant seat information is updated on the assumption that the new reserved seat cannot be reserved.

  Here, the case where a new reservation is accepted has been described, but the management of vacant seat information on the Web sites A and B is performed based on the same concept even in other cases described later.

  For example, depending on the specifications of Web site A (Web server device 20a), various information related to the new reservation (for example, reservation ID, user name, use date and time, number of people, and seat ID) are described in the reservation completion mail. May have been. In other words, information corresponding to the new reservation information acquired in step S14 may be acquired from the analysis result of the reservation completion mail by the mail analysis unit 15. In this case, the configuration may be such that the processing of step S13 is omitted, and new reservation information (information corresponding thereto) is acquired without logging in to the website A.

  Although the case where the user makes a new reservation for the target store via the website A has been described in FIG. 8, the user changes the content of the reservation for the target store accepted at the website A, for example. Alternatively, it is possible to cancel the reservation.

  Hereinafter, with reference to the flowchart of FIG. 9, for example, the processing procedure of the reservation management apparatus 10 when the user changes the content of the reservation for the target store accepted at the website A will be described.

  As described above, when the user changes the content of the reservation to the target store accepted on the website A, information indicating the content of the reservation change (hereinafter referred to as changed reservation information) is held on the website A. At the same time, a mail for notifying that the change of the reservation has been accepted (hereinafter referred to as a change completion mail) is transmitted from the Web server device 20a to the user. The changed reservation information is obtained by changing a part of the reservation information described in FIG. 6 (that is, information indicating the details of the reservation made by the user), and is associated with the reservation ID, for example. Includes name, email address, date and time of use, number of people and seat ID. The change completion mail includes information indicating a Web reservation service (here, Web site A) that has received a reservation change for the target store. A mail address included in the change reservation information is used to transmit the change completion mail from the Web server device 20a to the user.

  Note that, similarly to the reservation completion mail described above, the change completion mail from the Web server device 20a is also transmitted to the reservation management apparatus 10. For this reason, the reservation management apparatus 10 receives a change completion mail from the Web server apparatus 20a (step S21).

  The mail analysis unit 15 analyzes the change completion mail received in step S21. According to this, the mail analysis part 15 specifies the Web site (here, Web site A) on which the user has changed the reservation from the information indicating the Web reservation service included in the change completion mail (step S22).

  Next, the login processing unit 12 acquires the login information of the website A identified in step S22 from the storage unit 11, and logs in to the website A using the login information (step S23).

  Here, as described above, the Web site A holds the change reservation information indicating the change contents of the reservation. For this reason, the login processing unit 12 acquires the change reservation information held in the website A logged in in step S23 (step S24). The changed reservation information is a part of reservation information (hereinafter referred to as reservation information before the change) indicating the details of the reservation that has already been made as described above, such as the use date, number of people, seat ID, etc. Information.

  The reservation information before the change (that is, the reservation information before the contents are changed) stored in the storage unit 11 is changed to the changed reservation information acquired in step S24 (step S25).

Here, although a plurality of reservation information is held in the Web site A, as described above, the changed reservation information is information obtained by changing a part of the reservation information before the change. For this reason, for example, the reservation ID before the change and the reservation ID included in the changed reservation information match. Therefore, the reservation information before the change can be specified based on the reservation ID included in the changed reservation information.
When the process of step S25 is executed, the processes of steps S26 and S27 described below and the processes of steps S28 and S29 are executed in parallel.
In this case, the store management screen generation unit 13 generates a store management screen based on the changed reservation information (and the seat information and other reservation information) stored in the storage unit 11 (step S26).
When the process of step S26 is executed, the display processing unit 14 transmits the store management screen (data) to the store terminal 30 in order to display the store management screen generated in the step S26 on the store terminal 30. (Step S27). Thereby, the store management screen displayed on the store terminal 30 is updated to the store management screen in which the change reservation information is reflected.

  On the other hand, the login processing unit 12 acquires login information of a Web site (here, Web site B) different from the Web site A identified in step S22 from the storage unit 11, and uses the login information to perform Web access. Login to site B (step S28).

  The login processing unit 12 updates the vacant seat information (inventory information) held in the Web site B logged in in step S28 based on the changed reservation information acquired in step S24 (step S29).

  Hereinafter, for example, the process of step S29 when the user changes the seat reserved on the website A will be described.

  In the process of step S29, for example, the seat identified by the seat ID included in the change reservation information (hereinafter referred to as the change reservation seat of the website A) is indicated by the seat information held in the website B ( That is, it is determined whether the seat is assigned to the website B. In other words, it is determined whether the reservation reservation of the website A is managed even if the website B is the reserved seat.

  When the changed reserved seat of the website A is not managed by the website B, it is not necessary to update the vacant seat information held in the website B with the changed reservation information. In this case, the process of step S29 is omitted.

  On the other hand, when the changed reserved seat is also managed in the website B, the login processing unit 12 assumes that the reservation having the same content as the changed reservation information is accepted also in the website B, and the changed reserved seat The seat availability information is updated so that reservations cannot be made.

  Further, in the case where the seat identified by the seat ID included in the reservation information corresponding to the reservation information before the change (described as the reserved seat before the change) is managed on the website B, the login processing unit 12 Updates the vacant seat information so that reservation can be made for the reserved seat before the change managed on the Web site B.

  In the process of step S29, when the user changes the seat reserved on the website A as described above, the changed seat (change reserved seat) is reserved on the website B. It is possible to update the vacant seat information so that the reserved seat before the change can be reserved on the Web site B. In the case where there is no change in seats due to a change in reservation, vacant seat information need not be updated.

  That is, according to the process of step S29 described above, it is possible to automatically update the vacant seat information of the website B even when the contents of the reservation accepted at the website A are changed.

  As in the case of the reservation completion mail described above, if information corresponding to the change reservation information acquired in step S24 can be acquired from the analysis result of the change completion mail by the mail analysis unit 15, the process of step S23 is performed. May be omitted, and the change reservation information (information corresponding thereto) may be acquired without logging in to the website A.

  Next, a processing procedure of the reservation management apparatus 10 when the user cancels a reservation accepted at the target store via the website A will be described with reference to the flowchart of FIG.

  When the user cancels the reservation to the target store accepted on the website A as described above, information indicating the cancellation of the reservation (hereinafter referred to as reservation cancellation information) is held on the website A and the reservation is made. Is sent from the Web server device 20a to the user for notifying that the user has been canceled (hereinafter referred to as cancellation completion mail). The reservation cancellation information indicates, for example, the details of the canceled reservation, and includes, for example, a name, an e-mail address, a use date and time, the number of people, a seat ID, etc. in association with the reservation ID. In addition, the cancellation completion mail includes information indicating a Web reservation service (here, Web site A) that has received a reservation cancellation for the target store. An email address included in the reservation cancellation information is used to transmit the cancellation completion email from the Web server device 20a to the user.

  As described above, the cancellation completion mail from the Web server device 20a is also transmitted to the reservation management device 10. Therefore, the reservation management apparatus 10 receives a cancellation completion mail from the Web server apparatus 20a (Step S31).

  The mail analysis unit 15 analyzes the cancellation completion mail received in step S31. According to this, the mail analysis unit 15 specifies the website (here, the website A) where the user canceled the reservation from the information indicating the web reservation service included in the cancellation completion mail (step S32).

  Next, the login processing unit 12 acquires the login information of the website A specified in step S32 from the storage unit 11, and logs in to the website A using the login information (step S33).

  Here, as described above, the reservation cancellation information indicating the details of the canceled reservation is held in the Web site A. For this reason, the login processing unit 12 acquires the reservation cancellation information held in the website A that has logged in in step S33 (step S34). Note that the reservation cancellation information includes, for example, a reservation ID, name, e-mail address, use date and time, seat ID, and the like, similar to the reservation information.

The login processing unit 12 cancels (deletes) the reservation information corresponding to the reservation cancellation information acquired in step S34 from the storage unit 11 (step S35). It is assumed that the reservation ID included in the reservation cancellation information matches the reservation ID included in the reservation information before cancellation. For this reason, the reservation information corresponding to the reservation cancellation information can be specified based on the reservation ID included in the reservation cancellation information.
When the process of step S35 is executed, the processes of steps S36 and S37 described below and the processes of steps S38 and S39 are executed in parallel.
In this case, the store management screen generation unit 13 generates a store management screen based on the reservation information (and the seat information and other reservation information) canceled in the storage unit 11 (step S36).
When the process of step S36 is executed, the display processing unit 14 transmits the store management screen (data) to the store terminal 30 in order to display the store management screen generated in the step S36 on the store terminal 30. (Step S37). As a result, the store management screen displayed on the store terminal 30 is updated to a store management screen reflecting the cancellation of the reservation information.

  On the other hand, the login processing unit 12 acquires login information of a Web site (here, Web site B) different from the Web site A identified in step S32 from the storage unit 11, and uses the login information to acquire a Web site. Login to site B (step S38).

  The login processing unit 12 updates vacant seat information (inventory information) held in the Web site B logged in in step S38 based on the reservation cancellation information acquired in step S34 (step S39).

  In the process of step S39, for example, the seat identified by the seat ID included in the reservation cancellation information (hereinafter referred to as the cancellation seat of the website A) is indicated by the seat information held in the website B (that is, , A seat assigned to Web site B) is determined. In other words, it is determined whether or not the cancellation seat of the website A is managed even when the website B is the cancellation seat.

  When the cancellation seat of the website A is not managed by the website B, it is not necessary to update the vacant seat information held in the website B with the reservation cancellation information. In this case, the process of step S39 is omitted.

  On the other hand, when the canceled seat is managed on the Web site B, the vacant seat information is such that the cancel seat cannot be reserved on the Web site B, for example, by the processing shown in FIG. For this reason, the login processing unit 12 updates the vacant seat information so that a reservation can be made for the canceled seat.

  According to the process of step S39, the vacant seat information on the website B can be automatically updated so that the seat on which the reservation is canceled on the website A can also be reserved on the website B. It becomes.

  As in the case of the reservation completion mail described above, if information corresponding to the reservation cancellation information acquired in step S34 can be acquired from the analysis result of the change completion mail by the mail analysis unit 15, the process of step S33 is performed. The reservation cancel information (information corresponding to it) may be acquired without logging in to the Web site B.

  As described above, for example, when a new reservation, a change in a reservation, and a cancellation of a reservation are accepted on the website A, the vacant seat information can be automatically updated on the website B, and also on the store management screen. The new reservation, the reservation change and the reservation cancellation can be reflected.

  Here, the case where a new reservation, a change in a reservation, and a cancellation of a reservation are accepted on the Web site A has been mainly described. However, a new reservation, a change in a reservation, and a reservation on a different Web site (for example, the Web site B). The same applies to the case where the cancellation is accepted.

  In the present embodiment, as described above, it is assumed that reservations are made by distinguishing individual seats, but the number of seats that can be reserved at the target store is managed without distinguishing the seats. A configuration in which the number of seats is simply increased or decreased is also possible.

  Here, the new reservation may be performed when the user calls the store (that is, performed on the store terminal 30 side). Such a new reservation by telephone is also preferably managed on the store management screen and reflected in the vacant seat information on the Web sites A and B.

  Hereinafter, with reference to the flowchart of FIG. 11, a processing procedure of the reservation management apparatus 10 when a new reservation is registered on the store terminal 30 side will be described.

  In this case, the display processing unit 14 displays a reservation registration screen on the store terminal 30 (step S41).

  Here, FIG. 12 shows an example of a reservation registration screen. In the reservation registration screen 300 shown in FIG. 12, it is possible to input the date of visit (use date), reception method, status, visit time (use start time), number of people, seat and name (name), and telephone number. It is.

  The reception method includes, for example, “TEL” and “visit”. “TEL” indicates that the new reservation to be registered on the reservation registration screen 300 is a reservation by telephone. Here, a case where a new reservation by telephone is registered will be described. For example, when the user makes a reservation by directly visiting the target store, “visit” is selected.

  The state indicates the state of a new reservation registered on the reservation registration screen 300. The state includes, for example, “reservation”, “entered”, “cancel”, and the like. “Reservation” indicates that a reservation has been made (a reservation has been made). “Entered” indicates that the user (including the group) who made the reservation has entered the store. In addition, when the content of the new reservation is edited after the new reservation is registered on the reservation registration screen 300, a screen (reservation edit screen) similar to the reservation registration screen 300 can be displayed. When a user who has made a reservation enters the store, the employee or the like of the target store specifies that the user has entered the store terminal 30 by designating the item “enter” on the reservation edit screen. Can be entered. In the present embodiment, as described in FIG. 7, the display mode of the reservation information on the store management screen can be changed depending on whether the user has entered the store.

  In addition, the reservation registration screen 300 is provided with input fields 301 to 306 in which various information can be input.

  In the input field 301, the use start time can be input. In the input field 302 provided on the right side of the input field 301, the stay period described above is input. If no stay period is entered in this input field 302, the stay period is automatically set to a predetermined period or a period according to the course, for example.

  In the input fields 303 to 306, it is possible to input the number of people, the seat, the name and the telephone number, respectively.

  In the reservation registration screen 300, for example, a cooking course and information on a reservation person may be input in addition to the above.

  As described above, when various types of information are input to the reservation registration screen 300, the input information (for example, name, phone number, use date / time, number of people, seats, etc.) is transmitted from the store terminal 30 to the reservation management apparatus 10. The

  Returning again to FIG. 11, the reservation management apparatus 10 receives information from the store terminal 30. In this case, the reservation management apparatus 10 generates new reservation information based on the received information (step S42). The new reservation information is equivalent to the new reservation information described in FIG. 8 described above. However, if a telephone number is registered instead of an e-mail address on the reservation registration screen 300 as described above, the step The new reservation information generated in S42 may have a data structure including a telephone number instead of the mail address.

The new reservation information generated in step S42 is stored in the storage unit 11 (step S43). Thereby, a new reservation by telephone or the like is registered in the reservation management apparatus 10.
When the process of step S43 is executed, the processes of steps S44 and S45 and the processes of steps S46 and S47 are executed in parallel.
Note that the processing in steps S44 and S45 corresponds to the processing in steps S16 and S17 shown in FIG. Thereby, the store management screen displayed on the store terminal 30 is updated to a store management screen reflecting the new reservation made on the store terminal 30 side.

  On the other hand, the login processing unit 12 acquires, for example, login information of the website A from the storage unit 11, and logs in to the website A using the login information (step S46).

  Based on the new reservation information generated in step S42, the login processing unit 12 updates the vacant seat information held in the website A logged in in step S46 (step S47). Note that, in step S19 shown in FIG. 8 described above, the update of the vacant seat information held in the website B is described. However, the processing in this step S47 is the same as that except that the website B is the website A. Since it is the same as the process of step S19, the detailed description is abbreviate | omitted.

  In addition, here, it has been described that the vacancy information of the website A is updated by logging in to the website A. However, the processes in steps S46 and S47 described above are different from the website A (that is, the website It is also executed for site B).

  That is, as described above, when a new reservation is registered by telephone or the like via the reservation registration screen 300, for example, the vacant seat information update according to the new reservation (information) can accept a reservation at the target store. This is executed for all Web sites (that is, all Web sites storing login information).

  Note that employees of the target store can also change and cancel reservations registered on the store terminal 30 side, for example, via the reservation edit screen described above.

  First, the processing procedure of the reservation management apparatus 10 when a reservation is changed on the store terminal 30 side will be described with reference to the flowchart of FIG.

  In this case, the display processing unit 14 displays a reservation editing screen on the store terminal 30 (step S51). In the reservation editing screen, the items shown in FIG. 12 (for example, the visit time, the number of people, the seats, etc.) shown in FIG. 12 can be changed (that is, the reservation is changed) for a reservation that has already been accepted. it can.

  In this way, when a reservation is changed on the reservation editing screen, the changed information is transmitted from the store terminal 30 to the reservation management apparatus 10.

  The reservation management apparatus 10 receives information from the store terminal 30. In this case, the reservation management apparatus 10 generates changed reservation information based on the received information (step S52). This change reservation information is the same information as the change reservation information described in FIG.

When the process of step S52 is executed, the reservation information stored in the storage unit 11 is changed to the changed reservation information generated in step S52 (step S53). The reservation information changed to the changed reservation information is reservation information including the same reservation ID as the changed reservation information.
When the process of step S53 is executed, the processes of steps S54 and S55 and the processes of steps S56 and S57 are executed in parallel.
Note that the processing in steps S54 and S55 corresponds to the processing in steps S26 and S27 shown in FIG. Thereby, the store management screen displayed on the store terminal 30 is updated to the store management screen reflecting the change of the reservation made on the store terminal 30 side.

  On the other hand, the login processing unit 12 acquires, for example, login information of the website A from the storage unit 11, and logs in to the website A using the login information (step S56).

  The login processing unit 12 updates the vacant seat information held in the website A logged in in step S56 based on the changed reservation information generated in step S52 (step S57). In the above-described step S29 shown in FIG. 9, the update of the vacant seat information held in the website B has been described. However, the processing in this step S57 is the same as that except that the website B is the website A. Since it is the same as the process of step S29, the detailed description is abbreviate | omitted.

  In addition, here, it has been described that the vacancy information of the website A is updated by logging in to the website A. However, the processing in the above-described steps S56 and S57 is different from the website A (that is, the website It is also executed for site B).

  Next, with reference to the flowchart of FIG. 14, a processing procedure when a reservation is canceled on the store terminal 30 side will be described.

  In this case, the display processing unit 14 displays a reservation edit screen on the store terminal 30 (step S61). In this reservation editing screen, the reservation can be canceled by designating the item “cancel” in the state shown in FIG.

  In this way, when a reservation is canceled on the reservation editing screen, information on the canceled reservation is transmitted from the store terminal 30 to the reservation management apparatus 10.

  The reservation management apparatus 10 receives information from the store terminal 30. In this case, the reservation management apparatus 10 generates reservation cancellation information based on the received information (step S62). This reservation cancellation information is the same information as the reservation cancellation information described in FIG.

When the process of step S62 is executed, the reservation information corresponding to the reservation cancellation information is canceled (deleted) from the storage unit 11 (step S63). Note that the reservation information canceled from the storage unit 11 is reservation information including the same reservation ID as the reservation cancellation information.
When the process of step S63 is executed, the processes of steps S64 and S65 and the processes of steps S66 and S67 are executed in parallel.
Note that the processing in steps S64 and S65 corresponds to the processing in steps S36 and S37 shown in FIG. Thereby, the store management screen displayed on the store terminal 30 is updated to the store management screen reflecting the cancellation of the reservation made on the store terminal 30 side.

  On the other hand, the login processing unit 12 acquires, for example, login information of the website A from the storage unit 11, and logs in to the website A using the login information (step S66).

  The login processing unit 12 updates the vacant seat information held in the website A logged in in step S66 based on the reservation cancellation information generated in step S62 (step S67). Note that, in step S39 shown in FIG. 10 described above, the update of the vacant seat information held in the website B is described. However, the processing in this step S67 is the step except that the website B is the website A. Since it is the same as the process of S39, the detailed description is abbreviate | omitted.

  In addition, here, it has been described that the vacancy information of the website A is updated by logging in to the website A. However, the processing in the above-described steps S66 and S67 is different from the website A (that is, the website It is also executed for site B).

  Here, the store terminal 30 has been described as being able to make a new reservation, change a reservation, and cancel a reservation. However, the reservation (Web reservation) received on the Web site in the reservation management apparatus 10 according to the present embodiment. In the case where only the management of () is performed, a configuration in which the processes of FIGS. 11, 13, and 14 are not executed may be employed.

  Here, in the Web sites A and B, in addition to the normal reservation described above, it is possible to make a reservation called a request reservation.

  While a normal reservation is made at the same time as the user's reservation application is completed, the request reservation is made by notifying the user from the store whether or not to receive the reservation after completing the reservation application by the user. The point that the success or failure of the reservation is determined is different from the normal reservation.

  Hereinafter, the processing procedure of the reservation management apparatus 10 when the user makes a request reservation for the target store via the website A will be described with reference to the flowchart of FIG.

  As described above, when the user makes a request reservation to the target store via the website A, information indicating the content of the request reservation (hereinafter referred to as request reservation information) is held in the website A. A mail for notifying that the request reservation has been accepted (hereinafter referred to as a request reservation mail) is transmitted from the Web server device 20a to the user. The request reservation information includes, for example, a request reservation ID assigned to a request reservation accepted at the website A. The data structure of the request reservation information is the same as the reservation information described with reference to FIG. 6, for example, except that the request reservation ID is included instead of the reservation ID, and detailed description thereof is omitted.

  The request reservation is used when, for example, a user's request or the like is transmitted to the target store, the target store side determines whether or not the request can be realized, and whether or not the reservation is received. Therefore, the request reservation may include text such as the request.

  Further, the above-described request reservation mail includes information indicating a Web reservation service (here, Web site A) that has received a reservation for the target store. A mail address included in the request reservation information is used to transmit the request reservation mail from the Web server device 20a to the user.

  As described above, the request reservation mail from the Web server device 20a is transmitted to the reservation management device 10 as well as other mails. For this reason, the reservation management apparatus 10 receives a request reservation mail from the Web server apparatus 20a (step S71).

  The mail analysis unit 15 analyzes the request reservation mail received in step S71. According to this, the mail analysis part 15 specifies the Web site (here, Web site A) on which the user has made a request reservation from information indicating the Web reservation service included in the request reservation mail (step S72).

  Next, the login processing unit 12 acquires the login information of the website A specified in step S72 from the storage unit 11, and logs in to the website A using the login information (step S73).

  Here, as described above, the Web site A holds request reservation information indicating the content of the request reservation. For this reason, the login processing unit 12 acquires the request reservation information held in the website A logged in in step S73 (step S74).

  The request reservation information acquired in step S74 is stored in the storage unit 11 (step S75).

  When the process of step S75 is executed, the processes of steps S76 and S77 and the processes of steps S78 and S79 are executed in parallel.

  In this case, the store management screen generation unit 13 generates a store management screen based on the request reservation information (and seat information and other reservation information) stored in the storage unit 11 (step S76).

When the process of step S76 is executed, the display processing unit 14 transmits the store management screen (data) to the store terminal 30 in order to display the store management screen generated in the step S76 on the store terminal 30. (Step S77). Thereby, the store management screen displayed on the store terminal 30 is updated to a store management screen reflecting the request reservation information. Note that, as described in FIG. 7, the request reservation (indicating request reservation information) is displayed in a different form from the normal reservation (indicating reservation information). For this reason, employees of the target store can easily grasp the presence or absence of the request reservation.
On the other hand, the login processing unit 12 acquires login information of a Web site (here, Web site B) different from the Web site A identified in step S72 from the storage unit 11, and uses the login information to perform Web Login to site B (step S78).
Based on the request reservation information acquired in step S74, the login processing unit 12 updates the vacant seat information (inventory information) held in the website B logged in in step S78 (step S79). In addition, although the case where vacant seat information is updated based on new reservation information has been described in step S19 shown in FIG. 8 described above, the processing in step S79 is other than that the new reservation information is used as request reservation information. Since this is the same as the processing in step S19, detailed description thereof is omitted.

  When the request reservation for the target store is accepted as described above, the employee of the target store confirms the content of the request reservation at the store terminal 30 and determines whether the request reservation is received (that is, accepts). Answer). Hereinafter, the operation of the reservation management apparatus 10 when the request reservation is accepted and rejected will be described.

  The flowchart of FIG. 16 describes the processing procedure of the reservation management apparatus 10 when the request reservation is accepted.

  First, when the process of step S77 shown in FIG. 15 described above is executed, a store management screen on which a request reservation indicated by request reservation information as shown in FIG. . When an operation for specifying a request reservation is performed on the store management screen, the display processing unit 14 displays a request reservation confirmation screen on the store terminal 30 (step S81).

  Here, FIG. 17 shows an example of a request reservation confirmation screen. As shown in FIG. 17, the request reservation confirmation screen 400 displays the contents of the request reservation indicated by the request reservation information, and is provided with an “accept” button 401 and a “reject” button 402.

  The “Accept” button 401 is a button designated when accepting the request reservation displayed on the request reservation confirmation screen 400.

  The “reject” button 402 is a button that is designated when rejecting a request reservation displayed on the request reservation confirmation screen 400.

  Here, it is assumed that an employee of the target store determines that the request reservation is accepted and the “Accept” button 401 is designated on the request reservation confirmation screen 400. In this case, the store terminal 30 transmits an instruction for accepting the request reservation (hereinafter referred to as request reservation acceptance instruction) to the reservation management apparatus 10. The request reservation acceptance instruction includes, for example, a request reservation ID assigned to the request reservation.

  Thereby, the reservation management apparatus 10 receives a request reservation acceptance instruction from the store terminal 30 (step S82).

  Next, the login processing unit 12 acquires, for example, login information of the website A specified in step S72 illustrated in FIG. 15 (that is, the website that accepted the request reservation) from the storage unit 11, and stores the login information. Use to log in to the website A (step S83).

  The login processing unit 12 changes the status of the request reservation information, which is held in the website A and includes the request reservation ID included in the request reservation approval instruction received in step S82, to “established (accepted)” ( Step S84).

  When the process of step S84 is executed, the request reservation information (request reservation information including the request reservation ID included in the request reservation acceptance instruction) stored in the storage unit 11 is, for example, a request included in the request reservation information. The reservation ID is changed to new reservation information with the reservation ID (step S85). According to this, a reservation is established with the contents of the request reservation indicated by the request reservation information, and this request reservation information is handled in the same manner as the new reservation information.

  When the process of step S85 is executed, the processes of steps S86 and S87 corresponding to the processes of steps S16 and S17 shown in FIG. 8 are executed. Thereby, the store management screen displayed on the store terminal 30 is updated to a store management screen reflecting that the request reservation is established as a new reservation.

  Next, the processing procedure of the reservation management apparatus 10 when the request reservation is rejected will be described with reference to the flowchart of FIG.

  First, the process of step S91 corresponding to the process of step S81 shown in FIG. 16 is executed.

  Here, it is assumed that an employee of the target store determines that the request reservation is rejected and the “reject” button 402 is designated on the request reservation confirmation screen 400. In this case, the store terminal 30 transmits an instruction for refusing the request reservation (hereinafter referred to as a request reservation refusal instruction) to the reservation management apparatus 10. Note that the request reservation rejection instruction includes, for example, a request reservation ID assigned to the request reservation.

  Thereby, the reservation management apparatus 10 receives a request reservation rejection instruction from the store terminal 30 (step S92).

  Next, the login processing unit 12 acquires, for example, login information of the website A specified in step S72 illustrated in FIG. 15 (that is, the website that accepted the request reservation) from the storage unit 11, and stores the login information. Use to log in to the website A (step S93).

  The login processing unit 12 changes the status of the request reservation information, which is stored in the website A and includes the request reservation ID included in the request reservation rejection instruction received in step S92, to “cancel (reject)” ( Step S94).

When the process of step S94 is executed, the request reservation information stored in the storage unit 11 (request reservation information including the request reservation ID included in the request reservation rejection instruction) is deleted from the storage unit 11 ( Step S95).
When the process of step S95 is executed, the processes of steps S96 and S97 and the processes of steps S98 and S99 are executed in parallel.

Note that the processing in steps S96 and S97 corresponds to the processing in steps S36 and S37 shown in FIG. As a result, the store management screen displayed on the store terminal 30 is updated to a store management screen reflecting that the request reservation has been canceled (rejected).
On the other hand, the login processing unit 12 acquires login information of a website (here, website B) different from the website A identified in step S72 shown in FIG. Is used to log in to the website B (step S98).
Based on the request reservation information acquired in step S74 (that is, the request reservation information deleted in step S95), the login processing unit 12 uses the vacant seat information (inventory information) held in the website B logged in in step S98. ) Is updated (step S99). Note that the process in step S99 is the same as the process in step S39 shown in FIG. 10 except that the request reservation is canceled instead of the new reservation being canceled, and thus detailed description thereof is omitted.

  In the present embodiment, as described above, even when a request reservation is accepted on the website, it is possible to appropriately manage the reservation to the target store.

  By the way, in the Web site, a time zone (hereinafter referred to as site reception time) in which a reservation can be received in the Web site is set. However, this site reception time cannot generally be set (individually set) every day.

  On the reservation management apparatus 10 side, a Web reservation reception time (hereinafter, Web reception time) is set via the store management screen displayed on the store terminal 30 described above.

  Furthermore, it is possible to set not to accept web reservations (hereinafter referred to as blocks) for a part of the web reception time period via the store management screen displayed on the store terminal 30. .

  Therefore, even if the reservation is not performed as described above, it is necessary to adjust the vacancy information of each Web site depending on the site reception time, the Web reception time, and the setting status of the block.

  Hereinafter, a processing procedure of the reservation management apparatus 10 when adjusting vacant seat information will be described with reference to the flowchart of FIG.

  Here, the above-described Web reception time is set, for example, when the cooperation between the reservation management apparatus 10 and the Web server apparatus (others such as the Web server apparatuses 20a and 20b) is set. In this case, the login processing unit 12 specifies a website for which the web reception time is set (step S101). In the following description, the website specified in step S101 is referred to as a target website.

  Next, the login processing unit 12 acquires a site reception time (hereinafter referred to as a site reception time of the target website) set in the target website (step S102). The site reception time of the target website is acquired from the target website by, for example, logging in to the target website using login information of the target website stored in the storage unit 11. Note that the target website reception time acquired by the login processing unit 12 may be managed in the reservation management apparatus 10, for example.

  The login processing unit 12 determines whether or not the Web reception time set in the reservation management apparatus 10 matches the site reception time of the target Web site acquired in Step S102 (Step S103). In other words, in step S103, for example, it is determined whether or not there is a time zone that does not correspond to the site reception time of the target website within the Web reception time.

  When it is determined that the web reception time and the site reception time of the target website do not match (NO in step S103), the login processing unit 12 logs in to the target website as described above, and vacant seats of the target website Information is adjusted (step S104). A specific example of adjusting the vacant seat information in step S104 will be described later.

  On the other hand, if it is determined that the web reception time matches the site reception time of the target website (YES in step S103), the login processing unit 12 blocks the site reception time (and web reception time) of the target website. It is determined whether or not the time set for (the time when the Web reservation is not accepted) overlaps (step S105).

  When it is determined that the site reception time of the target website and the time for which the block is set overlap (YES in step S105), the process of step S104 is executed.

  On the other hand, if it is determined that the site reception time of the target website does not overlap with the time when the block is set (NO in step S105), the relationship between the site reception time of the target website, the Web reception time, and the block is Since adjustment of vacant seat information is not necessary, the process of step S104 is not executed.

  According to the process shown in FIG. 19, when the cooperation between the reservation management apparatus 10 and the Web server apparatus is set, for example, the Web reception time is set (edited), and the set time and the website site are set. It is determined that the vacant seat information needs to be adjusted when a time zone that does not coincide with the reception time occurs or when a time zone in which the Web reception time and the block setting time overlap is generated. Here, it has been described that the process of FIG. 19 is executed when the Web reception time is set, but the process shown in FIG. 19 is executed when the block is set at the store terminal 30, for example. It does not matter.

  Here, with reference to FIG. 20, the case where the vacant seat information needs to be adjusted and the case where the vacant seat information does not need to be adjusted in the process shown in FIG. 19 will be specifically described.

  In each case shown in FIG. 20, the site reception time, the Web reception time, the block setting time (block setting time), and the reservation status are shown for each time zone. Note that “reservation” in FIG. 20 indicates a time slot in consideration of the use start time and a preset use period in the reservation (that is, a time slot assumed to use the store).

  For example, in case 1 shown in FIG. 20, the site reception time is the time zone from 19:00 to 21:00, and the Web reception time is also the time zone from 19:00 to 21:00. In this case, the site reception time and the Web reception time are the same, and reservations can be received in the time zone from 19:00 to 21:00, so adjustment of vacant seat information is unnecessary.

  On the other hand, in case 2, the site reception time is a time zone from 19:00 to 21:00, and the Web reception time is a time zone from 19:00 to 20:30. In this case, in the time zone from 20:30 to 21:00, the site reception time and the Web reception time do not overlap, and the reservation cannot be received. For this reason, the vacant seat information on the website is adjusted so that reservations are not accepted in the time zone from 20:30 to 21:00.

  Next, in case 3, the site reception time and the web reception time are the same as in case 1, and the block setting time is the time zone from 18:00 to 19:00. In this case, since the site reception time and the web reception time coincide with each other and the block setting time does not overlap with the site reception time and the web reception time, it is not necessary to adjust the vacant seat information.

  On the other hand, in case 4, the site reception time and the web reception time are the same as in case 1, and the block setting time is the time zone from 20:30 to 21:30. In this case, the site reception time and the web reception time are the same, but in the time zone from 20:30 to 21:00, the block setting time, the site reception time, and the web reception time overlap, I can't accept it. For this reason, the vacant seat information on the website is adjusted so that reservations are not accepted in the time zone from 20:30 to 21:00.

  In case 5, it is shown that other reservations cannot be received even if the site reception time and the Web reception time are the same for the time zone in which the store is assumed to be used by reservation. ing.

  According to the process shown in FIG. 19, the vacant seat information can be automatically adjusted, for example, in cases 2 and 4 shown in FIG.

  As described above, in the present embodiment, each of Web sites A and B (first and second Web sites) managed by each of Web server devices 20a and 20b (first and second server devices). The reservation information (first reservation information) indicating the reservation accepted in step 1 is collected, a store management screen including the collected reservation information is generated, and the generated store management screen is displayed on the store terminal 30. . The reservation information is collected by logging into each of the websites A and B.

  In the present embodiment, with such a configuration, it is possible to easily manage reservations received at a plurality of Web sites.

  Further, in the present embodiment, when a reservation to the target store is accepted at the website A, an email transmitted from the web server device 20a is received and accepted at the website A based on the received email. Reservation information (second reservation information) indicating the reserved reservation is acquired, and a store management screen reflecting the acquired reservation information is generated. According to such a configuration, for example, when a new reservation is accepted on the website A, it is possible to display the store management screen on which the new reservation is reflected on the store terminal 30.

  Further, in this embodiment, when a new reservation is accepted at the website A as described above, the website A is logged in and the vacant seat information of the website B is updated. As a result, it is possible to avoid that a reservation that overlaps with a new reservation accepted at the website A is accepted at the website B.

  Moreover, in this embodiment, when the content of the reservation to the target store is changed on the website A, an email transmitted from the web server device 20a is received, and on the website A based on the received email. Reservation change information indicating the contents of the changed reservation is acquired, and a store management screen reflecting the acquired reservation change information is generated. According to such a configuration, for example, when a reservation is changed on the website A, a store management screen in which the change of the reservation is reflected can be displayed on the store terminal 30.

  Furthermore, in this embodiment, when the reservation is changed on the website A as described above, the website B is logged in and the vacant seat information on the website B is updated. Thereby, it becomes possible to automatically update the vacant seat information of the Web site B according to the contents of the reservation changed in the Web site A.

  Moreover, in this embodiment, when the reservation to the target store is canceled on the Web site A, the mail transmitted from the Web server device 20a is received, and the Web site A is canceled based on the received mail. Reservation cancellation information indicating the reserved reservation is acquired, and a store management screen reflecting the acquired reservation cancellation information is generated. According to such a configuration, for example, when a reservation is canceled on the Web site A, a store management screen in which the cancellation of the reservation is reflected can be displayed on the store terminal 30.

  Further, in the present embodiment, when the reservation is canceled at the website A as described above, the user logs in to the website B and updates the vacancy information of the website B. Thereby, it becomes possible to automatically update the vacant seat information of the website B in response to the cancellation of the reservation in the website A.

  Further, in the present embodiment, reservation information (second reservation) indicating reservation to the target store according to an operation on the store terminal 30 by a user (for example, an employee of the store) using the store terminal 30. Information) and update the vacant seat information (first and second vacant seat information) of the websites A and B based on the reservation information. According to such a configuration, for example, even when a new reservation is received by telephone or the like at the target store, it is possible to avoid that reservations overlapping with the new reservation are received on the websites A and B. Become.

  In the present embodiment, the case where there are two Web server devices (Web sites) has been described for convenience of explanation, but the number of Web server devices (Web sites) may be three or more.

  In the present embodiment, for convenience of explanation, only one store terminal 30 has been described. However, when the reservation management apparatus 10 is communicably connected to a plurality of store terminals, it is the same as the store terminal 30 described above. This process may be executed for each store terminal.

  Note that the present invention is not limited to the above-described embodiment as it is, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage. Moreover, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the embodiment. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, constituent elements over different embodiments may be appropriately combined.

  DESCRIPTION OF SYMBOLS 10 ... Reservation management apparatus, 10a ... Computer, 10b ... Storage device, 11 ... Storage part, 12 ... Login processing part, 13 ... Store management screen generation part, 14 ... Display processing part, 15 ... Mail analysis part, 20a, 20b ... Web server device, 30 ... store terminal.

According to one aspect of the present invention, first and second server devices that manage different first and second Web apostles for accepting reservations to a store, and a store terminal provided in the store, A reservation management device connected to be communicable is provided. The reservation management apparatus includes a first acquisition unit, a first update unit, a second acquisition unit, a second update unit, a collection unit, a generation unit, and a display processing unit. The first acquisition unit acquires a first site reception time set in the first Web site. When the acquired first site reception time and the Web reception time set in the reservation management device do not match, the first update unit makes a reservation in the time zone that does not match. The vacant seat information indicating the vacant seats that can be reserved in the first Web site, managed in the first server device, is updated so as not to be accepted. The second acquisition unit acquires a second site reception time set in the second Web site. When the acquired second site reception time and the Web reception time do not match, the second update means does not accept a reservation in the time zone that does not match the second update reception time. The vacant seat information indicating the vacant seats that can be reserved in the second Web site, managed in the server device is updated. The collection means accesses the first and second server devices, and each of the first and second Web sites based on vacant seat information managed in the first and second server devices. First reservation information indicating the accepted reservation is collected. The generation unit generates a store management screen including the collected first reservation information. The display processing means displays the generated store management screen on the store terminal.

Claims (11)

In a reservation management apparatus that is communicably connected to first and second server apparatuses that manage different first and second Web sites for accepting reservations to a store and a store terminal provided in the store,
A first reservation that accesses the first and second server devices and indicates reservations accepted by each of the first and second Web sites managed by the first and second server devices, respectively. A collection means for collecting information;
Generating means for generating a store management screen including the collected first reservation information;
A reservation management device comprising: display processing means for displaying the generated store management screen on the store terminal. Storage means for storing first and second login information for logging in to each of the first and second websites;
When the collection unit generates the store management screen, the collection unit sequentially uses each of the first and second login information stored in the storage unit to each of the first and second Web sites. The reservation management apparatus according to claim 1, wherein the first reservation information is collected by logging in. Receiving means for receiving an email transmitted from the first server device when a reservation to the store is accepted at the first Web site;
Based on the received mail, the user logs in to the first Web site managed by the first server device, and acquires the second reservation information indicating the reservation accepted at the first Web site. And further obtaining means,
The reservation management apparatus according to claim 2, wherein the generation unit generates a store management screen that reflects the acquired second reservation information.   Based on the acquired second reservation information, the second Web site managed by the second server device is logged into the second Web site managed by the second server device. 4. The reservation management apparatus according to claim 3, further comprising update means for updating vacant seat information indicating vacant seats that can be reserved on the site. Receiving means for receiving an e-mail transmitted from the first server device when the content of the reservation to the store is changed on the first Web site;
Based on the received mail, the user logs in to the first Web site managed by the first server device, and acquires reservation change information indicating the details of the reservation changed in the first Web site. And further obtaining means,
The reservation management apparatus according to claim 2, wherein the generation unit generates a store management screen that reflects the acquired reservation change information.   Based on the acquired reservation change information, the user logs in to the second Web site managed by the second server device, and in the second Web site managed in the second server device 6. The reservation management apparatus according to claim 5, further comprising update means for updating vacant seat information indicating a vacant seat that can be reserved. Receiving means for receiving an email transmitted from the first server device when the reservation to the store accepted at the first Web site is canceled;
Based on the received mail, an acquisition means for logging in to a first Web site simplified by the first server device and acquiring reservation cancellation information indicating a reservation canceled in the first Web site And further comprising
The reservation management apparatus according to claim 2, wherein the generation unit generates a store management screen reflecting the acquired reservation cancellation information.   Based on the acquired reservation cancellation information, the user logs in to the second Web site managed by the second server device, and in the second Web site managed in the second server device 8. The reservation management apparatus according to claim 7, further comprising update means for updating vacant seat information indicating a vacant seat that can be reserved. An acquisition means for acquiring second reservation information indicating a reservation to the store in response to an operation on the store terminal by a user using the store terminal;
When the second reservation information is acquired, the first Web site managed by the first server device is logged into the first Web site managed by the first server device. A first updating means for updating first vacant seat information indicating a vacant seat that can be reserved in;
When the second reservation information is acquired, the second Web site managed by the second server device is logged in to the second Web site managed by the second server device. The reservation management apparatus according to claim 2, further comprising: a second updating unit that updates second vacant seat information indicating a vacant seat that can be reserved. Executed by a reservation management apparatus communicably connected to first and second server apparatuses that manage different first and second Web sites for accepting reservations to a store and store terminals provided in the store. A reservation management method,
Accessing the first and second server devices and collecting reservation information indicating reservations accepted by each of the first and second Web sites managed by each of the first and second server devices And steps to
Generating a store management screen including the collected reservation information;
A reservation management method comprising: displaying the generated store management screen on the store terminal. Reservation management device computer communicably connected to first and second server devices for managing different first and second Web sites for accepting reservations to stores and store terminals provided in the stores A program executed by
In the computer,
Accessing the first and second server devices and collecting reservation information indicating reservations accepted by each of the first and second Web sites managed by each of the first and second server devices And steps to
Generating a store management screen including the collected reservation information;
Displaying the generated store management screen on the store terminal.

Images