POST /Locations

GENERAL INFORMATION

Purpose

This endpoint is used for creating Locations and updating them if they have been modified.

How the data is used

All the transactional data like sales and stock is connected to a location. Also the AI model generates transfers/stock targets on a location level, making it a mandatory dataset. In general all locations that either have stock and/or create revenue is determined as a location.

Best practices

1. It is needed to create your warehouse(s) as a location. Mostly the warehouse(s) that are involved in the replenishment/redistribution/initial distribution process.

2. It is also needed to create the brick and mortar store as a location and for the brick and mortar store the address of the location is mandatory if you need the AI model to generate predictions for these locations. We use the address data to establish the weather data which is crucial for the model, but the model also relies additional data that can be determined by the address, like demographic data.

3. If you also have online channels like webshops or apps, we recommend to create a location for each of these channels. This way you can connect these locationId’s in the POST /Sales endpoint to share the sales per channel. This is valuable especially if you want the AI model to generate predictions for these sales channels.

4. When you have B2B customers in your process, for example resellers of your product where you manage their inventory (VMI) and do the replenishment yourself, we also advise to create a location for each of your customer’s locations, so you are able to link the sales coming from their EDI sales reports to the correct location in the POST /Sales endpoint.

5. If you heavily depend on the GLN number of your locations/B2B customers, we recommend to share this GLN in this endpoint, because we can generate output using this GLN, like in the GET /Recommendations/transfers endpoint.

6. We can support multiple methods of sharing the address of the location, you can pick 1:

   a. Sharing the address in multiple fields called streetName + houseNo + houseNoAddition + postalCode + city

   b. Sharing the entire address string in 1 field called address

   c. Using the latitude and longitude

7. For our redistribution functionality we can use the email field on the location to send an email to locations who have goods to redistribute, where we attach a PDF file with all the information. So if you already manage the email addresses of you location and you want to use the redistribution functionality it is recommended to implement this. You can also manage the email addresses of the locations in our portal, so it is not required.

Common pitfalls

1. Not aligning correctly with the business which types of locations needs to be created at Wair.

2. Location names must be clear and unique. Example:

   ❌ “H&M”

   ✅ “H&M Amsterdam”, “H&M Rotterdam”

   This helps users easily identify and manage their stores.

TECHNICAL INFORMATION

Authentication

Bearer token, information on page POST /Token

Headers

QueryParameters:

Body example:

{
  "locations": [
    {
      "locationId": "1b935f00-dbf6-47eb-9e39-b3be667d44c3",
      "code": "0001",
      "name": "Store Amsterdam",
      "gln": "5449000009067",
      "postalCode": "0000AA",
      "address": "Locationstreet 1",
      "houseNo": "1",
      "houseNoAddition": "a",
      "streetName": "Locationstreet",
      "city": "Amsterdam",
      "country": "NLD",
      "email": "0001@location.com",
      "latitude": 26.357896,
      "longitude": 127.783809,
      "dateOpened": "2001-09-08T00:00:00.908Z",
      "dateClosed": "2024-09-08T08:21:02.908Z"
    }
  ]
}

Additional information:

RESPONSE

StatusCodes:

200 = OK.

401 = Unauthorized, which means an expired/missing/invalid token.

400 = Bad request, see body of the response to check which validation errors have occured.

500 = System error, see body of the response to check which error has occured or contact integration support.

Body Example:

No body in the response.