HK1223435B - Amenity, special service and food/beverage search and purchase booking system - Google Patents

Description

A system for searching and purchasing facilities, special services, and food/beverages

Technical Field

The present disclosure relates to systems, methods, and computer program products for use with an amenity, specialty service, and food/beverage search and purchase booking engine for hospitality and travel applications.

Background Art

In the field of travel accommodation search and booking, customers are presented with many options. Travel websites such as Orbitz, Expedia, and Travelocity allow customers to search for hotel rooms in a given location for a given date or date range. For example, a customer seeking hotel rooms in New York City for New Year's Eve can visit such a website and enter or select "New York, NY" in the "City" or "Destination" column on the page, and enter or select a check-in date of December 31 and a check-out date of January 1. The website will then use the customer's information to search its database for available rooms in New York on those dates and present a list of hotels with available rooms. However, if a customer is looking for a specific feature, most hotel or travel websites require the customer to read the detailed description of each hotel listed in the search results to determine whether any of the hotels offer that feature. In addition, even if it is possible to determine that a specific, listed hotel generally offers the feature, these websites do not provide provisions for determining whether the desired feature is actually available, nor for actually reserving, booking, or paying for the feature with or without a room reservation.

Other travel websites, such as hotels.com, BookIt.com, and Google Hotel Finder, offer similar accommodation search dialogs and similar search results for hotels in a specific location with available rooms for a desired time period. However, these sites differ from the others in that the hotels listed on the search results page can be "filtered" by the customer, who can choose to display only results that match additional criteria, such as being in a specific neighborhood or having certain general amenities. Filter selections are made by the customer using drop-down menus or checkboxes; however, only a limited selection of general amenities is provided. For example, Google Hotel Finder's amenities filter list only includes air conditioning, bar, beach, business center, gym, internet, parking, pet-friendly, swimming pool, restaurant, wheelchair-accessible facilities, child-friendly, laundry, and room service. Hotels.com's listing has similar amenities filters but adds several more, including free breakfast, crib availability, and spa treatments. Free-form feature search—that is, allowing customers to enter or type desired amenities, special services, or food/beverage options into the search input form—is not available. However, even when customers restrict search results to hotels that meet these specific restrictions, they are not given the opportunity to confirm availability, let alone book or reserve specific amenities through room booking. In fact, Google Hotel Finder and juicyhotels.com, another hotel and amenity search site that uses a checkbox method, do not even offer online reservations. Customers must make reservations through the hotel's website; other travel sites like BookIt.com, Travelocity, or Orbitz handle room reservations through offline means.

The OpenTable restaurant search website offers a similar user interface. In addition to selecting dates, customers also select a general location, such as a city or neighborhood, and a time of day. The website searches for available accommodations and presents a list of restaurants that match the selected criteria and availability. Similar to some hotel search sites, OpenTable offers customers the ability to filter the results list based on additional criteria, such as cuisine style and price range. OpenTable also displays a list of restaurants with "private dining facilities" such as chef's tables, parlors, and private dining rooms. However, customers cannot directly determine availability, pricing, or make reservations for these private dining features through the website. Customers are provided with a phone number and contact name, or can use a form-based web query. UrbanSpoon, another restaurant search website, additionally offers customers a list of selectable restaurant "options" for filtering restaurant listings, including "private parties" and "live music." However, there are no provisions for determining availability or pricing for these options for a given date and time, or for using these options to book a table. As with other hotel or travel websites, there is no free-form search and purchase functionality for features. Customers are limited to filtering results based on pre-selected options and amenities.

Another system, Orion from Ascension, is a web-based platform used by hotels to provide guests with online access to room service and amenity gift ordering. However, Orion does not allow for searching or purchasing any features. Rather, it provides a "catalog" of amenities and services available for ordering. Furthermore, Orion does not offer the ability to book or reserve a room in conjunction with ordering an amenity or service.

Therefore, there is a need for a menu hospitality/tourism and accommodation system that provides customers with the option to search for and purchase features within or separate from an accommodation that has desired, reservable/ticketable amenities and/or special services and/or food/beverage available at a desired date and time, as well as the additional ability to reserve/purchase features with such functionality without having to reserve a room or table at a menu accommodation, such as a restaurant. Furthermore, there is a need for customers to be able to freely enter any search item to search for desired features.

Summary of the Invention

The present invention relates to systems, methods, and computer program products for a menu facility, special service, food/beverage, and accommodation ("feature") search and booking engine. Aspects of the present invention enable customers to identify, via any search, available facilities and/or special services (including food/beverage) at lodging facilities, restaurants, clubs/lounge/bars, residences, and tourist accommodations. In this sense, "any" means that customers can type in search input rather than input provided in a checkbox list or other predetermined list. Customers are presented with goods and services that match or are related to their query terms and are allowed to select and confirm desired feature options and reserve, book, or purchase their selections; optionally, including reserving accommodations such as a room or a table at a restaurant.

According to one embodiment of the present invention, a system for identifying and booking features from a hospitality/tourism provider is provided, the system comprising: a processor; a network interface coupled to a network; a feature database stored on a non-transitory computer-readable medium; a non-transitory storage medium storing processor instructions; and an interface coupling the processor, the storage medium, the feature database, and the network interface. The feature database includes feature artifacts for associating bookable amenities, special services, or food/beverage items with hospitality provider identifiers. The processor instructions cause the processor to: receive, from a client device over the network, any feature identification information for a bookable feature; search the feature database for at least a partial match; transmit one or more hospitality/tourism provider identifiers associated with the match; receive a hospitality/tourism provider selection from the client device; and transmit, to the client device for display on the client device, an offer based on the any feature identification information and/or the selected hospitality/tourism provider booking feature.

In another embodiment, the processor instructions further direct the processor to perform part or all of the following processing in response to receiving any feature identification information: searching the feature database for feature artifacts having feature identifications that at least partially match the any feature identification information, and transmitting to the client device the feature identification associated with at least one of the partially matching artifacts for display on the client device in the form of an auto-completion list.

In another embodiment, the processor instructions further instruct the processor to: receive accommodation search constraints from the client device, the accommodation search constraints comprising: an indication of a desired booking period for the accommodation and an indication of a desired geographic location for the hospitality/tourism provider. The search feature database is further constrained to hospitality/tourism providers that are within the desired geographic location and can offer accommodation or bookable features during the desired booking period; the accommodation search constraints may also include a desired room configuration. In one embodiment, the processor instructions further instruct the processor to: transmit a booking query based on the accommodation search constraints to an external provider via a network; and receive availability information from the external provider for at least one accommodation provider that meets the accommodation search constraints. The external provider may be a GDS provider, a CRS provider, a CRM system, an inventory system, a sales/revenue management system, a loyalty system, a property/operation system, or a PMS of the accommodation provider. The processor instructions may also include instructions causing the processor to: receive an indication of acceptance of the booking offer and payment information from the client device; transmit the payment information to a payment processor; update an inventory record in the database to record the reservation of the feature and/or accommodation; and transmit a confirmation of the reservation to the client device.

