eBay Trading API889

ReviseInventoryStatus

Enables a seller to change the price and quantity of a currently- active, fixed-price listing. Using ReviseInventoryStatus to modify data qualifies as revising the listing.

Inputs are the item IDs or SKUs of the listings being revised, and the price and quantity that are being changed for each revision. Only applicable to fixed-price listings.

Changing the price or quantity of a currently- active, fixed-price listing does not reset the Best Match performance score. For Best Match information related to multi-variation listings, see the Best Match information at the following topic: Multi-quantity Fixed Price listings with variations.

As with all listing calls, the site you specify in the request URL (for SOAP) or the X-EBAY-API-SITEID HTTP header (for XML) should match the original listing's Item.Site value. In particular, this is a best practice when you submit new and revised listings.

Note: As of November 9, 2011, an upper limit of 2,000 has been placed on item revisions that have a pricing impact. Revisions that do not have a pricing impact will not count toward this 2,000 call limit. An item can be revised by the ReviseFixedPriceItem, ReviseItem, and ReviseInventoryStatus calls, and all item revisions (that have a pricing impact) made with these three calls count towards the maximum limit. Once the upper limit is reached, the seller will be blocked from revising the item in any manner, even for revisions that have no pricing impact. For GTC listings, the 2,000 call limit resets with each renewal.
Note to Large Merchant Services users: When you use ReviseInventoryStatus within a Merchant Data file, your requests must be enclosed within BulkDataExchangeRequests tags. After release 637, a namespace is returned in BulkDataExchangeResponses, a top-level container in the response. The Bulk Data Exchange tags are not shown in the call input/output descriptions of this document.

See:
    Standard Data for All Calls
    Listing an Item
    Listing an Item

See also the reference documentation for these calls:



Back to top

ReviseInventoryStatus Input

The box below lists all fields that could be included in the call request. To learn more about an individual field or its type, click its name in the box (or scroll down to find it in the table below the box).

See also Samples.

See also the Deprecated Objects link above. Fields presented in this color are deprecated, and fields presented in this color are (or soon will be) non-operational.

The XML prototype does not include requester credentials. This is a documentation limitation only (see Standard Requester Credentials for Making Calls).

<?xml version="1.0" encoding="utf-8"?>
<ReviseInventoryStatusRequest xmlns="urn:ebay:apis:eBLBaseComponents">
  <!-- Call-specific Input Fields -->
  <InventoryStatus> InventoryStatusType
    <ItemID> ItemIDType (string) </ItemID>
    <Quantity> int </Quantity>
    <SKU> SKUType (string) </SKU>
    <StartPrice> AmountType (double) </StartPrice>
  </InventoryStatus>
  <!-- ... more InventoryStatus nodes allowed here ... -->
  <!-- Standard Input Fields -->
  <ErrorLanguage> string </ErrorLanguage>
  <MessageID> string </MessageID>
  <Version> string </Version>
  <WarningLevel> WarningLevelCodeType </WarningLevel>
</ReviseInventoryStatusRequest>
Argument Type Occurrence Meaning
Call-specific Input Fields [Jump to standard fields]
InventoryStatus InventoryStatusType Required,
repeatable: [1..4]
Contains the updated quantity and/or price of a listing being revised. You should not modify the same listing twice (by using a duplicate ItemID or SKU) in the same request; otherwise, you may get an error or unexpected results. (For example, you should not use one InventoryStatus node to update the quantity and another InventoryStatus node to update the price of the same item.) You can pass up to 4 InventoryStatus nodes in a single request.
InventoryStatus.ItemID ItemIDType (string) Conditional The ItemID of a listing being changed.

In the ReviseInventoryStatus request, either ItemID or SKU is required. If both are passed in and the SKU does not match, eBay ignores SKU and considers only the ItemID.

Please note that the same ItemID can be returned multiple times in the same response if you revise several variations from the same multi-variation listing.
InventoryStatus.Quantity int Conditional Specifies the latest quantity of the listing (or of a variation within a multi-variation listing).

