{"id":1625,"date":"2026-09-30T01:30:56","date_gmt":"2026-09-30T01:30:56","guid":{"rendered":"https:\/\/www.maxmerce.com\/blog\/?p=1625"},"modified":"2026-10-09T01:21:02","modified_gmt":"2026-10-09T01:21:02","slug":"ebay-item-condition-codes","status":"publish","type":"post","link":"https:\/\/www.maxmerce.com\/blog\/ebay-item-condition-codes\/","title":{"rendered":"eBay Item Condition Codes: Check the Category Before Upload"},"content":{"rendered":"

eBay item condition codes are not universal shortcuts for \u201cnew\u201d or \u201cused.\u201d<\/strong> The numeric ID describes a condition in eBay\u2019s reference table, but the conditions you may use depend on the marketplace and the leaf category<\/em> of the item. Before putting a code into a listing template or integration, check that category\u2019s current condition policy and confirm the item actually meets the definition. eBay\u2019s US condition-ID reference<\/a> is a starting point, not a list of values accepted everywhere.<\/p>\n

What the number tells you\u2014and what it does not<\/h2>\n
\"Seller<\/div><\/figure>\n

In eBay\u2019s US reference, 1000<\/code> identifies a new item, 1500<\/code> is used for labels such as \u201cnew other\u201d or \u201copen box,\u201d and 3000<\/code> can appear as \u201cused\u201d or \u201cpre-owned \u2013 good.\u201d Apparel also has entries such as 2990<\/code> for \u201cpre-owned \u2013 excellent\u201d and 3010<\/code> for \u201cpre-owned \u2013 fair.\u201d 7000<\/code> describes \u201cfor parts or not working\u201d where that choice is supported. These are examples of reference meanings<\/em>, not approval for your particular category. The displayed wording and supported subset can change by category; refurbished options can additionally have eligibility limits.<\/p>\n

First choose the correct eBay category for the actual product. Then use eBay\u2019s category condition policy<\/a> or the current category-specific Seller Hub template to find the available condition choices. Do not move a camera strap into a camera category just because that category accepts a code you want to use.<\/p>\n

A four-gate preflight before you upload<\/h2>\n
\"US<\/div><\/figure>\n
    \n
  1. Marketplace and leaf category.<\/strong> Record the marketplace (for this guide, eBay US) and the exact leaf category. A broad department name is not enough for a dependable code check.<\/li>\n
  2. Physical evidence.<\/strong> Inspect the exact unit or a reliable seller-owned inspection record. Note what works, visible wear, missing accessories, packaging and anything untested. A listing description cannot turn an untested item into a verified \u201cfully operational\u201d one.<\/li>\n
  3. Supported value and field format.<\/strong> Check the leaf category\u2019s supported condition IDs. A Trading API Item.ConditionID<\/code> is numeric; eBay\u2019s Inventory API uses a text-based ConditionEnum<\/code>. Do not paste 3000<\/code> into an enum field or USED_EXCELLENT<\/code> into a numeric ID field just because an online chart puts them on the same row.<\/li>\n
  4. Submission review.<\/strong> In Seller Hub Reports, start from a fresh category-specific template and follow its accepted values. In an API flow, use the current condition policy for the target marketplace\/category. Validate a small representative batch before a large upload; read any errors against the actual category and SKU instead of applying one global replacement.<\/li>\n<\/ol>\n

    eBay\u2019s Trading API condition guide<\/a> says an invalid ID\u2014or a missing one where required\u2014can fail the listing request. This is a platform rule. The small-batch check is an editorial risk-control practice, not an eBay guarantee that the rest of a file will pass.<\/p>\n

    Use a code worksheet, not a memorized list<\/h2>\n
    \"Folded<\/div><\/figure>\n

    The following rows are illustrative candidates, not confirmed codes for a particular leaf category<\/strong>. They show which fact to verify before the field is filled. Keep one row per SKU; never assume two items in different categories accept the same code because both are \u201cused.\u201d<\/p>\n

    \n\n\n\n\n\n\n\n
    Illustrative eBay US condition-code preflight; candidate IDs must be confirmed against current leaf-category policy<\/caption>\n
    SKU scenario<\/th>\nCandidate from reference<\/th>\nBefore entering it<\/th>\n<\/tr>\n<\/thead>\n
    Tested, used camera<\/th>\n3000<\/code> (used)<\/td>\nConfirm the exact Cameras & Photo leaf category accepts it; keep test results and defects in the condition note.<\/td>\n<\/tr>\n
    Previously worn shirt with minimal wear<\/th>\n2990<\/code> (pre-owned \u2013 excellent)<\/td>\nCheck the specific apparel leaf category and the actual garment; do not use \u201cexcellent\u201d when photographed flaws contradict it.<\/td>\n<\/tr>\n
    Camera with a verified functional fault<\/th>\n7000<\/code> (for parts or not working)<\/td>\nCheck category support, name the failed function, and show the exact item. Do not rely on a vague \u201cas-is\u201d sentence.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    For the camera, keep a seller-owned test record and describe any fault or missing accessory. For apparel, inspect the actual garment and photograph visible wear. The worksheet addresses whether the chosen code is permitted in the leaf category; it does not replace evidence about the item.<\/p>\n

    When a condition code is rejected<\/h2>\n