In another embodiment, the processor instructions further direct the processor to receive a hospitality provider facility identification from a network-connected member device over the network and store an artifact associating the hospitality provider facility identification with an identification of the hospitality provider in a facilities database.

In another embodiment of the present invention, a computer-implemented method for identifying and booking features from an accommodation provider is provided, the method comprising the steps of transmitting, via a network, arbitrary feature identification information of bookable features from a network-connected client device to a network-connected server. The method comprises the steps of receiving, from the server on the client device, one or more accommodation/tourism provider identifications of accommodation/tourism providers that can offer bookable features corresponding to the arbitrary feature identification information; transmitting, from the client device to the server, an indication of a selected accommodation provider identification; and receiving, for display on the client device, an offer from the client to book features associated with the feature identification matching the arbitrary feature identification information and/or the selected accommodation/tourism provider.

The method may further include the following steps: transmitting a portion of the arbitrary feature identifier from the client device and receiving, on the client device, a facility identifier corresponding to the portion of the arbitrary feature identifier, for display on the client device in the form of an auto-completion list.

The method may further include transmitting, from the client device to the server, accommodation search constraints indicating a desired booking period for the accommodation and a desired geographic location for the hospitality/tourism provider. The one or more hospitality/tourism provider identifiers correspond to hospitality/tourism providers that are within the desired geographic location and can provide accommodation or bookable features during the desired booking period. The search constraints may indicate a desired room configuration.

The method may further comprise the steps of transmitting acceptance and payment information of the reservation offer from the client device to the server, and receiving confirmation of the reservation via the client device.

In another embodiment of the present invention, a computer program product for identifying and booking features from hospitality and travel providers is provided. The computer program product includes a non-transitory computer-readable storage medium storing processor instructions. The instructions instruct the processor to receive, from a client device over a network, arbitrary feature identification information for bookable amenities and/or special services and/or food/beverage. The instructions further include instructions for searching a feature database for a set of feature artifacts having feature identifications that at least partially match the arbitrary feature identification information. The feature database is stored on the non-transitory computer-readable medium and includes a plurality of feature artifacts, wherein the feature artifacts associate bookable feature identifications with provider identifications. The instructions further include instructions for: transmitting to a client device the hospitality/travel provider identification associated with the set of feature artifacts; receiving from the client device a selection of a hospitality/travel provider identification; and transmitting to the client device, for display, an offer for the client to book features associated with the feature identification that matches the arbitrary feature identification information and/or accommodations of the selected hospitality/travel provider.

In yet another embodiment of the present invention, a computer program product for identifying and booking features from a provider is provided. The computer program product includes a non-transitory computer-readable storage medium storing processor instructions. The instructions instruct the processor to receive, from a client device over a network, arbitrary feature identification information for bookable amenities and/or special services and/or food/beverage. The instructions further include instructions for searching a feature database for a set of feature artifacts having feature identifications that at least partially match the arbitrary feature identification information. The feature database is stored on the non-transitory computer-readable medium and includes feature artifacts that associate bookable feature identifications with provider identifications. The instructions further include instructions for: transmitting to the client device the provider identification associated with the set of feature artifacts; receiving from the client device a selection of a provider identification; and transmitting to the client device for display a quote for booking features associated with the feature identification that matches the arbitrary feature identification information and/or accommodations of the selected provider. In one embodiment, the provider may be a hospitality provider. In another embodiment, the provider may be a travel provider.

In yet another embodiment of the present invention, a computer-implemented method for identifying and booking features from a hospitality/tourism provider is provided, the method comprising the steps of: receiving, via a network, arbitrary feature identification information for a bookable accommodation from a network-connected client device; searching a feature database for a set of feature artifacts having a feature identification that at least partially matches the arbitrary feature identification information; the feature database being stored on a non-transitory computer-readable medium and comprising a plurality of feature artifacts, wherein the feature artifacts associate bookable feature identifications with hospitality/tourism provider identifications; transmitting, via the network, to the client device one or more hospitality/tourism provider identifications associated with the set of feature artifacts; receiving, from the client device, a selected hospitality/tourism provider identification; and transmitting to the client device an offer for a customer to book a feature associated with an accommodation with the feature identification that matches the arbitrary feature identification information and/or the selected hospitality/tourism provider.

In some embodiments, the hospitality provider and/or the tour provider is a boutique hotel. In some embodiments, the feature identification information includes location information derived from the geographic location or proximity of the client device. In some embodiments, semantic matching techniques are used to search the facility database. In some embodiments, the bookable features are amenities and/or special services and/or food/beverage. In some embodiments, the feature identification information may identify multiple features.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the present disclosure can be better understood with reference to the following drawings, in which like reference characters indicate corresponding parts throughout the several views.

FIG. 1 is a schematic diagram of an exemplary system according to an embodiment of the present invention.

FIG2 shows an exemplary venue.

FIG3 illustrates aspects of an exemplary booking engine according to some embodiments of the present invention.

FIG4 illustrates an affiliate profile administrator portal ("APAP") according to some embodiments of the present invention.

5 is a schematic diagram of aspects of a member profile according to some embodiments of the present invention.

6 is a schematic diagram of aspects of a payment gateway according to some embodiments of the present invention.

7, 8, 9 and 31 are diagrams of exemplary client user/system user interface flows according to some embodiments of the present invention.

10, 12, 13, 14, and 15 are portions of exemplary screen shots of a customer user portal main search input engine page according to an exemplary embodiment of the present invention.

11 is a portion of an exemplary screen shot of a customer user portal member login page according to an exemplary embodiment of the present invention.

16, 17, 18, 19, 20 and 21 are details of exemplary screen shots of a customer user portal search results and item selection pages according to an exemplary embodiment of the present invention.

22 is an exemplary screen shot of a customer user portal member profile page according to an exemplary embodiment of the present invention.

23 is a partial exemplary screen shot of a customer user extension component according to an exemplary embodiment of the present invention.

24 and 25 are portions of exemplary screen shots of customer user portal confirmation pages according to an exemplary embodiment of the present invention.

Figure 26 is a diagram of an exemplary member user/system user interface flow according to some embodiments of the present invention.

FIG. 27 is an exemplary screenshot of an APAP member information page (for hotel members) according to an exemplary embodiment of the present invention.

FIG. 28 is an exemplary screenshot of an APAP Room page (for hotel members) according to an exemplary embodiment of the present invention.

29 and 30 are schematic representations of exemplary server and client devices, respectively, according to embodiments of the present invention.

Specific embodiments

