During the High-Level Design (HLD) phase of a Communications Cloud implementation, Salesforce strongly recommends performing a storage assessment to ensure that data storage, file storage, and archival processes align with expected volumes. Public Salesforce architecture and data management guidance outlines three key tasks:

(A) Identify storage needs between data storage and file storage

Salesforce divides storage into Data Storage (records such as Accounts, Orders, Order Items, Subscriptions, Assets) and File Storage (documents, attachments, proofs, device images). A consultant must distinguish which objects consume which category because each impacts licensing and cost differently.

(D) Assess archiving strategy

Salesforce recommends establishing an archiving plan early to manage growth of high-volume objects (Orders, Order Items, Fulfillment Requests, Assets). Communications Cloud generates large order orchestration records, so storage must account for how data will be archived, purged, or externalized . This directly reduces storage consumption and improves performance.

(E) Calculate storage based on expected volumes and file requirements

Using volume estimates from HLD (records per month, attachment sizes, expected number of orders, subscriptions, assets), the consultant can calculate projected consumption for both data and file storage. This is standard planning guidance for Communications Cloud projects.

Options B and C are not part of Salesforce’s required steps for determining org storage needs. Analyzing legacy storage (B) is helpful but not required for Salesforce storage estimation. Considering an external storage system (C) is optional and not part of Salesforce’s recommended baseline steps.

This approach allows Field Reps to specifically assess and record the KPI related to the functionality of the Computer Display Unit and its effectiveness in assisting customers with backpack fitting.

In Communications Cloud, during a MACD (Modify/Add/Change/Disconnect) order, Order Management must determine which service plan the customer currently has . For asset-based ordering, Salesforce stores the current state of a service in the Inventory Items object. This includes all attribute values associated with the existing commercial product instance.

Because the commercial product is modeled with a plan attribute (Basic, Standard, Premium), the active value is part of the customer ' s Inventory Item record.

During MACD decomposition, Order Management retrieves the current state of the service—including all attribute values—from the Inventory Item. This allows the orchestration plan to compare:

“Existing value” (from Inventory Items) vs.

“New value” (from the Change Order)

This is core to Salesforce’s “ Inventory-Driven MACD ” design.

Option A is incorrect because the Change Order only stores the new values—Order Management must pull the existing value from Inventory.

Option C (custom objects) is unnecessary and not recommended.

Option D (callout to downstream system) defeats the purpose of asset-based ordering and introduces latency.

Action plan templates can have multiple planogram, inventory and promotion checks, which are predefined tasks that can be assigned to field reps to perform during their store visits. These tasks help to ensure compliance and optimize product placement and availability. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 26-27.

Assetization is the process in Salesforce Industries (Communications/Consumer Goods) where a successfully fulfilled order line item is converted into a permanent Asset record. This Asset record serves as the single source of truth for what the customer currently owns.

A Consultant should recommend assetization for a commercial product or service when it is likely to be involved in future customer management and transactions. The three main factors that necessitate creating an Asset record are:

The product/service sold has a recurring charge (B):

A recurring charge means the service/product will be billed repeatedly (e.g., monthly). To ensure the billing system receives the correct information and to manage any future pricing changes (like applying a promotional discount for a specific period), the service must exist as a persistent Asset record. Billing systems typically interface with the Asset/Subscription object to determine what to invoice each cycle.

The product/service sold can undergo future attribute changes (C):

The core purpose of the Move, Add, Change, Delete (MACD) process is to allow customers to modify their existing services. If a product attribute (e.g., Internet speed, color of a device, service plan) can be changed, the system needs an Asset record to track the current attribute values (the " As-Is " state). When a customer initiates a change, the system converts this Asset ' s current state into an order line item for modification.

The product/service sold will have child features added in the future (A):

Products that are part of a bundle or have a hierarchical structure (Parent $\rightarrow$ Child) must be tracked as Assets so that their children or sub-features can be managed, added, or removed later. For example, if a base service (Asset) allows for the addition of premium channels (new Assets), the base service must first exist as an Asset to act as the parent for the new features.

Why D and E are incorrect:

D (High-volume, one-time billing event, such as a pay-per-view): One-time, high-volume transactional items (like PPV events or movie rentals) are typically not assetized . They are billed once and retired. Creating millions of short-lived asset records would rapidly consume storage and severely degrade system performance.

E (Device accessory, such as a phone case): Simple, one-time purchase equipment without a service component (like a phone case or charger) is rarely assetized, as it has no recurring charge (B) and generally does not undergo MACD changes (C).

These components provide comprehensive information about promotions and inventory, vital for effective retail execution.

The Promotion object is directly associated with the Promotion Channel, which links promotional activities to specific channels and locations for execution.

To visualize store visits in their territory for the day by their current status, an Account Manager can create a map layer using visits as the base object and color code the markers by status. A map layer is a visual representation of data on a map that can be filtered and customized. A visit is an object that represents a scheduled or unscheduled interaction between a field rep and a retail store. The status of a visit indicates whether it is planned, in progress, completed, or canceled. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 34.

Promotions are linked to Retail Stores through Promotion Channel records, which define the connection and details of the promotional activities.