eCommerce Policies

eCommerce Polices define the network capabilities of plans and entitlement policies you offer through your catalog. There are 2 types of eCommerce polices:

• Service policies are used to define the service definition of plans. Service policies contain components that combine filters and policy events. Depending on your integration requirements, service policies may require bucket IDs or rating groups attached to them for network enforcement.
• Entitlement policies are used to provide functionality. Entitlement policies are associated with entitlement codes and can contain one or more components.

Both service policies and entitlement policies can be either voice, messaging, or data.

The eCommerce Policies page lists the following details for each feature:

• eCommerce Policy Name
• Created Date
• Created By
• Status (Draft, Testing, Published)

eCommerce Policy Statuses

eCommerce policies have three statuses, or modes, that define a workflow that ends with them being available to be added to products: Draft, Testing, and Published. eCommerce policies are in Draft mode when you first create them and configure them. Once you have configured those policies, you add testing subscribers, either individually or through subscriber groups. Then move the eCommerce policy to Testing mode, where the eCommerce policy is pushed to the defined, limited set of embedded-client devices, the subscribers you added, so you can test and validate the eCommerce policy definition. When you are satisfied that the eCommerce policy accomplishes your goal through testing, you move it to Published mode, and the eCommerce policy is made available to the policy list in products.

When eCommerce Policies are in Testing or Published mode, the subscriber records on the Customer Support page reflect the policies that embedded-client devices have received.