Title: Basket Request Schema The basket request provides details of a basket to be validated. It must provide enough information to identify the company the basket is coming from, and the date and store against which the basket will be validated. Custom Attributes and their values can be added at to basket or item elements where they have been defined. Version 1.0 : 2014-07-14. Initial schema creation. Version 1.1 : 2015-06-14. Updated to include 'confirmed' flag. Version 1.2 : 2015-10-02. Updated to include 'currencycode' attribute. Version 1.3 : 2017-01-09. Updated to include max lengths and ensure sequence is not fixed and descriptions. Version 1.4 : 2018-04-18. Company key is now optional as it is provided in the REST url (though required for WCF). The coupon code to be utilized by promotions. The selected item's id, as provided with the select list Flag indicating whether to use an existing item from the basket where available. The promotion id from the select list The unique id for the line in the basket. The identifier for the product. Can optionally be used in conjunction with the Variant Code, where the combination of the Product Code and Variant Code must be unique. The Variant Code for the product where applicable. A barcode reference for the product. Not used in product identification. The quantity for the line The price of each item on the line Where applicable, any manual discount already applied to the line by the integrating system. Flag indicating whether the item is a delivery charge Flag indicating whether the item should always be excluded from promotions processing Flag indicating whether the basket item is a gift card. A unique reference for the basket. Where a basket is submitted multiple times the reference should be persisted for all submissions. Typically this would be an order or transaction unique reference. The company key assigned to your company. To view the company key navigate to Configuration / Manage Company. The sale date for the basket. Where a basket is submitted multiple times, the basket date should be persisted for all submissions. The basket date is used to establish which promotions are available to the basket. The Store from which the basket is being submitted. Stores are part of the store hierarchy and the supported values for this attribute are managed as part of the hierarchy. The Store Group from which the basket is being submitted. The Channel from which the basket is being submitted. Where applicable, the group or segmentation of the customer. The unique identifier for the customer. An internal reference should be provided, not identifiable customer details. The currently selected delivery method for the basket The total value of the basket being validated. This is the total of all lines in the basket and a delivery price where applicable. Where applicable, a manual discount that has been applied to the basket from the integrating system. The price for the currently selected delivery method for the basket. Where applicable, a manual discount that has been applied to the delivery from the integrating system. A flag indicating whether to provide details on missed promotions A flag indicating whether the basket has been confirmed as a sale. When promotions issue or utilize coupon codes for the basket being validated, those codes will not be confirmed as issued or used unless the basket Confirmed flag has a value of true. The currency code for the basket being submitted. Where required currency codes can be used in the criteria of promotions to ensure a promotion targets only the required currency. Where applicable, the loyalty card number for the customer/contact.