Salesforce CMS: content, channels and store records
Assess Salesforce CMS for the retail team’s content workflow and check who controls the published guidance and its links to store records.
- Published
- Last updated
Salesforce CMS is a content management system for creating approved content in workspaces and delivering it through channels. It can own your buying guides and campaign images. Keep customer records and live commerce data with their designated systems, and connect the published guidance to those records deliberately.
Identify the Salesforce content product
Salesforce CMS manages editorial content. The wider Salesforce customer relationship management (CRM) system manages customer relationships. Experience Cloud supplies customer-facing sites, while the named commerce product supplies the store’s commerce functions. A proposal that says only Salesforce doesn’t identify which of those jobs you’re buying.
Salesforce’s CMS introduction describes enhanced and non-enhanced workspaces. Enhanced workspaces connect content to supported site channels and support content workflows. Non-enhanced workspaces still have documented destinations, including B2C Commerce Page Designer. Choose the workspace type for the actual destination.
The publishing documentation lists Lightning Experience with Enterprise, Performance, Unlimited and Developer editions. Treat that availability table as a feature prerequisite, then match the proposed licences and destination separately. A general Salesforce licence doesn’t describe your whole content-delivery arrangement.
Salesforce native CMS content and Salesforce CMS Connect follow different routes. CMS authors create native content inside Salesforce CMS. CMS Connect brings external content into a supported Experience Builder site. It doesn’t make the external CMS the same content repository.
The CMS Connect prerequisites distinguish HTML fragments from JSON content. HTML and JavaScript retrieval requires an externally accessible unauthenticated HTTPS source. Authenticated JSON sources work only for authenticated site users. The connection setup uses a named credential for authenticated connections, which support JSON only. Confirm that route before promising private external content on a public page.
Publish the approved product guidance
Move a buying guide from the author’s workspace to the intended channel, then verify the customer page. Saving the document and publishing it are separate actions.
Consider a fictional lighting retailer publishing a guide called Choosing a bedside lamp. The guide explains shade size and reading light. It links to catalogue product LAMP-204 without copying current stock into the article.
- The author creates the guide in the chosen CMS workspace and adds the approved image. A product-reference field stores LAMP-204 as the agreed catalogue identifier.
- The merchandising reviewer checks the advice and confirms that the identifier resolves to the correct catalogue product. This field mapping is part of the implementation, not an automatic product synchronisation claim.
- A content manager or content admin publishes the approved content to the workspace’s channels. In an enhanced workspace, the publisher includes the referenced image in the publication selection.
- The site implementer places the content on the destination page. For an Experience Cloud site, Experience Builder controls how the guide appears. A custom storefront needs its own delivery integration.
- The reviewer opens the customer page and follows the product reference. The catalogue remains the source for live price and availability. Order records remain in the order system.
Salesforce’s publication instructions say referenced content in an enhanced workspace must also be published. Publishing a new live version replaces the earlier one. Review the workspace’s channel list before publishing, because content becomes available to all channels attached to that workspace.
Check access and delivery
Match editorial permissions to the delivery channel and test the actual audience. An author’s ability to edit content doesn’t establish a customer’s ability to retrieve it.
The publishing permissions distinguish contributor access from publishing authority. Any workspace contributor role can create and edit content. Publishing and unpublishing require a content manager or content admin role. Assign review responsibility explicitly instead of giving every author publishing access.
The CMS channel documentation distinguishes public and restricted channels. Restricted delivery uses permission sets for users accessing content through application programming interfaces (APIs). Restricted content can’t be served through a content delivery network (CDN).
Match the API family to the content model. Salesforce documents limitations when non-enhanced APIs retrieve enhanced content, including complex custom types with repeatable or block elements. A successful simple article request doesn’t establish support for every custom guide field.
For site previews, the preview instructions require the appropriate site channel and content page. Contributors need site contributor access. Enhanced workspaces preview on enhanced Lightning Web Runtime (LWR) sites. Inspect the guest and authenticated views where the site supports them, plus the mobile layout.
Use one distinctive sentence in a test correction to compare the editor with the delivered page. Salesforce’s enhanced content details distinguish Draft, Published and Revised states. Revised means published content has edits awaiting republication.
When the customer page still shows the earlier sentence, check publication status before investigating delivery caching. Then compare the channel response with the rendered page. A current response with an old page points to the consumer’s rendering or cache. An old response points back to the channel and requested content version.
Check missing images and unresolved product references separately. Compare the guide’s referenced items with their publication states, then resolve the product identifier against the catalogue. An assistant consuming the guide needs the same published correction and working reference as the customer page. Connecting an assistant doesn’t publish the draft.
Price the proposed workflow
Price Salesforce CMS as a complete editorial and delivery workflow. Salesforce’s introduction describes limited CMS inclusion across Salesforce organisations and fuller access with Experience Cloud licences. That doesn’t establish your store’s total price or entitlement.
Ask for an itemised proposal with separate responsibilities and charges:
- Identify the CMS entitlement, edition and licensed contributors.
- List connected products, including the proposed Experience Cloud or commerce destination.
- Separate implementation of content types and catalogue references from the recurring licence.
- Include ongoing publishing administration, delivery maintenance and any contracted usage allowances.
Keep quoted limits and their effective dates in your procurement record. Put the currency, tax treatment and billing period beside each charge. Compare the same guide-to-storefront workflow across CMS platforms and use the CMS platform comparison to assess alternatives. Approve the proposal when it identifies who owns the content and demonstrates how the published version reaches your store.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.