INDEPENDENT MERCHANT INTELLIGENCEPUBLIC BETA / SEPTEMBER 2026 BASELINE
readiness / Merchant field guide

Salesforce Commerce Cloud merchant readiness

A practical review of product truth, public evidence and integration gaps for Salesforce Commerce Cloud merchants.

Merchant answer / Evidence review pending

Write down where catalog data, storefront experience and order services meet. The readiness question belongs to the deployed configuration, not just the platform name. Map this role to your existing stack and confirm the exact version, access conditions and implementation scope before making a merchant decision.

What this establishes
A practical way to inspect evidence and make the next merchant decision.

What it cannot establish
An unresolved dependency remains. Treat affected claims as provisional. Live merchant deployment, private account eligibility, purchase completion or guaranteed AI selection.

Evidence dates and document versions remain attached to the ledger below. Editorial presentation reviewed 30 September 2026; this is not a new source verification.

Start with your deployed store

Write down where catalog data, storefront experience and order services meet. The readiness question belongs to the deployed configuration, not just the platform name.

Where the decision gets specific

A commerce platform can coexist with a separate PIM, feed service and payment provider. Audit each boundary. Confirm which capabilities a proposed agentic integration consumes and which teams own failure recovery.

Make the audit repeatable

Select a small sample that covers normal products, variants and an unavailable item. Record the exact page, market, time and expected values. Run the public check, then compare its findings with your own authoritative records. For each issue, identify whether the repair belongs in source data, a template, a mapping or an account setting. Preserve the report before making changes so that the next check measures a real difference.

What public evidence cannot establish

The L0 scanner cannot inspect private feed acceptance, authenticated account configuration, payment authority or completed orders. A blocked page is not proof of a missing capability. Confirm those questions through official merchant tools and scoped provider documentation. Treat any suggested candidate as a capability to investigate, not a ready-made endorsement.

Your next step

Evidence ledger

Go to the source.

Primary documentation records what is publicly stated. It does not independently prove outcomes or your account’s eligibility.

  • UCP overview, 2026-08-25

    UCP · official primary · Checked 2026-09-28

    Claim scope: Discovery profile and commerce capabilities

    Version-pinned profile discovery; declared capabilities do not prove successful transactions.

    Source ID: ucp-spec · Published: Not stated

  • Product vocabulary

    Schema.org · official primary · Checked 2026-09-28

    Claim scope: Product properties

    Vocabulary presence is not validation, eligibility or certification.

    Source ID: schema-product · Published: Not stated

Dispute a fact or suggest a source