Component 
SUMMARY: XML REP | DERIVED | USE
DETAIL: DESC | XML SRC | TYPE | ATTR | CHILD
eBay Trading API

complexType "ns:VariationType"
Namespace:
Content:
complex, 13 elements, elem. wildcard
Defined:
globally in Schema in ebaySvc.wsdl; see XML source
Includes:
definitions of 13 elements, elem. wildcard
Used:
Component Diagram
XML Representation Summary
<...>
   
Content: 
</...>
All Direct / Indirect Based Elements (2):
ns:Variation (defined in ns:TransactionType complexType),
Known Usage Locations
Annotation
This type is used by the Variation container, which provides full details on each item variation in a multiple-variation listing.
XML Source (w/o annotations (14); see within schema source)
<xs:complexType name="VariationType">
<xs:sequence>
<xs:element minOccurs="0" name="SKU" type="ns:SKUType"/>
<xs:element minOccurs="0" name="StartPrice" type="ns:AmountType"/>
<xs:element minOccurs="0" name="Quantity" type="xs:int"/>
<xs:element minOccurs="0" name="VariationSpecifics" type="ns:NameValueListArrayType"/>
<xs:element minOccurs="0" name="UnitsAvailable" type="xs:int"/>
<!-- [TODO] Is this the original cost to the seller,
not necessarily the listing price? If the seller doesn't specify
a unit cost, what is returned?
-->
<xs:element minOccurs="0" name="SellingStatus" type="ns:SellingStatusType"/>
<xs:element minOccurs="0" name="VariationTitle" type="xs:string"/>
<xs:element minOccurs="0" name="VariationViewItemURL" type="xs:anyURI"/>
<xs:element default="false" minOccurs="0" name="Delete" type="xs:boolean"/>
<xs:element minOccurs="0" name="WatchCount" type="xs:long"/>
<xs:element minOccurs="0" name="PrivateNotes" type="xs:string"/>
<xs:element minOccurs="0" name="DiscountPriceInfo" type="ns:DiscountPriceInfoType"/>
<xs:any maxOccurs="unbounded" minOccurs="0" processContents="lax"/>
</xs:sequence>
</xs:complexType>
Content Element Detail (all declarations defined in this component; 14/14)
ns:Delete
Type:
xs:boolean, predefined, simple content
If this field is included and set to true, the corresponding variation is deleted from the listing with a successful call. In general, a listing with variations must have at least one variation with a non-zero quantity in order to remain active. Additional deletion rules depend on whether you are revising or relisting.

For ReviseFixedPriceItem only: This boolean field can now be used in a Revise call to delete a variation even if the variation still has quantity and/or has had one or more previous sales during the life of the listing. Previously, if a variation had any purchases, you could not delete the variation, but only set its quantity to zero.

To replace a varation, you can delete it and add the new or corrected one. However, you can't specify the same SKU twice in the same request (because the intent would be ambiguous). So, either use a new SKU for the newer variation, or use the call twice (once to delete the variation, and once to add the new variation with the same SKU).

For RelistFixedPriceItem only: You can delete any variation, as long as the relisted listing includes at least 1 variation with a non-zero quantity. (That is, when you relist, you could delete all but one variation, or you could delete all existing variations and add a new one.)
XML Representation Summary
<ns:Delete>
   
Content: 
{ xs:boolean }
</ns:Delete>
Simple Content
Default:
"false"
XML Source (w/o annotations (1); see within schema source)
<xs:element default="false" minOccurs="0" name="Delete" type="xs:boolean"/>

ns:DiscountPriceInfo
Type:
ns:DiscountPriceInfoType, complex content
This container provides information for a single variation (within a multiple-variation listing) that has a Strikethrough Price (STP) or a Minimum Advertised Price (MAP) discount pricing treatment. For a multiple-variation listing, the discount pricing information should be set at the variation level and not at the item level (e.g. Item.DiscountPriceInfo). STP and MAP apply only to fixed-price listings. STP is available on the US, eBay Motors, UK, Germany, Canada (English and French), France, Italy, and Spain sites, while MAP is available only on the US site.

Discount pricing is available to qualified sellers (and their associated developers) who participate in the Discount Pricing Program. Once qualified, sellers receive a 'special account flag' (SAF) that allows them to apply Discount Pricing to both single-variation and multi-variation items. STP is intended for eBay partners and their sellers only.

