<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2012 rel. 2 (http://www.altova.com) by Alin Pop (Zendor GSI Commerce) -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
	<xs:element name="returnStatus">
		<xs:complexType>
			<xs:sequence>
				<xs:element name="return" maxOccurs="unbounded">
					<xs:complexType>
						<xs:all>
							<xs:element name="orderId" type="xs:string">
								<xs:annotation>
									<xs:documentation>Web-store order identifier.</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="rmaNumber" type="xs:string" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Authorization identifier (RMA - return merchandise authorization).

										If the RMA interface is used in the feeds flow then this would be populated with the given RMA code from your system.

										Otherwise, It is automatically generated by Radial's system. It follows next pattern: RET-[webstore order number]-[RETURN COUNT  issued for the current sales order]. E.e. RET-1234567810-01</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="rmaStatus" type="xs:string">
								<xs:annotation>
									<xs:documentation>Status of the return. Valid value is RETURNED.</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="lines">
								<xs:annotation>
									<xs:documentation>Returns lines element.</xs:documentation>
								</xs:annotation>
								<xs:complexType>
									<xs:sequence>
										<xs:element name="line" maxOccurs="unbounded">
											<xs:annotation>
												<xs:documentation>Return line element.</xs:documentation>
											</xs:annotation>
											<xs:complexType>
												<xs:all>
												<xs:element name="lineNumber" type="xs:int">
												<xs:annotation>
												<xs:documentation>Sequence number representing the line position within this return message.</xs:documentation>
												</xs:annotation>
												</xs:element>
												<xs:element name="altSku" type="xs:string"
												minOccurs="0">
												<xs:annotation>
												<xs:documentation>Alternative SKU. In case this SKU has been provided in the catalogue file, then GSI can provide it.</xs:documentation>
												</xs:annotation>
												</xs:element>
												<xs:element name="sku" type="xs:string">
												<xs:annotation>
												<xs:documentation>Unique product identifier that will be used by GSI to communicate with the web-store on all feeds.</xs:documentation>
												</xs:annotation>
												</xs:element>
												<xs:element name="qty" type="xs:int">
												<xs:annotation>
												<xs:documentation>Quantity returned.</xs:documentation>
												</xs:annotation>
												</xs:element>
												<xs:element name="condition" type="xs:string">
												<xs:annotation>
												<xs:documentation>Condition of the product returned. Could have the follwoing values: GOOD, DAMAGED,UNDECIDED, USED, etc... A full list of conditions will be provided the time of the implementation.</xs:documentation>
												</xs:annotation>
												</xs:element>
												<xs:element name="reasonDescription"
												type="xs:string" minOccurs="0">
												<xs:annotation>
												<xs:documentation>Human readable return reason  description. The same as are printed on advice note. I.e. Too big, Too small, Wrong colour, etc.</xs:documentation>
												</xs:annotation>
												</xs:element>
												<xs:element name="returnReasonCode"
												type="xs:string" minOccurs="0">
												<xs:annotation>
												<xs:documentation>Ebay Enterprise internal return reason code. The codes will be provided at the time of integration.</xs:documentation>
												</xs:annotation>
												</xs:element>
												<xs:element name="externalLineReference"
												type="xs:string" minOccurs="0">
												<xs:annotation>
												<xs:documentation>External order line reference. This would be order line reference provided in sales order interface field: "lineNumber" </xs:documentation>
												</xs:annotation>
												</xs:element>
												<xs:element default="EEUK01" minOccurs="0"
												name="distributionCentre">
												<xs:annotation>
												<xs:documentation>Distribution centre (facility code) the stock has been booked in.
																The exact codes are provided  by the implementation manager.</xs:documentation>
												</xs:annotation>
												<xs:simpleType>
												<xs:restriction base="xs:string">
												<xs:maxLength value="15"/>
												<xs:whiteSpace value="preserve"/>
												</xs:restriction>
												</xs:simpleType>
												</xs:element>
												<xs:element minOccurs="0" name="rucItemId"
												type="xs:string">
												<xs:annotation>
												<xs:documentation>RUC primary item ID</xs:documentation>
												</xs:annotation>
												</xs:element>
												</xs:all>
											</xs:complexType>
										</xs:element>
									</xs:sequence>
								</xs:complexType>
							</xs:element>
						</xs:all>
					</xs:complexType>
				</xs:element>
				<xs:element name="messageId" type="xs:long" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Numeric unique Radial RUC outbound message ID.

							It's recommended to be used on:
							--------------------------------------
							1) Avoiding duplicate message processing;
							2) Debugging if a certain message has been sent/received/acknowledged.

							Limitation:  Radial doesn't guarantee the delivery of messages in the sequence order.</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element minOccurs="0" name="clientId" type="xs:string">
					<xs:annotation>
						<xs:documentation>Radial client code assigned during implementation phase.</xs:documentation>
					</xs:annotation>
				</xs:element>
			</xs:sequence>
		</xs:complexType>
	</xs:element>
</xs:schema>
