> For the complete documentation index, see [llms.txt](https://help.urbanpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.urbanpiper.com/pos-integrations/touchbistro/introduction.md).

# Introduction

UrbanPiper’s integration with TouchBistro allows you to seamlessly manage your online ordering operations directly from your POS system. 

This provides a centralised solution to handle multiple delivery service providers (DSPs) such as DoorDash, Uber Eats, and more from a single platform.

This article outlines the complete onboarding process to help you get your TouchBistro menu live and fully functional across DSP platforms using UrbanPiper.

 By following the steps in this document, you will be able to:

* Enable the integration between TouchBistro and UrbanPiper
* Prepare your TouchBistro menu for online ordering
* Import your menu into the UrbanPiper Atlas dashboard
* Set up store hours, brand configurations, and locations in Atlas
* Connect and activate your store on DSP platforms
* Manage essential workflows, including:
* Marking items out of stock (86'ing)
* Enabling or disabling stores
* Controlling item availability

<br>


---

# 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://help.urbanpiper.com/pos-integrations/touchbistro/introduction.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.