Content management systems for retail websites

Understand what a content management system controls. Follow a retail policy from editing to publication, separate from stock, orders and customer records.

A content management system (CMS) lets a team create, organise and publish website content through an editor. For a retailer, it manages material such as buying guides and delivery policies, while connected commerce systems manage prices, stock and orders.

The distinction explains a common problem: correcting a policy in the editor does not mean every customer-facing page or answer already contains the change. Publication and delivery are separate steps.

What a content management system does

A CMS stores content in records and gives authorised people tools to edit and publish those records. The public website displays the published content through a template or another presentation system.

The parts have different jobs:

  • The editor is the interface a staff member uses to enter content and inspect a preview.
  • Stored fields hold the content, such as a guide’s title, body and product references.
  • A template determines where that content appears and how the page presents it.
  • The public page is the result the customer reads, which can differ from an unpublished edit.

A content type defines a repeatable record structure. A Buying guide type, for example, can require a title and body for every guide. An entry is one guide stored using that structure. Contentful’s fields documentation describes typed fields, including text, media and references to other entries.

CMS stands for content management system. Phrases such as website CMS, CMS-driven website and web content management describe this authoring and publishing role. In marketing, the content can support campaigns or product education. The label does not establish that the software also processes payments or manages customer relationships.

Content records and commerce records

Content records explain the store’s products and policies, while commerce records describe what can be sold and what customers have bought. A customer relationship management system (CRM) keeps relationship information used by sales or service teams.

Retail records and their owners

RecordExample fieldsResponsible systemWho maintains it
Delivery-policy pageService regions, delivery guidance, page titleCMS or the commerce platform’s content editorRetail operations with the content team
Product-care guideMaterial, cleaning advice, related product IDsCMS, sometimes supplied by a product information systemProduct or merchandising team
Price and stockVariant ID, selling price, available quantityCommerce catalogue or connected stock systemMerchandising and inventory teams
OrderPurchased variants, charged amounts, payment and fulfilment statusCommerce platform or order-management systemRetail operations
Customer relationshipContact details, consent, service history, account ownerCRM or the platform’s customer-management functionCustomer service and authorised marketing staff

These are responsibility boundaries, not a requirement to buy five separate products. One commerce suite can contain a page editor, catalogue and customer records. A specialist CMS can also reference product identifiers supplied by another system.

Sharing a product identifier connects records without making them interchangeable. A care guide can reference the variant a customer bought, but editing that guide does not refund the order. Likewise, changing a customer’s service history must not silently change a public policy.

Keep personal customer details in systems with the appropriate access controls. A public content-delivery integration needs published policy text, not unrestricted access to customer or order records.

From an edit to a published answer

A policy correction reaches customers only after the approved revision is published and the interfaces using it receive the new content. Saving a draft is an internal change.

Consider this fictional retailer. Its returns page incorrectly says customers must post all returns, although the retailer also accepts returns at its stores. The content lead corrects the accepted return methods field and the explanatory text.

The example uses separate draft and live versions. Contentful documents this behaviour: a changed entry can retain its last published version in the Content Delivery API while pending changes remain in editing and preview interfaces.

  1. Draft the correction. The editor shows postal and in-store returns. Customers still read the published postal-only wording.
  2. Review the correction. Retail operations confirms the accepted locations and any applicable product conditions. The reviewer checks the preview, including links to store information.
  3. Publish the approved revision. The CMS makes the new content available to the public delivery path. The editor’s saved state alone is not proof of publication.
  4. Deliver the revision. The website retrieves it, or its publishing process rebuilds the affected page. Any cache or connected knowledge source must also receive the correction.
  5. Confirm the customer’s view. Open the public returns page and ask the connected shopping assistant how to return an item. Both must describe the approved methods and their conditions.

Contentful’s entry-state documentation distinguishes pending changes from published content. Its entry editor also keeps published versions for rollback. The exact approval roles and delivery steps depend on the implementation.

Find where an outdated answer comes from

Customer seesCheck firstResponsible owner
Old wording in both preview and public pageWhether the correction exists in the intended content recordContent lead
Correct preview but old published contentThe entry’s publication state and target environmentPublisher
Correct published record but old websitePage build, delivery cache and the content source that route readsWebsite or delivery team
Correct website but old shopping answerThe assistant’s connected policy source and its update pathShopping-assistance integration owner

