How-To Guide
How do you set correction rules for prices, dates, and availability in social posts?
One correction record per post, claims sorted by type, old prices proved by a log, dates changed everywhere or not at all, availability matched to the store.
By the Superdirector editorial team. The pages cited here, including Google Merchant Center help, Adobe Commerce documentation, captured Instagram and TikTok Help Center pages and the practitioner guides named in the text, were read November 14, 2026. Updated November 14, 2026.
At a glance
How do you set correction rules for prices, dates, and availability in social posts?
Write one correction record per post that carries a price, date or availability claim, and give each claim type its own rule: what can invalidate it, which live source proves it still holds, who may pause the post, and what gets checked after it goes out. Price claims rest on a log you can show, because the reference-price rules your country sets decide what an old number must prove. Date claims carry the exact end date and time zone in the caption, and every copy of a changed date moves together. Availability claims come from one source of truth with a freshness window shorter than your fastest change. When a claim breaks, correct or remove the post inside the window your rule sets, fix the destination page in the same pass, and record what changed.
- Three dates do different jobs on a scheduled post: publish time, review time and valid-until time. The rule lives in a record next to the post, not in an approval email.
- Price rule: the old number must sit in a log you can show. The two country readings in this article, EU 30 days and Turkey 10 days, disagree, which is why the log and your own law decide.
- Availability rule: one source matched everywhere. Google disapproves shopping feeds that disagree with the page, so a post contradicting the store carries the same risk in spirit.
Every claim type answers the same four questions, and each one names the record that decides it. Original diagram from this article's claim-type table, adapted from Branding Bull's per-post review record.
Make it work for your brand
Find it. Remake it. Post it. Superdirector turns the viral formats in your niche into your brand's carousels, X posts and video scripts, and keeps the calendar full.
Write one correction record per claim-bearing post
A correction rule you cannot apply is a slogan. Every price, date or availability claim in a scheduled post gets one record, stored next to the post in whatever calendar or sheet your team already checks. The fields below are adapted from Branding Bull's per-post review record, which pairs a promotion with exactly these responsibilities (Branding Bull); the wording is ours.
- Post and account: the channel, the scheduled item, and the claim it carries.
- Live source: the one page or system that proves the claim today, such as the offer page, the price log, or the booking system.
- Valid until: the latest moment the claim still holds, plus any earlier stop condition, such as the class selling out before registration closes.
- Review check: who checks the source, when, and what they look for.
- Pause authority: the named person who can hold publication if the check has not happened. Branding Bull's recommendation is to hold it when the required check has not happened, so silence never becomes approval (Branding Bull).
- Replacement: the only wording allowed to substitute, approved in advance, or an instruction to skip the slot.
- Closeout: who checks the post after it goes live and removes or updates it when the claim expires. Branding Bull assigns a closeout check for promotions that may keep attracting attention after the offer ends.
The record is what turns a rule into a correction. When a claim breaks, the person on pause authority acts from fields that already exist, instead of inventing a replacement and a deadline under pressure. Nothing in this article relies on a scheduler noticing anything by itself: the checks are human steps, run on a cadence your record sets.
Sort the queue by claim type and set each rule
| Claim type | Rule that fires | Live source that decides | Who pauses | After go-live |
|---|---|---|---|---|
| Deadline-bound (offer ends, registration closes) | Exact end date and time zone in the caption; valid-until equals the end | Offer or event page | Publisher holds if the pre-publish review has not happened | Closeout check after the end; remove or update |
| Price-bearing (any price, discount, was-now) | Price change updates caption, image, feed and page at the same time | Price log plus the store page | Owner of the price log | Fix the post and the page in the same pass |
| Availability-dependent (stock count, bookings, places left) | Check the count against the live source before publish; prefer wording that cannot go stale when it moves fast | Inventory or booking system | Review check owner | Correct, replace or remove when the answer changes |
| Date-bearing (event or launch date) | Date in the post matches the destination page; a changed fact moves every copy | Event page or launch plan | Record owner | Correction note and matching date changes |
Two failure modes the table is built against. The first is a customer meeting the wrong answer at the destination: GoDataFeed's mistake framing ends with a product displayed as available that the customer discovers out of stock at purchase (GoDataFeed). The second is the stale scheduled post that keeps a dead claim on screen for weeks, which is why the closeout column exists. Neither failure needs a new tool to fix; it needs the rule decided before the post is queued.
When the underlying fact moves fast, weaken the claim instead of tightening the review. Branding Bull's example suggests wording such as "check current availability" over a specific remaining count when nobody can monitor it (Branding Bull). That wording is itself a rule: the caption commits to nothing the source can silently prove wrong.
Set the price rule: prove the old number or drop it
A price claim is a promise about money, so the rule starts with evidence you can produce. Keep a price log with named fields, adapted from SemPost's list: product and SKU, the date of every change, the price before and after, whether a promotion was running, and who changed it and why (SemPost). Kurşun & Partners read Turkey's July 2026 advertising regulation the same way on the record side: proof depends on retained price records, and inspectors request them first (Kurşun & Partners).
Old-price claims carry a reference-price window, and the windows differ by market. SemPost reads the EU's amended Price Indication Directive as setting the pre-reduction period at not less than 30 days as of November 2026, and says to confirm your own country's text (SemPost). Kurşun & Partners read Turkey's regulation as requiring the pre-discount price to be the lowest price of the ten days before the discount began (Kurşun & Partners). Treat both readings as attributed, not universal: the log plus your own market's law decide what your brand may announce.
| Phrase | What you must be able to show | Safer wording that survives the same check |
|---|---|---|
| "20% off" | A reference price the log supports, and the percentage calculated from it | "20% off, through November 30, 2026" with the was-price in the caption |
| "Was $X, now $Y" | A log entry showing a real selling price at $X inside the window your law sets | "Now $Y" when the log cannot support $X |
| "Last day" or "only today" | The offer really stops, and nothing extends it silently | The exact end date and time zone written out in the caption |
| "While stocks last" or "only 5 left" | A stock count taken at publish time, and genuinely limited stock | A count taken that day, or "check current availability" when it moves fast |
| "Up to 50% off" | Items that really reach the top discount, and scope stated next to the number | "Selected pieces up to 50% off, prices on the page" |
State the scope next to the headline number, which is SemPost's rule for "up to" claims (SemPost), and write the end date and time zone inside the post so a late reader still reads a true sentence. Where the price lives also matters: text in a caption can be corrected, while a price baked into an image is wrong until the image is replaced (SemPost), so the price rule names which file gets re-made when the number changes.
Set the date rule: change the answer, then change every copy
For the post itself, write the date the way SemPost does: the exact end date and time with the time zone, so the claim is exact and stays true for a late reader. A schedule set somewhere else is not a caption claim: check the scheduling tool's displayed time zone separately from the date written in the post, the same separation Branding Bull draws between the calendar and the deadline (Branding Bull).
When a fact changes, the honest move is a change of answer and then a change of dates. Digital Applied's one-line rule, applied to pages but built on Google's own guidance, is that a post earns a new date when a reader would get a different answer than before (Digital Applied). Its router puts a corrected figure in its own row: the modified date moves, the change is labelled a correction rather than an update, and the published date stays. The same reading quotes Google's warning against changing dates to look fresh without a substantial change (Digital Applied).
Apply that rule to every copy of the date the post touches: the caption, the date printed on the image or video frame, the event or store page the caption points to, and any feed data the product runs in. Digital Applied's consistency rule is to change all copies of a date or none of them (Digital Applied), which for a social post means the correction is one task even though it lands in four places. Inside a store, the change may also need to be scheduled rather than hand-stopped: Adobe Commerce cannot add an end date to an active price rule that was scheduled without one, and instead takes a new scheduled update that switches the rule to Inactive (Adobe).
Set the availability rule: one source, matched everywhere
Pick the single system that owns the number: the inventory record, the booking calendar, the order queue. Every other surface, caption, image overlay, product feed, store page, is a copy, and the rule says the copies refresh from the source inside a window you choose. PPC Data Feed sizes that window with arithmetic: with a daily feed at 06:00, a 09:00 price change stays wrong for 21 hours, while an hourly update keeps it wrong for at most 60 minutes (PPC Data Feed). Set the window from your fastest observed change, not from a default.
Where the copy is a shopping feed, the mismatch is enforced, not just embarrassing: Google's Merchant Center help states that when a mismatch is found between the loaded landing page price and the feed price, the product may be disapproved (Google), and the same help family requires the submitted availability value to equal the landing page, warning that too many incorrect values can suspend the account (Google). The correction mechanics have their own clock: a fix triggers a re-crawl over the next few hours or days (Google), and a website review can take up to 12 hours (Google). Google's fix order also says to update your site and your product data at the same time (Google), which is the all-copies rule for availability in one line.
Keep sold-out items in the feed rather than deleting them: PPC Data Feed normalises stock wording to in_stock, out_of_stock, preorder or backorder and keeps sold-out products in the feed as out_of_stock (PPC Data Feed). Google agrees on which value not to use: out_of_stock must not be set merely to pause products, and the pause attribute covers only up to 14 days (Google). For the social caption itself, prefer wording that cannot go stale, and when a count must be stated, state it with the moment it was true.
One source of truth feeds four copies, and all of them refresh inside a single window sized from your fastest observed change. Original diagram from this section's one-source rule, whose freshness arithmetic the article attributes to PPC Data Feed.
Execute the correction on each network
The correction runs inside the edit window each network actually gives. ClimbX's guide to X's Edit post says the feature is Premium-only with a 1-hour window and up to 5 edits on original posts and quotes (ClimbX). Instagram documents caption, location and tag edits on an existing post, with an Edited note below edited captions, on a Help Center page captured in 2020; the same captured page makes clear that the media parts of a multi-photo post cannot be reordered or edited (Instagram Help Center, captured page). SubtitleBee's TikTok guide reads the app as allowing description, hashtag and cover changes after posting from the Edit post option (SubtitleBee).
| Network | Documented correction path | What it changes | What it cannot change |
|---|---|---|---|
| X | Edit post inside 1 hour, up to 5 edits, Premium only (climbx.so guide) | Text and attached media tags; the edited label and history are public | Replies, threads, polls, scheduled posts; the window after 1 hour |
| App Edit on the post, per the captured Help Center page | Caption, location, tagged accounts | Media parts of a shared multi-photo post; images already posted | |
| TikTok | Delete and restore within 30 days; description edits as SubtitleBee reads the app | Description text and cover on live posts; full removal with recovery | Caption text baked into the video's frames |
| Shopping feeds | Update the product data, then request the website review per Google's help | Feed price and availability values | Nothing organic; the re-crawl and review decide the timing |
Choose edit versus delete-and-repost by what has accumulated. ClimbX's rule is to edit when the post already has replies, and to delete and repost only when the post has nothing yet and the mistake sits in the first line (ClimbX). X's authenticity policy bounds the habit: it treats repeated posting and deleting of the same content as content spam (ClimbX). The 30-day recovery on TikTok exists for exactly the wrong-deletion case (TikTok Help Center, captured page), but treat recovery as a safety net, not a plan.
Fix the destination in the same pass, because a corrected caption pointing at an uncorrected page still misleads. Documented platform APIs are not a general correction API either: Facebook's IG Media reference documents enabling or disabling comments on an Instagram media, and no caption rewrite through the endpoint (Facebook), so a connected tool's correction reach ends where the network's does. Then record action, time, and what changed: Branding Bull asks for the action recorded rather than a chat message saying it was handled, and SemPost keeps the correction note short, what happened, when it was noticed, and what changed (Branding Bull; SemPost).
Where Superdirector fits and where it does not
Superdirector, which publishes this guide, carries the posting half of the workflow under the permission you set. Its offer runs at $199 a month for one social account its AI operates in the direction you set, and it publishes eligible Instagram carousels and single X text posts under the account-level posting permission you set once by answering its one warning; after that it posts by itself. The $29 a month plan is MCP-only for hands-on work from Claude or ChatGPT.
What it does not do is decide the correction rule for you. The claim-type table, the reference-price reading for your market, the freshness window and the pause call are brand decisions, and they belong in the record described in this article wherever the account is run, by you or by an operator. When you read the record before you queue a claim-bearing post, the correction, if it ever fires, becomes one task instead of an improvisation.