For the ReviseInventoryStatus request: Specify the entire quantity that is currently available for sale. (Typically, you only pass this in when you need to update the quantity.)

ReviseInventoryStatus requires either StartPrice or Quantity (or you can specify both) for each InventoryStatus node in the request.

For the ReviseInventoryStatus response: This returns a total of the quantity available for sale plus the quantity already sold. For example, suppose the listing originally had Quantity=10, and then 8 sold. Now you restock your inventory, and you pass Quantity=10 in the ReviseInventoryStatus request. In this case, ReviseInventoryStatus returns Quantity=18 (10 available + 8 sold). To determine the quantity available, use GetItem or GetSellerList, and subtract SellingStatus.QuantitySold from Quantity. Or see QuantityAvailable in GetMyeBaySelling.

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. Recent Sales history is tracked with a moving window to ensure it reflects the most recent activity. Due to he moving window, it is advantageous to maintain item availability (Quantity-QuantitySold) for a GTC listing.
InventoryStatus.SKU SKUType (string) Conditional The unique SKU of the item being revised. A SKU (stock keeping unit) is an identifier defined by a seller. SKU can only be used to revise an item if you listed the item by using AddFixedPriceItem or RelistFixedPriceItem, and:
1) You set Item.InventoryTrackingMethod to SKU at the time the item was listed; or
2) You are modifying a multi-variation listing, and the SKU identifies one of the variations. (In this case, if InventoryTrackingMethod was set to ItemID, then you also need to specify ItemID in the request.)
(These criteria are necessary to uniquely identify the listing or variation by a SKU.)

In the ReviseInventoryStatus request, if the listing has InventoryTrackingMethod set to SKU, then either ItemID or SKU is required. If both are passed in and they don't refer to the same listing, eBay ignores SKU and considers only the ItemID.

If the listing has variations and InventoryTrackingMethod is set to ItemID, then ItemID and SKU are both required.

In the response, SKU may be returned as an empty element if it was not defined on the listing.
InventoryStatus.StartPrice AmountType (double) Conditional Specifies the revised fixed price of the listing (or of a variation within a multi-variation listing). If you raise the price of a listing, the recent sales score of the listing is reset. (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.)

Raising a listing's price may also affect the insertion fee (and therefore the overall listing fee).

ReviseInventoryStatus requires either StartPrice or Quantity (or both) for each InventoryStatus node in the request.

See:
    Insertion Fees
    eBay.com Listing Fees

Standard Input Fields  
ErrorLanguage string Optional Use ErrorLanguage to return error strings for the call in a different language from the language commonly associated with the site that the requesting user is registered with. Specify the standard RFC 3066 language identification tag (e.g., en_US).

ID Country
en_AU Australia
de_AT Austria
nl_BE Belgium (Dutch)
fr_BE Belgium (French)
en_CA Canada
fr_CA Canada (French)
zh_CN China
fr_FR France
de_DE Germany
zh_HK Hong Kong
en_IN India
en_IE Ireland
it_IT Italy
nl_NL Netherlands
en_SG Singapore
es_ES Spain
de_CH Switzerland
en_GB United Kingdom
en_US United States

See Tags for the Identification of Languages.

MessageID string Optional Most Trading API calls support a MessageID element in the request and a CorrelationID element in the response. If you pass in a MessageID in a request, the same value will be returned in the CorrelationID field in the response. Pairing these values can help you track and confirm that a response is returned for every request and to match specific responses to specific requests. If you do not pass a MessageID value in the request, CorrelationID is not returned.

Note: GetCategories is designed to retrieve very large sets of metadata that change once a day or less often. To improve performance, these calls return cached responses when you request all available data (with no filters). When this occurs, the MessageID and CorrelationID fields aren't applicable. However, if you specify an input filter to reduce the amount of data returned, the calls retrieve the latest data (not cached). When this occurs, MessageID and CorrelationID are applicable.
Version string Conditional The version number of the API code that you are programming against (e.g., 859). The version you specify for a call has these basic effects:
- It indicates the version of the code lists and other data that eBay should use to process your request.
- It indicates the schema version you are using.
You need to use a version that is greater than or equal to the lowest supported version.