As a seller listing Discount Price items, you are required to maintain records of your discount pricing in the event you are called upon to substantiate your item pricing.
Component Diagram
XML Representation Summary
<ns:DiscountPriceInfo>
   
Content: 
</ns:DiscountPriceInfo>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="DiscountPriceInfo" type="ns:DiscountPriceInfoType"/>

ns:PrivateNotes
Type:
xs:string, predefined, simple content
A note a user makes on an item with variations in My eBay.

For eBay.com, only GetMyeBaySelling (not GetItem) returns this field, and only if you pass IncludeNotes in the request. Only visible to the user who created the note.

Not supported as input in ReviseFixedPriceItem. Use SetUserNotes instead.

In SoldList, notes for variations are only returned at the Item level, not the variation level.
XML Representation Summary
<ns:PrivateNotes>
   
Content: 
{ xs:string }
</ns:PrivateNotes>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="PrivateNotes" type="xs:string"/>

ns:Quantity
Type:
xs:int, predefined, simple content
This value indicates the quantity of the specific variation that are available for purchase. If you set Variation.Quantity to 0 when you create, revise, or relist an item listing, the variation is dropped from the listing. To prevent this, you can set SetUserPreferences.OutOfStockControlPreference to true.

For GetItem (and other related calls that retrieve the Item object), the Variation.Quantity value indicates the total quantity associated with the variation, including the quantity available and the quantity sold. To calculate the quantity available for sale, subtract SellingStatus.QuantitySold from this value.

For RelistFixedPriceItem:
  • For an item variation that had an available quantity greater than 0 when the listing ended, the Quantity value of the item variation for the newly relisted item is set to the actual quantity available. For item variations, there is actually no QuantityAvailable field, but this value may be derived if you look at the corresponding item variation in a GetMyeBaySelling) response and subtract the Variation.QuantitySold value from the Variation.Quantity value, which represents the original Variation.Quantity value at creation time of the previous listing.
  • For item variations with an available quantity of 0 when the listing ended, the relisted item will retain the Variaton.Quantity value that was passed in at creation time of the previous listing.
So, if you are relisting an item that had one or more item variations with an available quantity of 0 when the listing ended, we strongly recommend that you pass in the correct available quantity through the corresponding Variation.Quantity field of a relist call. Alternatively, you can update the correct quantity available by using a ReviseInventoryStatus call and passing in a Quantity value, while also making sure to pass in the correct SKU value(s) to identify the correct item variation. A ReviseInventoryStatus call can be used to revise the quantity of up to four single item listings and/or item variations (from the same or different listings).

For ReviseFixedPriceItem: You can revise a variation's quantity at any time, even if it has purchases. However, unless you set the OutOfStockControlPreference boolean field of the SetUserPreferences call to true, at least one variation must remain with a non-zero quantity in order for the listing to remain active. If you set the OutOfStockControlPreference field to true, a multiple-variation listing will remain active but hidden from search even if the quantity of all variations in the listing is set to 0. When you modify a variation during revise or relist, you need to include both its StartPrice and Quantity. If you revise the Quantity value for a variation after items have already sold, specify the quantity available for sale. (eBay will automatically add the quantity sold to the value you specify.) If you set the quantity to 0 and the variation has no purchases, the variation may be dropped from the listing.

For GetSellerTransactions: See Item.Quantity instead.

See the eBay Features Guide for more details about setting and modifying a variation's quantity.

Note: The number in the Variation.Quantity field represents the current quantity of the item variation that is available using the "Ship to home" fulfillment method. This number does not take into account any quantity of the item variation that is available through "local" fulfillment methods such as In-Store Pickup or Click and Collect. This is due to the fact that there is no current implementation (or API field) where the seller informs eBay about the quantity of item variations available through each local fulfillment method. In the case where a listing is only offering the item variations through a local fulfillment method, this value should default to 0, and the Item.IgnoreQuantity will also be returned as True.
XML Representation Summary
<ns:Quantity>
   
Content: 
{ xs:int }
</ns:Quantity>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="Quantity" type="xs:int"/>

ns:SellingStatus
Type:
ns:SellingStatusType, complex content
Contains the variation's quantity sold. Always returned when variations are present.
Component Diagram
XML Representation Summary
<ns:SellingStatus>
   
Content: 
</ns:SellingStatus>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="SellingStatus" type="ns:SellingStatusType"/>

