# Order Form terms and definitions

Definitions of terms that appear in commercetools Order Forms and are applicable to the use of the Service.

## General

### Purchase Order

In case a Customer's Purchase Order (PO) is required to issue an invoice, the Customer will provide such PO within five business days after the Order Form Effective Date. In case of any delay in providing such PO and after a written reminder notice to Customer, commercetools reserves the right to suspend Customer´s access to the Service under the Order Form for the time until such PO is provided.

## B2C/B2B/B2X Commerce, B2C/B2B/B2X Core Commerce, Product Catalog

B2C Commerce and B2B Commerce were previously named "Composable Commerce for B2C" and "Composable Commerce for B2B" respectively.

### Order

An [Order](https://docs.commercetools.com/api/projects/orders.md) is created through the Customer's commerce solution, regardless of any further change of the status or event (for example, before any cancellations or returns). Usually, an Order is created from a Cart after a checkout process is completed. Orders can be imported by a Customer; for example, in the case of historical orders.

### SKU

A [Product Variant](https://docs.commercetools.com/api/projects/products.md#productvariant) is counted as an SKU (Stock Keeping Unit).

### B2B Commerce

(formerly "Composable Commerce for B2B")

Functionalities annotated with a B2B label on the respective pages are subject to additional or different terms and pricing. For example, those are included if B2B use is specified in the Order Form as an Add-On, or if "B2B Commerce" or "Composable Commerce for B2B" is agreed upon as a whole.

### Project

A [Project](https://docs.commercetools.com/api/projects/project.md) is a set of data and store configuration settings and can be used either for production purposes, such as a production project, or non-production purposes, such as a development project or staging project.

### Redundant hosting

Every instance ([Region](https://docs.commercetools.com/api/general-concepts.md#regions)) uses a multi-zone setup in which all data points created by the Customer or commercetools are stored at a minimum in three locations that are physically separated from each other.

## Frontend

### Site admin

A user with direct access to Netlify's console for domain and site management.

### Bandwidth

The amount of data transfer used (in bytes) across your domains and data layers in Netlify Connect.

### Edge Functions

JavaScript runtime invocations.

## Related pages

- [Section overview page](https://docs.commercetools.com/offering.md)