30 properties → 23 clusters
New admitted properties after identity review
Regional storefronts and known brand affiliations are grouped conservatively; ultimate buying parents are not exhaustively verified.
← All company lists
Commerce · October 2026 research
Salesforce B2C Commerce merchant-operator research
Review 30 merchant-operator clusters with recorded Salesforce B2C Commerce / Demandware source configuration: seven retained pilot accounts and 23 new clusters. This covers merchant website configuration, with no Salesforce CRM, verified paid-customer or whole-company-use claim.
Research dated 2026-10-24. Original source dates and website scope stay with the records.
Salesforce B2C Commerce research summary
30 merchant-operator clusters
Research dated
Contact-free research examples · CSV
Review 30 merchant-operator clusters with recorded Salesforce B2C Commerce / Demandware source configuration: seven retained pilot accounts and 23 new clusters. This covers merchant website configuration, with no Salesforce CRM, verified paid-customer or whole-company-use claim.
Download the 4-row CSV previewCount operators after reviewing storefront overlap
23 of 67
New observations unresolved on access
Unsuccessful or disallowed collection remains unresolved and does not establish nonuse.
The 30 admitted new property observations reduce to 23 new operator clusters; seven retained pilot accounts make 30 joined accounts. Candidate observations, properties and operator clusters have separate denominators.
Preview the list
Research summary and 4 contact-free examples only. No full-file commercial offer or delivery terms are proposed.
CSV columns: name · domain · sourceClass · checkedOn · scope
Four companies in the preview
These approved examples illustrate the 2026-10-24 research. They are not a representative sample of all customers.
HUGO BOSS
www.hugoboss.com
Own-host storefront resource configuration · 2026-10-24
The root request returned the Singapore storefront. Its HTML referenced own-host Demandware resources; the observation applies to that returned page, not worldwide or whole-company use.
City Beach
www.citybeach.com
Own-host storefront resource configuration · 2026-10-24
The request returned a US storefront page whose HTML referenced own-host Demandware resources. Browser execution, transactions and paid status were not checked.
Weber
www.weber.com
Storefront-template resource configuration · 2026-10-24
An app-privacy document was served within the Austria storefront template, which referenced own-host Demandware resources. The observation concerns the website template, not the Weber Connect app stack.
vidaXL
www.vidaxl.es
Own-host storefront resource configuration · 2026-10-24
The Spain-domain storefront HTML referenced own-host Demandware resources. The source locale does not establish headquarters, complete geographic coverage or paid status.
Count operators after reviewing storefront overlap
WhosBuilt analysis of the saved October 2026 research. Findings describe this selected cohort, not market share.
30 properties → 23 clusters
Property and operator grouping
30 admitted new property observations reduce to 23 conservative operator clusters. Counting regional storefronts or known affiliated brands independently would overstate this selected list.
Merchant storefront/template configuration only. Locale paths identify the returned page, not headquarters or national deployment. Ultimate parent buyers are not exhaustively verified.
Research 2026-10-24 · property observations and operator clusters · WhosBuilt saved-record analysis
23 of 67
Access remains unresolved
23 of 67 new candidate observations remained unresolved because collection failed or was disallowed. A missing readable source does not establish that a merchant does not use B2C Commerce.
Merchant storefront/template configuration only. Locale paths identify the returned page, not headquarters or national deployment. Ultimate parent buyers are not exhaustively verified.
Research 2026-10-24 · new candidate observations · WhosBuilt saved-record analysis
How this list was checked
Source checks ran on 2026-10-24. The four examples have unknown publication dates; their timestamps date configuration observations rather than adoption. Checks ran on 24 October 2026; the seven pilot accounts keep their original observations without rechecking. Source configuration, corporate identity and operator grouping are separate checks. No browser runtime, Commerce API, transaction, paid-status or technology-buyer check was performed. Selected policy/resource windows favor visible classic storefront templates.
Review 30 merchant-operator clusters with recorded Salesforce B2C Commerce / Demandware source configuration: seven retained pilot accounts and 23 new clusters. This covers merchant website configuration, with no Salesforce CRM, verified paid-customer or whole-company-use claim.
| Source class | Count | Scope |
|---|---|---|
| Merchant storefront/template configuration | 30 | The 30 admitted new property observations reduce to 23 new operator clusters; seven retained pilot accounts make 30 joined accounts. Candidate observations, properties and operator clusters have separate denominators. |
Property and operator grouping: The 30 admitted new property observations reduce to 23 new operator clusters; seven retained pilot accounts make 30 joined accounts. Candidate observations, properties and operator clusters have separate denominators. The four examples have unknown publication dates; their timestamps date configuration observations rather than adoption. Checks ran on 24 October 2026; the seven pilot accounts keep their original observations without rechecking. Source configuration, corporate identity and operator grouping are separate checks. No browser runtime, Commerce API, transaction, paid-status or technology-buyer check was performed. Selected policy/resource windows favor visible classic storefront templates.
Access remains unresolved: The 30 admitted new property observations reduce to 23 new operator clusters; seven retained pilot accounts make 30 joined accounts. Candidate observations, properties and operator clusters have separate denominators. The four examples have unknown publication dates; their timestamps date configuration observations rather than adoption. Checks ran on 24 October 2026; the seven pilot accounts keep their original observations without rechecking. Source configuration, corporate identity and operator grouping are separate checks. No browser runtime, Commerce API, transaction, paid-status or technology-buyer check was performed. Selected policy/resource windows favor visible classic storefront templates.
- Merchant storefront/template configuration only. Locale paths identify the returned page, not headquarters or national deployment. Ultimate parent buyers are not exhaustively verified.
Source access dates do not refresh historical statements. Static signals do not prove execution, payment or buying intent. Published contacts do not establish deliverability or outreach permission.