Aspects of the present invention relate to systems, methods and computer program products for features such as facilities, special services, food/beverage and accommodation search and booking engines. In the context of the present invention, members are generally hotels and travel suppliers, such as places of accommodation facilities, restaurants, clubs/lounge/bars, residences and tourist accommodations. However, in some embodiments, members may be limited to boutique hotels. Travel suppliers are generally entities that provide travel-related products and services. The term "accommodation" relates to the core product of a hospitality service provider; for example, hotel accommodation includes guest rooms, and restaurant accommodation includes dining tables. With reference to Fig. 2, member hotels 200 can provide many features such as facilities and/or special services and/or food/beverage. For example, guest room accommodation can include a loft suite 210, a guest room 220 with a hot tub, a guest room 225 with a balcony, a guest room 260 with a bowling alley and a regular guest room 255. Member hotels 200 may also feature a helipad 205, a rooftop terrace 245, a spa 215, a greenhouse garden with a pond 250, a bar 265, a restaurant 235, a clothing boutique 270, a dance club 240, and a cinema 275. Member hotels 200 may also offer conference and multi-purpose or pop-up spaces 230. Some travel and hospitality providers may offer activities such as boat rentals or experiences such as theater performances. The term "customer" includes anyone searching for a member's products and services.

1 , in one embodiment, the present invention may be configured to operate within a network system 10 comprising a server 100, one or more client devices 160, and one or more member devices 180, all interconnected via a network 155. Network 155 may comprise the Internet, but may also comprise dedicated and/or proprietary network interconnections. System 10 may also include service provider systems, such as a global distribution system (GDS) 144, a property management system (PMS) 146, a customer relationship management system (CRM) 147, and a central reservation system (CRS) 148. System 10 may also include a commercial financial services provider, represented by a bank 142, for processing credit card and other financial transactions. System 10 may also include a social media service provider, an industry expert service provider, and a tour guide and review service provider, represented by a SOC 142. System 10 may also include (not shown) inventory systems, sales/revenue management systems, loyalty systems, and/or property/operation systems, all interconnected via network 155.

The loyalty system includes rewards for structured marketing efforts that encourage loyal purchasing behavior, methods within and outside the membership, products (such as credit/debit cards), and technical systems. These behaviors are used to earn money through incentive mechanisms to perpetuate desired behaviors through membership programs. Communication with the loyalty system can include records of each transaction stored in an analysis system for trend performance and recommendation models. Information from the loyalty system can be used to enhance adaptive searches for repeated or permanent business recommendations. Integration with the loyalty system enables enhanced searches and recommended purchase options via recommendations. The system's customer business input enables machine learning of repeated business to trigger an impact on the incentive system to generate new artifacts for score processing. In addition, incentives for continuous interaction are implemented through the search and purchase system to continuously optimize features and/or accommodation project results for selection and purchase.

Server 100 includes a data store 116, a booking engine 120, a member profile administrator portal 122, a payment gateway 132, a GDS interface 134, a PMS interface 136, and a CRS interface 138. Client device 160 is any network-connectable computing device capable of transmitting client search queries and receiving search results. Clients can enter queries using a client input device 164, such as a keyboard, and view the results on a client display 166. Client device 160 may run one or more applications, such as a client application 162 for interacting with server 100. In one embodiment, client application 162 is a web browser. Client device 160 may also include a geolocation component, such as a GPS receiver, and/or a proximity detection component 168, enabling client device 160 to determine its location and/or proximity to search inputs. In one embodiment, proximity detection component 168 may utilize RFID technology. Member device 180 is also a network-connectable computing device and may include a member input device 184, a member display 186, and a member application 182 for interacting with server 100 via a network. In one embodiment, member application 182 is a web browser. In an alternative embodiment, member application 182 is a branded application for interacting with server 100. Member device 180 may be one or more computers and may host a member's general inventory and/or sales module. Other methods of computing devices capable of transmitting search query data may include telepathic devices, scent devices, bio-integration, holographic integration, and artificial intelligence capabilities, any of which may be configured as potential search inputs to facilitate ticketing, reservations, appointments, and/or purchases of amenities and/or special services and/or food/beverages.

The modular components of the server 100 ensure dynamic interconnected communication, enabling customers to identify member facilities and/or special services and/or food/beverages through search and providing options for purchasing said items. In addition, the system allows member users to connect their facilities and/or special services and/or food/beverage systems to the system of the present invention, but is not limited to directly accessing their information center and uploading their facilities and/or special services and/or food/beverages.

The components of the system are connected to each other via data transmission channels. These data transmission channels are interchangeable with other related data transmission channels. Parts of system 10 can be cloud-based; however, cloud functionality is not required. The cloud system only provides optional resources and data transmission channels.

The data storage 116 includes one or more databases for storing customer user and member user artifacts. The booking engine 120 facilitates customer searches and results.

In one embodiment, data storage 116 includes both a relational database and a non-relational database. The relational database can handle customer user artifacts; the non-relational database can handle customizable member user artifacts. Using a non-relational database component enables the system to evolve by adapting to an increasing number of different artifact types, and to identify and store artifacts for recall within the system.

The database of the present invention is also useful for other purposes. In order to continuously improve search, queries and query trends are tracked as part of session data, and this data is used for, for example but not limited to, member feature matching and potential profit purposes.

Generally speaking, the user provides search content through text, commands that can be interpreted as text, image input, audio, electronic signals or through menu selection. The menu can take the form of other known options such as click boxes or selectable icons. When the user provides the necessary character strings and/or selections, these items are delivered to one or more databases in the database so that matching content is returned. In addition, the user can select non-matching content, such as members who do not want to be allowed to bring pets. The processor of the present invention is programmed to filter out such non-matching content from the items returned to the user. Similarly, the user can improve his selection by selecting multiple character strings and/or selections including non-matching items and replacing the previous query in the second search. As with the first search, the user can select the items to be filtered out.

In one embodiment, the relational database is Postgres and includes the following tables:

In one embodiment, the non-relational database is MongoDB and includes hotel and feature documents having the following structure:

3 , booking engine 120 can be broken down into three components: a search input form 310, session data 320, and algorithmic logic 330. Search input form 310 allows a client to query the database for existing artifacts and, through "autocomplete," invokes desired items hosted as artifacts, presenting them to the user for selection in an autocomplete list. If search input form 310 does not provide an artifact for the user to select, a management log is created, and the search query is evaluated and updated within the database to expand the use of new facilities and/or special services going forward.

The session data 320 stores and applies customer user interactions with the system to provide a learned user experience based on the user's preferences when navigating the user interface. For example, when searching for various facilities and/or special services and/or food/beverage, the user does not need to reset their time/date. The system will save these preferences unless the user resets the session data. The adaptive search function allows for the identification and scoring of customer input and type > score > human input processed through approval > matching of facilities/services/food/beverage to be added to the function. The customer user's interaction with the adaptive search enables the system of the present invention to generate technical impacts on the database system through machine learning of unmatched search input queries, wherein artifacts of unmatched and trending scores are clarified by the customer user and new feature categories are subsequently generated to search, use and purchase members that match and/or have specified evolving characteristics.

