Inventory API error details

VariationSpecifics or VariationSpecificsSet mismatch between item and Selling Manager product

The name-value pairs specified in the variesBy.specifications array of the getInventoryItemGroup response show the full list of variation specific (also know as pivoting aspects) values available through all inventory items in the inventory item group. For example, if each variation in this inventory item group varied by color and size, one of the variesBy.specifications.name node values would be Color with all available colors specified in the corresponding variesBy.specifications.values array, and one of the variesBy.specifications.name node values would be Size with all available sizes specified in the corresponding variesBy.specifications.values array. All inventory items in the inventory item group must have both Color and Size defined as their aspects through the product.aspects field and collectively as a group, or this error will occur.

To correct this error, review the sku.product.aspects that are present in group.variesBy.specifications. Correct any differences by updating the variants (sku.product.aspects) or varies by specification (group.variesBy.specifications).

Missing value in the NameValueList pair.

Missing value in the NameValueList pair within a Variation or within the VariationSpecificsSet container.

For all of the pivoting aspect values covered in the variesBy.specifications array, there should be inventory items in the inventory item group that cover these aspect values. For example, if the inventory item group involves t-shirts with multiple colors and sizes, there should be variation(s) with all colors and sizes defined through the variesBy.specifications array.

Sale Type does not Support variation listings

This error is triggered when you try to publish a multiple-SKU listing, but one or more offers for inventory items in the inventory item group have the listing format value set to AUCTION instead of FIXED_PRICE. Auctions do not support variations. You must review the offer objects to see which one(s) might be using as the AUCTION listing format. The listing format cannot be updated with the updateOffer method, so you must delete the offer using the deleteOffer method, and then create new offers for the SKU(s) where the listing format is AUCTION . Then you can try again to publish the multi-SKU listing using the publishOfferByInventoryItemGroup method.

Disabled as variant error.

The tags replaceable_value is/are disabled as Variant.

Not all aspects are allowed as a pivoting aspect. A pivoting aspect defines the difference between each inventory item within a inventory item group. To see which aspects are allowed as pivoting aspects, you can use the getItemAspectsForCategory method and look for a value of true in the aspectEnabledForVariations field for the corresponding aspect.

Too many trait values in variation specifics of the variation

This error occurs when multiple values have been specified for a product aspect that only supports one value. Many product aspects only support one value, so it is a good idea to use the getItemAspectsForCategory method, look for that product aspect in the response, and make sure the value of the aspectConstraint.itemToAspectCardinality field is MULTI and not SINGLE. Please search an inventory item's product.aspects field for that product aspect and remove one or more values based on what you discover.

Required Picture Variation Specific missing

Picture variations may be specified in the imageUrls array (using the createOrReplaceInventoryItemGroup method).

Provide aspectsImageVariesBy value in group and also provide images at sku level.

Picture Variation Specific disabled

Variation specific name replaceable_value cannot be used for variation pictures.

Not all aspects are allowed as a pivoting aspect, and only pivoting aspects can be used as a variesBy.aspectsImageVariesBy value in a createOrReplaceInventoryItemGroup request. To see which aspects are allowed as pivoting aspects, you can use the getItemAspectsForCategory method and look for a value of true in the aspectEnabledForVariations field for the corresponding aspect.

Invalid variation specific name for pictures

Make sure there is value in the picture varies by field (variesBy.aspectsImageVariesBy) and that value is part of specification (variesBy.specifications).

Variation specific value replaceable_value used for pictures does not exist in variation specific set.

See the imageUrls field in the createOrReplaceInventoryItemGroup method. Make sure there is only one value in picture varies by and that value is part of variesBy.specifications.

Requires Unique Variation Specifics and Item Specifics.

Variations Specifics and Item Specifics entered for a Multi-SKU item should be different.

The common product aspects for all inventory items in the inventory item group (specified through the aspects array of the createOrReplaceInventoryItemGroup request) and the varying aspects (aka pivoting aspects) unique for each inventory item (specified through the product.aspects array of the createOrReplaceInventoryItem request) should be different. If inventory items in an inventory item group vary by color and size, 'Color' and 'Size' should be defined in product.aspects array of the createOrReplaceInventoryItem request for each inventory item, but 'Color' and 'Size' should not be specified in the aspects array of the createOrReplaceInventoryItemGroup request.