For the SOAP API: If you are using the SOAP API, this field is required. Specify the version of the WSDL your application is using.

For the XML API: If you are using the XML API, this field has no effect. Instead, specify the version in the X-EBAY-API-COMPATIBILITY-LEVEL HTTP header. (If you specify Version in the body of an XML API request and it is different from the value in the HTTP header, eBay returns an informational warning that the value in the HTTP header was used instead.)

See:
    Routing the Request (Gateway URLs)
    eBay Schema Versioning Strategy
    Lowest Supported Version

WarningLevel WarningLevelCodeType Optional Controls whether or not to return warnings when the application passes unrecognized or deprecated elements in a request.

An unrecognized element is one that is not defined in any supported version of the schema. Schema element names are case-sensitive, so using WarningLevel can also help you remove any potential hidden bugs within your application due to incorrect case or spelling in field names before you put your application into the Production environment.

WarningLevel only validates elements; it doesn't validate XML attributes. It also doesn't control warnings related to user-entered strings or numbers, or warnings for logical errors.

We recommend that you only use this during development and debugging. Do not use this in requests performed in the Production environment.

Applicable values:

High
(in) Return warnings when the application passes unrecognized or deprecated elements in a request.
Low
(in) Do not return warnings when the application passes unrecognized or deprecated elements in a request. This is the default value if WarningLevel is not specified.

See Warning Level.



Back to top

ReviseInventoryStatus Output

The box below lists all fields that might be returned in the response. To learn more about an individual field or its type, click its name in the box (or scroll down to find it in the table below the box).

See also Samples.

See also the Deprecated Objects link above. Fields presented in this color are deprecated, and fields presented in this color are not returned (or soon will not be returned) or are not operational (or soon will be non-operational).

<?xml version="1.0" encoding="utf-8"?>
<ReviseInventoryStatusResponse xmlns="urn:ebay:apis:eBLBaseComponents">
  <!-- Call-specific Output Fields -->
  <Fees> InventoryFeesType
    <Fee> FeeType
      <Fee currencyID="CurrencyCodeType"> AmountType (double) </Fee>
      <Name> string </Name>
      <PromotionalDiscount currencyID="CurrencyCodeType"> AmountType (double) </PromotionalDiscount>
    </Fee>
    <!-- ... more Fee nodes allowed here ... -->
    <ItemID> ItemIDType (string) </ItemID>
  </Fees>
  <!-- ... more Fees nodes allowed here ... -->
  <InventoryStatus> InventoryStatusType
    <ItemID> ItemIDType (string) </ItemID>
    <Quantity> int </Quantity>
    <SKU> SKUType (string) </SKU>
    <StartPrice currencyID="CurrencyCodeType"> AmountType (double) </StartPrice>
  </InventoryStatus>
  <!-- ... more InventoryStatus nodes allowed here ... -->
  <!-- Standard Output Fields -->
  <Ack> AckCodeType </Ack>
  <Build> string </Build>
  <CorrelationID> string </CorrelationID>
  <Errors> ErrorType
    <ErrorClassification> ErrorClassificationCodeType </ErrorClassification>
    <ErrorCode> token </ErrorCode>
    <ErrorParameters ParamID="string"> ErrorParameterType
      <Value> string </Value>
    </ErrorParameters>
    <!-- ... more ErrorParameters nodes allowed here ... -->
    <LongMessage> string </LongMessage>
    <SeverityCode> SeverityCodeType </SeverityCode>
    <ShortMessage> string </ShortMessage>
  </Errors>
  <!-- ... more Errors nodes allowed here ... -->
  <HardExpirationWarning> string </HardExpirationWarning>
  <Timestamp> dateTime </Timestamp>
  <Version> string </Version>
</ReviseInventoryStatusResponse>
Return Value Type Occurrence Meaning
Call-specific Output Fields [Jump to standard fields]
Fees InventoryFeesType Always,
repeatable: [1..*]
Child elements contain the estimated listing fees for a listing that was revised. Use the ItemID to correlate the Fees data with the InventoryStatus data in the response. The fees do not include the Final Value Fee (FVF), which can't be determined until the listing has sales.

