> 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/integration/bevica_website_integration/web_integration_-_sales_prices.md). # Web Integration - Sales Prices Publish and maintain sales prices and discounts for the website. ### Sales Prices If you have set a ‘Default Price Group’ in **Web Site Setup** then the Item node of the **Web Product** will have a Duty Paid and/or Duty Free price calculated when the data is called by the website. If you have a tiered pricing structure, such as All Customers and Customer Price Groups and Customer prices then a full list of valid prices is made available. The system local currency from **General Ledger Setup** will always be returned rather than blank for currency when looking in the Bevica client. Bevica is very flexible in how prices are set up and will calculate a sales price across all the applicable prices which could apply. Often websites do not have the same structure so this is usually an area for technical discussion between consultants and your web developers. ### Sales Price data Depending on the pricing model being used two APIs are available: * [Get Sales Price List Prices](/documentation/guides/pricing-costs-and-charges/sales_and_purchase_price_lists_-_new_pricing_experience.md) - new pricing experience based on Price Lists * Get Sales Prices - legacy pricing model --- # 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://kb.bevica.com/documentation/integration/bevica_website_integration/web_integration_-_sales_prices.md?ask=&goal= ``` `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.