> For the complete documentation index, see [llms.txt](https://docs.fairmarkit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fairmarkit.com/buyers/administration/price-books.md).
# Price Books
From the Price books tab, you can upload your price books data to Fairmarkit. From the admin area, you can create your price books as well as create pricebook items directly in the UI. (You can also create pricebooks and pricebook items via API which can be found [here](https://developers.fairmarkit.com/reference/create_price_book_services_self_service_api_v4_price_books__post).
{% hint style="info" %}
**Access**: To access these settings, you will need to be assigned to the Admin role for your organization and have Price books enabled.
{% endhint %}
### Creating a new pricebook
{% stepper %}
{% step %}
Click **Create price book in the top right**.
{% endstep %}
{% step %}
Define the price book header information.
The required field of any pricebook are **title**, **supplier** (selection from uploaded suppliers), **type** (goods or services catalog), and **effective date from and to**.
{% endstep %}
{% step %}
You can define your own schema for the attributes of a price book directly in Fairmarkit. Using the visual builder in the Item schema tab, you can add any type of data point and shape the fields your price book items carry. Fairmarkit's Technical Architects are still on hand to help you design more complex schemas.
{% hint style="info" %}
**Required Fields:** Description, currency, Unit of Measure and Unit Price are required fields in the schema.
{% endhint %}
{% hint style="info" %}
**Important Note:** While you can have a different schema per pricebook, best practices would be to align on one schema for items and one for services to simplify management, especially if integrating via API.
{% endhint %}
{% endstep %}
{% step %}
Custom tags are used to filter when the pricebook and the items within should be shown. you can use standard attributes such as country, but also custom attributes you define in intake such as plant, business\_unit, etc. for filtering. To add multiple attributes to a single tag (i.e. multiple countries for a single pricebook) just click the + button to add multiple (as shown in the GIF below).
{% endstep %}
{% endstepper %}
### Add items to price book
{% stepper %}
{% step %}
Once the pricebook is created, you can navigate inside of it to see all items inside of it (will be blank to start).
{% endstep %}
{% step %}
You can then add items manually by clicking Create Item in the top right. This will show the required fields and any other fields you defined in your schema.
{% endstep %}
{% step %}
You also have the option to upload the content via a csv. The csv that gets downloaded is in the format that needs to be reuploaded (taking your custom fields into account)
{% endstep %}
{% endstepper %}
### Deactivate or delete a price book
* Any pricebook can be either deactived so it is no longer shown or deleted in the platform. Items can also be deleted.
* In order to change the schema of a pricebook, all items must be deleted out of the pricebook before it can be changed.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.fairmarkit.com/buyers/administration/price-books.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
