| Sub-package | -Description | -
|---|---|
| Umbraco.Commerce.Common | -A shared project of common, non-Commerce-specific patterns and helpers. | -
| Umbraco.Commerce.Core | -Core Commerce functionality that doesn't require any infrastructure-specific dependencies. | -
| Umbraco.Commerce.Infrastructure | -Infrastructure-specific project containing implementations of core Commerce functionality. | -
| Umbraco.Commerce.Persistence.SqlServer | -Persistence-specific project containing implementations of core Commerce persistence functionality for SQL Server. | -
| Umbraco.Commerce.Persistence.Sqllite | -Persistence-specific project containing implementations of core Commerce persistence functionality for SQLite. | -
| Umbraco.Commerce.Web | -Core Commerce functionality that requires a web context. | -
| Umbraco.Commerce.Cms | -Core Commerce functionality that requires an Umbraco dependency. | -
| Umbraco.Commerce.Cms.Web | -The Commerce functionality for the Umbraco presentation layer. | -
| Umbraco.Commerce.Cms.Web.Api | -A shared project of common API specific functionality. | -
| Umbraco.Commerce.Cms.Web.Api.Management | -The backoffice Management API layer. | -
| Umbraco.Commerce.Cms.Web.Api.Payment | -The Payment handling API layer. | -
| Umbraco.Commerce.Cms.Web.Api.Storefront | -The frontend Storefront API layer. | -
| Umbraco.Commerce.Cms.Web.UI | -The static Commerce assets for the Umbraco presentation layer. | -
| Umbraco.Commerce.Cms.Startup | -The Commerce functionality for registering Commerce with Umbraco. | -
| Umbraco.Commerce | -The main Commerce package entry point package. | -
@Model.Value("productTitle")
- @Model.Value("productDescription")
-
- Our price excluding VAT @price.WithoutTax.ToString("C0")
- - if (@Model.ValueSorry, out of stock
- } - else - { - - } - -} -``` - -The hidden field uses the `productReference` to be passed across to the Controller. - -## Adding the Controller - -For the button to work, you need to implement a controller. An example of this is shown below. - -Create a new Controller called `CartSurfaceController.cs`. - -{% hint style="warning" %} - -The namespaces used in this Controller are important and need to be included. - -``` -using Microsoft.AspNetCore.Mvc; -using Umbraco.Cms.Core.Cache; -using Umbraco.Cms.Core.Logging; -using Umbraco.Cms.Core.Models.PublishedContent; -using Umbraco.Cms.Core.Routing; -using Umbraco.Cms.Core.Services; -using Umbraco.Cms.Core.Web; -using Umbraco.Cms.Infrastructure.Persistence; -using Umbraco.Cms.Web.Website.Controllers; -using Umbraco.Commerce.Common.Validation; -using Umbraco.Commerce.Core.Api; -using Umbraco.Commerce.Core.Models; -using Umbraco.Commerce.Extensions; -using Umbraco.Extensions; -``` - -{% endhint %} - -```csharp -public class CartSurfaceController : SurfaceController -{ - public CartSurfaceController(IUmbracoContextAccessor umbracoContextAccessor, - IUmbracoDatabaseFactory databaseFactory, - ServiceContext services, AppCaches appCaches, - IProfilingLogger profilingLogger, - IPublishedUrlProvider publishedUrlProvider, - IUmbracoCommerceApi commerceApi) - : base(umbracoContextAccessor, databaseFactory, services, appCaches, profilingLogger, publishedUrlProvider) - { - _commerceApi = commerceApi; - } -} -``` - -Below you can see the equivalent code for having this as a Primary Constructor: - -```csharp -public class CartSurfaceController(IUmbracoContextAccessor umbracoContextAccessor, - IUmbracoDatabaseFactory databaseFactory, - ServiceContext services, AppCaches appCaches, - IProfilingLogger profilingLogger, - IPublishedUrlProvider publishedUrlProvider) - : SurfaceController(umbracoContextAccessor, databaseFactory, services, appCaches, profilingLogger, publishedUrlProvider) -{ -} -``` - -The CartDto class below is used to pass the `productReference` across to the Controller. This class has only one property for the `productReference`. - -```csharp -public class CartDto -{ - public string ProductReference { get; set; } -} -``` - -We now need to add the Action to add the item to the cart. This action will be called when the button is clicked. - -```csharp -[HttpPost] -public IActionResult AddToBasket(CartDto cart) -{ - commerceApi.Uow.Execute(uow => - { - var store = CurrentPage.Value@success
- }
-}
-```
-
-You can now run the application, click the button, and see the product added to the cart with a message displayed to the user.
diff --git a/14/umbraco-commerce/how-to-guides/configure-sqlite-support.md b/14/umbraco-commerce/how-to-guides/configure-sqlite-support.md
deleted file mode 100644
index 2fbaf3a6b1c..00000000000
--- a/14/umbraco-commerce/how-to-guides/configure-sqlite-support.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-description: How-To Guide to configure SQLite support for Umbraco Commerce.
----
-
-# Configure SQLite support
-
-Out of the box, Umbraco Commerce only supports SQL Server-based databases as this is the recommended database platform for live environments. To aid testing and rapid prototyping, however, Umbraco Commerce can be configured to use an SQLite database.
-
-{% hint style="warning" %}
-Whilst Umbraco Commerce does support SQLite for testing, we do not recommend using it in a live environment. Due to the high levels of active connections required to manage concurrent shopping carts, this is not something SQLite handles well at all.
-{% endhint %}
-
-## Install SQLite dependencies
-
-To add SQLite support, you will need to install the SQLite persistence layer NuGet package for Umbraco Commerce.
-
-```bash
-PM> dotnet add package Umbraco.Commerce.Persistence.Sqlite
-```
-
-Once the NuGet package is installed, you need to register SQLite support with Umbraco Commerce via the [`IUmbracoCommerceBuilder`](../key-concepts/umbraco-commerce-builder.md) interface.
-
-Add .`AddUmbracoCommerce()` below `.AddWebsite()` in the `Program.cs` file.
-
-```csharp
-.AddUmbracoCommerce(builder => {
- builder.AddSQLite();
-})
-```
-
-After configuring Umbraco CMS with SQLite, Umbraco Commerce will automatically utilize the same database configuration. If you wish to install Umbraco Commerce into its own SQLite database you can configure its connection string in the `appSettings.json` like so:
-
-```json
-{
- ...
- "ConnectionStrings": {
- "umbracoDbDSN": "Data Source=|DataDirectory|/Umbraco.sqlite.db;Cache=Private;Foreign Keys=True;Pooling=True",
- "umbracoDbDSN_ProviderName": "Microsoft.Data.Sqlite",
- "umbracoCommerceDbDSN": "Data Source=|DataDirectory|/Umbraco.Commerce.sqlite.db;Mode=ReadWrite;Foreign Keys=True;Pooling=True;Cache=Private",
- "umbracoCommerceDbDSN_ProviderName": "Microsoft.Data.Sqlite"
- },
- ...
-}
-
-```
diff --git a/14/umbraco-commerce/how-to-guides/delete-item.md b/14/umbraco-commerce/how-to-guides/delete-item.md
deleted file mode 100644
index ec7ac680cef..00000000000
--- a/14/umbraco-commerce/how-to-guides/delete-item.md
+++ /dev/null
@@ -1,174 +0,0 @@
----
-description: Learn how to remove items added to the shopping cart.
----
-
-# Delete item from cart
-
-{% hint style="info" %}
-This guide builds on the [Update Cart](update-cart.md) guide. It is recommended to follow that guide before starting this one.
-{% endhint %}
-
-This will teach you how to delete an item from the cart.
-
-Your view for the `cart.cshtml` page will be similar to the example below.
-
-```csharp
-@inherits UmbracoViewPage
-@{
- var store = Model.Value- @Html.Hidden($"orderLines[{item.Index}].Id", item.OrderLine.Id) - @item.OrderLine.Name @Html.Hidden($"orderLines[{item.Index}].Quantity", (int)item.OrderLine.Quantity, new { @type = "number" }) - @Html.Hidden($"orderLines[{item.Index}].ProductReference", item.OrderLine.ProductReference) - Remove Item -
- - } - - - - var success = TempData["SuccessMessage"]?.ToString(); - - if (!string.IsNullOrWhiteSpace(success)) - { -@success
- }
- }
-}
-```
-
-The code below allows the Umbraco `SurfaceAction` to call `RemoveFromCart` when the link is clicked. It will also pass the `OrderLineId`.
-
-```csharp
-Remove
-```
-
-## Adding the Controller
-
-For the button to work, you need to add some functionality via a Controller.
-
-Create a new Controller called `CartSurfaceController.cs`
-
-{% hint style="warning" %}
-
-The namespaces used in this Controller are important and need to be included.
-
-```cs
-using Microsoft.AspNetCore.Mvc;
-using Umbraco.Cms.Core.Cache;
-using Umbraco.Cms.Core.Logging;
-using Umbraco.Cms.Core.Models.PublishedContent;
-using Umbraco.Cms.Core.Routing;
-using Umbraco.Cms.Core.Services;
-using Umbraco.Cms.Core.Web;
-using Umbraco.Cms.Infrastructure.Persistence;
-using Umbraco.Cms.Web.Website.Controllers;
-using Umbraco.Commerce.Common.Validation;
-using Umbraco.Commerce.Core.Api;
-using Umbraco.Commerce.Core.Models;
-using Umbraco.Commerce.Extensions;
-using Umbraco.Extensions;
-```
-
-{% endhint %}
-
-```csharp
-public class CartSurfaceController : SurfaceController
-{
- public CartSurfaceController(IUmbracoContextAccessor umbracoContextAccessor,
- IUmbracoDatabaseFactory databaseFactory,
- ServiceContext services,
- AppCaches appCaches,
- IProfilingLogger profilingLogger,
- IPublishedUrlProvider publishedUrlProvider,
- IUmbracoCommerceApi commerceApi)
- : base(umbracoContextAccessor, databaseFactory, services, appCaches, profilingLogger, publishedUrlProvider)
- {
- _commerceApi = commerceApi;
- }
-}
-```
-
-The example below is the equivalent code for having this as a Primary Constructor:
-
-```csharp
-public class CartSurfaceController(IUmbracoContextAccessor umbracoContextAccessor,
- IUmbracoDatabaseFactory databaseFactory,
- ServiceContext services,
- AppCaches appCaches,
- IProfilingLogger profilingLogger,
- IPublishedUrlProvider publishedUrlProvider,
- IUmbracoCommerceApi commerceApi)
- : SurfaceController(umbracoContextAccessor, databaseFactory, services, appCaches, profilingLogger, publishedUrlProvider)
-{
-}
-```
-
-The `CartDto` is a class used to pass data to the Controller. In this instance, it passes over the `OrderLineId`.
-
-```csharp
- public class CartDto
- {
- public Guid OrderLineId { get; set; }
- }
-```
-
-You need to add the `Action` to delete the item from the cart. This will be called when the button is clicked.
-
-```csharp
-[HttpGet]
-public IActionResult RemoveFromCart(CartDto cart)
-{
- try
- {
- _commerceApi.Uow.Execute(uow =>
- {
- var store = CurrentPage?.Value| Migrate from Vendr to Umbraco Commerce | migrate-from-vendr-to-umbraco-commerce |
| Configure SQLite support | configure-sqlite-support.md |
| Add item to Cart | add-item.md |
| Update Cart | update-cart.md |
| Delete item from Cart | delete-item.md |
| Limit Order Line Quantity | limit-orderline-quantity.md |
| Use an alternative database for Umbraco Commerce tables | use-an-alternative-database-for-umbraco-commerce-tables.md |
- @Html.Hidden($"orderLines[{item.Index}].Id", item.OrderLine.Id) - @item.OrderLine.Name | @Html.TextBox($"orderLines[{item.Index}].Quantity", (int)item.OrderLine.Quantity, new { @type = "number" }) - @Html.Hidden($"orderLines[{item.Index}].ProductReference", item.OrderLine.ProductReference) - Remove -
- - } - - - - var success = TempData["SuccessMessage"]?.ToString(); - - if (!string.IsNullOrWhiteSpace(success)) - { -@success
- }
-}
-```
-
-You first loop through each item in the `cart/order` and display the product name and quantity.
-
-A hidden input is added for the order ID, quantity, and product reference. This is so you can update the cart with the new number.
-
-```csharp
- @Html.Hidden($"orderLines[{item.Index}].OrderId", item.OrderLine.Id)
-```
-
-The line below sets the ID of the order line (or the item in the current cart/order).
-
-```csharp
- @item.OrderLine.Name @Html.Hidden($"orderLines[{item.Index}].Quantity", (int)item.OrderLine.Quantity, new { @type = "number" })
-```
-
-As well as setting the product name, the line below sets the quantity of the product in the cart/order. Finally, the number is set to a number input type.
-
-```csharp
- @Html.Hidden($"orderLines[{item.Index}].ProductReference", item.OrderLine.ProductReference)
-```
-
-This is setting the product reference in the cart/order so there is a way to distinguish between products. This is hidden as it does not need to be displayed to the user.
-
-{% hint style="warning" %}
-
-The `remove` button is added here but is not covered in this guide. Learn more in the [Delete item from Cart](delete-item.md) article.
-
-{% endhint %}
-
-Finally, a button is added to submit the form to update the cart. This will call the `UpdateCart` action in the `CartSurfaceController` which will then show a success message to the user.
-
-## Adding the Controller
-
-Create a new Controller called `CartSurfaceController.cs`
-
-{% hint style="warning" %}
-
-The namespaces used in this Controller are important and need to be included.
-
-```cs
-using Microsoft.AspNetCore.Mvc;
-using Umbraco.Cms.Core.Cache;
-using Umbraco.Cms.Core.Logging;
-using Umbraco.Cms.Core.Models.PublishedContent;
-using Umbraco.Cms.Core.Routing;
-using Umbraco.Cms.Core.Services;
-using Umbraco.Cms.Core.Web;
-using Umbraco.Cms.Infrastructure.Persistence;
-using Umbraco.Cms.Web.Website.Controllers;
-using Umbraco.Commerce.Common.Validation;
-using Umbraco.Commerce.Core.Api;
-using Umbraco.Commerce.Core.Models;
-using Umbraco.Commerce.Extensions;
-using Umbraco.Extensions;
-```
-
-{% endhint %}
-
-```csharp
-public class CartSurfaceController : SurfaceController
-{
- public CartSurfaceController(IUmbracoContextAccessor umbracoContextAccessor,
- IUmbracoDatabaseFactory databaseFactory,
- ServiceContext services, AppCaches appCaches,
- IProfilingLogger profilingLogger,
- IPublishedUrlProvider publishedUrlProvider,
- IUmbracoCommerceApi commerceApi)
- : base(umbracoContextAccessor, databaseFactory, services, appCaches, profilingLogger, publishedUrlProvider)
- {
- _commerceApi = commerceApi;
- }
-}
-```
-
-The following is the equivalent code for having this as a Primary Constructor:
-
-```csharp
-public class CartSurfaceController(IUmbracoContextAccessor umbracoContextAccessor,
- IUmbracoDatabaseFactory databaseFactory,
- ServiceContext services, AppCaches appCaches,
- IProfilingLogger profilingLogger,
- IPublishedUrlProvider publishedUrlProvider,
- IUmbracoCommerceApi commerceApi)
- : SurfaceController(umbracoContextAccessor, databaseFactory, services, appCaches, profilingLogger, publishedUrlProvider)
-{
-}
-```
-
-The `CartDto` is a class that passes data to the Controller. This is a class that has a property for the `productReference` and an array of `OrderLineQuantityDto[]`.
-
-```csharp
- public class CartDto
- {
- public string ProductReference { get; set; }
- public OrderLineQuantityDto[] OrderLines { get; set; }
- }
-
- public class OrderLineQuantityDto
- {
- public Guid Id { get; set; }
- public decimal Quantity { get; set; }
- }
-```
-
-{% hint style="warning" %}
-The code example above adds the `ProductReference` but it is not used in this guide.
-
-It is an example of passing the product reference to the controller for similar tasks.
-{% endhint %}
-
-You need to add the `Action` to update the items in the cart. This will be called when the button is clicked.
-
-```csharp
-[HttpPost]
- public IActionResult UpdateCart(CartDto cart)
- {
- try
- {
- _commerceApi.Uow.Execute(uow =>
- {
- var store = CurrentPage?.Value| Umbraco Properties | Umbraco Commerce is based on Umbraco CMS, which means that some of the things you'll be working with are native to the core product. | umbraco-properties.md |
| Calculators | Learn more about the different calculators that Umbraco Commerce ships with and how you can customize and extend them. | calculators.md |
| Product Variants | With Umbraco Commerce you can create a large array of different product variants. Learn more about how this all works. | product-variants |
Variants editor table view
Product attributes
Product attributes values
Product attribute presets
Product attribute preset values
Create variants presets
Create variants attributes
Edit variant
Variant filtering
| Alias | -Type | -Description | -
|---|---|---|
store |
- Umbraco.Commerce.StorePicker | -- Often placed on the site root node, but can be placed on any node higher - than the product nodes themselves, this property links the website to a - specific Umbraco Commerce store configuration. - | -
productName |
- Textstring | -
- Optional product node property that allows you to define an explicit
- product name other than the product nodes .Name property,
- which will be used as fallback.
- |
-
sku |
- Textstring | -
- Product node property defining the unique SKU of the
- product.
- |
-
price |
- Umbraco.Commerce.Price | -Product node property defining the prices for the product. | -
stock |
- Umbraco.Commerce.Stock | -Product node property defining the stock level of the product. | -
image |
- Umbraco.MediaPicker3 | -Optional product node property defining an image for the given product. | -
measurements |
- Umbraco.Commerce.Measurements | -Optional (depending on the shipping configuration) node property defining physical dimensions and weight of the product. | -
taxClass |
- Umbraco.Commerce.StoreEntityPicker | -
- Optional product node property that allows you to define an explicit
- Tax Class for the product, should it differ from the stores
- default.
- |
-
isGiftCard |
- True/False | -- Optional product node property that defined whether the product node - should be considered a Gift Card product, in which case it triggers the - automatic generation of a Gift Card in the backoffice and emails it - directly to the customer on checkout. - | -
productSource |
- ContentPicker | -- Optional product node property allowing you to link a product to another - product outside of it's hierarchy to be used as it's source of product - information. - | -
-
-
-
-Session
- -When working with Umbraco Commerce's C# Api, Umbraco Commerce will normally keep track of a series of items for you. This could be the current Order ID or the current Language, which it tracks in a cookie. When working in a headless manner however we can no longer rely on cookies for this behavior. It becomes the implementor's responsibility to remember these items and pass them as Headers to the endpoints that need to use them for context. - -The following is a list of supported headers used for session management: - -* `Store` - The ID or Alias of the store the given operation is being performed against. -* `Current-Order` - The ID of any current "in-progress" order. -* `Customer-Reference` - A unique reference for the current customer. -* `Accept-Language` - The ISO Culture Code of the current front-end language. -* `Currency` - The ID or ISO Code of the current currency. If not supplied, will fall back to the default currency of the default country defined on the store. -* `Tax-Class` - The ID or Alias of the default tax class. If not supplied, will fall back to the default defined on the store. -* `Billing-Country` - The ID or ISO Code of the default billing country. If not supplied, falls back to the default country defined on the store. -* `Billing-Region` - The ID or ISO Code of the default billing region. -* `Shipping-Country` - The ID or ISO Code of the default shipping country. If not supplied, falls back to either the supplied billing country or the default country defined on the store. -* `Shipping-Region` - The ID or ISO Code of the default billing region. - -
-
-
-
-Expansion
- -**Expansion** allows you to retrive additional data about related entities in the API output for a given resource. - -By default, where a resource is connected with another resource, such as an Order holding a reference to it's Currency, the Storefront API will return those connected resources as "Reference" objects which usually only contain the resources ID and Alias/Code. - -```json -{ - "cartNumber": "CART-01280-054677-RP4L9", - "createDate": "2023-07-03T15:11:17.9220005", - "currency": { - "$type": "CurrencyRef", - "code": "GBP", - "id": "30b62176-6a9e-4a51-b2f0-7ce6c80a461a" - }, - "customerInfo": { ... }, - "discountCodes": [], - ... -} -``` - -Should you wish to retrieve the connected resource, you could perform an additional get operation against that resources own endpoint, however this could result in multiple wasteful network requests. To help with this, you can pass an `expand` query parameter with a path to properties you wish to expand, which for those targeted properties will return the full resource object instead of the reference entity. - -**Request** - -```http -GET /umbraco/commerce/storefront/api/v1/order/af697207-d370-4aee-824c-15711d43a9f2?expand=currency -``` - -**Response** - -```json -{ - "cartNumber": "CART-01280-054677-RP4L9", - "createDate": "2023-07-03T15:11:17.9220005", - "currency": { - "$type": "Currency", - "allowedCountries": [ - { - "country": { - "$type": "CountryRef", - "code": "GB", - "id": "af697207-d370-4aee-824c-15711d43a9f2" - } - } - ], - "code": "GBP", - "culture": "en-GB", - "id": "30b62176-6a9e-4a51-b2f0-7ce6c80a461a", - "name": "GBP" - }, - "customerInfo": { ... }, - "discountCodes": [], - ... -} -``` - -The `expand` query parameter can accept a comma seperated list of property keys to expand for properties at the same level, and can also expand nested objects using a `[...]` syntax. In the following example we retrieve a Country entity, expanding it's `defaultCurrency` and `defaultPaymentMethod` whilst at the same time expanding the `allowedCountries.country` properties within the `defaultCurrency`. - -```http -GET /umbraco/commerce/storefront/api/v1.0/country/GB?expand=defaultCurrency[allowedCountries[country]],defaultPaymentMethod -``` - -**Response** - -```json -{ - "code": "GB", - "defaultCurrency": { - "$type": "Currency", - "allowedCountries": [ - { - "country": { - "$type": "Country", - "code": "GB", - "defaultCurrency": { - "$type": "CurrencyRef", - "code": "GBP", - "id": "30b62176-6a9e-4a51-b2f0-7ce6c80a461a" - }, - "defaultPaymentMethod": { - "$type": "PaymentMethodRef", - "alias": "invoicing", - "id": "e35677ac-a544-45a0-ba4a-a78dd43dbaf2" - }, - "defaultShippingMethod": { - "$type": "ShippingMethodRef", - "alias": "pickup", - "id": "2ecb73ed-1b13-4ca4-8502-c1c4a8df533d" - }, - "id": "af697207-d370-4aee-824c-15711d43a9f2", - "name": "United Kingdom" - } - } - ], - "code": "GBP", - "culture": "en-GB", - "id": "30b62176-6a9e-4a51-b2f0-7ce6c80a461a", - "name": "GBP" - }, - "defaultPaymentMethod": { - "$type": "PaymentMethod", - "alias": "invoicing", - "id": "e35677ac-a544-45a0-ba4a-a78dd43dbaf2", - "imageUrl": "https://localhost:44313/media/k4apjvbo/logo.png", - "name": "Invoicing", - "sku": "4815" - }, - "defaultShippingMethod": { - "$type": "ShippingMethodRef", - "alias": "pickup", - "id": "2ecb73ed-1b13-4ca4-8502-c1c4a8df533d" - }, - "id": "af697207-d370-4aee-824c-15711d43a9f2", - "name": "United Kingdom" -} -``` - -#### Shortcuts - -As well as expanding explicit properties, the Storefront API supports shortcut expansion keys that when passed will expand all entities of a given type. Shortcut keys are idenfitied by a `$` prefix. There is currently only one supported shortcut key which is `$prices`. - -**$prices** - -Prices in Umbraco Commerce can contain a lot of meta data, such as listing applied discounts/adjustments and all values including or excluding those discounts. These are useful when displaying a full order breakdown, but when only needing to present an orders total value, are not necesarry. By default, the Storefront API will only return the final `value` property of a price object, but should you wish to receive this full pricing breakdown you can pass the `$prices` shortcut key to expand all price values to include this extra meta data. - -**Request** - -```http -GET /umbraco/commerce/storefront/api/v1/order/af697207-d370-4aee-824c-15711d43a9f2?expand=$prices -``` - -**Response** - -```json -{ - ... - "totalPrice": { - "previousAdjustments": { - "currency": { - "$type": "CurrencyRef", - "code": "GBP", - "id": "30b62176-6a9e-4a51-b2f0-7ce6c80a461a" - }, - "formatted": { - "tax": "-£0.45", - "withTax": "-£2.60", - "withoutTax": "-£2.15" - }, - "tax": -0.45, - "withTax": -2.60, - "withoutTax": -2.15 - }, - "totalAdjustment": { - "currency": { - "$type": "CurrencyRef", - "code": "GBP", - "id": "30b62176-6a9e-4a51-b2f0-7ce6c80a461a" - }, - "formatted": { - "tax": "-£0.45", - "withTax": "-£2.60", - "withoutTax": "-£2.15" - }, - "tax": -0.45, - "withTax": -2.60, - "withoutTax": -2.15 - }, - "value": { - "currency": { - "$type": "CurrencyRef", - "code": "GBP", - "id": "30b62176-6a9e-4a51-b2f0-7ce6c80a461a" - }, - "formatted": { - "tax": "£5.80", - "withTax": "£33.40", - "withoutTax": "£27.60" - }, - "tax": 5.80, - "withTax": 33.40, - "withoutTax": 27.60 - }, - "withPreviousAdjustments": { - "currency": { - "$type": "CurrencyRef", - "code": "GBP", - "id": "30b62176-6a9e-4a51-b2f0-7ce6c80a461a" - }, - "formatted": { - "tax": "£5.80", - "withTax": "£33.40", - "withoutTax": "£27.60" - }, - "tax": 5.80, - "withTax": 33.40, - "withoutTax": 27.60 - } - }, - ... -} -``` - -
-
-
-
-## Endpoints
-
-The Storefront API is broken down into a number of endpoints grouped by resource type. Select a resource type below to review the available endpoints.
-
-{% content-ref url="endpoints/order.md" %}
-[order.md](endpoints/order.md)
-{% endcontent-ref %}
-
-{% content-ref url="endpoints/checkout.md" %}
-[checkout.md](endpoints/checkout.md)
-{% endcontent-ref %}
-
-{% content-ref url="endpoints/product.md" %}
-[product.md](endpoints/product.md)
-{% endcontent-ref %}
-
-{% content-ref url="endpoints/customer.md" %}
-[customer.md](endpoints/customer.md)
-{% endcontent-ref %}
-
-{% content-ref url="endpoints/store.md" %}
-[store.md](endpoints/store.md)
-{% endcontent-ref %}
-
-{% content-ref url="endpoints/currency.md" %}
-[currency.md](endpoints/currency.md)
-{% endcontent-ref %}
-
-{% content-ref url="endpoints/country.md" %}
-[country.md](endpoints/country.md)
-{% endcontent-ref %}
-
-{% content-ref url="endpoints/payment-method.md" %}
-[payment-method.md](endpoints/payment-method.md)
-{% endcontent-ref %}
-
-{% content-ref url="endpoints/shipping-method.md" %}
-[shipping-method.md](endpoints/shipping-method.md)
-{% endcontent-ref %}
-
-{% content-ref url="endpoints/content.md" %}
-[content.md](endpoints/content.md)
-{% endcontent-ref %}
-
-## Swagger UI
-
-You can access a Swagger document for the Storefront API at `{yourdomain}/umbraco/swagger`, selecting `Umbraco Commerce Storefront API` from the definitions dropdown in the top right. From here you can see a full list of supported APIs, the parameters they accept and the expected payloads and responses.
-
-
-
-## Value Converters
-
-As Umbraco Commerce uses content nodes as products, the Storefront API comes with some replacement value converters that automatically extend the default value converter functionality to return Storefront entities when accessed through the Content Delivery API. You don't need to do anything to enable these.
-
-* **Store Picker** - Returns a Store "Reference" by default, or a complete Store response object if the store picker property is being expanded.
-* **Store Entity Picker** - Returns an entity "Reference" by default, or a complete entity response object if the store entity picker property is being expanded.
-* **Price** - Returns a price for the product based on session information passed through in headers. See the ["Session" concept detailed above](./#concepts).
-* **Stock** - Returns the stock level of the given product.
-* **Variants** - See notes on the [variants value converter](./#variants-value-converter) below.
-
-### Variants Value Converter
-
-To help with common scenarios when working with variants, the Variants value converter will return a series of data items used when building a relevant UI.
-
-```json
-{
- attributes: [
- {
- alias: "color",
- name: "Color",
- values: [
- {
- alias: "red",
- name: "Red"
- },
- {
- alias: "blue",
- name: "Blue"
- }
- ]
- },
- {
- alias: "size",
- name: "Size",
- values: [
- {
- alias: "md",
- name: "Medium"
- },
- {
- alias: "lg",
- name: "Large"
- }
- ]
- }
- ],
- items: [
- {
- attributes: {
- color: red,
- size: md
- },
- isDefault: true,
- content: { }
- },
- {
- attributes: {
- color: blue,
- size: lg
- },
- isDefault: false,
- content: { }
- }
- ],
- variantContentUrl: "https://{your_domain}/umbraco/delivery/api/v1/content/item/8df5c8bd-b524-4513-805a-c119fc8090e3/variant"
-}
-```
-
-* `attributes` will contain a list of "in use" attributes which means there is at least one variant content item that makes use of that attribute. These should be used to build the attribute options UI.
-* `items` returns a list of variant items. By default, this will return the attribute combinations, and whether it is the default combination but its content value will be empty. The content value can be populated by expanding the variants property through the Delivery API, however, it's important to know this could return a lot of data and be intensive. Instead, it is preferred to return the non-expanded value and use the `variantContentUrl` to fetch individual content items as they are requested. The `items` collection should also be used to check if a combination exists as whilst the root level `attributes` collection contains all in-use attributes, it doesn't mean every possible combination of those attributes exists so you can use the `items` collection to validate a combination.
-* `variantContentUrl` as the URL to a specialized Delivery API route that can return a single variant item content based on a passed-in attribute combination.
diff --git a/14/umbraco-commerce/reference/storefront-api/endpoints/README.md b/14/umbraco-commerce/reference/storefront-api/endpoints/README.md
deleted file mode 100644
index 97a1a9a3114..00000000000
--- a/14/umbraco-commerce/reference/storefront-api/endpoints/README.md
+++ /dev/null
@@ -1,43 +0,0 @@
-# Storefront API Endpoints
-
-The Storefront API is broken down into a number endpoints of grouped by resource type. Select a resource type below to review the available endpoints.
-
-{% content-ref url="order.md" %}
-[Order](order.md)
-{% endcontent-ref %}
-
-{% content-ref url="checkout.md" %}
-[Checkout](checkout.md)
-{% endcontent-ref %}
-
-{% content-ref url="product.md" %}
-[Product](product.md)
-{% endcontent-ref %}
-
-{% content-ref url="customer.md" %}
-[Customer](customer.md)
-{% endcontent-ref %}
-
-{% content-ref url="store.md" %}
-[Store](store.md)
-{% endcontent-ref %}
-
-{% content-ref url="currency.md" %}
-[Currency](currency.md)
-{% endcontent-ref %}
-
-{% content-ref url="country.md" %}
-[Country](country.md)
-{% endcontent-ref %}
-
-{% content-ref url="payment-method.md" %}
-[Payment Method](payment-method.md)
-{% endcontent-ref %}
-
-{% content-ref url="shipping-method.md" %}
-[Shipping Method](shipping-method.md)
-{% endcontent-ref %}
-
-{% content-ref url="content.md" %}
-[Content](content.md)
-{% endcontent-ref %}
\ No newline at end of file
diff --git a/14/umbraco-commerce/reference/storefront-api/endpoints/checkout.md b/14/umbraco-commerce/reference/storefront-api/endpoints/checkout.md
deleted file mode 100644
index 69320d69687..00000000000
--- a/14/umbraco-commerce/reference/storefront-api/endpoints/checkout.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# Checkout Endpoints
-
-The checkout endpoints provide ways of performing a checkout process against an Order. The Storefront API supports two ways of checking out an order, one using hosted checkout pages, and a more advanced option for inline payment processing.
-
-## Hosted
-
-With the hosted checkout flow it is required that before redirecting to the payment gateway a checkout token should be generated. This token is passed to the pay endpoint to ensure that only the given order can be processed in response to the checkout request. The pay endpoint should be launched in a WebView/iframe with this token which will redirect to the given Orders payment gateway for payment capture. To determine the outcome of the payment developers should monitor the WebView/iframes URL. They will be redirected to the same pay endpoint URL with either a `/completed`, `/canceled` or `/errored` suffix.
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/checkout/{orderId}/token" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/checkout/{orderId}/pay/{token}" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-## Inline
-
-With the inline checkout flow, it is left to the implementing developer to perform payment capture. Before a capture can begin, the order should be initialized using the `initialize` endpoint which prepares the Order for capture. The `initialize` endpoint will return the settings of the Orders selected payment method, along with details of expected metadata needed by the payment provider. Developers can use this data to perform an inline capture and call the `confirm` endpoint when the capture is successful, passing back any metadata captured.
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/checkout/{orderId}/initialize" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/checkout/{orderId}/confirm" method="post" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
\ No newline at end of file
diff --git a/14/umbraco-commerce/reference/storefront-api/endpoints/content.md b/14/umbraco-commerce/reference/storefront-api/endpoints/content.md
deleted file mode 100644
index 378f116863d..00000000000
--- a/14/umbraco-commerce/reference/storefront-api/endpoints/content.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# Content Endpoints
-
-The content endpoints provide additional endpoints to the Umbraco Content Delivery API to help with fetching product related content.
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/delivery/api/v1/content/item/{id}/variant" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
\ No newline at end of file
diff --git a/14/umbraco-commerce/reference/storefront-api/endpoints/country.md b/14/umbraco-commerce/reference/storefront-api/endpoints/country.md
deleted file mode 100644
index a808cd95bb7..00000000000
--- a/14/umbraco-commerce/reference/storefront-api/endpoints/country.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# Country Endpoints
-
-The Country API endpoints allow fetching supported countries and their allowed currencies, payment methods and shipping methods from a store.
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/countries" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/country/{idOrAlias}" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/country/{idOrAlias}/currencies" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/country/{idOrAlias}/paymentmethods" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/country/{idOrAlias}/shippingmethods" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/country/{countryIdOrAlias}/region/{regionIdOrAlias}/paymentmethods" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/country/{countryIdOrAlias}/region/{regionIdOrAlias}/paymentmethods" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
\ No newline at end of file
diff --git a/14/umbraco-commerce/reference/storefront-api/endpoints/currency.md b/14/umbraco-commerce/reference/storefront-api/endpoints/currency.md
deleted file mode 100644
index 81476377282..00000000000
--- a/14/umbraco-commerce/reference/storefront-api/endpoints/currency.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# Currency Endpoints
-
-The Currency API endpoints allow fetching supported currencies from a store.
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/currencies" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/currency/{idOrAlias}" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
\ No newline at end of file
diff --git a/14/umbraco-commerce/reference/storefront-api/endpoints/customer.md b/14/umbraco-commerce/reference/storefront-api/endpoints/customer.md
deleted file mode 100644
index f62eb46d2b9..00000000000
--- a/14/umbraco-commerce/reference/storefront-api/endpoints/customer.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# Customer Endpoints
-
-The Customer API endpoints allow fetching all orders associated with a customer.
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/customer/{customerReferenceOrEmail}/orders" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
\ No newline at end of file
diff --git a/14/umbraco-commerce/reference/storefront-api/endpoints/order.md b/14/umbraco-commerce/reference/storefront-api/endpoints/order.md
deleted file mode 100644
index 0ede104e2c8..00000000000
--- a/14/umbraco-commerce/reference/storefront-api/endpoints/order.md
+++ /dev/null
@@ -1,59 +0,0 @@
-# Order Endpoints
-
-The Order endpoints are where you will manage your carts/orders and perform cart management functionality. Some examples are adding items to the cart, or setting up billing and shipping details.
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/orders" method="post" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/order/{orderId}" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/order/{orderId}" method="patch" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/order/{orderId}" method="delete" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/order/{orderId}" method="post" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/order/{orderId}/items" method="patch" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/order/{orderId}/items" method="delete" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/order/{orderId}/item/{orderLineId}" method="patch" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/order/{orderId}/item/{orderLineId}" method="delete"%}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/order/{orderId}/bundle/{bundleId}" method="post" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/order/{orderId}/bundle/{bundleId}/items" method="patch" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/order/{orderId}/bundle/{bundleId}/items" method="delete" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/order/{orderId}/bundle/{bundleId}/item/{orderLineId}" method="patch" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/order/{orderId}/bundle/{bundleId}/item/{orderLineId}" method="delete" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
\ No newline at end of file
diff --git a/14/umbraco-commerce/reference/storefront-api/endpoints/payment-method.md b/14/umbraco-commerce/reference/storefront-api/endpoints/payment-method.md
deleted file mode 100644
index 3b35fff07c1..00000000000
--- a/14/umbraco-commerce/reference/storefront-api/endpoints/payment-method.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# Payment Method Endpoints
-
-The Payment Method API endpoints allow fetching supported payment methods from a store.
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/paymentmethods" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/paymentmethod/{idOrAlias}" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
\ No newline at end of file
diff --git a/14/umbraco-commerce/reference/storefront-api/endpoints/product.md b/14/umbraco-commerce/reference/storefront-api/endpoints/product.md
deleted file mode 100644
index 4505b5edac3..00000000000
--- a/14/umbraco-commerce/reference/storefront-api/endpoints/product.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# Product Endpoints
-
-The Product API endpoints allow fetching essential product related data such as pricing and stock levels.
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/products" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
\ No newline at end of file
diff --git a/14/umbraco-commerce/reference/storefront-api/endpoints/shipping-method.md b/14/umbraco-commerce/reference/storefront-api/endpoints/shipping-method.md
deleted file mode 100644
index b5375e9cc39..00000000000
--- a/14/umbraco-commerce/reference/storefront-api/endpoints/shipping-method.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# Shipping Method Endpoints
-
-The Shipping Method API endpoints allow fetching supported shipping methods from a store.
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/shippingmethods" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/shippingmethod/{idOrAlias}" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
\ No newline at end of file
diff --git a/14/umbraco-commerce/reference/storefront-api/endpoints/store.md b/14/umbraco-commerce/reference/storefront-api/endpoints/store.md
deleted file mode 100644
index a1c2aa879f3..00000000000
--- a/14/umbraco-commerce/reference/storefront-api/endpoints/store.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# Store Endpoints
-
-The Store API endpoints allow fetching supported store details.
-
-{% swagger src="../../../.gitbook/assets/storefront_swagger.json" path="/umbraco/commerce/storefront/api/v1/store/{idOrAlias}" method="get" %}
-[storefront_swagger.json](../../../.gitbook/assets/storefront_swagger.json)
-{% endswagger %}
\ No newline at end of file
diff --git a/14/umbraco-commerce/reference/stores/README.md b/14/umbraco-commerce/reference/stores/README.md
deleted file mode 100644
index 4131a1752ae..00000000000
--- a/14/umbraco-commerce/reference/stores/README.md
+++ /dev/null
@@ -1,83 +0,0 @@
----
-description: Information on Umbraco Commerce Stores
----
-
-# Stores
-
-Stores represent a single shop / commercial entity and contain all the settings a configuration specific to that particular store. They are the root entity from which all other Umbraco Commerce entities are connected. They are also able to be linked to content nodes to connect a store to a site.
-
-## Store Settings
-
-General settings for a store can be accessed via the UI by clicking on a store node in the `Settings > Commerce` section.
-
-### General
-
-| Name | Description |
-| -- | -- |
-| Base Currency | Defines the base currency a store operates in and for which all order values will be converted for the basis of reporting and analytics. |
-| Default Location | Defines the main location of the store and is used by shipping calculators to work out shipping rates. |
-| Default Country | Defines the default country of the store and is used to set the default payment/shipping country of newly created orders. |
-| Default Order Status | Defines the order status to assign newly created orders to. |
-| Error Order Status | Defines the order status to assign orders to when an error occurs during order processing. |
-| Measurement System | Defines whether to use a Metric or Imperial measurement system when capturing product measurement. |
-| Prices Include Tax | Defines whether all prices entered into the system are inclusive or exclusive of tax. |
-| Use Cookies | Defines whether cookies should be used for tracking a customer's current order, allowing them to last between browser sessions. |
-| Cookie Timeout | If using cookies, define the length of time in minutes the cookie should be persisted for. |
-
-### Notification Settings
-
-| Name | Description |
-| -- | -- |
-| Confirmation Email | Defines the email to send to customers when an order is successfully completed. |
-| Error Email | Defines the email to send to customers when an error occurs when completing their order. |
-
-### Order Settings
-
-| Name | Description |
-| -- | -- |
-| Cart Number Template | Defines a string formatting template to use when generating a Cart Number, eg: 'CART-{0}'. |
-| Order Number Template | Defines a string formatting template to use when generating an Order Number, eg: 'ORDER-{0}'. |
-| Order Rounding Method | Defines At what level in the order calculation process prices should be rounded. Can be either `Unit` where prices are rounded at the item level, `Line` where prices are rounded at the order line level after quantity multiplication or `Total` where prices are rounded at the order total level. |
-
-### Product Settings
-
-| Name | Description |
-| -- | -- |
-| Product Property Aliases | Defines a comma-separated list of property aliases to be copied to the order line when added to the cart. For more details, see the [Automatic Properties](../../key-concepts/properties.md#automatic-properties) section. |
-| Product Uniqueness Property Aliases | Defines a comma-separated list of property aliases to be used to define product uniqueness. For more details, see the [Product Uniqueness Properties](../../key-concepts/properties.md#product-uniqueness-properties) section. |
-
-### Gift Card Settings
-
-| Name | Description |
-| -- | -- |
-| Code Length | Defines the length of a gift card code when auto-generated. |
-| Code Template | Defines a string formatting template to use when auto-generating a gift card code, eg: 'GIFTCARD-{0}'. |
-| Valid For | Defines the number of days gift cards should be valid for by default. |
-| Gift Card Property Aliases | Defines a comma-separated list of property aliases to be copied to the gift card from the order line. |
-| Activation Method | Defines the method by which gift cards become active. Can be `Manual` where the store owner must manually active the gift card, `Automatic` where the gift card automatically becomes active after purchase or `Order Status` where the gift card becomes active when the purchase order moves into a specific order status. |
-| Activation Order Status | When the activation method is `Order Status`, it defines the order status that activates the gift card. |
-| Default Gift Card Email | Defines the email to be sent to customers if an order contains a gift card item. |
-
-## Store Configuration
-
-Further store configuration can be achieved by setting up different categories of configuration that can be accessed as child nodes to the store node.
-
-The available configuration options are:
-
-* **Locations** - Defines different locations for a store. See [Locations reference documentation](../locations/README.md) for more details.
-* **Order Statuses** - Defines the order statuses to be used by a store.
-* **Shipping Methods** - Defines the different shipping options available in the store. See [Shipping reference documentation](../shipping/README.md) for more details.
-* **Payment Methods** - Defines the different payment options available in the store.
-* **Countries** - Defines the different shipping countries supported by the store.
-* **Currencies** - Defines the different currencies accepted by the store.
-* **Taxes** - Defines the different rates supported by the store.
-* **Templating** - Defines the different email, print, and export templates available to the store.
-
-## Store Permissions
-
-When editing a store, the permissions app allows you to control who can access the store management interface. The options are:
-
-* **User Groups** - A set of toggles to allow/deny access to members of a particular user group.
-* **Users** - A set of toggles to allow/deny access to explicit individuals.
-
-In both cases, a positive access control will always override a deny control setting.
\ No newline at end of file
diff --git a/14/umbraco-commerce/reference/taxes/README.md b/14/umbraco-commerce/reference/taxes/README.md
deleted file mode 100644
index eca67862b71..00000000000
--- a/14/umbraco-commerce/reference/taxes/README.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-description: Tax calculation options in Umbraco Commerce.
----
-
-# Taxes
-
-Umbraco Commerce offers two different tax calculation method configurations for calculating an order's tax amounts.
-
-### [Fixed Tax Rates](./fixed-tax-rates.md)
-
-This option allows you to define a single fixed tax rate to apply for all products of the same type shipped to the same country. This option is useful for countries that have a fixed tax rate (the norm in EU countries).
-
-### [Calculated Tax Rates](./calculated-tax-rates.md)
-
-This option allows you to dynamically calculate the tax obligations of an order by using third-party calculation platforms. This complex option is useful for countries with different tax rates for different product types or regions within the country (the norm in the US).
diff --git a/14/umbraco-commerce/reference/taxes/calculated-tax-rates.md b/14/umbraco-commerce/reference/taxes/calculated-tax-rates.md
deleted file mode 100644
index 96144f6eb11..00000000000
--- a/14/umbraco-commerce/reference/taxes/calculated-tax-rates.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-description: Calculated Rate Taxes in Umbraco Commerce.
----
-
-# Calculated Tax Rates
-
-This option allows you to dynamically calculate the tax obligations of an order by using third-party calculation platforms. This complex option is useful for countries with different tax rates for different product types or regions within the country (the norm in the US).
-
-When using calculated rate taxes, taxes are calculated as a single price adjustment against the order total price and will not offer any breakdown.
-
-Calculated tax rates are configured using **Tax Calculation Methods**. A tax calculation method provides a connection to a third-party calculation service via a [Sales Tax Provider](../../key-concepts/sales-tax-providers.md). The sales tax provider passes the order details to the calculation service and returns the tax amount to be applied to the order.
-
-{% hint style="info" %}
-Before you can configure a tax calculation method, you will need to install at least one [sales tax provider](../../key-concepts/sales-tax-providers.md).
-
-A TaxJar example is provided on GitHub at [https://github.com/umbraco/Umbraco.Commerce.SalesTaxProviders.TaxJar](https://github.com/umbraco/Umbraco.Commerce.SalesTaxProviders.TaxJar)
-{% endhint %}
-
-## Tax Calculation Method Configuration
-
-1. Go to **Settings > Stores > {Your Store} > Taxes > Tax Calculation Methods**.
-
-
-
-2. Click on the **Create Tax Calculation Method** button.
-3. Choose a **Sales Tax Provider** from the list.
-
-
-
-4. Enter the **Tax Calculation Method Name** and **Alias**.
-5. Configure the **Tax Calculation Method** settings.
-
-
-
-6. Click **Save**.
-
-## Assigning a Tax Calculation Method
-
-Tax calculation methods are assigned to a **Country** entity. This allows you to define different tax calculation methods for different countries. The tax calculation method assigned to an order's shipping country will be used to calculate the tax amount for the order.
-
-
-
-## Providing Tax Codes
-
-When calculating taxes, you may need to provide product tax codes to the calculation service. Tax codes are used to identify the type of product being sold and used by the calculation service to determine the correct tax rate. To assign a tax code to a product, you can use a **Tax Class** with a code defined for the given country.
-
-
-
-See [Tax Classes Configuration](./fixed-tax-rates.md#tax-class-configuration) for more information on how to configure tax classes.
-
-## Prices Inclusive of Tax
-
-It is possible to configure a store to accept prices including tax. When using tax calculation methods it is not possible to enable this feature. A warning will show if you try to do so and a tax calculation method is already defined on a stores country.
-
-
diff --git a/14/umbraco-commerce/reference/taxes/fixed-tax-rates.md b/14/umbraco-commerce/reference/taxes/fixed-tax-rates.md
deleted file mode 100644
index 0e3e2261bb7..00000000000
--- a/14/umbraco-commerce/reference/taxes/fixed-tax-rates.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-description: Fixed Rate Taxes in Umbraco Commerce.
----
-
-# Fixed Tax Rates
-
-Fixed-rate taxes allow you to dynamically calculate the tax obligations of an order by using third-party calculation platforms. This complex option is useful for countries with different tax rates for different product types or regions within the country (the norm in the US).
-
-When using fixed-rate taxes, taxes will be calculated for each price object in the order.
-
-Fixed-rate taxes are defined using **Tax Classes**. A tax class is a classification for a specific type of product and can be configured to have different tax rates for different countries.
-
-## Tax Class Configuration
-
-1. Go to **Settings > Stores > {Your Store} > Taxes > Tax Classes**.
-
-
-
-3. Click on the **Create Tax Class** button.
-4. Enter the **Tax Class Name**, **Alias**, **Default Tax Rate** and optional **Default Tax Code**.
-
-
-
-5. Optionally, define any country-specific tax rates by toggling the checkbox in the **Country Tax Classes** for the country.
-
-
-
-6. Click the **Edit Tax Class** button to define the country-specific tax rate/tax code.
-
-
-
-7. Click **Save**.
-
-## Assigning a Tax Class
-
-There are two ways to assign a tax class to a product:
-
-### Store Default Tax Class
-
-In the store settings editor, set the **Default Tax Class** for the store. This will be the default tax class for all products in the store.
-
-
-
-### Product Tax Class
-
-In the product Document Type, define a **Store Entity Picker** property configured for the **Tax Class** entity type, with the property alias **taxClass**.
-In the products content editor, set the **Tax Class** for the product. This will override the store default tax class for the product.
-
-
diff --git a/14/umbraco-commerce/reference/telemetry.md b/14/umbraco-commerce/reference/telemetry.md
deleted file mode 100644
index 91cd6639cd2..00000000000
--- a/14/umbraco-commerce/reference/telemetry.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-description: Get started with Commerce telemetry.
----
-
-# Telemetry
-
-Commerce telemetry is connected directly to the CMS telemetry pipeline and runs with the [ReportSiteJob](https://github.com/umbraco/Umbraco-CMS/blob/v14/dev/src/Umbraco.Infrastructure/BackgroundJobs/Jobs/ReportSiteJob.cs).
-
-It pulls commerce data using a custom provider.
-
-## Captured data
-
-Through the custom provider, the Commerce telemetry pipeline captures the following data defined per store:
-
-* Store ID
-* Product Count
-* Order Count
-* Location Count
-* Country Count
-* Country Codes
-* Currency Count
-* Currency Codes
-* Payment Method Count
-* Payment Providers
-* Shipping Method Count
-* Shipping Providers
-* Shipping Method Types
-* Tax Calculation Method Count
-* Sales Tax Providers
-* Is Custom Product Adapter Used
-* Is Custom Product Calculator Used
-* Is Custom Order Line Calculator Used
-* Is Custom Payment Calculator Used
-* Is Custom Shipping Calculator Used
-* Is Storefront API Enabled
-
-## Settings
-
-Commerce telemetry reporting can be managed in the [Telemetry Data](https://docs.umbraco.com/umbraco-cms/fundamentals/backoffice/settings-dashboards#telemetry-data) dashboard.
diff --git a/14/umbraco-commerce/reference/umbraco-commerce-cms-startup/README.md b/14/umbraco-commerce/reference/umbraco-commerce-cms-startup/README.md
deleted file mode 100644
index 02c142d2964..00000000000
--- a/14/umbraco-commerce/reference/umbraco-commerce-cms-startup/README.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Umbraco.Commerce.Cms.Startup
-description: API reference for Umbraco.Commerce.Cms.Startup in Umbraco Commerce
----
-## Umbraco.Commerce.Cms.Startup assembly
-
-| Namespace |
-| --- |
-| [Umbraco.Commerce.Cms](umbraco-commerce-cms/README.md) |
-| [Umbraco.Commerce.Cms.Composing](umbraco-commerce-cms-composing/README.md) |
-| [Umbraco.Commerce.Cms.Events.Notification.Handlers](umbraco-commerce-cms-events-notification-handlers/README.md) |
-| [Umbraco.Commerce.Extensions](umbraco-commerce-extensions/README.md) |
-
-
diff --git a/14/umbraco-commerce/reference/umbraco-commerce-cms-startup/umbraco-commerce-cms-composing/README.md b/14/umbraco-commerce/reference/umbraco-commerce-cms-startup/umbraco-commerce-cms-composing/README.md
deleted file mode 100644
index 1d121f2d57a..00000000000
--- a/14/umbraco-commerce/reference/umbraco-commerce-cms-startup/umbraco-commerce-cms-composing/README.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Umbraco.Commerce.Cms.Composing
-description: API reference for Umbraco.Commerce.Cms.Composing in Umbraco Commerce
----
-## Umbraco.Commerce.Cms.Composing namespace
-
-| Public Type | Description |
-| --- | --- |
-| class [UmbracoCommerceAssemblyProvider](umbracocommerceassemblyprovider.md) | |
-
-
diff --git a/14/umbraco-commerce/reference/umbraco-commerce-cms-startup/umbraco-commerce-cms-composing/umbracocommerceassemblyprovider.md b/14/umbraco-commerce/reference/umbraco-commerce-cms-startup/umbraco-commerce-cms-composing/umbracocommerceassemblyprovider.md
deleted file mode 100644
index d1af065a390..00000000000
--- a/14/umbraco-commerce/reference/umbraco-commerce-cms-startup/umbraco-commerce-cms-composing/umbracocommerceassemblyprovider.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: UmbracoCommerceAssemblyProvider
-description: API reference for UmbracoCommerceAssemblyProvider in Umbraco Commerce
----
-## UmbracoCommerceAssemblyProvider
-
-```csharp
-public class UmbracoCommerceAssemblyProvider
-```
-
-**Namespace**
-* [Umbraco.Commerce.Cms.Composing](README.md)
-
-### Constructors
-
-#### UmbracoCommerceAssemblyProvider
-
-```csharp
-public UmbracoCommerceAssemblyProvider(ILoggerFactory loggerFactory)
-```
-
-
-### Properties
-
-#### Assemblies
-
-```csharp
-public IEnumerable