For a retail example, shoppa is an AI shopping agent added to a site with two lines of code. It helps customers find, compare and buy products in the chat and supports them after the sale. Its answers use the retailer’s own catalogue and documents.

That makes the retailer’s policy documents part of the answer’s update path. Correct the approved source and deliver the correction to the agent as well as the website. The CMS owns the authored policy, while shopping assistance uses it to answer the customer’s question.

Coupled, headless and other delivery choices

A coupled CMS manages content and renders the website through its own presentation system. A headless CMS supplies structured content to a separately built website or application.

A retailer can publish a care guide in WordPress and display it through the site’s theme. WordPress’s template documentation explains that templates control the layout of posts and pages. Editing a shared template can therefore affect several guides, while editing one guide changes its content.

In a headless example, a retailer stores care instructions in Contentful and retrieves them through an application programming interface (API). The retailer’s website and mobile app can display the same record in different layouts. Contentful’s headless CMS explanation describes that separation between content storage and the interfaces that display it.

The headless approach gives the team control over those interfaces and reuse across destinations. It also leaves someone responsible for building the presentation, previews and content-refresh process. A CMS field will not appear in the website until the interface knows how to display it.

A coupled system can reduce that separate presentation work when its themes and editing model fit the store. Its built-in layout controls also define what editors can change without development. Both approaches need someone to maintain the public result.

Some systems support both page rendering and API delivery. A static website can also build pages from CMS content instead of fetching it on every visit. The architecture name alone does not tell you when a policy correction becomes visible. Specify that delivery behaviour alongside the editor’s controls.

Capabilities to check before choosing a system

Choose CMS capabilities around the people who maintain content and the places customers read it. A feature list is useful only when it answers a real publishing requirement.

For the selection brief, record the following requirements:

  • Define who can edit, review, publish and change templates. WordPress, for example, distinguishes a Contributor who cannot publish posts from an Editor who can manage other people’s posts.
  • Specify reusable fields and references. Decide whether one delivery-policy record must supply several pages, and who can change its structure.
  • Describe media needs, including image descriptions, usage rights and replacement behaviour when several pages share one image.
  • List required languages and markets. Decide who approves translations and what customers see when a translation is missing.
  • Require accessible editing and output. Authors need usable controls, while templates must preserve headings, link meaning and image alternatives on the public page.
  • Define previews, publication approval, scheduled changes and rollback. Include which connected interfaces must receive each update and how the team detects a failed delivery.

WordPress’s roles documentation shows why edit and publish permissions must be distinguished. Contentful’s localisation documentation similarly shows that language support involves configured locales and fields, not just a translated page title.

Use those requirements to compare CMS platforms without treating the longest feature list as the best fit. An implementation brief must name the records and destinations involved before selecting an architecture.

What a social CMS label can mean

A social CMS label needs a more specific description of the records and destinations it manages. It can describe software for planning social posts, which is a different job from publishing the retailer’s website policy.

For example, Hootsuite’s publishing tools organise scheduled social posts in a content calendar and support approval workflows. Its social inbox product handles customer conversations. A scheduled post, a website page and a private customer message have different permissions and delivery paths, even when one software suite contains tools for several of them.

Ask which item the team edits and where it appears. That answer establishes the workflow more reliably than the social CMS label.

Separate content and commerce responsibilities

A commerce platform can include content-management features while keeping stock and orders in separate records. The phrase Magento CMS commonly points to those content features within a commerce installation.

Identify the actual product as Magento Open Source or Adobe Commerce. Adobe’s content documentation covers pages and reusable CMS blocks within the store, while marking some capabilities as edition-specific. Its Content menu guide identifies Content Staging as an Adobe Commerce feature unavailable in Magento Open Source.

A delivery page in that content area still explains the policy. The product catalogue still owns the sellable item, and order records still own the transaction. Calling the content area a CMS does not establish the approval or publishing capabilities of every edition.

For your next content change, name the authoritative record and the person allowed to publish it. Then name each public interface that uses it and the person responsible for delivering the update there. That gives a policy correction an accountable path from the editor to the customer.

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.

See it in actionFree trial · Simple setup