> ## Documentation Index > Fetch the complete documentation index at: https://docs.m1amdocs.com/llms.txt > Use this file to discover all available pages before exploring further. # Products Products are created and managed by Merchant organizations. Products are Merchants' services or what the customer receives. Examples of products include streaming services, online software products, cloud services, and applications. **Note:** The packaging of a product with pricing, promotional discounts, and recurrence terms, is done separately in a subscription management system. ## Product Details | Field Name | Description | | - | - | | **Status** | The status of the product. For example: **Published**. | | **Product Group** | The product group the product belongs to. | | **Product Code** | The product code. | | **Agreement** | The agreement the product is attached to. | | **Product Lifecycle** | The **Product Lifecycle** for a product can be one of the following:- **Platform-managed**: The Reseller (Service Provider) resells Merchant services through their own digital store. The Reseller manages the lifecycle of customer subscriptions through Partner Ecosystem Management. - **Merchant-managed**: The Merchant uses the Reseller's (Service Provider's) billing as a payment option. The Merchant sell services to customers from their own store. | | **Target Market** | The industry in which the Merchant is selling the product. | | **Entitlement Type** | The **Entitlement Type** for a product can be either:- **Standard**: customers can buy a single entitlement to the Merchant's product. - **Quantity** (Platform-managed only): this type enables purchasing a number (quantity) for the product subscription entitlement. During product provisioning for the customer, you must provide a quantity (for example, license seats). This entitlement type also supports the ability to update the quantity in subscription entitlements at a later date. | | **Product Type** | The type of product. For example: **Over the Top Service**. | | **Countries of Sale** | The countries in which the product can be sold. | | **Documents** | Official product documents the Merchant has uploaded to provide potential customers with legal, regulatory, and other product information on your storefront. | | **Tags** | Search terms the Merchant has added that can help customers find the product on your storefront. | | **Informational Features** | Descriptions of what the customer will receive from the product. This information conveys the benefits of the product to customers. | | **Customer Attributes** | Merchants can create required or optional customer attributes for their products. Customer attributes allow Merchants to inform Resellers (Service Providers) what fields are required or optional to pass from the Reseller's ordering system to Partner Ecosystem Management when provisioning the product for a customer. For example, a Merchant could provide **Mobile Identifier** (name) and **MSISDN** (value) as a required customer attribute. This attribute would require the customer's MSISDN be provided when provisioning the customer's subscription. The Reseller's ordering system would pass the MSISDN to Partner Ecosystem Management in the provisioning process. Optionally, you could store the value in Partner Ecosystem Management for future use. **Note:** To view customer attributes, navigate to the **Discover** space and then select a Merchant. After the Merchant's profile appears, select the **Products** tab. Select a product. The product page appears. Any customer attributes associated with the product are visible here. If you have partnerships, you can also view customer attributes and other product information in the **Partnerships** and **Agreements** spaces. | ## Customer Attribute Flow The customer attribute flow, from the creation of the attribute to the activation of a subscription, is as follows: 1. The Merchant creates the required and optional customer attributes for a product. 2. The Reseller (Service Provider) creates an agreement for the product. The Reseller indicates if they want to store any of the customer attributes for future use (in the allowlist). 3. The Merchant approves the agreement, and the product information is published to the external catalog. 4. Partner Ecosystem Management sends the product specification along with the required and optional customer attributes to the Reseller's external catalog through a webhook event. The catalog then provides the attributes to the ordering system. 5. When a customer purchases a subscription, the Reseller's ordering system sends the required customer attribute values. Optional customer attribute values can be sent as desired. Any attributes that were previously added to the allowlist will be stored. 6. Partner Ecosystem Management sends the customer attribute values to the Merchant. 7. The customer activates the subscription with the Merchant. **Parent topic:**[Discover](discoverAbout) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.