{"section":"tracks","requestedLocale":"en","requestedSlug":"preco-base-definicao-de-conceito","locale":"en","slug":"preco-base-definicao-de-conceito","path":"docs/en/tracks/vtex-modules-getting-started/prices-101/preco-base-definicao-de-conceito.md","branch":"main","content":"## Definition\n\nA SKU's base price is the value which results from merging the **Cost Price** with the **Markup**, the desired profit margin with the SKU's sale. It represents the SKU's __reference price__ for all price tables. \n\n![base-price-en](https://cdn.statically.io/gh/vtexdocs/help-center-content/refs/heads/main/docs/en/tracks/vtex-modules-getting-started/prices-101/preco-base-definicao-de-conceito_1.png)\n\nThis **base price** can be combined with a price table's applied **price rule**. If there are no registered price rules, a price table's selling price will be equal to the base price itself.\n\n## List Price\n\nThe __list price__ functions as a SKU's suggested selling price. Later on, this price can receive a reduction, allowing you to showcase a SKU with the following information in the store's window display:\n\n```\nOriginal Price: U$ 199,00\nSales Price: U$ 149,00\n```\n\nThus, the list price is the **original price** and the selling price is the __sales price__. \n\n## Examples\n\nAs previously mentioned, the base price is the *reference price* for all your store's price tables. \n\nIn the article on the Prices module architecture, we saw that if you *only* add a SKU base price without configuring other rules or fixed prices, that base price value will be considered the __computed price__ for your price tables.\n\nIf your strategy does not entail having different prices for different contexts, you just have to add one base price for your SKUs."}