Algorithmic logic 330 represents the algorithms and programming that enable the system to interpret data and communicate between components of the system to facilitate desired user outcomes.

Pseudo code corresponding to an algorithm that facilitates searching for reservations, appointments, and purchases of amenities and/or special services includes:

The pseudo code corresponding to the semantic smart search input with auto-completion call function includes:

In one embodiment, a machine learning feature is provided wherein, if a search input is not recognized by the system, a record is generated to evaluate the input value. In another embodiment, a user enters a data string, and if the data string is not recognizable, the system of the present invention can perform various searches to return similar-sounding or similar-looking suggestions for the user to select. When selected, the selection is stored in memory in association with the original search string so that similar suggestions can be provided to subsequent users.

When the input values are validated, new adaptive search inputs are implemented by enabling the member to update the search to facilitate booking, reservations, reservations and/or purchases of amenities and/or special services and/or food/beverages.

Pseudocode illustrating this includes:

The pseudo code corresponding to the optional serial operation is as follows:

Customers interact with the system via the search function, thereby adding search capabilities to the system through adaptive search updates. Member users add search capabilities to the system via APAP. The pseudo code corresponding to dual user input (customer user and member user) includes:

The pseudocode corresponding to the dynamic pricing update is:

The pseudo code corresponding to an availability search using an inventory control system includes:

The pseudo code corresponding to an availability search using an inventory control system includes:

UserInput=READ MachineHumanInterface

#LanguageAnalysis returns a list of languages and the probabilitiespercentage values

Languages=LanguageAnalysis(UserInput)

Location = READ UsersLocation

LocationLanguage=QUERY Language WHERE Location=UsersLocation

Language=LocationLanguage JOIN Location

Database=SELECT Database WHERE Database.Language=Language

END

Autocomplete or text snippets from local expert reviews, blogs, and social media can enhance search input and/or be connected to reference items via search and purchase booking search links. Thus, a consumer user can copy and paste terms they discovered online or through the expert/social news update feature of server 100 into a search to invoke travel tips or recommendations. Content supporting this feature can be retrieved by crawling SOC service 149 through SOC interface 139, and the terms can be stored as artifacts in the database.

In one embodiment, autocomplete and text snippets used to enhance search can be derived from expert reviews that can be uploaded and associated with artifacts. Thus, search results can include one or more reviews and associated artifacts. Customers viewing a review are provided with a search and purchase "book button" within the review text that takes the customer to the exact item (amenities, special services, food or beverages, or accommodations) for reservation.

4 , the member profile administrator portal 122 (also referred to as “APAP”) is broken down into two parts: an asset management dashboard 410 and an inventory control system 420 .

The asset management dashboard 410 is both a front-end user interface and a back-end artifact integration tool. Members use the dashboard to upload and manage their artifact assets (referred to as items when considering client users) so that they are presented in a searchable profile on the system. The dashboard 410 maintains a hierarchy of administrator access rights between members and our system, which is coupled to the computerized system maintained by operators.

Members may also have the opportunity to upload and manage contract documents, such as terms and conditions associated with accommodations and/or features, which the customer must accept when booking the item. Such documents may be presented to the customer or made available to the customer prior to purchase or check-out.

The inventory control system 420 is a system that works in tandem with the asset management dashboard 410. Here, an algorithm treats items as artifacts, such as "features," to segment them within the database, enabling artifacts to be retrieved via search input. These features are driven both manually and dynamically based on supply and demand through price controls. More specifically, members can log into the inventory control system via the APAP 122 and upload/manage specific artifacts. Furthermore, members can dynamically upload/manage their artifacts between their own systems and the inventory control system in real time. With dynamic linking, once an artifact is linked, the inventory control system automatically updates whenever a change occurs within the member's system.

Referring to Figure 5 , a member profile is divided into three sections: Type 510, Products 520, and Services 530. Type 510 refers to the member's category, such as hotel, motel, guest accommodation, travel partner, entertainment partner, dining, club/lounge, residence, or any other hospitality and food/beverage provider. Products 520 refer to any assets a member can offer for immediate or future purchase. Services 530 refer to any services a member can offer for immediate or future purchase. Profiles are generated and maintained within the APAP dashboard 410 and rely on the member's ability to search for, reserve, or purchase: food/beverage, amenities, and/or special services. Profile components may include images or spatial renderings as augmentable artifacts. Feature examples may include, but are not limited to, visually identifiable and/or selectable venues, rooms, or amenities through search availability and/or purchase pricing.

Although not shown in the figure, the present invention collects a large amount of data from users. All searches are captured and stored. Therefore, the system of the present invention has the ability to quickly identify trends and changes in user expectations. Such changes can, for example, identify when user demand increases or decreases rapidly or is outside the normal range. When these atypical conditions are identified and if they are coupled with other information such as general location (such as part of a city), the system of the present invention can recommend pricing changes to members such as hotels, restaurants, clubs/lounge/bars and other tourist accommodations. For example, when demand increases in a particular place, members can adjust the rates of non-rental features upwards. And if demand decreases on a specific date or time, pricing can be reduced. Members can use these price changes to inform customer groups, for example, via digital notifications.

Referring now to FIG6 , to comply with Payment Card Industry ("PCI") regulations, the payment gateway is divided into three third parties: a payment processing API 610, a tax collection API 620, and a merchant bank 630. When a customer user creates a profile on the system in the form of a user profile, not all information required for credit card processing is stored in accordance with PCI. Therefore, the system may rely on these third parties to receive customer user information from the booking engine along with their featured orders to facilitate purchases via financial transactions between the customer user and the member user. Payment for the purchased products and/or services is received by both the system provider and the member, along with confirmation from all parties (customer user, member user, and system provider).

Figure 7 illustrates an exemplary process for a customer interacting with the system. Beginning at the home user interface, the customer can enter their itinerary details, accept search results, select a membership profile to make purchases, check out, and pay through a payment gateway. A variation of this process can be understood with reference to Figure 8 . Typically, the customer begins at the home/login interface 810 . Here, the customer user can perform an item search query or a time/date query by selecting one of the login options 820 . The system utilizes fuzzy logic and algorithms to interpret the data input via the itinerary detail engine. The system then scores the data for processing to validate trend analysis using database components and assess availability via the inventory control system.

Alternatively, the customer can access their customer user profile 826. When logged in, the customer can call up previously explained data through the profile management interface. This information call is extracted from the customer profile database.

Alternatively, the client can access the general member profile via selection 828. The client user can select from various general member profiles presented for query. The information populated on the main/login interface is managed and presented by APAP, which enables the system to present a continuous data deployment of the interface.

