Question 1

How is this different from Sales Cloud and Marketing Cloud?

Accepted Answer

Salesforce has multiple distinct products: Sales Cloud (CRM), Marketing Cloud (email marketing), and Commerce Cloud (ecommerce). Each has its own API, auth model, and data schema. Many orgs use all three, and Ana can query each independently or join across them.

Question 2

SCAPI or OCAPI?

Accepted Answer

TextQL uses the newer Salesforce Commerce API (SCAPI) by default for better performance and a cleaner data model. For legacy Commerce Cloud instances still on OCAPI, the connector falls back automatically. Both work transparently from Ana's perspective.

Question 3

Can Ana write orders or update products?

Accepted Answer

By default the connector is read-only. Admins can grant write scopes during setup if you want Ana to update product catalogs, create promotions, or process orders. Most teams start read-only and expand deliberately.

Question 4

How is multi-storefront handled?

Accepted Answer

Configure one connector per Commerce Cloud site or instance. Each connector has its own domain whitelist and OAuth scope, so data stays isolated per brand or storefront. Ana automatically routes queries to the right connector based on context.

Question 5

How are tokens secured?

Accepted Answer

OAuth tokens are encrypted at rest in TextQL's credential vault. When Ana makes a Commerce Cloud API request, tokens are injected at the network boundary by our egress proxy. Ana's Python sandbox never sees raw credentials.