--- schema_version: "1" id: 055d17d3cd86433dbe552d3e6a899ebe81a9dbc8b888db20632877728b13a14c title: Set Up Point of Sale External Client App for Salesforce Core CRM Connector collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/commerce/264-0-0/rt_adv_config_sf_int_sfsc_connector_eca.md canonical_url: https://help.salesforce.com/s/articleView?id=commerce.rt_adv_config_sf_int_sfsc_connector_eca.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: ff406b9b942a0086c2d8c3d27b4d113d043287672fbafd89e638248bb16986cf description: Use REST APIs to integrate POS with the Salesforce Core CRM Connector for clienteling purposes. As of Spring '26, new merchants must create an External Client App instead of a Connected App. products: - Commerce release: "264" --- # Set Up Point of Sale External Client App for Salesforce Core CRM Connector Use REST APIs to integrate POS with the Salesforce Core CRM Connector for clienteling purposes. As of Spring '26, new merchants must create an External Client App instead of a Connected App. Customer must have a Salesforce Core product that has access to Person Account objects. This object is available with core products, including but not limited to Service, Sales, Field Service, Order Management, and other industry clouds. Work with your Salesforce Account Executive to confirm your access to the right supporting Salesforce Product to use as your POS CRM source. Refer to [POS Access List - URLs and IP Addresses](https://help.salesforce.com/s/articleView?id=commerce.rt_adv_config_3p_int_erp_pos_access_list.htm&release=264.0.0&type=5 "To enable POS and cloud services to interact with external, third-party services, allowlist specific URLs and IP addresses within the merchant's firewall. Ensure necessary communication for Adyen Payments, Elavon Payments, and other connectors by allowlisting URLs configured on CMS and product or order systems. The in-store IT team handles store firewall and POS app URLs, while the corporate IT team manages backend outbound NAT gateway IPs for connectors.") for a list of URLs and IP addresses to be allowlisted. This is to turn on the necessary communication. Turn on the Person Accounts feature in your Salesforce environment. Point of Sale's API connectors use queries for "Person Account" account types. It won't function if not turned on. ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/images/icon_important.png) Important As of Spring '26, new connected apps can no longer be created. New merchants must create an External Client App instead. If you already have a connected app, you can continue using it. See [Set Up Point of Sale Connector for Salesforce Core CRM Connector](https://help.salesforce.com/s/articleView?id=commerce.rt_adv_config_sf_int_sfsc_connector.htm&release=264.0.0&type=5 "Use REST APIs to integrate POS with the Salesforce Core CRM Connector for clienteling purposes. Create a Salesforce Connected App in Salesforce for Point of Sale to access the requisite APIs. The primary objects of interaction are Accounts and Notes. POS provides capabilities like search, create, and update for customer accounts that are maintained in Salesforce Core CRM.") for instructions on using existing connected apps. 1. Create an External Client App in your Salesforce org. Follow the steps in [Set Up an External Client App for Service](https://help.salesforce.com/s/articleView?id=commerce.rt_adv_config_sf_int_eca.htm&release=264.0.0&type=5 "Create an External Client App (ECA) to provide Point of Sale access to Salesforce APIs for clienteling purposes. As of Spring '26, new merchants must use External Client Apps instead of Connected Apps.") to create the External Client App with client credentials flow enabled. 2. After creating the External Client App, obtain the following credentials from Salesforce: - Consumer Key (Client ID) - Consumer Secret - My Domain URL (for example, `https://mycompany.my.salesforce.com` for production or `https://mycompany.sandbox.my.salesforce.com` for sandbox) - API Version (for example, v51.0) ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/images/icon_important.png) Important External Client Apps do NOT support generic login endpoints (`login.salesforce.com` or `test.salesforce.com`). You must use your My Domain URL. 3. In CMS, go to **Store Management** | **Store Settings** | **System** | **Rollout** and set **Salesforce App Type** to `EXTERNAL_CLIENT_APP`. 4. Update your CRM or OMS settings with your External Client App credentials. ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/images/icon_important.png) Important When configuring for External Client App: - For **URL base**, use your Salesforce My Domain URL (`https://.my.salesforce.com` for production or `https://.sandbox.my.salesforce.com` for sandbox). Do NOT use generic login endpoints (`login.salesforce.com` or `test.salesforce.com`). - Leave **Username** and **Password** fields blank (not required for client credentials flow). - For **Client ID**, enter the Consumer Key from your External Client App. - For **Client Secret**, enter the Consumer Secret from your External Client App. 5. Click **SAVE**. ![OAuth Token Endpoint](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/images/icon_example.png) OAuth Token Endpoint Point of Sale uses the following endpoints to obtain access tokens: - **Production:** `https://.my.salesforce.com/services/oauth2/token` - **Sandbox/Dev:** `https://.sandbox.my.salesforce.com/services/oauth2/token` ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/images/icon_important.png) Important External Client Apps do NOT support generic login endpoints (`login.salesforce.com` or `test.salesforce.com`). Always use your My Domain URL. After completing this setup, you can configure Customer 360 in CMS to use Service as a data source. See [Configure Customer 360 Clienteling for Point of Sale](https://help.salesforce.com/s/articleView?id=commerce.rt_pos_clienteling_customer_360_config.htm&release=264.0.0&type=5 "Configure the connector or service that powers each Customer 360 area in the POS app, giving store associates a unified view of customer data from Commerce or Service. The configured connector or service applies only to the Customer Profile, Address, and Wish List flows."). ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/images/icon_note.png) Note Using SFCC as a CRM with SFOM for orders may cause issues because their customer identifiers don't align. SFCC's customer ID isn't available in SFOM, but the Salesforce Core CRM customer ID is visible in SFOM.