Most Installed Product records are created automatically by order fulfillment, which is the recommended path. You can also create one directly in an Industries org for data correction, migration, or a one-off, as long as the object is part of your cloud's data model.
- Confirm the object is enabled
Check that your org uses the Industries Common Data Model and that Installed Product is part of your cloud (Communications, Media, or Energy and Utilities). If your processes run on Field Service instead, use the Asset object rather than Installed Product.
- Open the record creation flow
From the Installed Products tab or related list on an Account, choose New. In most implementations you will reach this through an order or provisioning flow rather than a raw New button, so prefer the order path when one exists.
- Set the account, product, and location
Link the record to the owning Account, the catalog Product or product offering it represents, and the place or service point where it operates. These three links are what make the record useful for service and billing.
- Set status and lifecycle dates
Set the status to match reality, usually Active for a live service, and fill the activation date. If the record is part of a bundle, set its parent so the hierarchy is correct.
- Save and verify against the order
Save, then confirm the record matches the source order. Mismatches between Installed Product and the order that created it are the usual source of reporting errors.
The customer that owns the installed product. This is the anchor for the customer view and for billing context.
The catalog item the installed product is an instance of, linking the live service back to what was sold.
The lifecycle state, such as Active, Suspended, or Disconnected, which drives billing and operational reports.
The place where the product operates, which lets the business answer location-specific service questions.
- Do not key in Installed Products by hand when an order process exists. Manual records drift from the order data that fulfillment is supposed to write.
- Confirm whether your cloud uses Installed Product or Asset before modeling. Field Service is built on Asset, while Communications and Energy and Utilities are built on Installed Product.
- Set the parent link for bundle components. A flat set of records loses the ability to suspend or report on a bundle as one unit.
- Match status to the real service state. A record left Active after a disconnect keeps billing context wrong and pollutes churn reporting.