Magento automation: the store jobs worth automating first

Which Magento jobs to hand to automation first, which to leave with a person for now, and how to start without putting a live store at risk.

Webgentic team16 November 20264 minute read

Magento automation pays off fastest on the jobs that happen every week and can be checked from outside: sale pages, banners, category text, cache and indexer checks. Deploys, patches and feed fixes come next, once each one has a written plan and a way back. Product data, checkout and anything you cannot undo stay with a person for now.

In short

  • There are two kinds of Magento automation: what Magento runs for itself, and the developer and admin work around the store.
  • Start with jobs that are frequent and easy to check, such as sale pages, banners and category text.
  • Deploys, patches and feed checks can be automated too, but only with a plan, proof and a way back.
  • Prices, stock, checkout and anything irreversible still need a person to decide.
  • Pick one repeated job, write down its checks and run it that way for a month before adding the next.

Two kinds of Magento automation

The first kind is built into Magento. Cron runs scheduled jobs. Indexers keep prices, categories and search up to date. Catalogue price rules apply discounts on a schedule, and imports and exports run at set times. Extensions add more of the same: feed exports, emails, stock syncs. When this layer stops, the store keeps serving pages, just with yesterday's data, which is why it is easy to miss.

The second kind is the work around the store that a developer or store manager does by hand: putting up a sale page, rewriting category text, clearing the right cache, applying a patch, deploying a module, checking the feed against the shop. This is where most of a Magento team's week goes, and it is the part an AI developer can now take on, as long as each job is planned first and proved after.

The store jobs worth automating first

Rank each job by two things: how often it happens, and how easily someone can check the result without trusting the tool that did it. The higher a job scores on both, the earlier it goes on the list.

JobHow oftenHow it is checkedStart
Sale pages and bannersWeekly, sometimes dailyThe page on desktop and phone, the menu link, the right cache clearedFirst
Category textWeeklyThe words on the live category page, before and afterFirst
Cache and indexer healthDailyIndexer status, cron's last run, a search and a filter that should return productsFirst
Feed checksWeeklyEvery price in the feed compared with the price the store showsSecond
Security patchesMonthlyEvery service that runs the software checked after, not only the version numberSecond
Module deploysMonthlyNo failed requests during the swap, the basket and checkout tested, the old build keptSecond
The daily order runEvery dayThe same orders out, in a fraction of the timeWhen the steps are written down

The order run is a good example of what is possible once a job is understood. At Fragrance Samples UK, a tool built by our developers took the daily job of getting orders out from 1.5 to 2.5 hours down to 5 to 10 minutes.

Why the checks matter more than the automation

On Magento, a job can look finished and not be. A cache can hide a broken page. An indexer can report as valid while search returns nothing. A version command can show the patched number while an old process still serves the old code. Automation that skips the check repeats the fault faster.

So every automated job needs three things written down before it runs: what will change, how you will know it worked, and how to put it back. If you cannot write the second and third, the job is not ready to automate.

Example: a module deployed without taking the shop down

The one step that takes a Magento shop down during a deploy is the compile. The agent put the new module on the server switched off, built the site in a copy, then swapped the built files into place in one step.

The swap was over in a moment, and the old build was kept as the way back.

Example based on a real job, details changed.

What not to automate yet

  • Prices, stock and product data, unless a person approves a plan first and checks the result. A wrong price is live the moment it is saved.
  • Checkout and payment changes without a full test of the basket, payment, tax, shipping and order emails.
  • Anything that cannot be undone, such as a database change on a busy store. A person decides when and whether.
  • Deploys at your busiest hour. The agent can prepare everything and wait. Someone picks the quiet time.

How to start

  1. Pick one job that happens at least weekly, such as the sale banner.
  2. Write down the checks you already do by hand when you do it.
  3. Run it with a plan and proof for a month, and keep every record.
  4. Only then add the next job from the list above.

Where Webgentic fits

Webgentic for ecommerce is a request bar on your own store. On Magento it changes CMS pages, CMS blocks, category text and design config, so sale pages, banners and category text are covered. It does not edit products, prices or stock. There is no approval step: the change appears as you watch, Stop cancels the job, and any earlier version restores in one click.

Store care is for the rest of the list. Our developers run your store's jobs every month through the Orchestrator: patches, speed, feeds, checkout and fixes. A developer checks each job first, you approve each plan and you get the proof.

The Orchestrator is for agencies running many client stores, with one agent per client project and, by default, a plan your team approves before anything changes.

  • Magento AI tools

    What a store can hand to AI today, job by job.

    Read the guide
  • Sales and promotions

    Your sale live the morning you ask for it, undone in one click.

    See the use case
  • AI for Magento stores

    Hyvä themes, deploys and servers, each job proved.

    See the Magento page

Questions about Magento automation

  • What is the difference between Magento cron and Magento automation?

    Cron is Magento automating itself: indexers, catalogue price rules, imports and emails on a schedule. Magento automation in the wider sense also covers the developer and admin work around the store, such as sale pages, patches and deploys.

  • Which Magento job should I automate first?

    A frequent job that is easy to check from outside, such as sale pages, banners or category text. Leave prices, stock and checkout until the rest runs reliably.

  • Can Webgentic change my products, prices or stock?

    Webgentic for ecommerce cannot. Product data and feed jobs go through Store care, where a developer checks the plan first, or through the Orchestrator, where by default nothing changes until the plan is approved.

  • How do I deploy a Magento module without downtime?

    Put the module on the server switched off, build in a copy, then swap the built files in one step and keep the old build as the way back. Check the basket and checkout afterwards.

  • Something else on your mind?

    Ask us directly and a developer will reply.

    Ask a question

Tell us which Magento job you would automate first.

Send us the job and how you check it today. A developer replies with how we would run it.

  • Read by a developer who works on Magento stores
  • Add your store address and we look at the shop first

For example yourstore.co.uk

One of our developers reads it and replies by email. How we use your details is in the privacy policy.