Creating an Asset is most often automated, triggered by Order fulfillment or by an integration with a fulfillment or provisioning system. The manual create flow still matters for one-off Assets (free trials, NFR licenses, replacements) and for testing automation paths after changes.
- Open the Account or Contact
Most healthy orgs create Assets from the customer record they belong to, either Account or Contact, through the Assets related list. Starting from the customer record auto-populates AccountId or ContactId.
- Click New Asset
The New button on the Assets related list opens the create form. If your profile lacks Create on Asset, the button is hidden; service-cloud and field-service permission sets typically grant it.
- Pick a record type if prompted
Many orgs use record types to separate Hardware, Software, Subscription, and other Asset categories, each with its own page layout and required fields. Pick the one that matches the product.
- Fill the name and Product reference
Asset Name is required. Most orgs also require Product2Id (the Product the Asset is an instance of), which drives reporting, entitlements, and Field Service work-order routing.
- Set Status, Install Date, and Serial Number
Status drives lifecycle reporting. Install Date drives warranty and renewal calculations. SerialNumber is required for any Asset that needs to be uniquely identified in the field.
- Connect to parent or related Assets if applicable
For complex installations, set ParentAssetId or create AssetRelationship records as part of the same workflow. The hierarchy needs to be set at create time, not as an afterthought.
- Save
Click Save. If your org runs Field Service, automation may fire here to associate the Asset with a service territory and dispatch queue.
Required. The display name that shows up in reports and related lists.
- Asset and Order are different objects. An Order describes the transactional commitment; an Asset describes the customer-owned thing that results from fulfillment. Build the Order-to-Asset creation flow explicitly; do not assume they sync automatically.
- Asset Hierarchy must be enabled in Setup before the UI renders the parent-child tree. Without enablement, you can store the relationships but the tree view does not appear.
- Asset-level Entitlements override Account-level Entitlements on Case SLA calculations. If your support tiers vary by product, configure Asset-level explicitly.
- Status changes to Inactive or Retired do not automatically cancel scheduled Service Appointments. Build a Flow or trigger to clean up future work orders when an Asset is retired.