Duda CMS: content editing and store boundaries

Evaluate Duda for retail content. Check page editing, connected collections and publishing, then separate those functions from selling and orders.

Duda CMS supports retail page editing and structured content, while the installed store component determines how customers buy and how staff manage orders. It suits a retailer that wants a managed website editor with a clearly defined commerce setup. The proposal needs to identify both parts and the access you retain.

Define the Duda website setup

A Duda website proposal must name the editor, content features and store component it includes. The website design alone does not establish which selling functions you receive or who manages them.

Duda documents both native ecommerce and a third-party store option. Its store comparison states that the third-party option applies to the Classic Editor, not Editor 2.0. A store described only as “Duda ecommerce” leaves that distinction unresolved.

Have the provider identify the account holder and your own login permissions. Name the site plan separately from the commerce subscription and any paid apps. Include who changes delivery rules and who can publish a policy correction. Those are ongoing store responsibilities, even if a provider builds the site for you.

Maintain consistent guidance on the site

Use editable pages for individual guides and connected content for information that must appear consistently across several pages. Duda collections hold structured records, while dynamic pages reuse a layout to display those records. This separates an article’s data from its page design.

For an illustrative homewares retailer, a collection could hold care guides with a material name, image and care instructions. A dynamic page displays each guide through the same layout. An editor changes the record’s advice without redesigning every guide. Duda’s dynamic-page documentation explains how widgets connect to collection fields.

Dynamic pages need a route for visitors to find them. Duda states that they do not automatically appear in site navigation. Add a guide listing or another navigation path, then inspect a published guide from the customer’s starting page.

Keep the full delivery policy in one maintained location. Connect a reusable summary where the site needs the same guidance, and link it to the full policy. Avoid manually copying a delivery threshold into every guide. A repeated sentence becomes stale whenever someone updates only one copy.

Publication behaviour depends on the data source. Duda’s collections table distinguishes internal data published through the site or content library from external sources with automatic updates. An external database collection is refreshed hourly. That delay makes it unsuitable as an assumed live-stock source without a separate design for stock accuracy.

Give staff the permissions their work needs. Duda separates widget-content access from site republishing and connected-data editing in its permissions table. Permission to edit a visible widget does not necessarily grant access to the record behind it. Name who approves a delivery-policy change and who can make it live.

Separate content from transactions

The store component must own sellable product records and checkout, with payment processing and order handling assigned to named services or staff. A content collection that displays products is not enough to establish that transaction setup.

For a native store, Duda documents catalogue management and inventory alongside store settings. Its Store JS API lets developers read product and category data, with filtering and pagination. A custom guide can use that documented interface to display public catalogue references instead of maintaining a second product list.

Duda also documents a Cart JS SDK for cart and checkout operations. This browser interface is available when the relevant commerce feature is installed. It is a separate capability from reading a collection or editing a guide. A developer must handle readiness and errors when using it.

For the proposed implementation, trace one product from its editable record to its public page, checkout and resulting order. Identify where staff correct a price and where a payment provider reports settlement. Include refunds and stock updates in that responsibility map. If the store runs in another service, use that service’s documented interfaces and account permissions.

An on-site shopping assistant needs approved product information and policies from those same owners. Public guide content can supply buying advice. Access to customer orders requires its own permission design, independent of whether a guide is publicly readable.

Check ownership and ongoing work

Compare the proposal’s plan entitlements with the features the provider intends to build. Duda’s plan matrix distinguishes levels of connected data, dynamic content and developer access. A small internal collection and an externally connected collection have different requirements. Record the purchased entitlement alongside the expected number of records and who maintains the connection.

Code access and code export answer different questions. Editing HTML and CSS helps a developer customise a site within Duda. Export concerns what you can take to another host. Neither describes the full operating cost of a custom integration, which needs someone to maintain it.

The site-export documentation makes export available on Agency plans and higher, to account owners or staff members. It exports the published site’s files. Its exclusions include the store and dynamic pages, and it states that contact forms stop working outside the platform. An exported page is not a replacement for the Duda editor or a complete store migration.

Plan separate exports for content collections and store records. Duda provides a native-product CSV export, but product data alone does not recreate checkout configuration or order operations. Preserve media and destination URLs with the content you intend to move.

Before accepting the website, agree who owns custom code, who pays each subscription and who supplies exports if the provider relationship ends. Approve the setup when your staff can maintain a guide and policy, the transaction responsibilities are clear and the exit deliverables cover your actual content.

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