Variation cannot be deleted during restricted revise.

This error will occur if one or more of the inventory items in the inventory item group has a quantity of 0 when trying to create a new multiple-SKU listing or when trying to revise an active multiple-SKU listing while that listing is in restricted revise mode.

Mismatch name combination in name value list pair in variation specifics.

This error will occur if the corresponding pivoting aspect name/value pair(s) in the product.aspects array of an inventory item do not match. For example, if 'Color' was the pivoting aspect, only color values should be specified.

Missing required variation specifics.

This error will occur if one or more inventory items in an inventory item group are missing the pivoting aspects that are defined through the variesBy.specifications array of the inventory item group object. If the inventory items vary by color and size, the 'Color' and 'Size' name/value pairs must be defined for each inventory item in the inventory item group.

Invalid trait value(s) for eBay recommended trait name replaceable_value.

This error may occur if the seller uses a different product aspect value than what eBay is expecting for a specific product aspect. For example, this error might occur if you had a typo for a color value. eBay might have been expecting Blue, but you had Bleu.

Reference the invalid value in the error message and then check and correct that value for your inventory item or inventory item group.

Name replaceable_value only allows a single value in variation specifics

This error occurs when you are trying to enter multiple values for a product aspect name that only supports one value. Many product aspect names only support one value, so it is a good idea to use the getItemAspectsForCategory method to verify which product aspect names only support a single value (SINGLE is returned in itemToAspectCardinality field) and which ones support multiple values (MULTI is returned  in itemToAspectCardinality field). Please revisit your product.aspects array of the inventory item object or the aspects array of the inventory item group object request for that product aspect name and remove additional value(s).

Variation specifics cannot be changed in restricted revise

When an active multiple-SKU listing is in restricted revise mode, no product aspect changes can be made to the inventory item group object nor pivoting aspect changes to inventory items within that inventory item group.

Seller is not eligible to create variations in product, template, or listing

The seller will not be able to create a multiple-SKU listing if the seller's account is not eligible for this feature. To check if a seller's account if eligible for this feature, the GetUser call in Trading API can be used. In the GetUser request payload, the IncludeFeatureEligibility boolean should be included and set to True. The FeatureEligibility.QualifiesForVariations field in the response will indicate whether the seller is eligible to create multiple-SKU listings.

All variation specifics require a name and a value.

All inventory items belonging to an inventory item group must have name/value pairs that match the data specified through the variesBy.specifications array of the inventory item group object. If that array has Color and Size as pivoting aspects, each inventory item in the group must have both Color and Size defined as product aspects in the product.aspects field, and the values for both of these aspects must be in the list of values in the variesBy.specifications.values array of the inventory item group object.

At least one trait value is required in NameValueList pair in VariationSpecifics container.

This error will occur if a pivoting aspect name is defined through the product.aspects field of an inventory item object that belongs to an inventory item group, but that pivoting aspect name is missing a corresponding value.

Variation specific names exceed limit replaceable_value

This error will occur if one or more inventory item objects belonging to an inventory item group has more pivoting aspects defined through product.aspects field than the inventory item group has specified through the variesBy.specifications array. The number of pivoting aspects should match.

Values per name-value list exceed limit replaceable_value in variation specifics set container.

This error will occur if the number of image URLs passed in through the imageUrls array of the inventory item group object exceeds the number of values available for the product aspect set as the aspectsImageVariesBy value. For example, if the aspectsImageVariesBy value is Color, and there are only 8 different color values specified through the variesBy.specifications.values array, there should not be more than 8 different image URLs in the imageUrls array.

Duplicate names in name value list in variation specifics container.

This error will occur if the same product aspect name is included more than once in the product.aspects field of an inventory item object.

Duplicate VariationSpecifics trait value in the VariationSpecificsSet container.

This error occurs if the variesBy.specifications.values array in an inventory item group object repeats the same product aspect value more than once. Each value should only appear once for each pivoting aspect.

Variation is required for a listing that previously had variations.

This error may occur if the createOrReplaceInventoryItemGroup is being used to add one or more inventory items (aka SKUs) to the inventory item group, but the data in the product.aspects field(s) of those inventory item object(s) is not matching the product aspect names and values defined in the variesBy.specifications array of the inventory item group being updated.

