> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/1.-resort-pos-integration/rtp/3.-non-flaik-related-rtp-configuration/order-import-service.md).

# Order Import Service

A user guide to implement the RTP functionality which allows resorts to upload group sales orders into the system instead of entering them manually.

### What It Is

Are you a resort that needs to enter in large group bookings into RTP but find it very time consuming to add in all the details to Customer Manager, create an order, sell the correct product to each person, etc? RTP has a tool to help with this exact scenario that isn't widely known. Called 'Order Import Service', it's a tool that allows users to import an Excel spreadsheet to create an order in RTP. 

Steps the tool can do:

* Create customers - first name, last name, & DOB
* Create an order
* Sell products
* Create/update someone's Rental Profile

### Installation

* Install the RTP One Order Import Service on to the RTP One application server.
* To do this, either follow RTP documentation or reach out to flaik's Managed Services team.
* Contact flaik for a copy of the sample template spreadsheet.

### Import File

* Open the sample template spreadsheet.
* Save the spreadsheet as a copy (eg give it a unique name so as to not overwrite the original template)
* Update the fields in row 2 with the order details.
* Update rows 4+ with customer & product details, creating a row per customer.

#### Order Details (row 2)

<table><thead><tr><th width="160">Field</th><th width="105">Required</th><th width="253">Details</th><th>System Defaults</th></tr></thead><tbody><tr><td>Order Type</td><td>Yes</td><td>System Administration > Transaction Management > Order Category</td><td>1. Consumer<br>2. Reseller<br>3. Reseller Direct<br>4. Reseller Indirect</td></tr><tr><td>Order Description</td><td>No</td><td>Can be whatever you like. eg 'Smith Primary School'</td><td></td></tr><tr><td>Customer ID</td><td>No</td><td>IP must be entered into either Customer ID or Reseller ID (or both)</td><td></td></tr><tr><td>Reseller ID</td><td>No</td><td>Only required for order types 2-4</td><td></td></tr><tr><td>Relationship Type</td><td>No</td><td>System Administration > Customer System Management > Relationship</td><td>1 Family Member<br>2 Friend<br>3 Employee<br>4 Group Member<br>101 Reseller Customer<br>102 Reseller Employee</td></tr><tr><td>Sales Channel</td><td>Yes</td><td>Product Administration > Product Property Management > Sales Channel</td><td></td></tr><tr><td>Sales Location</td><td>Yes</td><td></td><td></td></tr><tr><td>Quote Date</td><td>Yes</td><td></td><td></td></tr><tr><td>Arrival Date</td><td>Yes</td><td></td><td></td></tr><tr><td>Arrival Time</td><td>Yes</td><td>Format like '11:00:00 AM'</td><td></td></tr><tr><td>Departure Date</td><td>No</td><td></td><td></td></tr><tr><td>Delivery Date</td><td>No</td><td></td><td></td></tr><tr><td>Delivery Method</td><td>No</td><td>Product Administration > Delivery Management > Delivery Method</td><td>1 Default Delivery Method</td></tr><tr><td>Delivery Detail</td><td>No</td><td></td><td></td></tr><tr><td>Delivery Timeframe</td><td>No</td><td></td><td></td></tr><tr><td>Delivery Comment</td><td>No</td><td></td><td></td></tr><tr><td>Order Print Line</td><td>No</td><td></td><td></td></tr><tr><td>Order Comment</td><td>No</td><td></td><td></td></tr><tr><td>Reseller Reference</td><td>No</td><td></td><td></td></tr></tbody></table>

###

#### Customer Details

<table><thead><tr><th width="176">Field</th><th width="115">Required</th><th width="255">Details</th><th>System Defaults</th></tr></thead><tbody><tr><td>Customer IP Code</td><td>No</td><td></td><td></td></tr><tr><td>Customer First Name</td><td>No</td><td>Required if leaving Customer IP Code field blank</td><td></td></tr><tr><td>Customer Last Name</td><td>No</td><td>Required if leaving Customer IP Code field blank</td><td></td></tr><tr><td>Date of Birth</td><td>No</td><td>Required if leaving Customer IP Code field blank</td><td></td></tr><tr><td>DIN Age</td><td>No</td><td>Rental Administration > Rental Management > Rental DIN Age</td><td>0:  10- 49yrs<br>1: either 9yrs &#x26; under or 50yrs &#x26; over</td></tr><tr><td>DIN Weight</td><td>No</td><td>Rental Administration > Rental Management > Rental DIN Weight</td><td></td></tr><tr><td>DIN Height</td><td>No</td><td>Rental Administration > Rental Management > Rental DIN Height</td><td></td></tr><tr><td>DIN Skier Type</td><td>No</td><td>Rental Administration > Rental Management > Rental DIN Skier Type</td><td></td></tr><tr><td>DIN Shoe Size</td><td>No</td><td>Rental Administration > Rental Management > Shoe Size Type</td><td></td></tr><tr><td>DIN Goofy Indicator</td><td>No</td><td></td><td>Y / N</td></tr><tr><td>Product Header Code</td><td>Yes</td><td>Multiple can be entered if separated by the pipe symbol |</td><td></td></tr><tr><td>Product Date</td><td>Yes</td><td></td><td></td></tr><tr><td>Product Quantity</td><td>Yes</td><td></td><td></td></tr></tbody></table>

### Required Fields

Although the grids above indicates some fields as being not required, that can change depending on what has been entered in other fields. Examples:

* The Customer IP and Reseller IP are both listed an *not required*, but one field must be included.
  * If the Order Type is 2-4 (Reseller orders), then the reseller's IP must be included. The Customer IP can be left blank though, and the customers will be created in rows 4+.
  * If the Order Type is 1 (Consumer Order), then the customer attached to the order must be included.&#x20;
    * eg - creating an order for a group such as a school. Create the School as a customer (if needed) and then enter in their IP# into the Customer field. Create the customers in rows 4+.
* In the Customer Details section, either the IP or the First Name/Last Name/DOB must be filled in.
* Rental DIN details - not required for non-rental items, but required if Rental Tools will be utilized to calculate DIN.

### Rental Details

For the Rental fields, the following system defaults must be used. Customer weights or heights will need to be converted accordingly.

![](https://3412627069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdh5JD0cdH4KWbjolN2Aa%2Fuploads%2FPldZII7kBLfXyA2Dubqo%2Fimage.png?alt=media\&token=34875bb2-ecb9-4b9e-8992-2912b615b85f)![](https://3412627069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdh5JD0cdH4KWbjolN2Aa%2Fuploads%2FK27pFNUY85uYTnQs2zHy%2Fimage.png?alt=media\&token=11990c09-194f-41d2-adc3-7523ef909ea5)![](https://3412627069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdh5JD0cdH4KWbjolN2Aa%2Fuploads%2F6qhDWaW6LZ52RHWP0yhV%2Fimage.png?alt=media\&token=b254343d-2a93-4ebb-9eb0-77683b3b55bc)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/1.-resort-pos-integration/rtp/3.-non-flaik-related-rtp-configuration/order-import-service.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.