XML Responses

Store Fulfillment/DropShip Manager to Retailer

Overview

Store Fulfillment always responds to all HTTP/HTTPS POSTs. You can optionally configure it to respond to files. The XML response has the same root tag as the inbound document. Child nodes of either “Success” or “Errors” are added for each order or SKU in the document. Following is an example response to an order import document indicating both a successfully processed order and an error:

<ImportOrders>				
    <Success>				
        <Order>				
            <OrderNumber>123456789</OrderNo>				
            <Date>20090815</Date>				
            <Time>093023</Time>				
        </Order>				 
    </Success>				
    <Errors>				
        <Order>				
            <OrderNumber>987654321</OrderNo>				
            <ErrorNumber>12345</ErrorNumber>				
            <ErrorDescription>Description of the error that was detected</ErrorDescription>				
            <Date>20090815</Date>				
            <Time>093023</Time>				
        </Order>				
    </Errors>				
</ImportOrders>

Similarly, StoreNet expects an XML response to documents that it submits via an HTTP/HTTPS POST. To confirm receipt and acceptance of the post, the site

must respond with the same root tag as the submitted document. A child node named “Success” should be added containing either a value of “Yes” or “No”.

Following is an example of a Store Fulfillment response to a document indicating success:

<CustomerServiceUpdate>
    <Success>Yes</Success>
</CustomerServiceUpdate>

If Store Fulfillment does not receive a successful response, it attempts to send the document again at the next scheduled time.

File Layout

Column Description

#	Tag	Req	Max Len	Occurs	Type	Nest Level	Parent Tag	Description
1	<conditional>	Yes	0	1/Doc	Node	0	None	Root tag indicating the beginning of a response document. The root tag will be the same as the inbound document to which it is responding.
2	<Success>	No	0	1	Node	1	<conditional>	Tag indicating the beginning of the success data.
3	<Order>	No	0	1+	Node	2	<Success>	Tag indicating the beginning of the order data.
4	<OrderNumber>	Yes	20	1	String	3	<Order>
5	<Date>	Yes	8	1	Date	3	<Order>	Response date (yyyyMMdd).
6	<Time>	Yes	6	1	String	3	<Order>	Response time (HHmmss).
7	</Order>			1+	Node	2	<Success>	Tag indicating the end of the order data.
8	</Success>	No	0	1	Node	1	<conditional>	Tag indicating the end of the success data.
9	<Errors>	No	0	1	Node	1	<conditional>	Tag indicating the beginning of the errors data.
10	<Order>	No	0	1+	Node	2		Tag indicating the beginning of the order data.
11	<OrderNumber>	Yes	20	1	String	3	<Errors>
12	<ErrorNumber>	Yes	30	1	String	3	<Errors>	Error number code of error.
13	<ErrorDescription>	Yes	256	1	String	3	<Errors>	Description of error.
14	<Date>	Yes	8	1	Date	3	<Errors>	Response date (yyyyMMdd).
15	<Time>	Yes	6	1	String	3	<Errors>	Response time (HHmmss).
16	</Order>			1+	Node	2		Tag indicating the end of the order data.
17	</Errors>	No	0	1	Node	1	<ImportReceipts>	Tag indicating the end of the errors data.
18	</conditional>	Yes	0	1/Doc	Node	0	None	Root tag indicating the end of a response document. The root tag will be the same as the inbound document to which it is responding.

Response Errors

ErrorNumber	ErrorDescription	Cause	Resolution
1304	Duplicate Order Passed	An order attempted to import that is already in VendorNet.	Resend the order with a new order number
1200	Vendor Item (SKU) No contains an apostrophe	An item is attempting to import that has an apostrophe in the Vendor SKU	Remove the apostrophe from this and any other SKU and resend the order or product
1321	There are no shippable products on the order
1311	Vendor does not exist	Vendor/Store number does not exist in VendorNet	Add the vendor/store to VendorNet and resend the order or product
9999	Invalid OrderNo length	An order was passed with an OrderNo longer than the maximum allowable length of 20 characters
1500	Order on an integrated vendor must be integrated	The ship method passed on the order is not set up on the vendor/store as a carrier-integrated ship method	Set the appropriate ship method on the vendor/store to be associated with a carrier and resend the order, or resend the order with a valid ship method