Variations number exceeds limit replaceable_value

This error may occur if the number of inventory items in the inventory item group has reached the maximum threshold. The maximum threshold value of SKUs in one listing can vary by marketplace in category. If this error occurs, you may need to remove one or more of the SKU values specified through the variantSKUs array of the inventory item group object.

Duplicate custom variation label.

This error will occur if one or more inventory items in the inventory item group are using the same pivoting aspect value combination. For example, if Color and Size are the pivoting aspects, each inventory item in the inventory item group should have a unique color and size combination.

Duplicate variation specifics

This indicates product aspects name-value pairs are duplicated.

Missing name in name-value list.

The name-value list pairs in the aspects collection show the full list of variation specific (also know as pivoting aspects) values available. For example, if each variation in this listing varied by color and size, all available colors and all available sizes would be specified in separate name-value pairs. All of the variations defined under each variesBy.specifications array should have Color and Size defined as name-value pairs in the aspects collection. Please review the schema mentioned above and correct any discrepancies.

Who pays for shipping is required

The return business policy being used by the offer object does not indicate whether the buyer or seller is responsible for return shipping cost, and this field is required if the seller accepts returns. Make a getOffer call and look at the listingPolicies.returnPolicyId field in the response to see which return business policy is being used.  Use the updateReturnPolicy method of the Account API v1 and set the returnShippingCostPayer value to indicate whether the buyer or seller are responsible for shipping costs when an item is returned.

Return window is required

The return business policy being used by the offer object does not indicate the return period,, and this field is required if the seller accepts returns. Make a getOffer call and look at the listingPolicies.returnPolicyId field in the response to see which return business policy is being used.  Use the updateReturnPolicy method of the Account API v1 and set the returnPeriod value to indicate how long the buyer has to return the item after receiving it.

The original retail price is required for listing a minimum advertised price item. The discounted pricing information must contain the original retail price to list a minimum advertised price item.

This error will occur if the minimumAdvertisedPrice for an offer is set, but the originalRetailPrice is not set. Both are required for eligible sellers to use the Mininum Advertised Price feature.

Listing is missing item specific(s): replaceable_value. Category <i>replaceable_value</i> will require the following item specific(s): replaceable_value.

This warning is returned if the inventory item object is missing a recommended product aspect that is expected to be mandated in the future. If the product aspect applies to your product, you should add this aspect name/value pair through the product.aspects field. Use the getItemAspectsForCategory method of the Taxonomy API to retrieve the required, recommended, and optional product aspects for an eBay category. Some recommended product aspects will also have expectedRequiredByDate fields that indicate the approximate date when that product aspect will become required.

Shipping policy is required.

A fulfillment business policy is required for all offers. You can find available fulfillment business policies using the getFulfillmentPolicies of the Account API v1. Add the fulfillmentPolicyId to the offer using the updateOffer method.

Payment policy is required.

A payment business policy is required for all offers. You can find available payment business policies using the getFulfillmentPolicies of the Account API v1. Add the paymentPolicyId to the offer using the updateOffer method.

Return policy is required.

A return business policy is required for all non-vehicle offers. You can find available return business policies using the getFulfillmentPolicies of the Account API v1. Add the returnPolicyId to the offer using the updateOffer method.

Before you can list this item we need some additional information to create a seller's account.

This error occurs if the seller associated with the user token has one or more actions to take in their selling account. This can be for any number of things, including missing registration information or missing payment information. See Registering as a seller for details on the seller registration process. Check the error parameter for further details.

We are sorry, but the credit card that you have on file has expired. Please visit My eBay to update your account information.

Sellers must have at least one bank account and/or credit card on file to handle selling-related fees. If the primary/only payment method on file is an expired credit card, this error will occur and the seller will not be able to create/revise new listings until an updated payment method is provided through the Payments tab in Seller Hub.

Direct Debit Rejected.

This error will occur if eBay tried to process an invoice against the seller's account, but payment failed. The seller should check their payment method(s) on file with eBay, and make sure that everything is correct. The seller will not be able to create/revise new listings until a valid payment method is provided through the Payments tab in Seller Hub.