If you revise a variation in a multi-variation listing, the fees are for the entire listing. The insertion fee and listing fee are affected by the highest priced variation in the listing (which is not necessarily the variation that you passed in the request).

Also note that the call returns only one Fees node per listing. For example, if you revise 4 variations from the same multi-variation listing, the response includes 4 InventoryStatus nodes and 1 Fees node.

See:
    eBay.com Fees
    Fees per Site
    Final Value Fees and Credits
    Final Value Fees

Fees.Fee FeeType Always,
repeatable: [1..*]
Contains the data for one fee (such as name and amount).
Fees.Fee.Fee AmountType (double) Always Amount of the fee that eBay will charge the member for the associated listing feature.

See:
    eBay.com Fees for A current schedule of listing features and their associated fees.
    Fees Resulting from Listing an Item for A table listing the type of fees that can be charged when you list an item.

Fees.Fee.Fee
  [ attribute currencyID ]
CurrencyCodeType Always Amount of the fee that eBay will charge the member for the associated listing feature.

For a list of possible enumeration values, see CurrencyCodeType.
Fees.Fee.Name string Always Name of the listing feature, for identification purposes.

See Fees Resulting from Listing an Item.

Fees.Fee.PromotionalDiscount AmountType (double) Always This field exists in the response when the user has selected a feature that participates in a promotional discount.

Note: Verify calls might not return the PromotionalDiscount fee in the response.

See Standard selling fees for A current schedule of listing features and their associated fees..

Fees.Fee.PromotionalDiscount
  [ attribute currencyID ]
CurrencyCodeType Always This field exists in the response when the user has selected a feature that participates in a promotional discount.

Note: Verify calls might not return the PromotionalDiscount fee in the response.



For a list of possible enumeration values, see CurrencyCodeType.
Fees.ItemID ItemIDType (string) Always The ItemID of the listing being changed.

The ReviseInventoryStatus response includes a separate set of fees for each item that was successfully revised.

Use the ItemID to correlate the Fees data with the InventoryStatus data in the response.
Max length: 19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits).
InventoryStatus InventoryStatusType Always,
repeatable: [1..4]
Confirms the quantity and price associated with a listing or variation that was revised.
InventoryStatus.ItemID ItemIDType (string) Always The ItemID of a listing being changed.

In the ReviseInventoryStatus request, either ItemID or SKU is required. If both are passed in and the SKU does not match, eBay ignores SKU and considers only the ItemID.

Please note that the same ItemID can be returned multiple times in the same response if you revise several variations from the same multi-variation listing.
InventoryStatus.Quantity int Always Specifies the latest quantity of the listing (or of a variation within a multi-variation listing).

For the ReviseInventoryStatus request: Specify the entire quantity that is currently available for sale. (Typically, you only pass this in when you need to update the quantity.)

ReviseInventoryStatus requires either StartPrice or Quantity (or you can specify both) for each InventoryStatus node in the request.

For the ReviseInventoryStatus response: This returns a total of the quantity available for sale plus the quantity already sold. For example, suppose the listing originally had Quantity=10, and then 8 sold. Now you restock your inventory, and you pass Quantity=10 in the ReviseInventoryStatus request. In this case, ReviseInventoryStatus returns Quantity=18 (10 available + 8 sold). To determine the quantity available, use GetItem or GetSellerList, and subtract SellingStatus.QuantitySold from Quantity. Or see QuantityAvailable in GetMyeBaySelling.

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. Recent Sales history is tracked with a moving window to ensure it reflects the most recent activity. Due to he moving window, it is advantageous to maintain item availability (Quantity-QuantitySold) for a GTC listing.
InventoryStatus.SKU SKUType (string) Always The unique SKU of the item being revised. A SKU (stock keeping unit) is an identifier defined by a seller. SKU can only be used to revise an item if you listed the item by using AddFixedPriceItem or RelistFixedPriceItem, and:
1) You set Item.InventoryTrackingMethod to SKU at the time the item was listed; or
2) You are modifying a multi-variation listing, and the SKU identifies one of the variations. (In this case, if InventoryTrackingMethod was set to ItemID, then you also need to specify ItemID in the request.)
(These criteria are necessary to uniquely identify the listing or variation by a SKU.)

