I. Business Use Case Examples

• As a core sales unit, product management must precede sales initiatives. The batch import feature allows rapid creation of product information in CRM, including product categories, pricing, and specifications.

  • For sellable products, set them to Active status. For discontinued products, set them to Inactive.

  • For active products, users can quickly add them to Sales Orders via barcode scanning. Sales prices can be adjusted during order placement with applicable discounts.

• Serving as a centralized product repository, Product Management ensures clean, unified data for daily employee reference. Managers can analyze sales and return trends in Reports to inform production decisions.

II. Product Feature Details

2.1 Default Product Scenarios

• All Products:

  • Records where the owner is the current user or their subordinates

  • Or records where the Related Teams include the current user or their subordinates

  • Or records under departments managed by users with Order Management or Order Finance Roles (e.g., User A with “Order Finance” Role can view all products owned by Dept. B if they approve orders submitted by Dept. B).

  • Or records shared via “Data Permission Management” rules where ownership or department-based sharing applies to the current user, their department, or user group

  • Or records under “My Responsible Departments”.

• Active Products: Records with “Active” status

• Inactive Products: Records with “Inactive” status

• My Responsibilities: Records owned by the current user

• Participated by Me: Records where Related Teams include the current user

• Responsible by My Subordinates: Records owned by the current user’s subordinates

• Participated by My Subordinates: Records where Related Teams include the current user’s subordinates

• Shared With Me: Records shared via “Data Permission Management” rules (ownership or department-based sharing)

• My Responsible Departments:

  • Current user is the head of their primary department

  • And the record’s Related Teams include this department

  • Note: Visibility of subordinate department data depends on “CRM Settings > Rules > Basic Settings > Superior Data Access Scope”.

Notes:
- “CRM Administrators” can view all records.
- Only “CRM Administrators” can view records with “Voided” status.

2.2 Product Operations

2.2.1 Creating Products

• Methods:

  • Manual creation:

    • Entry points:

      • [Products] list page

      • [Products] tab under related [Account] details

      • [Products] tab under related [Opportunity] details

      • [Products] tab under related [Product] details

      • [Products] tab under related [Visit] details

  • Reuse from existing Sales Orders (via order details)

  • Import (see Import Guide)

• Specification Configuration:

  • For products with specifications (e.g., a phone with “Storage” [16GB/64GB/128GB] and “Color” [White/Silver]), define specifications and values during creation as shown below:

picture coming soon:

Note: Configured specifications auto-populate in product names and cannot be modified.

2.2.2 Activating Products

• Only Active products can be sold (selectable in Sales Orders or Return Orders).

• Users can batch-select products and set them to “Active”.

2.2.3 Deactivating Products

• Discontinued products should be deactivated (“Inactive” products cannot be selected for Sales/Return Orders).

• Users can batch deactivate products. Only inactive products can be voided.

2.3 Common Operations

• List page actions: See List Operations

• Adding sales records: See Sales Records

• Core operations (reassign owner, add team members, print, import/export, edit, void, delete): See Common Operations

• Collaboration tools (forward, Calendar, reminders, calls, emails): See Common Operations