> For the complete documentation index, see [llms.txt](https://docs.partssource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.partssource.com/api/domain-concepts/product-condition.md).

# Product Condition

Understanding product condition values and their impact on pricing and warranty

The `condition` field describes the state of a product being offered for sale. Each pricing option returned from `/catalog/detail` has a unique condition—you won't see duplicate conditions within a single response.

***

## Where Condition Appears

| Endpoint           | Field Location        |
| ------------------ | --------------------- |
| `/catalog/detail`  | `options[].condition` |
| Order confirmation | Line item details     |

The condition is locked in when you select a `priceOptionId`.

{% hint style="info" %}
**One option per condition**

Each condition appears at most once in a catalog detail response. If a product is available as both "New OEM" and "Refurbished", you'll get two options with different conditions—never two options with the same condition.
{% endhint %}

***

## Condition Values

These conditions appear in catalog detail responses:

| Condition                 | Description                                     |
| ------------------------- | ----------------------------------------------- |
| **New OEM**               | Brand new from original equipment manufacturer  |
| **OEM Original**          | Original OEM part (may be older stock)          |
| **OEM Replacement**       | OEM-sourced replacement part                    |
| **Refurbished**           | Restored to working condition with testing      |
| **Certified Refurbished** | Refurbished with manufacturer certification     |
| **Aftermarket**           | Third-party manufactured compatible part        |
| **Tested**                | Used part verified to be functional             |
| **Not Tested**            | Used part without functional verification       |
| **Demo**                  | Demonstration unit, typically lightly used      |
| **Open Box**              | New but opened, may have cosmetic imperfections |

***

## Example Response

```json
{
  "options": [
    {
      "priceOptionId": "OPT-001",
      "condition": "New OEM",
      "price": 2500.00,
      "warranty": "24 Months"
    },
    {
      "priceOptionId": "OPT-002",
      "condition": "Refurbished",
      "price": 1250.00,
      "warranty": "12 Months"
    },
    {
      "priceOptionId": "OPT-003",
      "condition": "Aftermarket",
      "price": 850.00,
      "warranty": "6 Months"
    }
  ]
}
```

Each option represents a different condition available for this product. The user selects based on their preference for condition, price, and warranty.

***

## Condition and Warranty

Each condition has its own price and warranty terms:

{% hint style="info" %}
**Condition determines the option**

Since each condition appears only once, selecting a condition effectively selects the pricing option. Price and warranty are tied to that specific condition.
{% endhint %}

***

## Best Practices

1. **Display condition prominently** - Users need this information to make purchasing decisions
2. **Show warranty alongside condition** - Warranty varies even when condition is the same
3. **Handle all values** - Your UI should gracefully display any condition string, including unexpected values
4. **Consider filtering** - Some organizations only allow certain conditions (e.g., "New OEM only" policies)

***

## Related Concepts

* [Price Option ID](/api/domain-concepts/price-option-id.md) - The quote that locks in condition and price
* [Required Fields](/api/domain-concepts/required-fields.md) - Additional information vendors may require
* [Search to Order Cookbook](/api/cookbooks/search-to-order.md) - Complete ordering workflow


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.partssource.com/api/domain-concepts/product-condition.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.