> For the complete documentation index, see [llms.txt](https://api-docs.urbanpiper.com/downstream/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api-docs.urbanpiper.com/downstream/getting-started/onboarding-process.md).

# Onboarding Process

**Merchant account creation**

* **Conversion** - The POS partnership team creates a merchant account (Atlas) in our system.
* **Creation -** Partner shall receive an email containing Atlas dashboard and Satellite Prime login details and the Auth key to populate the data in the production environment.

**Merchant data population for go-live**

This would be the final step to be done before taking an outlet live. You would have the production host URL by now and are expected to push the required data through the API like store creation, menu push etc. The flowchart below will guide you to complete this step.

![Making the store go-live ready](https://1025490410-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1Mp6yf12d7ZUOZCcbZU0%2Fuploads%2FhN1IL7sy9FJ8al0Lo5jg%2FUntitled%20Diagram-go-live.drawio.png?alt=media\&token=413595d1-6891-488f-8eb3-ac4f2dc84dc8)

* **Login -** Log in to Atlas (the merchant portal) with the credentials you received.
* **Webhooks -** Make sure the right API key and production URL are used at your end. Configure your webhook URLs via API or manually through Atlas.
* **Stores & Menu** - Push the Stores, add the platform details for each store and Menu data using the API or configure the same through Atlas manually. Verify the data using the callbacks or through Atlas.
* **Go-Live** **-** Data pushed will be verified by the Onboarding Manager post which outlet will be sent for mapping to the aggregator. Once the mapped menu will be pushed to the aggregator we will communicate the go-live.


---

# 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://api-docs.urbanpiper.com/downstream/getting-started/onboarding-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.