Adding listings to facilities
What are listings?
Listings are the items we offer in a facility. Even though they are optional, they are very helpful for several functionalities, especially dynamic order routing.
Why does every facility have its own listings?
An article we offer in Lisbon might not run in Helsinki. That's why it makes more sense not to list that article in facilities that do not sell an item. In this tutorial, the items offered are very similar. In Helsinki, LU.XY does not sell summer dresses and sandals. In Lissabon, they don't sell winter boots and parkas.
Adding listings to the facilities
After we decide which items to list in which facility, we can start adding them to the facilities. In this tutorial page, we start with the store in Frankfurt, where all items are sold. You need the facility ID for which you want to create a listing. The ID can be received via the facility endpoint, which we used to create the facility.
For adding a listing, we send a PUT request to the listings endpoint containing a ListingsForCreation object:
The response should be an empty 200 OK response if the request was successful. Let's have a look at the properties:
tenantArticleId: The ID the article has in your systems must be unique.price: The price at which the article is sold.title: The title that article has.imageUrl: URL where an image of that article is found will be shown to the clients we offer.scannableCodes: List of scannable codes for that item. Used while picking. Might be the EAN or any other barcode.measurementUnitKey: Unit in which that article is counted; in this case, we sell whole units of garments. In the food context, that might be a weighing unit like kilograms.
With the facilities and the listings being set, we can start using the orders endpoint for testing.
Last updated