From the landing page 810, the customer can use the trip details engine 822 to search by: name; destination; amenities; special offers; or food/beverage using search input 823. In some embodiments, the "destination" input is provided by the customer's device's location system 168 and can include the device's geographic location or the detection of a nearby beacon. The source of the data input is captured and interpreted accordingly by the trip details engine 822.

The customer can also provide dates and search input by selecting 824. This combines the ability to search for items and event availability to narrow the search results to the specific items offered or selected. This combines the inventory control search element within the trip details engine 822.

Via time/date selection 825 , the client user can search by item availability.

History is a subcomponent of the client user profile 826 where the client can select previous actions within the system. Session data and analytics enable the system to call and present a history interface to process the availability of previous input.

When accessing the main/login interface 810, or via search results presented from the trip details engine 822, a client user can select from various member profiles presented for querying. The selected member profile is presented by the main/login interface or as a result of one or more inputs generated by the trip details engine 822.

With respect to the search results, member profiles for which items are available are presented based on the search input from the trip details engine 822 .

Item selection involves an interface that enables a customer user to select a pre-ordered item from a search. The selected item is then identified by the system, facilitating ticketing, reservations, appointments, and/or purchase of the feature via an inventory control system used to process transactions within a payment gateway. In one embodiment, as shown in FIG9 , after selecting an item, the user may have the option to add additional items for checkout. This may be accomplished via a "+ Accommodation"-type button, such as link 1036 shown in FIG12 and link 1056 shown in FIG13 and FIG14 . Such a button or link may include a "+ Amenities"-type function for adding items such as food and beverages, seating options or tables, meeting space, room service, equipment rentals, amenities, or activities. Furthermore, in some embodiments, membership terms and conditions may be presented to or made available to the customer prior to checkout; if the customer does not accept the terms and conditions, the transaction cannot be completed.

Project selection may also include an interface that allows for configuration of the environment for the selected project. The capabilities of the selected project are uploaded and managed in the inventory control system through a series of input and management fields, such as seating arrangement, equipment convenience, lighting specifications, occupancy/capacity, catering, orientation, etc. The customer can select a configuration for the selected project or submit a request for an alternative configuration for approval (not shown).

Checkout includes an interface where the customer user confirms the desired item selections through an editable confirmation of the desired purchase. The system interacts with the payment gateway to complete the scheduled transaction through session data stored within a systematic "breadcrumb" navigation of item selections throughout the process.

A method according to the present invention may follow the flow shown in FIG. 31 , comprising: step 3120 , whereby a customer transmits arbitrary feature search parameters for bookable features to a server; step 3130 , whereby the server searches a feature database for one or more features and their providers that at least partially match the search parameters; step 3140 , whereby the customer receives from the server one or more features and/or one or more identifiers of providers that can provide the one or more features; step 3150 , whereby the customer transmits a selection of providers to the server; and step 3160 , whereby the customer receives from the server a quote for booking the provider's features and/or accommodations. Such a method may also include step 3170 , whereby payment information (optionally) is transmitted to the server and processed. Such a method may also include step 3180 , whereby inventory records for the booked one or more features and/or one or more accommodations are updated. Such a method may also include step 3135 , whereby an external provider database is queried to identify matching one or more features/one or more providers and/or to determine availability. Such a method may also include step 3125 , whereby the server provides auto-complete information to the customer device.

Referring now to Figures 10 and 12 , a portion of an exemplary screenshot 1000 is provided in which a customer user may enter their query to search for available features. Screenshot 1000 includes a query area 1005, which includes a free-form input box 1010, a data selector 1020, a check-in selector area 1030, and a "Search" button 1040. Data selector 1020 may include a time input box and/or a time selector (not shown). Screenshot 1000 may include a member general profile area 1050. In addition to the member's name or destination, features of the member's overall space or even room-specific features may be presented in the search results, allowing the user to select based on their preferences. Figure 12 illustrates the customer user's ability to further specify the search input (travel details) engine by selecting a check-in time/date 1022 and a check-out time/date 1024 for the desired search/purchase of features. In some embodiments where a rate matrix is provided for time/date selection (see, e.g., FIG20 ), specification of timing information via 1022 and 1024 is optional. The occupancy selector area 1030 may include a drop-down box for the number of adults 1032 and a drop-down box for the number of children 1034. Additional rooms may be added to the query by selecting the Add Room link 1036.

11 , in one embodiment, a client user may “log in” on a member login page (e.g., exemplary login page 1001) and initiate a search using a free form input box 1010 and a search button 1010. Additionally, the free form input 1010 is available in navigation throughout the interface, enabling the user to search the free form or focus within a member profile.

With reference to Figures 13 and 14 , according to one embodiment, the search add-on enables coupled searching via a menu-selectable item category housed within a shopping cart-style function. With reference to Figures 14 and 22 , these add-on features also enable post-initial transaction functionality, where a customer can recall their transaction through a history interface and add search items to their existing purchases, as shown in section 1070 . The customer user can also specify search input (travel details) to the engine by selecting a check-in time/date and a check-out time/date via date selector 1075 . In a preferred embodiment, items from more than one member can be added to the shopping cart function for a single checkout transaction.

15 , according to one embodiment, it is possible to enable searching by category within a search engine input. Users can search for specific “items” not only through auto-completion identified by the system, but also through “category sections” such as destinations 1080, membership (e.g., hotels) 1082, facilities 1084, services 1086, and food and beverages 1088.

Referring now to Figures 16, 17, and 18, when a search query is entered into the search input (travel details) engine, user results 1650 are presented in search-specific results displays such as displays 1600, 1601, and 1602. The user can then sort based on sorting preferences 1620 and select members based on their unique search criteria. Displays 1600, 1601, and 1602 may include a breadcrumb navigation indicator 1610. If the user identifies acceptable results in the list, the user may select a Book Now link 1660 to initiate the reservation and/or booking process.

Figures 19 and 20 illustrate time period pricing and pop-up screens presented to the user, wherein pricing is related to the time period. In Figure 19, pop-up screen 1603 shows that certain facility types are configured to change prices based on the time of day and the day of the week. In Figure 20, pop-up screen 1604 shows that certain room types (if available) are configured to change prices based on the day of the week. In some embodiments, pricing can be algorithmically based on availability; for example, if twenty items are available, the price may be lower than if only one or two are available.

22 , according to one embodiment, a search extension component 1670 can also implement a post-initial transaction for invoking and querying inventory availability of selected items to extend a reservation for a specified time increment. The customer user interface may include an extend time selector 1673, a confirm request selection 1674, and an extend request selection 1675. If a specific request is made to include a transaction for additional items, an operator can optionally work with the technical system via a "Concierge Instructions" input form 1671. This functionality can be implemented at the corporate level or entered from the member interface. Finally, search items added to an existing purchase, such as during check-out, can be summarized through the reservation details 1672 history interface for a single transaction, assuming inventory availability, before the selected date/time was entered. Subsequent searches and purchases can be accounted for in other ways.

