Operation: StockTransmitB2B
Availability
A typical scenario is that a supplier presents its products on its brand website, naming retailers that carry its products (e.g., BikeLocal). The supplier can show customers the availability of individual products at respective local dealers if they provide him with the availability or inventory of the products.
Example: Bike manufacturer XYZbike shows its bikes on its website. A customer would like to test ride a bike and is looking for a dealer near him. He enters his ZIP code on the supplier's brand homepage and is shown a dealer in his vicinity where it is indicated that the bike is currently available in the correct variant in the store.
Here, it is usually sufficient if availabilities are transmitted.
Inventory
Another conceivable scenario is that a supplier agrees with bike dealers on an automatic ordering system with minimum stock quantities in the store:
As part of a shop-in-shop system, the supplier stocks a self-service merchandise wall and sends replenishment whenever the inventory of the merchandise falls below a specified minimum stock quantity. Stocks are regularly updated according to sales and transferred to the supplier. (The control of the minimum stock quantities is done in the WaWi.) Here it is mandatory to transmit the stock.
Valid for both scenarios:
Article identification (StockTransmitB2BLine).
For the identification of an item the order number of the supplier (SellersItemIdentification) is sufficient, since this is known to both partners. This information is mandatory. It may also be useful to transmit the item number of the merchant (BuyersItemIdentification) to enable a unique identification of the item in the merchant's inventory control system when the server responds. (The item could be created twice in the merchant's WaWi with two different numbers). The specification is optional.
Transmission (StockTransmitB2BRequest)
For the transmission (StockTransmitB2BRequest), specify a time and whether it is a full or incremental upload. (FrequenceType)
For each item, in addition to the IDs, at least the availability must be transmitted, which can correspond to the following values:
1 = available
2 = limited availability
3 = not available.
Additionally the stock can be transmitted. (StockTransmitB2BLine)
Processing Server
In a complete upload, the server saves the data and deletes all previously saved data - regardless of whether the new upload is to the same extent or with the same items. In an incremental upload, the server overwrites only the data of those articles for which a new value is sent.
The data remains valid until the following complete upload or until it is overwritten by an incremental upload.
Response (StockTransmitB2BResponse)
In an initial, immediate response (StockTransmitB2BResponse), the server must acknowledge receipt or processing of the upload and transmit a transaction ID.
The following Transaction States apply here:
84 = Data is imported
85 = Data has been imported, from now on the status of the items can be returned.
184 = Transaction closed. Items can no longer be returned
ItemStatus
Processing log (GetItemStatusStockTransmitB2BRequest)
After a successful StockTransmit, the merchant's Wawi fetches a log of the processing with the corresponding transaction ID by request (GetItemStatusStockTransmitB2BRequest).
The following transaction states apply:
430 = Transaction still running
200 = Transaction completed
Response (GetItemStatusStockTransmitB2BResponse)
The response (GetItemStatusStockTransmitB2BResponse) is in the form of an item list (StockTransmitB2BResponseLine) with the following information per item:
Vendor Item Number (SellersItemIdentification) Mandatory.
Seller item number (BuyersItemIdentification) (if transmitted in the request)
The item was found at the supplier (true) or not found (false)
The list can be divided into packages that client and server negotiate with each other
(similar to the TextSearch transaction).
Translated with www.DeepL.com/Translator (free version)