How to Schedule Category & Product Content Changes in Magento 2

Promotions rarely touch just the homepage. A campaign usually means new category imagery and copy, a different navigation colour, a set of products with promo-only options and photos, and then putting it all back when the sale ends. This guide covers how stores handle that today, and how to do it without duplicate products or late-night edits.

The problem: campaign content lives in many places

A typical "spring sale" in a furniture, fashion or homeware store changes:

• Category pages: the hero image and thumbnail, the description, sometimes a custom attribute such as a menu highlight colour.
• Products: the gallery (promo photography), the name or short description, which customizable options or fabrics are on offer, and often the price.
• Which products sit in which category: a "Great Deals" category filled for the campaign and emptied afterwards.
• CMS blocks and pages: banners, landing pages, the homepage.

Magento Open Source lets you edit all of these, but only live and one at a time. There is no way to prepare the whole campaign, check it, switch it on at 9am on launch day, and switch it off again a fortnight later.

Option 1: Edit live on the day

Someone sits down at launch time and works through a checklist. It's slow and error-prone, and the store is inconsistent while it happens. Reversing it at the end of the campaign means doing it all again in reverse, from memory or from screenshots.

Option 2: Create duplicate "promo" products

A common workaround for product changes: clone the product as a promo version with the campaign photography and the offer options, put the clone in the sale category, hide the original, and swap them back afterwards.

This works until it doesn't:

• Feeds and integrations see a new SKU every campaign. Google Shopping, marketplaces, the ERP and the warehouse all have to cope with products that exist for three weeks.
• Reviews, URLs and rankings belong to the original product, not the clone.
• Reporting splits one product's sales across two SKUs.
• Cleanup is manual and easy to forget.

Option 3: Adobe Commerce Content Staging

Adobe Commerce (the paid edition) includes Content Staging: scheduled updates to products, categories and CMS content, with a preview. It solves the problem, but it comes with an enterprise licence, and its scheduled updates are famously awkward to untangle when campaigns overlap or need editing after they're created.

Option 4: Stage the changes as a release with MageDrop

MageDrop adds staging, preview, scheduling and rollback to Magento Open Source, for the content teams change most: CMS pages and blocks, categories and products, at any store view.

Set up the campaign

1. Create a release in the MageDrop dashboard, for example "Spring Sale: Sofas", with a deploy time and a rollback time.
2. Edit the category in the Magento admin as you normally would: upload the new hero image and thumbnail, change the description, set the navigation colour, add or remove products in the "Products in Category" grid. Switch to a store view first if the change is for one store view only. Then choose MageDrop > Save & Stage instead of Save.
3. Edit each promo product: upload the campaign photography into the gallery and set the base image, hide the images that shouldn't show during the sale, change the name or copy, adjust the customizable options to the promo set, add a tier price. Choose Save & Stage to the same release.
4. Stage the CMS banners and landing page the same way.

Nothing has changed on the live store yet. Each staged change is stored as a delta: only the fields you changed, with the store view they apply to.

Check it

Click Preview on the release. You get a link that shows your real storefront with every staged change overlaid (category pages, the menu, product pages and listings) for you only. Share the link with whoever needs to sign it off. If anything doesn't look right, edit it again and re-stage; the change in the release is replaced.

Launch and end automatically

Click Schedule. At the deploy time MageDrop deploys everything in one go and records what each field was before. At the rollback time it rolls all of it back: the previous images, copy, options, product assignments and store-view overrides come back exactly as they were, including fields that had no store-view override before the campaign. No duplicate SKUs, no morning checklist, no reverse checklist.

Keep the history

Every admin save of a category or product, staged or not, is captured as a revision. If something is edited by hand during the campaign, you can see who changed what and restore any earlier version of that one entity without touching the rest of the release.

What about prices and stock?

Price and special price are attributes like any other, so they can be staged and scheduled with the rest of the campaign. Stock is never staged: quantities keep moving with every order, so they stay with Magento, your ERP or your warehouse system. Many stores with an ERP also leave prices to the ERP sync and use MageDrop for the content around them. If the ERP overwrites a field on a schedule of its own, let the ERP own it.

Summary

Getting started

1. Create a free MageDrop account and connect your store.
2. Install the MageDrop module (composer require magedrop/magento2:^2.0) and grant the integration the MageDrop API permission.
3. Create a release with a deploy and rollback time, and start staging from the category and product forms.