> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/developers-api/vendor-management/get-item-pricing-rules.md).

# Get Item Pricing Rules

Retrieves pricing rules for items based on ItemNumber, Customer, UOM, and Date.\
This endpoint is used to determine the applicable price, discount, and level price for an item.\
If the Multi-UOM setting is enabled, the UOM field becomes mandatory because pricing may differ by unit of measure.

* Fields

  | Field          | Data Type | Default Value | Description                                                                                                   |
  | -------------- | --------- | ------------- | ------------------------------------------------------------------------------------------------------------- |
  | `ItemNumber`   | string    | NA            | Unique identifier of the item.                                                                                |
  | `CustomerName` | string    | NA            | Customer name for which pricing is fetched.                                                                   |
  | `UOMName`      | string    | NA            | Unit of measure (mandatory if Multi-UOM is ON).                                                               |
  | `Date`         | string    | NA            | If the pricing rule's date flag is enabled, the provided date must fall within the rule's From-To date range. |

```json
{"openapi":"3.0.3","info":{"title":"Xorosoft ERP Public API","version":"2026.07"},"tags":[{"name":"Vendor Management","description":"Use Vendor Management APIs to retrieve vendors and maintain vendor-related item mappings and pricing references. These endpoints help purchasing, supplier, and catalog integrations connect vendor data, vendor part numbers, pricing rules, and item/customer mappings with Xorosoft ERP records."}],"servers":[{"url":"https://res.xorosoft.io","description":"Xorosoft ERP API server"}],"security":[{"basic":[]}],"components":{"securitySchemes":{"basic":{"scheme":"basic","type":"http"}}},"paths":{"/api/xerp/item/getitempricingrules":{"post":{"responses":{"200":{"content":{"application/json":{"schema":{"properties":{"Data":{"items":{"properties":{"Amount":{"type":"number"},"Discount":{"type":"number"},"Id":{"type":"number"},"LevelPrice":{"type":"number"},"Name":{"type":"string"},"Priority":{"type":"number"},"StandardPrice":{"type":"number"},"UomName":{"type":"string","nullable":true}},"type":"object"},"type":"array"},"Message":{"type":"string"},"Result":{"type":"boolean"}},"type":"object"}}},"description":"OK","headers":{}}},"tags":["Vendor Management"],"description":"Retrieves pricing rules for items based on ItemNumber, Customer, UOM, and Date.  \nThis endpoint is used to determine the applicable price, discount, and level price for an item.  \nIf the Multi-UOM setting is enabled, the UOM field becomes mandatory because pricing may differ by unit of measure.\n\n+ Fields\n\n    | Field          | Data Type | Default Value | Description |\n    |----------------|-----------|----------------|-------------|\n    | `ItemNumber`   | string    | NA             | Unique identifier of the item. |\n    | `CustomerName` | string    | NA             | Customer name for which pricing is fetched. |\n    | `UOMName`      | string    | NA             | Unit of measure (mandatory if Multi-UOM is ON). |\n    | `Date`         | string    | NA             | If the pricing rule's date flag is enabled, the provided date must fall within the rule's From-To date range. |","operationId":"post_item_getitempricingrules","requestBody":{"content":{"application/json":{"schema":{"items":{"properties":{"CustomerName":{"type":"string"},"Date":{"type":"string"},"ItemNumber":{"type":"string"},"UOMName":{"type":"string"}},"type":"object"},"type":"array"}}}},"summary":"Get Item Pricing Rules"}}}}
```


---

# 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.xorosoft.com/developers-api/vendor-management/get-item-pricing-rules.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.