ns:SKU
Type:
ns:SKUType, simple content
A SKU (stock keeping unit) is a seller-defined identifier. It is only intended for the seller's use (not for buyers). A SKU value is not required, but many large sellers like to add SKU value to their listings. If defined on a listing, a SKU value can be used by sellers to reconcile their eBay inventory with your own inventory system, instead of using the VariationSpecifics identifying values.

If specified, all SKU values must be unique within the Variations node. That is, no two variations within the same listing can have the same SKU.

If you include the Item.InventoryTrackingMethod field in an 'FixedPriceItem' call and set its value to SKU, the Variation.SKU values become required for each variation..

For GetItem, GetOrders and other 'Get' calls: Only returned if the seller specified a SKU for the variation.
XML Representation Summary
<ns:SKU>
   
Content: 
{ xs:string }
</ns:SKU>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="SKU" type="ns:SKUType"/>

ns:StartPrice
Type:
ns:AmountType, simple content
The fixed price for this item variation. For example, a "Blue, Large" variation price could be USD 10.00, and a "Black, Medium" variation price could be USD 5.00.

Each variation requires this field, and the prices can be the same for all variations, or be different for each variation. This enables sellers to provide discounts on certain variations without affecting the price of others. Required (and always returned) for listings with variations.

You can revise a variation's price at any time (even if it has purchases). When you modify a variation during revise or relist, you need to include both its StartPrice and Quantity.
Component Diagram
XML Representation Summary
<ns:StartPrice
   
 = 
("AFA" | "ALL" | "DZD" | "ADP" | "AOA" | "ARS" | "AMD" | "AWG" | "AZM" | "BSD" | "BHD" | "BDT" | "BBD" | "BYR" | "BZD" | "BMD" | "BTN" | "INR" | "BOV" | "BOB" | "BAM" | "BWP" | "BRL" | "BND" | "BGL" | "BGN" | "BIF" | "KHR" | "CAD" | "CVE" | "KYD" | "XAF" | "CLF" | "CLP" | "CNY" | "COP" | "KMF" | "CDF" | "CRC" | "HRK" | "CUP" | "CYP" | "CZK" | "DKK" | "DJF" | "DOP" | "TPE" | "ECV" | "ECS" | "EGP" | "SVC" | "ERN" | "EEK" | "ETB" | "FKP" | "FJD" | "GMD" | "GEL" | "GHC" | "GIP" | "GTQ" | "GNF" | "GWP" | "GYD" | "HTG" | "HNL" | "HKD" | "HUF" | "ISK" | "IDR" | "IRR" | "IQD" | "ILS" | "JMD" | "JPY" | "JOD" | "KZT" | "KES" | "AUD" | "KPW" | "KRW" | "KWD" | "KGS" | "LAK" | "LVL" | "LBP" | "LSL" | "LRD" | "LYD" | "CHF" | "LTL" | "MOP" | "MKD" | "MGF" | "MWK" | "MYR" | "MVR" | "MTL" | "EUR" | "MRO" | "MUR" | "MXN" | "MXV" | "MDL" | "MNT" | "XCD" | "MZM" | "MMK" | "ZAR" | "NAD" | "NPR" | "ANG" | "XPF" | "NZD" | "NIO" | "NGN" | "NOK" | "OMR" | "PKR" | "PAB" | "PGK" | "PYG" | "PEN" | "PHP" | "PLN" | "USD" | "QAR" | "ROL" | "RUB" | "RUR" | "RWF" | "SHP" | "WST" | "STD" | "SAR" | "SCR" | "SLL" | "SGD" | "SKK" | "SIT" | "SBD" | "SOS" | "LKR" | "SDD" | "SRG" | "SZL" | "SEK" | "SYP" | "TWD" | "TJS" | "TZS" | "THB" | "XOF" | "TOP" | "TTD" | "TND" | "TRL" | "TMM" | "UGX" | "UAH" | "AED" | "GBP" | "USS" | "USN" | "UYU" | "UZS" | "VUV" | "VEB" | "VND" | "MAD" | "YER" | "YUM" | "ZMK" | "ZWD" | "ATS" | "CustomCode")
   
>
   
Content: 
{ xs:double }
</ns:StartPrice>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="StartPrice" type="ns:AmountType"/>