Figure 23 shows a partial display 2300 of a selected exemplary member profile page. The customer user has the ability to review available offerings in detail, including images and room renderings 2340, descriptions 2330, amenity lists 2320, and desired amenities 2310. Interface 2305 summarizes the search and booking criteria and provides links for booking accommodations or events. Breadcrumb navigation indicator 2350 allows the user to view the progress of the booking process and return to previous steps and screens.

Figure 24 shows a partial screenshot 2400 of a page through which a customer user can interact with the payment gateway to confirm feature selections. The page includes a billing information area 2420, a guest information area 2430, and a hotel concierge instructions area 2440. In one embodiment, a communication input in this field causes a communication, such as an email, to be sent to the concierge along with a check-out confirmation, thereby notifying the member of the customer's request. Once the user confirms their desire to reserve the features shown at point 2410, the customer user can "reserve" their selections and receive a confirmation. Simultaneously, the member and the system provider will receive payment for the products/services purchased via a third-party processing partner. Figure 25 shows a partial screenshot of an exemplary menu cart check-out, showing accommodation and facility policies and cancellation terms 2418 (which can be provided by the member using the APAP interface) and a summary of the check-out transaction 2416. The terms of service checkboxes 2412 and a "reserve" button 2414 are included. The user can edit and delete items in the cart, and one or more items from one or more members can accumulate in the cart. As described above with reference to FIG. 11 , additional terms may be added by performing a new search in the persistent search query box 1010 provided throughout the interface.

In an exemplary user experience, a user can interact with user interface 1000, shown in FIG10 , by entering, for example, "helicopter" into box 1010. The interface may present a category pre-entered drop-down box, as shown in FIG15 , from which the user can select "helicopter" from example category section 1084. The user may then be presented with the tour details interface, shown in FIG13 , where the user can specify a date and time. Upon selecting item pricing link 1057 , the user is presented with a rate matrix 1603 , as shown in FIG19 . Upon selecting the desired item from rate matrix 1603 , the user is presented with the item accounting tour details interface, shown in FIG14 , where the user sees the selected helicopter item in section 1070 and can specify additional requests using section 1056 . For example, if the user selects "+Add Room," the user is presented with a room rate selection matrix, such as 1607 , shown in FIG21 . When selecting room accommodations, returning to the travel details interface and selecting "Book It!", the user will be presented with a menu cart checkout summary 2405 as shown in FIG. 25 , in which the user can review the transaction details, complete the reservation, or make changes.

Figure 26 shows an exemplary member user interaction with the system. Member users typically begin interacting with the system at the main UI; however, this step can be bypassed when a profile is generated. Members can log in to access an existing member profile or generate a member login.

Based on member user input, the system stores user assets as artifacts within the inventory control system. The Member Profile Administrator Profile ("APAP") is a dashboard interface that allows member users and operations personnel to collaborate to maintain member profiles. The interface is maintained within the inventory control system. When member assets are uploaded to the system, the data is interpreted as artifacts used to invoke member functions for product/service quoting. The system can be static and/or dynamic relative to the member system; it includes the ability to work collaboratively with operations personnel. Operations personnel serve as support functions as needed.

The Member Profile consists of a dedicated representation of the Member's information data within the interface, enabling the User to review and select offers for products/services available for purchase. These are presented by searching for the Customer User. The Member Profile is generated by the System through a data transmission channel that statically and/or dynamically exchanges Member Assets with APAP.

Member Profile General Functionality refers to the member's public space pricing. The system maintained within APAP delineates functionality between public and subsidiary spaces. Subsidiary Functionality refers to the member's private space pricing.

FIG27 shows a partial screenshot 2700 of the hotel's amenities section, where members can select their standard amenities and/or special services in section 2710. Here, members can also create new features by selecting Add 2712 and typing the feature into a text box such as box 2714. Alternatively, members can cancel the pre-entered feature. Generally speaking, the items in this section are available for spaces across the entire range; in this example, the member is the hotel.

The hotel image area 2720 attributes images, such as photos 2729, to bookable/reservable/purchasable food and beverages, facilities, and/or special services through a sub-interface (not shown) that enables dynamic pricing of features coupled by availability. Member users can click Add 2722, enter features into box 2724, and select their categories using checkboxes 2726, 2727, and 2728. These two areas can provide searchable features to users. Breadcrumb navigation indicator 2750 allows users to see the progress of the process and return to previous steps and screens.

FIG28 shows a partial screenshot of an exemplary room's amenities screen 2800. If a member user has alternatives to their available product or service offerings, such as rooms, the APAP interface allows for more specific searching and purchasing of those features. The Room Amenities section 2810 is where members can select their standard features independently of the membership itself. Here, members can also create new features by selecting Add 2812 and typing the feature into a box, such as text box 2814. Alternatively, members can remove pre-entered amenities and/or special services by unchecking the associated checkbox. Generally speaking, items in this section are available for the entire space; in this example, the member is the room within the hotel.

Room type area 2820 attributes images to bookable/reservable/purchasable food and beverages, amenities, and/or special services via a sub-interface (not shown) that enables dynamic pricing of features coupled with availability. Room photos, such as photo 2829, can be added, and room details can be added, deleted, or updated using control area 2824. Both sections provide users with searchable features. Breadcrumb navigation indicator 2850 allows users to see the progress of the process and return to previous steps and screens.

In another embodiment, the module interface can be placed or embedded within the member and/or supplier's website and/or can be displayed on the client device to provide a user interface for searching, obtaining and purchasing features, such as amenities and/or special services and/or food/beverage. The module interface can also use the external provider to process reservation queries for desired room configurations through the network gateway.

Embodiments of the present invention can interface with a member's general inventory and/or sales/revenue module by enabling data to be imported into APAP. For example, a comma-separated value (CSV) formatted file from a small hotel or travel member can categorize its inventory in a simple table (e.g., room type in rows and day of the week in columns, allowing prices to vary based on supply and demand). Members can use a spreadsheet program to maintain these table features, export the data, and then utilize the upload>export feature of the system to populate an input form for APAP with rows (e.g., rooms, items, facilities, services, food and beverages; tables) and columns (e.g., days of the week). Pricing can vary throughout the week via ADR (average daily rate) for any category (e.g., rooms, items, facilities, services, food and beverages) and at a fine granularity, such as within a specific 24-hour period. See Figures 19 and 20 for examples of changing the granularity of time-based pricing. Pricing can also be managed by adjusting promotional periods by members or system operators.