In the ReviseInventoryStatus request, if the listing has InventoryTrackingMethod set to SKU, then either ItemID or SKU is required. If both are passed in and they don't refer to the same listing, eBay ignores SKU and considers only the ItemID.

If the listing has variations and InventoryTrackingMethod is set to ItemID, then ItemID and SKU are both required.

In the response, SKU may be returned as an empty element if it was not defined on the listing.
InventoryStatus.StartPrice AmountType (double) Always Specifies the revised fixed price of the listing (or of a variation within a multi-variation listing). If you raise the price of a listing, the recent sales score of the listing is reset. (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.)

Raising a listing's price may also affect the insertion fee (and therefore the overall listing fee).

ReviseInventoryStatus requires either StartPrice or Quantity (or both) for each InventoryStatus node in the request.

See:
    Insertion Fees
    eBay.com Listing Fees

InventoryStatus.StartPrice
  [ attribute currencyID ]
CurrencyCodeType Always Specifies the revised fixed price of the listing (or of a variation within a multi-variation listing). If you raise the price of a listing, the recent sales score of the listing is reset. (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.)

Raising a listing's price may also affect the insertion fee (and therefore the overall listing fee).

ReviseInventoryStatus requires either StartPrice or Quantity (or both) for each InventoryStatus node in the request.

For a list of possible enumeration values, see CurrencyCodeType.
Standard Output Fields  
Ack AckCodeType Always A token representing the application-level acknowledgement code that indicates the response status (e.g., success). The AckCodeType list specifies the possible values for the Ack field.

Applicable values:

CustomCode
(out) Reserved for internal or future use.
Failure
(out) Request processing failed
Success
(out) Request processing succeeded
Warning
(out) Request processing completed with warning information being included in the response message

(Not all values in AckCodeType apply to this field.)
Build string Always This refers to the specific software build that eBay used when processing the request and generating the response. This includes the version number plus additional information. eBay Developer Support may request the build information when helping you resolve technical issues.
CorrelationID string Conditionally Most Trading API calls support a MessageID element in the request and a CorrelationID element in the response. If you pass in a MessageID in a request, the same value will be returned in the CorrelationID field in the response. Pairing these values can help you track and confirm that a response is returned for every request and to match specific responses to specific requests. If you do not pass a MessageID value in the request, CorrelationID is not returned.

Note: GetCategories is designed to retrieve very large sets of metadata that change once a day or less often. To improve performance, these calls return cached responses when you request all available data (with no filters). When this occurs, the MessageID and CorrelationID fields aren't applicable. However, if you specify an input filter to reduce the amount of data returned, the calls retrieve the latest data (not cached). When this occurs, MessageID and CorrelationID are applicable.
Errors ErrorType Conditionally,
repeatable: [0..*]
A list of application-level errors (if any) that occurred when eBay processed the request.

See Error Handling.

Errors.ErrorClassification ErrorClassificationCodeType Conditionally API errors are divided between two classes: system errors and request errors.

Applicable values:

CustomCode
(out) Reserved for internal or future use.
RequestError
(out) An error has occurred either as a result of a problem in the sending application or because the application's end-user has attempted to submit invalid data (or missing data). In these cases, do not retry the request. The problem must be corrected before the request can be made again. If the problem is due to something in the application (such as a missing required field), the application must be changed. If the problem is a result of end-user data, the application must alert the end-user to the problem and provide the means for the end-user to correct the data. Once the problem in the application or data is resolved, resend the request to eBay with the corrected data.
SystemError
(out) Indicates that an error has occurred on the eBay system side, such as a database or server down. An application can retry the request as-is a reasonable number of times (eBay recommends twice). If the error persists, contact Developer Technical Support. Once the problem has been resolved, the request may be resent in its original form.

