Hotel-Spider Connectivity Solutions
Hotel-Spider is a Software-as-a-Service solution designed for the hospitality market. Through an unique entry point into the world of online distribution, hoteliers (Hotels, Appartments, Bed-n-Breakfasts, etc..) can manage all there is to being a 21st century hospitality provider. Proper distribution of inventories, rates and stay restrictions being the basics of a successfull online strategy, Hotel-Spider offers multiple solutions for:
- SpiderXML: Third party software providers to push inventory, rates and stay restrictions to Hotel-Spider and to pull/receive reservations/modifications/cancellations/communications from Hotel-Spider. Examples of third party providers that might potentially be interested by this solution are:
- Property Management Systems
- Revenue Management Systems
- Channel-Managers seeking to extend the number of channels they wish to offer.
- Web-Booking Engines seeking to extend the services offered to their customers.
- Central Reservation Systems seeking to extend the services offered to their customers.
- SpiderConnect: Third party software providers to receive inventory, rates and stay restrictions from Hotel-Spider via PUSH notification and to return reservations/modifications/cancellations to Hotel-Spider via PULL or via PUSH notification. Examples of third party providers that might potentially be interested by this solution are:
- Online Travel Agencies with their own backoffice for managing inventory, rates and stay restrictions.
- SpiderCRS / SpiderWBE: Third party software providers to query for property descriptive information, to query for the property's available offers and the book/amend/cancel a reservation. Examples of third party providers that might potentially be interested by this solution are:
- Web-Agencies seeking to offer a fully integrated web-booking experience.
- New online hotel booking portals that wish to sell hotels but do not wish to cope with all the complexity of the hospitality market.
- An online hotel portal seeking to gain access to additional properties.
Depending on the manner a third party wishes to integrate with Hotel-Spider one or several XML interfaces are available. All our interfaces have been developped according to the internationally recognised protocols OTA (Open Travel Alliance: http://www.opentravel.org) and HTNG (Hotel Technology Next Generation: http://www.htng.org). An extensive implementation of both protocols should allow the vast majority of third party software providers to re-use previous developments against the same standards.
Throughout the different chapters that will follow the different implementations of the protocols will be explained.
- Getting started
- Changelogs
- Understanding the data model
- SpiderXML (PMS) interfaces
- Alpinebits
- Hotel Technology Next Generation (HTNG)
- Open Travel Alliance (OTA)
- Transmission
- Authentication methods
- Room type and/or rate plan codes
- Best practices
- OTA_HotelAvailNotifRQ / OTA_HotelAvailNotifRS
- OTA_HotelBookingRuleNotifRQ / OTA_HotelBookingRuleNotifRS
- OTA_HotelBookingRuleRQ / OTA_HotelBookingRuleRS
- OTA_HotelDescriptiveInfoRQ / OTA_HotelDescriptiveInfoRS
- OTA_HotelInvCountNotifRQ / OTA_HotelInvCountNotifRS
- OTA_HotelInvCountRQ / OTA_HotelInvCountRS
- OTA_HotelRateAmountNotifRQ / OTA_HotelRateAmountNotifRS
- OTA_HotelRatePlanNotifRQ / OTA_HotelRatePlanNotifRS
- OTA_HotelRatePlanRQ / OTA_HotelRatePlanRS
- OTA_HotelRoomListRQ / OTA_HotelRoomListRS
- OTA_PingRQ / OTA_PingRS
- OTA_ReadRQ / OTA_HotelResNotifRQ or OTA_ResRetrieveRS
- OTA_NotifReportRQ / OTA_NotifReportRS
- OTA_HotelResNotifRS / OTA_HotelResNotifRS
- OTA_HotelResNotifRQ / OTA_HotelResNotifRS
- Success, Warning and Error Types
- Data types
- OTA_CodeType
- Additional Detail Type (ADT)
- Address Use Type (AUT)
- Age Qualifying Code (AQC)
- Booking Channel Type (BCT)
- Business Srvc Type (BUS)
- Charge Type (CHG)
- Contact Location (CON)
- Contact Srvc Code (CSC)
- Content Format Code (CFC)
- Email Address Type (EAT)
- Error Codes (ERR)
- Error Warning Type (EWT)
- Hotel Amenity Code (HAC)
- Hotel Status Code (HST)
- Meal Plan Type (MPT)
- Payment Card Code type
- Payment Type (PMT)
- Phone Location Type (PLT)
- Picture Category Code (PIC)
- Position Accuracy Code (PAC)
- Profile Type (PRT)
- Proximity (PRX)
- Rate Plan Type (RPT)
- Room Amenity Type (RMA)
- Unique Id Type (UIT)
- Unit of Measure Code (UOM)
- Guest Room Info (GRI)
- Architectural Style Code (ARC)
- Property Class Type (PCT)
- Segment Category Code (SEG)
- Location Category Codes (LOC)
- Standard types
- Enumeration types
- Gender Type (Gender_Type)
- Guarantee Type (Guarantee_Type)
- Offset Drop Time type (OffsetDropTime_Type)
- Currency Code Type (CurrencyCode_Type)
- Sharing Type (Sharing_Type)
- Availability Status Type (AvailabilityStatus_Type)
- PMS Reservation Status Type (PMS_ResStatusType)
- Service pricing type (ServicePricingType)
- Target Type (Target_Type)
- OTA_CodeType
- Reservation XML structure
- Specific call : retrieve channels list
- SpiderCRS / SpiderWBE
- SpiderConnect
- Transmission from Hotel-Spider to an online booking solution
- Managing errors
- Retrieving the room types and the rate plans
- Transmission of the inventories
- Transmission of the prices
- Transmission of the booking rules
- Transmission of the reservations
- SpiderMeta
- Support Resources
- Finance & Accounting
- RunMyAccounts
- Zuora doc
- Zuora Tenant configuration
- Limiting affectation of BookingChannel per Zuora ProductRatePlan
- Moving a hotel from a Tenant A to a Tenant B
- Changing ZuoraCurrencyCode for a hotel
- Common check on billrun
- Zuora Accounts Receivables for dummies
- Stripe v2 integration
- Re-Invoice Reconline GDS invoices to customers
- Bexio
- Zoho Expense