How a configurator can connect with Salesforce

CRM and salesAssessed per project

Salesforce is the CRM of larger sales teams. It usually holds not just the pipeline but price books, approvals and the reporting that production planning depends on.

What a configuration could hand over

In a larger team specifications are usually retyped by hand. The configurator holds them as structured data, so an opportunity can be created with line items priced by the rules already in Salesforce. How they map onto your objects and price books is verified while the solution is designed.

  • Lead

    A new customer could arrive as a Lead with contact details and a summary of the configuration, which the salesperson qualifies and converts the usual Salesforce way.

  • Account and Contact

    If you want enquiries as opportunities from the start, the connection could find or create the Account and Contact and add an Opportunity at the stage you choose.

  • Opportunity Products

    The parts of a configuration could be written as opportunity products through entries in the price book assigned to the opportunity.

  • Custom fields

    Dimensions, material and the 3D view link could go into custom fields on the Lead or Opportunity that your administrator sets up.

What we need to connect it

  1. Access would be set up through an OAuth 2.0 app in your org and an integration user with the API Enabled permission and rights to the objects it needs, nothing more.

  2. The API is on by default in Enterprise, Performance, Unlimited and Developer editions; Professional Edition needs it as a paid add-on.

  3. With your administrator we write down which configurator options correspond to which products and which price book.

  4. Development and testing would run in a sandbox, and the connection would move to your production org only after sign-off.

Worth deciding up front

  • Every opportunity product has to come from the opportunity’s price book and, with multiple currencies enabled, have an entry in the same currency. A missing price book entry would stop the line item from being saved.
  • If pricing in your org is governed by Salesforce rules such as discounts or approvals, you decide whether the configurator price is a starting point or the final figure.
  • Salesforce counts daily API calls by edition and number of licences; a normal flow of configurator enquiries uses little of that allowance.

Questions about this connection

Will it use our price book or the configurator’s price?

Either is possible. An opportunity product could carry the configurator’s price as its sales price, or only reference a product priced from your price book. This is decided while the solution is designed.

Professional needs API access as an add-on. Without it Salesforce rejects API calls, so we check this before any design work.

Before creating a record, the connection could look for an existing Lead or Contact by email. How duplicates are handled is set to match the rules already in your org.

Other integrations

Put Salesforce to work in your sales.

Tell us what you sell and how an enquiry is handled today. On the demo you will see the configurator, and we will go through which data could flow from it into your system.

treede is not an official partner or reseller of the systems named here. All names and marks belong to their owners. Integration options are verified during implementation against the system interface and version. Salesforce official site