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

complexType "ns:InventoryStatusType"
Namespace:
Content:
complex, 4 elements, elem. wildcard
Defined:
globally in Schema in ebaySvc.wsdl; see XML source
Includes:
definitions of 4 elements, elem. wildcard
Used:
Component Diagram
XML Representation Summary
<...>
   
Content: 
</...>
All Direct / Indirect Based Elements (2):
Known Usage Locations
Annotation
This type is used by the ReviseInventoryStatus call to update the price and/or quantity of an item or an item variation within a single-variation or multiple-variation, fixed-price listing.
XML Source (w/o annotations (5); see within schema source)
<xs:complexType name="InventoryStatusType">
<xs:sequence>
<xs:element minOccurs="0" name="SKU" type="ns:SKUType"/>
<xs:element minOccurs="0" name="ItemID" type="ns:ItemIDType"/>
<xs:element minOccurs="0" name="StartPrice" type="ns:AmountType"/>
<xs:element minOccurs="0" name="Quantity" type="xs:int"/>
<xs:any maxOccurs="unbounded" minOccurs="0" processContents="lax"/>
</xs:sequence>
</xs:complexType>
Content Element Detail (all declarations defined in this component; 5/5)
ns:ItemID
Type:
ns:ItemIDType, simple content
The unique identifier of the listing being revised.

For a single-variation listing, either the ItemID of the listing or the SKU value of the item (if it exists) is required, and which one to use will depend on the value of the InventoryTrackingMethod setting. If the value of InventoryTrackingMethod is ItemID, the ItemID field should be used. If the value of InventoryTrackingMethod is SKU, the SKU field should be used. ItemID is the default value of InventoryTrackingMethod, and its value can only be set/changed to SKU through either an AddFixedPriceItem or RelistFixedPriceItem call.

For a multiple-variation listing, the SKU value of the item variation is required in order to identify a specific item variation. An ItemID field is also required if the InventoryTrackingMethod value is set to ItemID. However, if the InventoryTrackingMethod value is set to SKU, only the SKU value of the item variation is needed to identify a specific item variation. Note that a seller-defined SKU value is required when a seller creates a multiple-variation listing, regardless of whether they decide to track inventory by Item ID or SKU.

Please note that the same ItemID value can be used multiple times in the same call if you revise several item variations from the same multiple-variation listing.

The ItemID field is always returned in the response, even if an ItemID value was not included in the request.
XML Representation Summary
<ns:ItemID>
   
Content: 
{ xs:string }
</ns:ItemID>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ItemID" type="ns:ItemIDType"/>

ns:Quantity
Type:
xs:int, predefined, simple content
Note: The Quantity response field is being deprecated, and it will no longer be supported after April 30, 2022. eBay has found that the value returned for this field is not reliably accurate and recommends that the response for this field be ignored.

The Quantity request field can still be used, and sellers can leverage the GetItem call to verify that the requested quantity updates were successful.

This field is used to set the revised quantity of the listing (or of a variation within a multiple-variation listing).

In each InventoryStatus container, either StartPrice or Quantity (or both) are required.

The Quantity field is always returned in the response, regardless of whether the quantity was changed or not through a Quantity field in the call request. However, the Quantity field in the response is actually a total of the quantity available for sale plus the quantity already sold for the item or item variation. For example, suppose the item or item variation originally had a quantity of 10, and then a quantity of 8 was sold. Now, you restock your inventory, and you pass in a quantity of 10 in the ReviseInventoryStatus request. In this case, the response of this ReviseInventoryStatus call would show a quantity of 18 (10 available + 8 sold). To determine the quantity available, use the GetItem or GetSellerList call, and subtract the SellingStatus.QuantitySold value from the Quantity value. Or, you can also use the GetMyeBaySelling call, search for the correct item or item variation in the response by ItemID or SKU value, and then look at the QuantityAvailable field for that item or item variation.

It is a good idea to maintain an adequate quantity available for fixed-price GTC listings to prevent the search rankings from dropping. Best Match search ranking is based on buyer activity, and one of the factors affecting search ranking for fixed-price listings is the recent sales score. Fixed-price items that are selling the fastest are given a relative lift in search results.
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:SKU
Type:
ns:SKUType, simple content
This value is the seller-defined SKU value of the item being revised.

For a single-variation listing, either the ItemID of the listing or the SKU value of the item (if it exists) is required, and which one to use will depend on the value of the InventoryTrackingMethod setting. If the value of InventoryTrackingMethod is ItemID, the ItemID field should be used. If the value of InventoryTrackingMethod is SKU, the SKU field should be used. ItemID is the default value of InventoryTrackingMethod, and its value can only be set/changed to SKU through either an AddFixedPriceItem or RelistFixedPriceItem call.

For a multiple-variation listing, the SKU value of the item variation is required in order to identify a specific item variation. An ItemID field is also required if the InventoryTrackingMethod value is set to ItemID. However, if the InventoryTrackingMethod value is set to SKU, only the SKU value of the item variation is needed to identify a specific item variation. Note that a seller-defined SKU value is required when a seller creates a multiple-variation listing, regardless of whether they decide to track inventory by Item ID or SKU.

The SKU field is always returned in the response, and if a SKU value doesn't exist for a single-variation listing, it is returned as an empty tag.
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
Note: The StartPrice response field is being deprecated, and it will no longer be supported after April 30, 2022. eBay has found that the value returned for this field is not reliably accurate and recommends that the response for this field be ignored.

The StartPrice request field can still be used, and sellers can leverage the GetItem call to verify that the requested price updates were successful.

This field is used to set the revised price of the listing (or of a variation within a multiple-variation listing).

In each InventoryStatus container, either StartPrice or Quantity (or both) are required.

The StartPrice field is always returned in the response and reveals the current price of the item or item variation, regardless of whether the price was changed or not through a StartPrice field in the call request.
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"/>

{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.