A bakery display with seasonal pear pastries and neutral menu stand
A bakery display with seasonal pear pastries and neutral menu stand
In this guide
  1. Distinguish sales dates from publication dates
  2. Link each offer to its publication surfaces
  3. Understand what scheduling actually publishes
  4. Prepare the post-offer state in advance
  5. Treat stock changes and extensions as revisions
  6. Keep a single-offer workflow simple
  7. Test both activation and retirement

Distinguish sales dates from publication dates

For a pastry sold from 1 November with an October preview, announcement, sale start, sale end and post-sale guidance are separate states. Managing only the publication date can leave a page implying that an expired offer is still orderable. Confirm the dates per item and agree what happens if stock runs out earlier. This is an editorial scheduling design, not a guarantee of stock or availability. Keep producing promotional material separate from controlling which version customers see and which ordering destination is active at a particular point in the season.

Link each offer to its publication surfaces

Use an offer ID and record participating locations, dates, landing page, menu page, announcement, ordering destination, image and owner. When the same item appears in several places, the register should reveal every affected surface. Verify content and price before scheduling publication. Record branches that do not participate. If considering a previous season’s product image, verify that it still represents the current offer; visual similarity is not enough. For this site’s editorial workflow, select a distinct image suited to the actual product or process rather than automatically assigning a generic category photograph.

Understand what scheduling actually publishes

Wix Blog documents scheduled posts, while Webflow CMS provides item publishing states and scheduling. Scheduling a blog post does not necessarily change every menu element or ordering destination at the same moment. Check the product and plan you actually use, and list the remaining actions in the schedule. Updating an existing published item and scheduling a new one may have different conditions. Automate the supported part deliberately, then assign a person and time for anything still manual. Do not describe a page as fully scheduled merely because one announcement has a future publication time.

Working fields and completion checks
Working fields and completion checks
FieldRecordCompletion check
PreviewMessage and participating locationsSeparate from sale start
Sale windowStart, end and time zoneMatch ordering route
ExceptionsSell-out or extensionReview scheduled actions
AfterwardReplacement copy and destinationRemove availability implications
Two blank menu cards beside an empty pastry display tray at closing time
Two blank menu cards beside an empty pastry display tray at closing time

Prepare the post-offer state in advance

Prepare useful post-offer copy before launch: a regular menu, the next announcement or a clearly historical reference may be appropriate. Decide whether to retain, archive or consolidate the page based on its remaining reader value. Check ordering links as well as the headline. A retained page must not suggest that the old product is currently available. Assign ownership of the end-of-offer check and leave that task open after launch. Publication success is only the beginning of the content lifecycle; it does not complete the scheduled retirement or replacement work.

Treat stock changes and extensions as revisions

An early sell-out requires verification of the affected branch and ordering route before the message changes. Extending a sale requires more than editing the end date: check already scheduled closing posts and removal actions too. Record the revision and approver so another editor does not continue following the earlier plan. Keeping dates and prices as editable text reduces the number of visual assets that must be replaced. Photography should still match the actual offer. A scheduling register coordinates decisions; it cannot discover a shop’s current stock unless that information is supplied through a reliable process.

Keep a single-offer workflow simple

One seasonal item can be handled with existing editing features and a checklist. Consider a CMS or notifications when offers and locations create repeated update work. Compare CMS capacity, scheduling availability, collaborator seats and additional services separately. If using Make, define its publishing authority and a manual fallback for interruptions. An annual schedule may make a reusable review process more valuable than a new automation for every campaign. The relevant cost is the work required to keep the public information correct throughout the offer, including early withdrawal and an unexpected extension.

Test both activation and retirement

Test preview, launch, sell-out, extension, closure and next-season reuse with fictional dates. Inspect the live URL for dates, price, image and order destination, including on a narrow screen. Follow the test through to the post-offer message instead of checking launch alone. The menu guide covers content fields, seasonal research covers demand and the retirement guide supports the decision about old pages. This schedule controls who applies those decisions and when; it should not turn a useful historical article into a misleading current product page.

Resources for the next step

Websites for shops and classes

Choose a website approach around menus, opening hours and trial-class requests, including who will keep the information current.

Official sources

Pricing, availability and feature limits can change. Check the linked official pages before subscribing.

How we compareAdvertising disclosure