> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/guides/pricing-costs-and-charges.md).

# Pricing, Costs & Charges

Pricing, cost, and charge setup in Bevica, including price lists and target cost controls.

### Summary

* Set up and maintain sales and purchase pricing in Bevica.
* Understand the “new” vs “old” pricing experiences and when each applies.
* Configure costing inputs that impact margin and valuation.
* Apply automated charges (delivery, distribution, landed costs) when needed.

### Next steps

* If you’re using the new pricing experience, start with [Initialising the New Sales and Purchase Price Experience](https://kb.bevica.com/documentation/guides/pricing-costs-and-charges/initialising_the_new_sales_and_purchase_price_experience.md).
* Then use [Sales and Purchase Price Lists - New Pricing Experience](https://kb.bevica.com/documentation/guides/pricing-costs-and-charges/sales_and_purchase_price_lists_-_new_pricing_experience.md).
* For stock pricing and supplier price visibility, read [Inventory Price List](https://kb.bevica.com/documentation/guides/pricing-costs-and-charges/inventory_price_list.md).
* To manage margin expectations on sales lines, review [Item Sales Line 'Target Cost'](https://kb.bevica.com/documentation/guides/pricing-costs-and-charges/item_sales_line_target_cost.md).
* If you need landed costs / delivery charges, go to [Distribution Costs Management](https://kb.bevica.com/documentation/guides/distribution_costs_management.md).


---

# 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://kb.bevica.com/documentation/guides/pricing-costs-and-charges.md?ask=<question>&goal=<user_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.
