DataFeedManager XML file
format The DataFeedManager XML file format is ideal
for platform integrations although it can be used for a single
store import.
It is also the preferred format for large product set imports for
stores with tens of thousands of SKUs since it has a built in
paging mechanism to make the import process more efficient. There
are three XML node sections to this file’s schema, Fields, Products
and Paging; each is discussed below.
Fields node The Fields node section lets DataFeedManager know what
product attributes to expect for your import. This node contains
multiple child Field nodes (up to 50), each representing a product
attribute to be imported from your system. Each Field node must
contain a name attribute that contains the field name as a
value.
For example:
<Fields> <Field name="UniqueID" /> <Field
name="Name" /> <Field name="Description" /> <Field
name="Price" /> More Field nodes… </Fields> Products node
The Products node section provides your product listings to
DataFeedManager.
This node contains multiple child Product nodes, each representing
a product in your system. Each Product node must contain child
nodes named according to the Fields node section, all fields from
the Fields node section must be present in each Product node.
For example:
<Products> <Product>
<UniqueID>6816916</UniqueID>
<Name>Apple iPod Video 30GB White 5.5 GEN</Name>
<Description>With 5.5 generation iPods all your music at your
fingertips you may never want to stop
listening…</Description>
<Price>237.99</Price>
More fields … </Product> More Product nodes…
</Products>
- 4 -
Paging node The Paging node section allows DataFeedManager to relay
paging calls to your system, providing an efficient mechanism for
large product set imports and eliminating server timeouts on large
XML files. The Paging node contains three child nodes:
Start– This is the
starting index of the first product to be returned
Count - The number of
products to return
Total – The total products
to be returned for this import
Must populate each of these nodes
as calls are made to your system.
For example:
<Paging> <Start>1</Start>
<Count>100</Count> <Total>1000</Total>
</Paging> DataFeedManager will make calls to your system via
HTTP and will pass query string parameters that indicate which
product page to return.
The HTTP call will be similar
to the following:
http://www.MyStore.com/MyWebPage?start=1&count=100
To retrieve the second page of a 1000 products file the call will
be similar to the following:
http://www.MyStore.com/MyWebPage?start=101&count=100