Document type: Offer

[ 1 Rule: Offer document type (server) ] [ 2 Rule: Offer document type (client) ]

The Offer document type makes it possible to deliver information on offers via Veloconnect.

In practice, two basic use cases of various forms are conceivable here, in particular:

Provision of a trader-specific offer.
Supplier's order proposals to their trader, based on past orders/pre-orders.
Order proposals based on trader classification (compulsory items in the assortment)
Publication of general, e.g. seasonal offers
Discontinued list of previous year's reduced models
Weekly promotion

Note: The offer purely comprises a list of articles. The trader can order these articles in full or also in part by means of their merchandise management system via the functions described in Veloconnect 1.1. The supplier must ensure that the trader receives the prices specified in the offer in response to all price queries made during the offer's validity period. A direct reference to an offer is not provided for in the ordering process. Deviations between prices in the offer and, for example, a GetItemDetails query must be strictly avoided.

Rule: Offer document type (server)

The Offer document type is optional. A Veloconnect-compliant server implements the document type via the two operations OfferQuery and OfferDetails.
Special search terms for offers and their purpose can be communicated by using the SpecialRequestReference elements in the profile.

Rule: Offer document type (client)

A Veloconnect-compliant client intending to use the Offer document type must check whether the server's profile contains SpecialRequestReference elements, and whether these are appropriately indicated to the user.