Next, with reference to Figures 29 and 30, schematic block diagrams of an exemplary server 100 and an exemplary client device 160 according to an embodiment of the present disclosure are shown, respectively. The server 100 and the client device 160 include respective processors 2955, 3055 and memory/storage media 2950, 3050, both of which are coupled to local interfaces 2960, 3060. As can be appreciated, the local interfaces 2960, 3060 may include, for example, a data bus with an accompanying address/control bus or other bus structure. The client device 160 includes a display 166 coupled to the local interface 3060 to allow the processor 3055 to apply visual data to the display 166, such as a user interface generated by the client application 162. The display 166 may be a holographic display, a super-applied display image, or an augmented reality display. In some embodiments, as will be appreciated, the server 100 and/or client device 160 may include other elements coupled to their respective local interfaces 2960, 3060, such as a positioning system 168 configured to obtain location, proximity, or position data, and other systems. In addition, the client device 160 may include client inputs 164 such as a touch screen, keyboard, switch, mouse, and buttons. The server 100 and client device 160 also include network interfaces 2965, 3065 coupled to the local interfaces 2960, 3060. The network interfaces 2965, 3065 are adapted to allow the server 100 and client device 160 to communicate with each other and with other network resources via a network 155 (see FIG. 1 ), which may be, for example, the Internet, an intranet, or other network systems. The network interfaces 2965, 3065 may employ protocols such as TCP/IP and may communicate over a medium such as WiFi, wired Ethernet, or other network medium.

Stored in the respective memories 2950, 3050 are several components executable by the processors 2955, 3055. Specifically, stored in the memory 2950 of the server 100 may be a reservation module 2920, a member profile manager module 2922, a payment module 2932, a GDS module 2934, a PMS module 2936, a CRM module 2937, a CRS module 2938, and data storage 116. Stored in the memory 3050 of the client device 160 may be the client application 162 and other data and applications. It should be understood that other applications may be stored in the memories 2950, 3050 and executed by the respective processors 2955, 3055, as will be appreciated. When any component discussed herein is implemented in software, it may be in the corresponding machine code of the processor 2955, 3055 or in a source programming language such as C, C++, Java, JavaScript, Perl, PHP, Python, Flash, and/or other programming languages.

Many software components are stored in the respective memories 2950, 3050 and are executable by the respective processors 2955, 3055. In this regard, the term "executable" refers to a program file in a form that can be essentially run by the processor 2955, 3055. Examples of executable programs may be, for example: a compiler that can translate into machine code in a format that can be loaded into a random access portion of the memory 2950, 3050 and run by the respective processor 2955, 3055; source code that can be represented in a suitable format, such as object code that can be loaded into a random access portion of the memory 2950, 3050 and executed by the processor 2955, 3055; or source code that can be interpreted by another executable program to generate instructions in the random access portion of the memory 2950, 3050 that are executed by the processor 2955, 3055, etc. The executable program may be stored in any portion or component of memory 2950, 3050, including, for example, random access memory (RAM), read-only memory (ROM), a hard drive, a solid-state drive, a USB flash drive, a memory card, an optical disk such as a compact disk (CD) or a digital versatile disk (DVD), a floppy disk, a magnetic tape, or other memory component.

Memory 2950, 3050 is defined herein as both volatile and non-volatile memory and data storage components. A volatile component refers to a component that does not retain data values when power is off. A non-volatile component refers to a component that retains data when power is off. Thus, memory 2950, 3050 may include, for example, random access memory (RAM), read-only memory (ROM), a hard drive, a solid-state drive, a USB flash drive, a memory card accessed via a memory card reader, a floppy disk accessed via an associated floppy disk drive, an optical disk accessed via an optical drive, a magnetic tape accessed via an appropriate tape drive, and/or other memory components, or any combination of two or more of these memory components. In addition, RAM may include, for example, static random access memory (SRAM), dynamic random access memory (DRAM), or magnetic random access memory (MRAM), as well as other such memory devices. ROM may include, for example, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or other similar memory devices. Although described herein as a single memory and a single processor, it should be appreciated that both distributed memory and distributed processing are encompassed by the present invention. Such distributed memory can be allocated in any of several known ways, such as, but not limited to, allocation by data type or across multiple data stores housed in different locations. Similarly, distributed processing encompasses any of several known ways, including, but not limited to, processor arrays and multiple different processors located in different locations performing different types of functions.

Furthermore, processors 2955, 3055 may represent multiple processors, and memories 2950, 3050 may represent multiple memories operating in parallel. In this case, local interfaces 2960, 3060 may be a suitable network that facilitates communication between any two of the multiple processors, between any processor and any of the memories, or between any two of the memories. Local interfaces 2960, 3060 may include additional systems designed to coordinate such communication, including, for example, performing load balancing. Processors 2955, 3055 may be electronic or of some other usable configuration.

It will be appreciated that the member device 180 shown in FIG. 1 may utilize similar processor, memory, bus, and network interface architectures as depicted for the server 100 or client device 160 as shown in FIG. 29 and FIG. 30 , respectively.

While the various systems and applications described above may be described as being implemented in software or code executed by general-purpose hardware, such as the processor-based systems described above, alternatively, the various systems and applications described above may be implemented in dedicated hardware or a combination of software/general-purpose hardware and dedicated hardware. If embedded in dedicated hardware, such systems and applications may be implemented as circuits or state machines employing any one or a combination of a variety of technologies. These technologies may include, but are not limited to: discrete logic circuits having logic gates for implementing various logic functions when one or more data signals are applied; application-specific integrated circuits having appropriate logic gates, programmable circuits such as field programmable gate arrays (FPGAs), or other components.

Although the flowcharts of Figures 7, 8, 9 and 26 show the specific order of execution, it should be understood that the execution order may be different from that depicted. For example, the execution order of two or more blocks may be scrambled relative to the order shown. In addition, two or more blocks shown in Figures 7, 8, 9 and 26 may be executed simultaneously or partially simultaneously. In addition, any number of counters, state variables, warning semaphores or messages may be added to the logic flow described herein for purposes of enhancing utility, billing, performance measurement, or providing troubleshooting assistance. It should be understood that all such variations are within the scope of this disclosure.

In addition, when the various systems and applications described herein include software or code, each can be implemented by an instruction execution system such as a processor in a computer system or other system or in combination with any tangible, non-transient computer-readable medium used by the instruction execution system. In this sense, such a system or application may include, for example, instructions and declared statements that can be read from a computer-readable medium and executed by the instruction execution system. In the context of the present disclosure, "computer-readable medium" can be any tangible, non-transient medium that can contain, store, or maintain the above-mentioned systems and applications used by or in combination with the instruction execution system. Computer-readable media can include many physical media, for example, any one of electronic, magnetic, optical, or semiconductor media. More specific examples of suitable computer-readable media include, but are not limited to, tapes, magnetic floppy disks, magnetic hard drives, memory cards, solid-state drives, universal serial bus (USB) flash drives, or optical disks. In addition, the computer-readable medium can be a random access memory (RAM), including, for example, static random access memory (SRAM) and dynamic random access memory (DRAM), or magnetic random access memory (MRAM). Additionally, the computer readable medium may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or other types of memory devices.

