Adding listings to facilities
Listing overview
Listings represent the articles offered at a specific facility. Although optional, they are essential for certain functionalities, such as dynamic order routing.
Facility-specific listings
Different facilities may carry different assortments. For example, an article sold in Lisbon might not be offered in Helsinki. This is why listings are managed per facility, ensuring that only available articles are listed. In this tutorial's example, the assortments are mostly similar, but the Helsinki facility does not offer summer dresses and sandals, while the Lisbon facility does not offer winter boots and parkas.
Create listings for a facility
Once the desired articles for a facility are determined, the listings can be added. This tutorial uses a store in Frankfurt as an example, where all articles are sold.
To create listings, the target facility's ID is required. This ID can be retrieved from the facility endpoint that was used to create the facility. A PUT request containing a ListingsForCreation object is sent to the listings endpoint to add the listings.
A successful request returns an empty 200 OK response. The properties in the request body are detailed below:
tenantArticleId: The unique identifier for the article within the tenant's system.price: The selling price of the article.title: The display title for the article.imageUrl: A URL for the article's image, which can be displayed in client applications.scannableCodes: A list of scannable codes for the article, such as a European Article Number (EAN) or other barcodes. These are used during the picking process.measurementUnitKey: The unit in which the article is measured. For example,UNITfor individual garments or a weight unit likeKILOGRAMSin a food context.
With facilities and listings configured, the next step is to use the orders endpoint for testing.
Last updated