WooCommerce shops, kept moving.

Everything the WordPress page covers, around a shop. In the Orchestrator that means templates, checkout changes, shipping rules and the cache, with every plan approved first.

Join the waiting list See the demo shops

A shop is a WordPress site, so the WordPress page applies too.

The shop jobs that fill an agency's week.

A shop is a WordPress site with money moving through it. These jobs sit on top of everything on the WordPress page.

Shop and category templates
How the shop, category and product pages are laid out, in the theme or the builder.
Checkout and thank-you pages
Layout and wording changes to the checkout, and to the page a customer sees after paying.
Shipping rules
Zones and rates updated when your delivery terms change.
Landing pages for sales
Campaign and sale pages built to match the shop's design.
Speed and cache
A faster shop, with the cache set so forms and checkout keep working.
Updates, checked where it matters
Checked on the shop, product and checkout pages, not only the home page.

What the Orchestrator does on a shop.

Shops sit inside our 41 WordPress client projects, so we publish no separate count. Anything that touches checkout starts as a plan you approve.

Checkout changes that leave the order confirmation intact.

Some checkout templates quietly empty the page a customer sees after paying. The plan names that risk before anything changes, and the agent checks the confirmation page when it is done.

  • Risk and the way back on every plan
  • The confirmation page checked, not only the checkout
  • Desktop and phone screenshots attached

Caches that break forms, found before a customer does.

A page saved in the cache can carry a form token that expires about a day later, so the form quietly stops working. The agent keeps form pages out of the cache, clears it page by page, and checks as a plain visitor.

  • Form pages kept out of the page cache
  • Cache cleared and checked per page
  • Checked as a visitor with no login

What Webgentic for sites does on a shop.

It works on the WordPress side of a shop, one site at a time, and you watch each change appear on the page as it is made.

What it can change today

  • Pages and landing pages
  • Posts and media
  • Menus
  • Custom fields
  • Theme files
  • Any earlier version, restored in one click with a plain-English note

Not built yet

  • Editing products. We have no date, and the demo shops do not show it.

How it stays safe: it shows a plan first, the change appears on the page as it is made, and Stop cancels the job on the server. Every change is saved, and one click restores any earlier version.

See the WordPress page

An Orchestrator job, start to finish.

Rebuilding the cart and checkout on a Divi 5 shop. Five steps, the same every time.

  1. Brief

    Larch client, a Divi 5 shop. "Rebuild the cart and checkout to match the new design."

  2. Plan

    Build the cart and checkout templates. Keep the page after payment on its own template. The plan flags that risk.

  3. Approve

    You read the risk and the way back, then approve. Nothing changes before that.

  4. Deliver

    Cart and checkout built in Divi 5. The confirmation page is left out of the new checkout template, so it still shows the order.

  5. Prove

    Screenshots of the cart, checkout and confirmation page on desktop and phone, with the checks listed.

Example based on a real job, details changed. The risk is real: in Divi 5, a template built for checkout can leave the page after payment empty, so a customer who has just paid sees nothing.

What our playbooks cover for shops.

There is no separate WooCommerce playbook. These topics come from our WordPress and Divi playbooks, written from jobs we have done.

  • Building cart, checkout and shop pages in Divi 5
  • The page after payment going empty, and how to stop it
  • Caching, and why a change does not show
  • Forms that stop working a day after the page is cached
  • Checking a change as a plain visitor, with the cache cleared per page
  • Contact forms and email that reach the right inbox
  • Adding a tracking pixel and server-side conversion events
  • Refreshing staging from live without rewriting email addresses
  • Core security releases across many sites

Try it on a demo shop.

Three demo shops, one for each page builder. They use invented businesses, hold no real customer data, and reset every night at 03:30. They show page and theme changes. Editing products is not built yet.

Sign-in logins are issued on request, so you can try a change yourself.

Ask for a demo login

WooCommerce questions

  • Can it edit my products?

    Not yet. Editing products in Webgentic for sites is not built, and we have no date. The Orchestrator handles the templates, checkout changes, shipping rules and cache around your products.

  • Can you change my checkout?

    Yes, as an Orchestrator job. The plan names the risk and the way back, you approve it, then the agent checks every step, including the page a customer sees after paying, on desktop and phone.

  • Do the demo shops hold real customer data?

    No. They are invented businesses with no real customer data, and they reset every night at 03:30. Ask for a demo login and we will issue one.

  • How is a shop different from a WordPress site?

    It is still WordPress, but checkout, orders and product data raise the stakes. The difference is money: a bad change to checkout or the page after payment can stop a customer paying or confirming. So those changes are planned and approved first.

  • Can I undo a change it made?

    Yes. In Webgentic for sites every change is saved with a plain-English note, and one click restores any earlier version. In the Orchestrator every plan names the way back before you approve it.

  • Can it change my shipping rules?

    Yes, as an Orchestrator job. The plan names the risk and the way back, and you approve it before anything changes. Webgentic for sites does not edit shop settings.

  • Which page builders have a demo shop?

    Three: the block editor with the Ollie theme, Divi and Elementor. The WordPress page has five demo sites, including Visual Composer and Beaver Builder.

  • Something else on your mind?

    Ask us directly and a developer will reply.

    Ask a question

Bring us a shop job you keep putting off.

Join the waiting list. Or look at a WooCommerce demo shop first.

Join the waiting list Try a WooCommerce demo