Connecting Boutique DX to Salesforce

Integrations · 2026-07-11

Your CRM is the maison's system of record. Your boutiques are where the information actually appears: a first visit, a booking, a client who just connected on LINE. The Boutique DX Salesforce integration closes that gap — what happens in the boutique shows up in Salesforce automatically, without an advisor ever re-typing a client's details.

What the integration does

Boutique DX creates and updates Salesforce Contacts as clients register and interact at your boutiques:

• A client registers at the door, books an appointment, or connects via LINE — Boutique DX matches them to an existing Contact by email or phone number, or creates a new one.
• If the client has a linked LINE account, their LINE User ID is written to the Contact, so your CRM knows which clients are reachable for LINE clienteling.
• Updates flow continuously in the background. No CSV exports, no end-of-week reconciliation.

Your marketing and clienteling teams keep working in Salesforce; your boutique teams keep working in Boutique DX. Both see the same client.

The security model: no passwords, no user sessions

The integration uses Salesforce's OAuth 2.0 JWT Bearer Flow — the server-to-server pattern Salesforce recommends for exactly this case:

• No stored passwords. Authentication is certificate-based; Boutique DX never holds a Salesforce user's credentials.
• A dedicated integration user. All changes are attributed to one clearly-named user (for example boutiquedx@yourcompany.com), so every synchronized Contact shows exactly who — or rather, what — touched it.
• Admin-approved access only. The connected app is pre-authorized by your Salesforce administrator, scoped to API access, and can be revoked by them at any time.
• Least privilege in production. We recommend a dedicated Integration Profile rather than administrator rights, so the integration can touch Contacts and nothing else.

This mirrors the platform's general posture: your data stays in your chosen region, client identifiers are hashed at rest in Boutique DX, and the sync sends Salesforce only what it needs to maintain Contacts.

What setup looks like

Configuration is a one-time exercise for your Salesforce admin, typically under an hour:

1. Create the dedicated integration user.
2. Create an External Client App, enable OAuth with API scope, and switch on the JWT Bearer Flow with the certificate we provide.
3. Set the user-access policy to admin-approved and assign the integration user's profile.
4. Add a LINE User ID field to the Contact object (if you use LINE).
5. Send us the integration username and the app's OAuth Client ID.

We handle the rest — matching rules, retries, and monitoring are managed by the platform. The full step-by-step guide with screenshots is part of our onboarding documentation.

Also speaking: Odoo, SAP SuccessFactors, and your ERP

Salesforce is one connector among several. Contacts can equally sync to Odoo; staff and HR data can flow from SAP SuccessFactors; and the same principles apply everywhere — server-to-server authentication, a dedicated identity, least privilege, and no manual re-keying.

If your client data currently lives in Salesforce while your boutique operations live in spreadsheets and personal phones, this is the shortest path to one coherent picture. Book a demo and bring your Salesforce admin.

---

Boutique DX is the operating system for luxury boutiques: AI-powered scheduling, client appointments, queue management, events, and analytics in one platform.