Errors.ErrorCode token Conditionally A unique code that identifies the particular error condition that occurred. Your application can use error codes as identifiers in your customized error-handling algorithms. See the "Errors by Number" document.
Errors.ErrorParameters ErrorParameterType Conditionally,
repeatable: [0..*]
This optional element carries a list of context-specific error variables that indicate details about the error condition. These are useful when multiple instances of ErrorType are returned.
Errors.ErrorParameters
  [ attribute ParamID ]
string Conditionally This optional element carries a list of context-specific error variables that indicate details about the error condition. These are useful when multiple instances of ErrorType are returned.
Errors.ErrorParameters.Value string Conditionally The value of the variable (e.g., the attribute set ID)
Errors.LongMessage string Conditionally A more detailed description of the condition that raised the error.
Errors.SeverityCode SeverityCodeType Conditionally Indicates whether the error is a severe error (causing the request to fail) or an informational error (a warning) that should be communicated to the user.

Applicable values:

CustomCode
(out) Reserved for internal or future use.
Error
(out) The request that triggered the error was not processed successfully. When a serious application-level error occurs, the error is returned instead of the business data.

If the source of the problem is within the application (such as a missing required element), change the application before you retry the request.
  • If the problem is due to end-user input data, please alert the end-user to the problem and provide the means for them to correct the data. Once the problem in the application or data is resolved, you can attempt to re-send the request to eBay.
  • If the source of the problem is on eBay's side, An application can retry the request as-is a reasonable number of times (eBay recommends twice). If the error persists, contact Developer Technical Support. Once the problem has been resolved, the request may be resent in its original form.


See the Compatible Application Check section of the eBay Features Guide for more information.
Warning
(out) The request was processed successfully, but something occurred that may affect your application or the user. For example, eBay may have changed a value the user sent in. In this case, eBay returns a normal, successful response and also returns the warning.

When a warning occurs, the error is returned in addition to the business data. In this case, you do not need to retry the request (as the original request was successful). However, depending on the cause or nature of the warning, you might need to contact either the end user or eBay to effect a long term solution to the problem to prevent it from reoccurring in the future.

Errors.ShortMessage string Conditionally A brief description of the condition that raised the error.
HardExpirationWarning string Conditionally Expiration date of the user's authentication token. Only returned within the 7-day period prior to a token's expiration. To ensure that user authentication tokens are secure and to help avoid a user's token being compromised, tokens have a limited life span. A token is only valid for a period of time (set by eBay). After this amount of time has passed, the token expires and must be replaced with a new token.
Timestamp dateTime Always This value represents the date and time when eBay processed the request. The time zone of this value is GMT and the format is the ISO 8601 date and time format (YYYY-MM-DDTHH:MM:SS.SSSZ). See the Time Values section in the eBay Features Guide for information about this time format and converting to and from the GMT time zone.

Note: GetCategories and other Trading API calls are designed to retrieve very large sets of metadata that change once a day or less often. To improve performance, these calls return cached responses when you request all available data (with no filters). When this occurs, this time value reflects the time the cached response was created. Thus, this value is not necessarily when the request was processed. However, if you specify an input filter to reduce the amount of data returned, the calls retrieve the latest data (not cached). When this occurs, this time value does reflect when the request was processed.
Version string Always The version of the response payload schema. Indicates the version of the schema that eBay used to process the request. See the Standard Data for All Calls section in the eBay Features Guide for information on using the response version when troubleshooting CustomCode values that appear in the response.



Back to top

ReviseInventoryStatus Detail Controls


DetailLevel

This call does not support varying Detail Levels. You do not need to pass DetailLevel in the request.



Back to top

ReviseInventoryStatus Samples

New to making API calls? Please see Routing the Request.

Note: Some item IDs, user IDs, or other data in these samples might no longer be active on eBay. If necessary, you can substitute current eBay data in your requests.

Sample: Basic Call

Revises price and quantity for multiple active listings

Description

