# Create/Update Store

The first step in the integration, or even to get started otherwise, is to create a store for which will lay the platform for the menu to be pushed. You may also choose to create stores in bulk at one go provided you already have the data ready for the same. There are two ways for store creation:

1. It can be directly created through Atlas, or
2. Creating it through the Store create/update API.

Creation of a store through Atlas is a manual process where you would need to login to Atlas and add the store under the "Locations" tab. To know more about Atlas, you can follow this [article](/downstream/resources/atlas.md).

The Creation of store(s) through the API is a more encouraging way for getting stores added to our platform. The stores can also be updated once created by referencing it through the reference id of the store, more about which is explained in the [API documentation](/downstream/api/endpoints/stores/add-update-stores.md). Once the API is called, the store creation request is processed asynchronously and the success or failure of the processing is made available through the Store Add/Update Callback mentioned in the [Webhooks](/downstream/getting-started/webhooks-callbacks.md) section.

In Gamma, please make sure that you set the status of the API to *In-Progress* when you plan to start its implementation and once the implementation is done on your side, change it to *To-be-verified*.

#### **Create/Update Stores API**

![Create/Update Stores Feature Update in Gamma](/files/piAJoXfbrx75ulM8Xi7a)

#### Create/Update Stores Callback

![Create/Update Stores Callback Feature Update in Gamma](/files/ZFltlrWgC9MoEHD5oblx)


---

# Agent Instructions: 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:

```
GET https://api-docs.urbanpiper.com/downstream/manage-stores/create-update-store.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.