It should be emphasized that the above-described embodiments of the present disclosure are merely possible examples of implementations set forth for a clear understanding of the principles of the present disclosure. Many variations and modifications may be made to one or more of the above-described embodiments without departing substantially from the spirit and principles of the present disclosure. All such modifications and variations are intended to be included within the scope of the present disclosure and to be protected by the claims.

Claims (17)

1. A method for selecting and booking customized hospitality/tourism reservations using a processor-based server, said server including a network interface and access to a data store for user preferences, a mismatch query database, a database of hospitality/tourism features including location settings associated with features, and a third party, said method comprising the following steps: Receive at least one desired reception/tourism feature with constraints from a user-controlled network-connected computing device, the constraints including the desired time period and user preferences for the reception/tourism feature, the at least one desired reception/tourism feature including free form input received through a graphical user interface (GUI); Search the database of the reception/tourism characteristics for the availability of the desired time period and at least one desired reception/tourism characteristic that matches the attribute; The user preferences are retrieved from the data storage; the user preferences are populated based on at least one of the responses to user queries and previous bookings; The user preferences are delivered to the network-connected computing device for selection; The network-connected computing device is delivered a list of matching hospitality/tourism locations that match the at least one desired hospitality/tourism feature for selection. The list includes hospitality/tourism locations available during the desired time period, those matching the desired feature, and those chosen based on user preference. Receive instructions from the network-connected computing device regarding the selected reception/tourism location from the list, as well as the user's billing information; The reservation for the reception/tourism location is made by transmitting the reservation details and features to a server associated with the selected reception/tourism location. Deliver a confirmation of the reservation to the network-connected computing device; Entering adaptive learning mode includes: Store any mismatch features in the mismatch query database; Entries from the database that do not match the query are sent to a third party for display; Receive the association between the entry and the bookable feature from the third party; and The database that at least partially conforms to the associated reception/tourism features is reconfigured by adding a new feature field that is associated with at least one of the mismatched entries or evolutionary features; The pre-bookable features include relevant identification characteristics. 2. The method according to claim 1, further comprising the following step: Transmitting booking queries based on the constraints to external providers via the network; and Receive, via the network, an indication of the availability of at least one accommodation provider that meets the constraints from the external provider. 3. The method according to claim 2, further comprising the following step: Receive an indication of acceptance of the reservation quote from the network-connected computing device; Receive payment information from the network-connected computing device; The payment information is transmitted to the payment processor; Update the inventory records in the database of the aforementioned reception/tourism features to record bookings for locations and features; and Confirmation of the reserved quote is transmitted to the network-connected computing device. 4. The method of claim 2, wherein the external provider is selected from the following providers: global distribution system provider, central reservation system provider, inventory system provider, customer relationship management system provider, sales/revenue management system provider, loyalty system provider, and provider's property management system. 5. The method according to claim 1, wherein the at least one reception/tourism feature is provided by at least one boutique hotel. 6. The method according to claim 1, further comprising the following step: Receive the characteristic identifier of the hospitality/tourism provider from the network-connected member device via the network; and The database of the reception/tourism features stores artifacts that associate the identifiers of the reception/tourism features with the identifiers of the reception/tourism providers. 7. The method of claim 1, wherein the constraint further includes a desired room and/or layout configuration. 8. The method of claim 1, wherein the bookable feature is a facility, special service, or food/beverage. 9. The method of claim 1, wherein the mismatch feature is associated with at least one descriptive workpiece for use in multiple facilities. 10. The method of claim 1, wherein the at least one desired reception/tourism feature with constraints is obtained at least partially corresponding to a free form input. 11. A system for identifying and booking menu features from a hospitality/tourism provider, the system comprising: processor; An adaptive feature database stored on a non-transitory computer-readable medium, the adaptive feature database comprising multiple feature artifacts, wherein each feature artifact associates a bookable feature identifier with a reception provider identifier; and A preference database stored on a non-transitory computer-readable medium, the preference database including preferences for reception characteristics and set by the user; and The processor is specified as: Receives arbitrary feature identification information of adaptive pre-orderable features from a network-connected client device via a network, wherein the arbitrary feature identification information is at least partially obtained by using free form input using a graphical user interface on the client device; Analyze the arbitrary feature identification information and determine at least one pre-orderable feature identification; Identification is performed by searching the adaptive feature database for a set of feature artifacts that at least partially match the arbitrary feature identification information; Search the preference database for the user's preferences and the user's preferences associated with the network connection client device; Transmit one or more reception provider identifiers associated with a set of identified feature artifacts and identified user preferences to the client device via the network; Enter adaptive learning mode, thus: Store mismatch features in the database for mismatch queries; Entries from the mismatched query database are sent to a third party for display; Receive the association between the entry and the bookable feature from the third party; and The adaptive feature database, which at least partially conforms to the association, is reconfigured by adding a new feature field that is associated with at least one of the mismatched entries or evolutionary features. Among them, the feature workpiece is the recognizable characteristic of the pre-defined features. 12. The system of claim 11, wherein the processor instructions further include instructions that cause the processor to perform the following processes: The client device receives adaptive accommodation search constraints, which include: an indication of the desired booking period and an indication of the desired geographic location of the accommodation provider; The search of the adaptive feature database is also constrained by multiple artifacts having a reception provider identifier for identifying a reception provider within the desired geographic location and capable of providing accommodation or the bookable feature during the desired booking period. 13. The system of claim 12, wherein the processor instructions further include instructions that cause the processor to perform the following processes: Transmitting booking queries based on the accommodation search constraints to external providers via the network; and Receive, via the network, an indication of the availability of at least one accommodation provider that satisfies the accommodation search constraints from the external provider. 14. The system of claim 13, wherein the processor instructions further include instructions that cause the processor to perform the following processes: Receive an indication of acceptance of the quote from the client device; Receive payment information from the client device; The payment information is transmitted to the payment processor; Send a confirmation of the reservation to the client device. 15. The system of claim 11, wherein the arbitrary feature identification information includes location-based information obtained from the geographic location of the client device or from the detection of neighboring beacons by the client device. 16. The system of claim 11, wherein the processor instructions further include instructions that cause the processor to perform the following processes: Store information identifying any non-matching features in the non-matching query database; Entries from the database that do not match the query are sent for the commenter to view; Receive the adaptive association between the entry and the pre-bookable feature identifier; The associations are stored in the adaptive feature database; Receive the reception provider's identifier from the network-connected member device via the network; and The adaptive feature database stores artifacts that associate the identifiers of reception features with the identifiers of the reception providers; The adaptive feature database includes multiple associations, and searching the adaptive feature database includes searching the associations. 17. The system of claim 11, wherein the mismatch feature is associated with at least one descriptive workpiece used in multiple facilities.