Newer Version Available
Channel Order App Objects
| Object | Description |
|---|---|
| Customer |
Contains information about a customer who’s purchased your product. For example, the name of the company and its billing address. |
| Partner Product Catalog |
Contains information about a product in your catalog. For example, the product’s revenue share model. Salesforce Partner Operations configures the products in your catalog and you import them to your org during setup. Unless permitted by your agreement with Salesforce, you can’t edit product details. |
| Partner Contract Terms |
Contains information about the contract terms for a product in your catalog. For example, the length of the contract and how often the customer is billed. Salesforce Partner Operations configures contract terms and you import them to your org during setup. Unless permitted by your agreement with Salesforce, you can’t edit contract term details. |
| Service Order |
Contains information about an order you’re submitting to Salesforce. For example, the type of order and the date the service starts. |
| Service Order Detail |
Represents an instance of a product in an order. When you add a product to an order, the COA creates an underlying service order detail record. You can’t access service order details directly. To view service order detail data, open the corresponding service order. |
To better understand how these objects fit together, let’s look at an example.
- On the Service Orders tab in the COA, create an order.
- Add details about the customer, like the billing address. The COA uses these details to create a customer record that you can reference in future orders.
- Specify a contract type. The COA looks up the corresponding partner contract terms record and associates it with the order.
- Specify a product from your catalog to activate, along with pricing and license details. The COA adds these details to a service order detail record and associates it with the order.
- Select a start date, review the order, and submit it to Salesforce for activation.
In this process, you created only two object records: one for the customer and another for the service order. The COA creates the other records as needed.