The user named magicalbookseller has a listing for MacBook Pro's which shows a quantity of 6. She just received another six of them, and wants to change the quantity listed to 12.

Input

To revise the quantity, the user must specify the ItemID and the new Quantity.

XML format (HTTP POST). Also available are the .txt version of this XML.

<?xml version="1.0" encoding="utf-8"?>
<ReviseInventoryStatusRequest xmlns="urn:ebay:apis:eBLBaseComponents">
  <RequesterCredentials>
    <eBayAuthToken>ABC...123 OF SELLER</eBayAuthToken>
  </RequesterCredentials>
  <Version>589</Version>
  <ErrorLanguage>en_US</ErrorLanguage>
  <WarningLevel>High</WarningLevel>
  <InventoryStatus>
    <ItemID>110035400937</ItemID>
    <Quantity>20</Quantity>
  </InventoryStatus>
  <InventoryStatus>
    <SKU>cmg00002</SKU>
    <ItemID>110035406664</ItemID>
    <Quantity>20</Quantity>
  </InventoryStatus>
  <InventoryStatus>
    <ItemID>110035406665</ItemID>
    <StartPrice>9.95</StartPrice>
  </InventoryStatus>
  <InventoryStatus>
    <SKU>cmg00002</SKU>
    <ItemID>110035407916</ItemID>
    <StartPrice>19.95</StartPrice>
    <Quantity>80</Quantity>
  </InventoryStatus>
</ReviseInventoryStatusRequest>

Output

Success in making the call is indicated by the "Success" value of the Ack field. The response indicates the revised values of the fields that ReviseInventoryStatus can change, Quantity among them, and shows any fees charged due to the revision.

XML format.
<?xml version="1.0" encoding="utf-8"?>
<BulkDataExchangeResponse xmlns="urn:ebay:apis:eBLBaseComponents">
 <ReviseInventoryStatusResponse xmlns="urn:ebay:apis:eBLBaseComponents">
  <Timestamp>2008-10-30T03:19:35.835Z</Timestamp>
  <Ack>Success</Ack>
  <Version>589</Version>
  <Build>e589_core_Bundled_7477537_R1</Build>
  <InventoryStatus>
    <SKU/>
    <ItemID>110035400937</ItemID>
    <StartPrice>8.95</StartPrice>
    <Quantity>20</Quantity>
  </InventoryStatus>
  <InventoryStatus>
    <SKU>1122334455-AA</SKU>
    <ItemID>110035406664</ItemID>
    <StartPrice>11.95</StartPrice>
    <Quantity>20</Quantity>
  </InventoryStatus>
  <InventoryStatus>
    <SKU>1122334455-AB</SKU>
    <ItemID>110035406665</ItemID>
    <StartPrice>9.95</StartPrice>
    <Quantity>37</Quantity>
  </InventoryStatus>
  <InventoryStatus>
    <SKU>1122334455-AC</SKU>
    <ItemID>110035407916</ItemID>
    <StartPrice>19.95</StartPrice>
    <Quantity>80</Quantity>
  </InventoryStatus>
 </ReviseInventoryStatusResponse>
</BulkDataExchangeResponse>



Back to top

ReviseInventoryStatus Change History

Version Description
747
2011-11-09
  • (modified) The maximum limit that an item can be revised per month is 2,000 times. In addition to the ReviseInventoryStatus call, an item can also be revised by the ReviseItem and ReviseFixedPriceItem calls. However, each time an item is revised, it counts towards the 2,000 per month limit.
695
2010-11-10
  • Quantity (doc change): Clarified that Quantity in the request is the quantity available, and Quantity in the response is quantity available plus already sold.
629
2009-08-05
  • SKU (modified): You can now modify variations even when InventoryTrackingMethod is not set to SKU on the listing.
625
2009-07-08
  • Fees (doc change): Clarified that if multiple variations from the same listing were revised, only one set of fees is returned for that listing.
623
2009-06-24
  • Fees (added): Fees are returned for each listing that was revised.
589
2008-10-30
  • (added) New call.



Back to top

User-Contributed Notes