Harlow Tools
A Magento shop on the Luma theme. Ask for a change to a CMS page or block.
View the site: Harlow Tools (opens in a new tab) Open sign-in: Harlow Tools (opens in a new tab)
Magento work, planned, proved and remembered.
We have run 24 Magento client projects through the Orchestrator. Hyvä themes, Page Builder, large catalogues, extensions, cPanel and server work: each job is planned, approved and proved.
The Magento jobs agencies hand us.
The work that fills a Magento agency's week, and the work that is hard to staff.
-
Hyvä themes
Child themes, templates and the Tailwind build, checked on the page a shopper sees.
-
Page Builder and CMS content
Banners, landing pages and blocks, built so your client can edit them afterwards.
-
Large catalogues
Categories, layered navigation, search and indexers on shops with a lot of products.
Extensions, patches and upgrades
Version upgrades, security patches and extension conflicts, with the way back written first.
cPanel and server work
PHP versions, cron, Varnish, caches and hosting limits, handled alongside the code.
Speed and Core Web Vitals
Front-end weight, images and the main content paint, measured before and after.
The Orchestrator on Magento.
24 client projects have run through our own Orchestrator. This is how a Magento job goes.
One agent per store, with its own memory.
Each store's project agent remembers the theme, the extensions, the hosting and every change made so far. A new job starts from that history, not from a blank page.
- Hyvä and Luma themes, Page Builder content and extensions
- Hosting notes for cPanel and your own servers
- Limited to that one project's files, enforced in code
Magento client board
- Acme client · Hyvä bannerWorking
- Larch client · Shipping moduleReview
- Northgate client · Patch upgradeComplete
- Hale client · Category textPlanning
Plans that spell out the risk and the way back.
Anything that changes a store starts as a short numbered plan. You approve it, change it or reject it. Nothing touches the store before you say so.
- Deploys planned to keep the shop up
- A written way back on every plan
- Approve from the board, the chat or your phone
Larch client · Shipping module
Project agent · Magento
PLAN
- Copy the module onto the server, switched off.
- Build the site code in a copy.
- Swap the built files in, then check the basket.
RISK: low · shop stays up
UNDO: previous build kept
Nothing changes until you approve.Approve plan
Proof from the page a shopper sees.
Every job ends with a written validation: what changed, what was tested and what is still open. Visible changes come with screenshots on desktop and phone.
- Checks listed with pass or fail
- Two AI vision models read every screenshot
- Lessons from past Magento jobs loaded before the next one
Validation
Complete- Banner shows on desktop and phone
- Basket and checkout unchanged
- Only the home page cache was cleared
Evidence: 4 screenshots · 3 of 3 checks passed
Webgentic for sites on Magento.
Webgentic for sites adds a request bar to one Magento shop. The owner asks for a change in plain words and watches it happen. On Magento it changes content and design, not products.
| On a Magento shop | Today | In practice |
|---|---|---|
| CMS pages | Yes | Page content kept in the Magento CMS. |
| CMS blocks | Yes | Reusable content blocks. |
| Category text | Yes | The words on category pages. |
| Design config | Yes | The shop's design settings. |
| Restoring an earlier version | Yes | Put back in one click, with the caches cleared. |
| Products | Not built | Product editing is not built. |
A plan comes first and you see each change appear as it is made. Stop cancels the job on our server. Every change is saved with a plain-English note, and any earlier version can be put back in one click.
No approval step in Webgentic for sites.
The change is made as you watch, and every earlier version is kept. Plan approval belongs to the Orchestrator. See how Webgentic for sites works
An Orchestrator job, start to finish.
A new module on a live shop, with no downtime.
Brief
Acme client needs a new module on its live shop. The shop must stay up while it goes in.
Plan
The agent finds the one step that takes a Magento shop down: the compile, about 30 seconds. Its plan builds in a copy and swaps the result in.
Approve
You read the plan, its risk and its way back, then approve it.
Deliver
The module goes onto the server switched off, so it has no effect. The agent builds in a copy, then swaps the built files into place in one step.
Prove
The swap took 138 ms and no request failed. A control build without the module still showed 238 differing files, so the module was not to blame. The old build is kept as the way back.
What the Magento playbooks cover.
Each job loads the playbook topics that match it, so past mistakes are not repeated. The playbook is reviewed every night, so what one job learns reaches the next.
- Deploying a new module without taking the shop down
- Hyvä child themes and the Tailwind build
- Page Builder banners, CMS blocks and landing pages
- Clearing Varnish and the cache without emptying the whole shop
- Security patches, and checking a store for malware
- Search, filters and indexers that look healthy but are not
- Core Web Vitals on Hyvä
- Google Shopping and product feeds
- Magento on cPanel hosting
Try it on a Magento demo site.
All 13 demo sites reset every night at 03:30. They are invented businesses with no real customer data.
Hoovers Direct
A Magento shop on a Hyvä child theme. The one to open if your clients use Hyvä.
View the site: Hoovers Direct (opens in a new tab) Open sign-in: Hoovers Direct (opens in a new tab)
Saltmarsh
A second Magento shop on the Luma theme, to try a change to category text.
View the site: Saltmarsh (opens in a new tab) Open sign-in: Saltmarsh (opens in a new tab)
Magento questions agencies ask first
Do you work on Hyvä stores?
Yes. Hyvä is covered in the Magento playbooks, and one of our demo sites is a Hyvä store.
Can Webgentic for sites edit products?
No. On Magento it changes CMS pages, blocks, category text and design config. Product editing is not built.
Does anything change on a live shop without my approval?
The Orchestrator plans first, and nothing changes until you approve. Webgentic for sites has no approval step: each change appears as it is made, Stop cancels the job on our server, and every earlier version can be put back in one click.
What can the Orchestrator reach on a client project?
A project agent can only read and change its own project's files. That limit is enforced in code, not left to good behaviour.
What happens when I restore an earlier version?
Every change in Webgentic for sites is saved with a plain-English note. Restoring one puts it back and clears the caches.
Something else on your mind?
Ask us directly and a developer will reply.
Ask a question
Bring us your Magento stores.
Join the waiting list. When your place comes up, we will show you the Orchestrator running on one of your real jobs in the first call.