Genesis CMS: identify the platform and workflow

Which Genesis CMS does the proposal mean? The guide separates providers, content models and retail integration work before you choose.

Genesis CMS needs a provider name before you can assess it: Dobble’s Australian website platform and IuVe’s self-hosted product family are separate products. For a Dobble site, the decision centres on the editing access you receive and the licence and service arrangement that keeps the website running. This guide assesses Dobble’s Genesis CMS.

Establish which Genesis CMS you have

Match the proposal’s supplier to the organisation behind the installed website. Record the legal supplier, website address and product name from the agreement. For an inherited site, use its administrator details and support records to connect that installation to the supplier.

Dobble describes Genesis CMS as its proprietary website platform. IuVe’s marketplace uses Genesis for a separate family of self-hosted applications, including travel and automotive products. Their shared name does not make their editor controls or hosting arrangements interchangeable.

Keep a short identification record with your website handover documents. It must connect the provider and product to your domain, the applicable agreement and the person who manages access. A proposal saying only “Genesis CMS included” leaves the operating arrangement undefined.

For broader requirements, the CMS platforms guide helps place this assessment alongside other website publishing options.

Check the identified site’s publishing workflow

Assess Dobble Genesis with the account your staff will actually receive. Dobble says it can grant requested CMS access through a limited user account, with permissions assigned at its discretion. Basic training and documentation are available on request. Treat editing access as part of the agreed service scope.

Use a delivery policy as an acceptance exercise. Give a staff member a draft policy change and follow its path to the public page. The exercise must establish these outcomes:

  • The editor can find the correct page and change its delivery regions or exclusions.
  • The page’s content fields keep headings and links usable without editing the underlying template.
  • An image or document can be replaced, with meaningful alternative text where the interface supports it.
  • The right person can approve and publish the change, while another account has only its agreed permissions.
  • Staff can correct a mistaken publication using the recovery process included in their agreement.

Record which tasks the retailer completes and which become support requests. A useful handover shows the full sequence from a saved revision to the public page, including any approval step. Repeat the exercise with a buying guide that has product links and images, because its editing needs differ from a policy page.

Separate the CMS and commerce responsibilities

Map each type of information to the system that holds it. The CMS can publish buying guidance and store policies, while the store’s commerce system controls records such as stock and orders. Establish the actual split for your installation before commissioning a connection.

Use one product to follow the data. Locate its description, current price and availability, then identify where an order is created. Record which system staff update and how the storefront receives each change. A copied price in a buying guide is a separate piece of content that can become outdated.

For a customer-answer service, identify the approved policy source and the catalogue connection separately. Ask the implementation team to name the documented interface, data direction and refresh behaviour in the project scope. A public policy page can supply text, but it does not establish access to live stock or private order records.

Dobble presents custom integration work separately within its development services. Specify the connection your store needs and who maintains it. Do not infer a ready-made commerce connector from the Genesis name.

Review hosting, support and exit terms

Dobble’s published development terms separate ownership of client-supplied content from its proprietary software. The website and CMS licence depends on an active service level agreement (SLA) and an account in good standing. If the SLA ends, Dobble says a static export may be available, while proprietary software and development files stay with Dobble.

A static export preserves pages for hosting elsewhere. It does not give you a working copy of the CMS editor. Establish what happens to content editing and any dynamic store functions before treating that export as your exit route.

Make the proposal assign responsibility for hosting, security updates and backups. Include the support response you are buying, how a failed change is restored and who can approve custom development. Request the export format and its scope, including media and redirects, in the same agreement.

Choose Dobble Genesis when the demonstrated editor covers your routine publishing and the provider’s service terms fit the work you want managed. Before signing, turn any essential task that still needs provider work into an explicit deliverable with its ongoing cost and owner.

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