I'm looking for quick feedback on why people choose to use or not use default contracts, and orders objects as part of their implementation.
If you are using contracts and/or orders object, please post back with the following:
- Any integration with external CPQ apps, if so, which one
- Top requirements for enhancement
If you have chosen not to user contracts and/or orders in an implementation please post back with the following:
- Key reason for not using default contracts/orders objects
- Alternate design used: custom objects or solely rely on external apps for these functions
@Annie Gibbons You are right, all three have their own line items with Products. Salesforce CPQ (and any other CPQ) will sync the Quote Lines to the Opportunity Lines. Salesforce CPQ also handles creating native Orders with Order Lines from the Opp/Quote. You can have it split the Quote into multiple Orders based on some Line attribute (like Family, or Type), or just make one monolithic Order.
For a custom Order object or another CPQ app, you can fill the gap with Flow or APEX. Because you will need to lookup the lines and iterate over them, Process Builder is not an option (yet).
Salesforce CPQ (and Billing) have done a good job of making the native Order object more relevant and connected to the sales process. Now, that's kind of the nexus of Sales Cloud, CPQ, and Billing. And it's the right place to focus integrations with ERP. We are starting to do that with clients now, ensuring that the resulting Orders in Salesforce are 1-to-1 with the Sales Order in a target ERP system. With Orders finally becoming available in LEX and Lightning Communities, things are looking up!
