Craft CMS vs WordPress for retail content

Compare Craft CMS with WordPress on the same retail content task, including editing, publication, commerce records and ongoing operating work.

Choose Craft CMS when you want a tailored editorial system and have a developer to maintain it. Choose WordPress when your team wants block-based publishing and a maintained WordPress setup meets your commerce requirements. The Craft CMS vs WordPress decision turns on who controls shared content and who repairs the connection to your store.

Choose between Craft CMS and WordPress

Craft CMS fits a retailer that wants developers to define content fields and editors to work within those fields. WordPress fits a retailer whose content works well as pages, posts and reusable block patterns. Either can need custom development once product records or approval rules become more demanding.

A content management system (CMS) holds and publishes editorial content. The CMS name alone doesn’t tell you which system runs checkout. For a useful comparison, separate the product guide from the records that set its product prices and availability.

Two comparable retail proposals

RequirementCraft CMS proposalWordPress proposal
Editorial setupCraft CMS 5 Pro, custom entry types and templatesSelf-hosted WordPress, a block theme and configured patterns
Reusable guideDefined fields with references to product recordsA guide page with reusable structure and product blocks or a maintained custom block
Shared policyOne policy entry rendered wherever requiredOne synced pattern used wherever the policy text repeats
Commerce in this comparisonCraft Commerce 5, separately licensedWooCommerce core, separately installed
Maintenance capacityDeveloper owns templates, configuration and integrationsDeveloper owns theme, plugins and any custom blocks

These are illustrative proposals built from documented capabilities. They aren’t claims that every installation has the same configuration.

Craft’s supported-version policy lists CMS 5 and Commerce 5 as supported. WordPress’s release inventory lists 7.1.4, and WooCommerce’s release list lists 11.3.0 as stable. Pin compatible versions in the proposal and assign updates to a named maintainer.

If you already have a commerce platform, compare keeping it as the record owner in both proposals. A new CMS doesn’t automatically require moving your store’s transactions.

Compare the same retail content task

Both proposals must publish the same guide and correct the same delivery policy without creating a second source of product truth. Consider a fictional retailer with 200 products, 20 guides and three staff who edit content.

The retailer needs a reusable guide to choosing a desk lamp. Each guide has buying advice, images and selected products. A delivery-policy correction changes the dispatch promise from two business days to four.

Build and publish the guide

In Craft, the developer defines a guide entry type with fields for advice and images. A product-reference field connects the entry to Commerce products. The template reads current variant prices and availability from Commerce instead of saving those values in the guide’s prose. Craft documents entry types and field layouts, while its Commerce listing documents relationships between products and content.

An editor fills the guide fields and saves a draft. Craft’s draft and preview system lets the editor inspect unpublished changes through configured preview targets. A publisher with the required section permission applies the draft to the live entry. The developer must configure the preview to render the same product references as the public template.

In WordPress, the developer configures a guide layout using the block editor. An unsynced pattern can supply each guide’s starting structure while its advice stays independent. A WooCommerce product block, or a maintained custom block, reads the selected product record. The custom option adds development and compatibility work to the proposal.

The author saves the new guide as a draft and previews it. WordPress documents previewing a page in a new tab. An Editor can review and publish content from other authors under the standard role model. A separate approval stage for changes to an already-published guide needs its own demonstrated workflow.

Correct the policy once

The Craft proposal stores the dispatch wording in one policy entry. Product pages and guides render that entry through their templates. The editor drafts the correction, previews its affected contexts and the publisher applies it. A hard-coded copy in a template still needs a developer’s correction.

In the WordPress proposal, the policy text is a synced pattern. Editing that pattern changes each place that uses it, as the synced-pattern documentation explains. A detached copy becomes independent and won’t receive the correction. The maintenance agreement must include finding those copies and checking the pattern’s publication permissions.

After publication, inspect a guide and a product page as a signed-out visitor. Confirm the four-business-day wording appears in both. Check any cached copy too. Preview success doesn’t establish that the public response has changed.

Keep commerce records with their owners

