Documentation.

How to use Webgentic for ecommerce, what it can change on each platform, starting with Magento and WooCommerce, and the Orchestrator in brief.

Getting started with Webgentic for ecommerce

Webgentic for ecommerce lets you change your website by asking in plain words, in a panel on the site itself. It is invite-only while it is in preview. Join the waiting list and we will email you when your place comes up.

What you need before we connect your site

  • Your website address.
  • The hosting access your provider gave you. Your onboarding says exactly which details we need.
  • Your permission for us to connect to your site with that access.

If you do not hold that access yourself, the connection page can email the steps to your developer instead.

Connect your site

  1. Choose how we connect. The connection page lists the options and recommends the one that shares no password.
  2. Run Test the connection. It only reads. It checks the connection and finds the folder that holds your website, with its best guess already selected.
  3. Choose Connect my site. We then read your site, set it up and check that Webgentic is live on it.

If your site is unusual and needs setting up by hand, we quote a one-off fee first, and you can say no. Otherwise connecting is free.

What goes on your site

A small connector. On WordPress, a plugin adds it for you. On other platforms your onboarding tells you where to put it, and a button checks that it is live.

Webgentic for ecommerce is hosted by us. Each site is kept to its own folder and access, and changes are sent back to your live website.

Open Webgentic on your site

  1. Visit your own site. The first visit asks you to sign in to edit that site.
  2. After that, a blue strip along the bottom of your pages opens and closes Webgentic.
  3. You can also open it from the address bar: take your site address and add /#webgentic to the end.

Visitors never see the strip. It only appears in a browser signed in to your site.

Asking for a change

Write a good request

  • Ask for one change at a time.
  • Say which page it is on.
  • Give the exact words, if the change is to text.

For example: “On the contact page, change the opening hours to 9am to 5pm, Monday to Friday.”

What happens next

  1. Webgentic writes a numbered plan and ticks the steps off as it works.
  2. While it works, the part of the page being changed is framed, and the change appears in the page as it is made, before any reload.
  3. When it finishes, the change is live on your site.
  4. If it is not right, restore an earlier version.

There is no approval step. A change is live the moment it is written. What you have instead is the plan you can read first, the live view of the change, Stop, and history with one-click restore.

Stop a job

Stop cancels the job on our server, not only on your screen.

Uploads, voice and images

  • Uploads. Attach files and images to a request. They upload as soon as they are attached, and sending waits for the last one.
  • Voice. Dictate a request instead of typing it.
  • Images. Ask for an image in plain English. You are offered several, you pick one, and Webgentic puts it into the page. Reject them all and it asks for more.
  • Past conversations. They are listed, and you can reopen any one and carry on.

You can also choose which AI model does the work. We keep the default current.

What it can change on each platform

Depth differs by platform. Magento and WooCommerce stores come first. This is what Webgentic for ecommerce does today. See all platforms for the work behind each one.

PlatformWhat it can changeWhat it cannot
Magento 2 CMS pages, blocks, category text and design config. Products. There is no product editing.
WooCommerce The ordinary WordPress content on the site, as in the WordPress row. Shop products. Editing them is not built.
WordPress Pages, posts, media, custom fields and menus. It can also move items to trash. It has guides for Divi 4 and Divi 5. Elementor, Beaver Builder, Visual Composer and Oxygen sites work as ordinary WordPress sites. There are no builder-specific guides beyond Divi 4 and Divi 5.
Drupal Files only. Content held in the database, which includes enabled modules and most content. Restore goes no further than files.
Plain PHP and static sites Files only. Anything in a database. These sites have no database content to edit.
Shopify Each store is set up with us. Talk to us about what yours needs. Agreed for each store when it is set up.

History and restore

Every change is saved as a version with a plain-English note. You can see what changed, which files it touched, and the difference.

Restore an earlier version

  1. Find the version you want in the history.
  2. Restore it. It takes one click.

Restoring is free and never costs a credit.

What a restore covers

  • Magento 2. The files and the content Webgentic can edit. Caches are cleared on restore.
  • Drupal, plain PHP and static sites. Files only.

Credits and plans

One credit pays for one request, whatever its size. Restoring an earlier version uses none. Unused credits roll over for one month, and you can change plan or cancel whenever you like. Everything Webgentic has already built stays on your site.

Plans, prices and what each one includes are on one page: see plans and prices.

Connecting Search Console

Webgentic can connect to your site’s Google Search Console, so it has real search data to work from when you ask for search changes.

We connect it with you, rather than leaving you to work it out. Ask us to connect it and a developer will set it up with you.

The Orchestrator in brief

The Orchestrator is a different product from Webgentic for ecommerce. It is an AI agent for a web agency, each client and each project. It is for agencies, freelance developers and in-house web teams who run work for many clients.

It is not self-serve. Our developers install it, load your clients, access and house rules, and train your team. See how setup works.

How a job runs

  1. You brief it in plain words.
  2. It writes a numbered plan, with the risk and the way back.
  3. By default, a person approves, changes or rejects the plan before anything changes on a client site.
  4. It does the work kept to that one project's folder and access.
  5. It ends with a written validation, and with screenshots or a short video where the change is visible.

We built it for our own agency and use it every day: 6,600+ agent runs so far. Read more about the Orchestrator.

Getting help

Support comes from our developers. Pick whichever way suits you.

Questions about using Webgentic

  • Is there an approval step?

    Not in Webgentic for ecommerce. It writes a plan first and shows the change as it is made, but a change is live the moment it is written. You can press Stop, and you can restore any earlier version in one click. The Orchestrator is different: by default, a person approves each plan before it runs.

  • Can it break my site?

    It edits real files, so a wrong change is possible. Every change is saved as a version with a plain-English note, and any earlier version restores in one click for free. Stop cancels a job that is going wrong. On Drupal, plain PHP and static sites, a restore covers files only.

  • What happens to my site if I cancel?

    You can change plan or cancel whenever you like, and everything Webgentic has already built stays on your site.

  • Which platforms does it work on?

    WordPress, WooCommerce, Magento 2, Drupal, and plain PHP or static sites. Magento products and WooCommerce shop products are not edited, and Drupal and plain PHP are files only. Shopify stores are set up with us. Craft CMS is not supported.

  • Do I need a developer?

    Not to ask for changes. You ask in plain words. To connect your site you need the hosting access your provider gave you, and if you do not hold it, the connection page can email the steps to your developer.

  • Something else on your mind?

    Ask us directly and a developer will reply.

    Ask a question

Ask us anything about Webgentic.

Join the waiting list for Webgentic for ecommerce, or ask a developer a question first.