# Why does Kit Pricing have to be set up in Sales Settings when using Kits if the Item Org record has Kit Pricing configured?
**URL:** https://community.nextw.com/t/why-does-kit-pricing-have-to-be-set-up-in-sales-settings-when-using-kits-if-the-item-org-record-has-kit-pricing-configured/1811
**Category:** Sales
**Created:** [March 10, 2026, 4:25pm UTC](https://community.nextw.com/t/why-does-kit-pricing-have-to-be-set-up-in-sales-settings-when-using-kits-if-the-item-org-record-has-kit-pricing-configured/1811 "2026-03-10T16:25:42Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@ian.p](https://community.nextw.com/u/ian.p)
#### Post date: [March 10, 2026, 4:25pm UTC](https://community.nextw.com/t/why-does-kit-pricing-have-to-be-set-up-in-sales-settings-when-using-kits-if-the-item-org-record-has-kit-pricing-configured/1811/1 "2026-03-10T16:25:42Z")
There is a validation at line 060 of `ValidateSOLine` that requires `Kit Pricing` to be configured in `Sales Settings` when using Kits on a Sales Order - else error `Error - Kit definition type and kit pricing settings must be configured in the sales setup application before using the selected item.` gets thrown.
However if the Item Org record on the Sales page has `Kit Pricing` configured, why does what’s configured in Sales Settings even matter? Shouldn’t those be fall backs in case `Kit Pricing` isn’t configured for the Item Org record? Or does this validation exist for a different reason?
---
### Author:  [@ian.p](https://community.nextw.com/u/ian.p)
#### Post date: [March 10, 2026, 8:07pm UTC](https://community.nextw.com/t/why-does-kit-pricing-have-to-be-set-up-in-sales-settings-when-using-kits-if-the-item-org-record-has-kit-pricing-configured/1811/2 "2026-03-10T20:07:21Z")
This has been confirmed as being a bug.