Squiz CMS: content operations and store connections

Check the Squiz CMS proposal against the retailer’s editing and publication work, with clear responsibility for content and commerce connections.

Squiz CMS is the content-management part of Squiz’s digital experience platform, documented as Squiz Content Management and Matrix 6 CMS. It manages website content through assets, permissions and publication workflows. For a retailer, the decision is whether the proposed implementation gets approved guidance to customers while keeping commerce records with their declared owners.

Name the Squiz content product

Name Squiz Content Management and its version in the proposal, alongside the hosting arrangement and included services. The current CMS documentation identifies the content product, while Matrix 5 has separate legacy documentation. A proposal that only says Squiz DXP leaves the content implementation unclear.

The wider digital experience platform includes capabilities beyond content management. Search and integration services have their own scope. Ask for an itemised architecture showing which services the retailer purchases and which the implementation actually uses.

Keep the CMS assessment tied to editorial work. An editor needs to find a policy, make a correction and submit it for approval. A developer needs to know how the approved content reaches the public page and any connected application. Neither task is answered by a platform-wide feature list.

Trace a retail content correction

Follow one policy correction from its authorised owner to the customer-facing answer. In this fictional example, a homewares retailer’s delivery page promises dispatch within two business days. The operations team corrects that promise to four business days for made-to-order cushions. These are example policy terms, not delivery claims about Squiz.

Squiz’s asset model stores content in assets and supports reuse across pages. For the retailer, create one approved policy asset with a defined scope for made-to-order cushions. Reuse that content where the delivery guidance appears, instead of pasting independent copies onto category and help pages.

The editor puts the live policy into Safe edit and changes the relevant wording. Squiz’s workflow documentation describes applying for approval, followed by the configured approver steps. The operations reviewer checks that four business days means dispatch time and that the advice identifies the affected products.

After approval and publication, a customer viewing an eligible cushion must receive the corrected dispatch guidance. A connected assistance service must retrieve or refresh the same approved policy. Specify how it associates that policy with the product and how it stops using the previous version.

Keep content ownership distinct from commerce ownership:

RecordDeclared ownerHow the CMS guidance connects
Dispatch policyRetailer’s operations teamApproved policy asset reused on relevant pages
Product eligibilityCatalogue teamProduct or category identifiers select the applicable policy
Price and stockCommerce team’s nominated systemsDisplayed through the agreed lookup or synchronisation
Customer orderOrder systemOrder reference remains with the transaction record
Published buying guidanceEditorial teamReferences the product and approved policy without duplicating transaction records

If a cushion changes from made-to-order to stocked, the catalogue change must update which guidance applies. Correct policy wording can still mislead a customer when the product reference selects the wrong policy.

Check the published version and access

Check account permissions and workflow together, using the actual editor and reviewer roles proposed for the retailer. Squiz’s content-editor documentation requires read permission to view an asset and write permission to edit it. An account type alone doesn’t grant access to every policy.

Safe edit preserves a live version while an editor prepares changes. However, Squiz’s asset-status documentation identifies settings outside draft protections, including permissions and asset URLs. Keep those structural changes under a separate release check. Editing a draft policy doesn’t make every surrounding configuration change private.

Use Preview to inspect the policy before publication, then inspect the public page signed out. Test reused content at each intended location. A correct preview proves neither that a public visitor gets the same version nor that a connected service has refreshed it.

For headless delivery, Squiz’s Content API is a REST interface with access controlled by its configured asset scope and user profile. Define the consumer’s permitted policy assets and fields. Prove that its permissions return the intended public content without exposing draft advice.

The store connection still needs implementation decisions. Record the identifiers used to match products, the direction of each transfer and the refresh interval. Assign failure alerts and recovery to a named operator. A content interface doesn’t establish that a retailer’s order system is already connected.

Use these acceptance checks on a representative test implementation:

  • Reject the four-day policy draft. The draft remains available for further editing, while the public page and connected response retain the approved two-day version.
  • Correct and approve the draft. A signed-out customer sees the four-day dispatch term only for the affected products. Every reused public passage shows the same policy.
  • Request the policy through the connected service after publication. If it still returns two days, compare its stored version with the CMS response and repair the refresh path.
  • Run the editor account against an unrelated restricted asset. Its access must match the agreed responsibility, including through the content interface.

Caching needs its own acceptance interval. Squiz’s recommended cache configuration says public changes appear within five minutes when that configuration is used. Establish the actual setup before applying that interval. A downstream content copy has its own refresh process and needs a separate check.

Assign cost and maintenance

Price the named CMS implementation and each required surrounding service separately. The retailer needs a written commercial scope covering the products, hosting and support it will use. Attach implementation work and ongoing editorial work as distinct items.

Cost or responsibilityWhat to put in the agreement
ProductsExact CMS and any additional services included in the purchase
HostingEnvironments, capacity, availability commitments and operational owner
ImplementationTemplates, reusable policy assets, permissions and commerce mappings
SupportIncident ownership, response terms and work excluded from the service
UpgradesWho checks custom rendering and integrations after platform changes
Editorial workPolicy owner, approver cover, access reviews and obsolete-content removal

The retailer owns the truth of its dispatch promise and the catalogue rules that select it. The provider owns the contracted implementation and its maintenance. If those duties overlap, name who diagnoses the first failure and who authorises the correction.

Compare CMS software through the same policy journey before choosing a proposal. Make the approved correction, rejected draft and connected-content checks part of acceptance, with an operating owner for each failure.

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