In these proposals, Craft Commerce and WooCommerce respectively own the store’s variant prices, inventory and orders. Their payment gateway connects the order to the payment processor, which holds the payment transaction. If an external stock system supplies inventory, record that system as the upstream owner and define how updates reach the store.

A CMS guide needs a product identifier and a way to render the right record. Copying “$80 and in stock” into editorial text creates a value that can outlive the stock record. The same risk exists in both systems.

For the lamp guide, change the selected product’s price in the commerce record. The guide must show the new value without an editor rewriting its advice. Then make the variant unavailable and confirm the guide’s purchase action respects that state.

Check commerce and extension dependencies

Craft CMS and WordPress need an explicit commerce implementation before their editorial features can be compared as store features. Craft CMS Pro doesn’t include a Craft Commerce licence. WordPress alone doesn’t establish that WooCommerce, a gateway or a required extension is installed.

For each proposal, list the commerce product and version, the gateway integration and every paid extension needed by the brief. Include external services such as inventory feeds or transactional email. Record which supplier supports each dependency and who pays its renewal.

Craft Commerce 5 has product variants and configurable checkout development. Its permission documentation separates product management from order editing, payment capture and refunds. A person who writes product guides can have a narrower role than someone who refunds orders.

WooCommerce adds Customer and Shop Manager roles to WordPress. Its role documentation gives Shop Managers broad store responsibilities. Use WordPress’s capability model to assess the actual editorial role. Don’t grant store-management access merely so an author can change delivery text.

A proposal passes the permission check when an author can complete the guide workflow while unauthorised commerce changes remain blocked. If custom code supplies that boundary, include its maintenance in the quote.

Compare the complete operating cost

Compare the two proposals over the same three-year period, with the same product count and editorial team. Include implementation and recovery work alongside licence costs. A free core package can still need a paid maintainer.

Craft lists CMS Pro at USD $399 per project, with one year of updates and USD $99 per year for later updates. Its Pro upgrade guidance identifies the currency. The CMS pricing page owns the plan terms. Commerce Pro is an additional USD $1,199 per project, then USD $299 per year for updates, according to Commerce pricing.

For those two licences, the three-year list-price subtotal is USD $2,394: USD $1,598 initially plus two USD $398 renewals. This is a licence subtotal before purchaser-specific tax and currency conversion. It excludes hosting and implementation. Paid licences are perpetual, but update eligibility and developer support have renewal terms.

WooCommerce’s pricing page lists its core platform as free. Hosting and paid extensions are separate. Obtain prices for the exact theme, gateway and extensions in the WordPress proposal instead of pricing an unspecified plugin collection.

Use the same cost categories

Cost categoryCraft CMS proposalWordPress proposal
LicencesCMS edition plus Commerce and any commercial pluginsCore software plus any paid theme and extensions
HostingProduction environment, preview environment and backupsEquivalent production environment, preview environment and backups
ImplementationContent model, templates, migration and commerce setupBlock theme, patterns, migration and commerce setup
Ongoing updatesCMS, Commerce, plugins and template compatibilityWordPress, WooCommerce, extensions and theme compatibility
RecoveryRestore procedure that protects orders accepted after the backupEquivalent restore procedure that protects newer orders
SupportNamed developer, response window and included hoursNamed developer, response window and included hours

Require both quotes to use the same tax basis and currency. Add payment-processing fees using the same sales assumptions. Record renewal prices separately from introductory prices.

The editorial lead owns an incorrect policy or an unapproved guide. The developer owns a failed template publication or broken product reference. The host owns infrastructure within its contract. The commerce maintainer investigates a failed gateway or inventory connection and coordinates with that provider.

WooCommerce’s update procedure calls for backups and staging checks. Apply an equivalent recovery requirement to the Craft proposal. Restoring an old database on a trading store needs a plan for preserving newer orders.

Choose the proposal whose maintainers can show the corrected policy on the public site and repair a broken product reference within the agreed support terms. Those responsibilities determine what the CMS costs after launch.

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