> For the complete documentation index, see [llms.txt](https://developer.rategain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.rategain.com/content/integration-process.md).

# Integration Process

This document outlines the end-to-end process for integrating a Demand Partner with RateGain and Hotel Suppliers. It includes all necessary steps, ownership, and milestones from commercial setup to full rollout.

***

### 🧾 Step 1: Commercial Arrangements

* A commercial agreement must be signed between the **Demand Partner & RateGain**.
* A separate commercial agreement is required between the **Demand Partner & Hotel Supplier**.
* **Approval from RateGain’s commercial team** is mandatory before initiating integration.

***

### 📞 Step 2: Tri-Party Kick-off Call

* A **Tri-Party Kick-Off Call** is conducted between **RateGain, the Demand Partner, and the Hotel Supplier**.
* Objectives of the call:
  * Review the **Kick-Off Questionnaire** to clarify tasks, ownership, and next steps.
  * Understand expected **timelines** from the demand partner for setup, development, testing, and certification.
  * **Highlight exceptions** (if any).
  * Create the Statement of Work (SOW) pre-Kick-off call.
  * Define and agree on **integration quality metrics** for the Pilot and Go-Live phases.

***

### ⚙️ Step 3: Configuration Setup

* Company profile creation
* IP whitelisting
* Generation of SGA (Source Code)
* VIP URL creation for:
  * Availability
  * Booking
* Portal self-registration (documentation provided separately)
* SFTP setup
* Nightly **ODDCCN** enablement
* Creation of **NRCs (Negotiated Rate Codes)**
* **Portal access** for PDS (Property Download Site)

***

### 💻 Step 4: API Development

* **SOW sign-off** by Demand Partner (prepared by RateGain)
* **API walkthrough** for:
  * ARI (Availability, Rates, Inventory)
  * Static Content (if applicable)
* RateGain to provide:
  * API documentation
  * Sample XMLs
  * Ongoing technical support
* A **project plan** is created and tracked by RateGain based on committed timelines.
* Regular **weekly/bi-weekly sync-up calls** for:
  * Status tracking
  * Query/blocker resolution

***

### ✅ Step 5: Certification

* Certification to be conducted in **UAT or Production**
* Quality Check:
  * Verify data consumption by the Demand Partner
  * Ensure the correct display of **mandatory content** on the Demand Partner’s platform
* Run a **pilot** with a limited number of properties
* Upon successful results → **Go Live**

***

### 🚀 Step 6: Roll Out

* Pilot launch with a **limited set of properties**
* Execute a **scheduled rollout plan** for upcoming batches
* Complete **final rollout** for all properties under contract

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.rategain.com/content/integration-process.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