ns:UnitsAvailable
Type:
xs:int, predefined, simple content
Quantity of items in the seller's inventory for this Selling Manager product. This is not the same as the quantity available in a listed item. Required when a Selling Manager product defines variations.
XML Representation Summary
<ns:UnitsAvailable>
   
Content: 
{ xs:int }
</ns:UnitsAvailable>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="UnitsAvailable" type="xs:int"/>

ns:VariationProductListingDetails
Type:
This container is used to provide one or more product identifiers for a product variation within a multiple-variation, fixed-price listing. The same product identifier type(s) must be used for all product variations within the listing. For instance, if one product variation uses ISBNs, all product variations must use ISBN values.

Note: Currently, the EAN, ISBN, or UPC fields are used to specify a Global Trade Item Number (GTIN), and the GetCategoryFeatures call is used to see if particular product identifier types are supported/required. The ProductReferenceID field can only be used to specify an ePID for an eBay Catalog product that is part of the Product-Based Shopping Experience mandate. For more information about PBSE, see the Product-Based Shopping Experience page.
When you include the VariationProductListingDetails container in a call, you must specify at least one GTIN or ePID. If an ePID is provided, a matching eBay catalog product must exist for the value that is passed in.

For ReviseItem and RelistItem only: When you revise a listing, if it ends within 12 hours, you cannot change the product identifier and you cannot remove existing product variation listing details data.
Component Diagram
XML Representation Summary
<ns:VariationProductListingDetails>
   
Content: 
</ns:VariationProductListingDetails>
XML Source (w/o annotations (1); see within schema source)

ns:VariationSpecifics
Type:
ns:NameValueListArrayType, complex content
A list of name/value pairs that uniquely identify the variation within the listing. All variations must specify the same set of Item Specific names, but each variation must provide a unique combination of values for those Item Specific names. For example, if the items vary by color and size, then every variation must specify 'Color' and 'Size' as Item Specific names, but no two variations can specify the same combination of 'Color' and 'Size' values.

When you revise a listing that includes variations, you can change names of Variationpecifics by using the Variations.ModifyNameList container. You can also add, delete, or replace individual variations as needed to match your current inventory. Use the Variation.Delete field to delete a variation that has no sales (order line items). If the variation has sales, then set the Quantity to 0.

For GetSellerEvents To keep the GetSellerEvents response smaller, Variationpecifics are not returned if the variation has a SKU. If the variation has no SKU, then Variationpecifics are returned instead. Optionally, you can pass IncludeVariationSpecifics as true in the request to force Variationpecifics to be returned, even when the SKU is returned.
Component Diagram
XML Representation Summary
<ns:VariationSpecifics>
   
Content: 
</ns:VariationSpecifics>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="VariationSpecifics" type="ns:NameValueListArrayType"/>

ns:VariationTitle
Type:
xs:string, predefined, simple content
The title of the variation. This is a concatenation of the listing title plus the values (no names) from Variationpecifics. For example, if the Title is "Polo Shirt" and the variation is for a medium pink shirt, the variation title could be "Polo Shirt[Pink,M].
XML Representation Summary
<ns:VariationTitle>
   
Content: 
{ xs:string }
</ns:VariationTitle>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="VariationTitle" type="xs:string"/>

ns:VariationViewItemURL
Type:
xs:anyURI, predefined, simple content
URL for the variation on eBay. This links to eBay's View Item page, with the page configured to show details of the specified variation. The syntax of this URL is similar to Item.ViewItemURL (not optimized for natural search).
XML Representation Summary
<ns:VariationViewItemURL>
   
Content: 
{ xs:anyURI }
</ns:VariationViewItemURL>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="VariationViewItemURL" type="xs:anyURI"/>

ns:WatchCount
Type:
xs:long, predefined, simple content
The number of watches placed on this variation by eBay users.
XML Representation Summary
<ns:WatchCount>
   
Content: 
{ xs:long }
</ns:WatchCount>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="WatchCount" type="xs:long"/>

{any element from any namespace}
XML Source (see within schema source)
<xs:any maxOccurs="unbounded" minOccurs="0" processContents="lax"/>

 Component 
SUMMARY: XML REP | DERIVED | USE
DETAIL: DESC | XML SRC | TYPE | ATTR | CHILD
eBay Trading API

WSDL documentation generated with FlexDoc/XML 1.13 using FlexDoc/XML WSDLDoc 1.2.5 template set. All XSD diagrams generated by FlexDoc/XML DiagramKit.