Price Updates vs New Posts: Different Cadence Rules

The used-car desk cuts $500 on a 45-day Civic at 10:40 a.m. The manager's instruction to the associate is two words: "update Facebook." The associate, trying to be fast, takes the live listing down, copies the photos, writes a new title that screams the markdown, and submits it as a fresh post. Twenty minutes later the same associate is told to "get the rest of the aged list live," so six more units that already have Marketplace ads are posted again. By lunch the account has a cluster of near-duplicate vehicles, the original ads are still findable, and the Civic's conversation history with two serious buyers is gone.

That is not a merchandising problem. It is a cadence problem. Price updates vs new posts are different actions with different risk, and they do not share the same daily ceiling. Treating every markdown as a reason to fire a new listing is how lots accidentally look like they are flooding Marketplace even when they did not add a single new unit to the floor.

This article is a floor operating standard for internet directors, used-car managers, and associates: when to edit a live listing, when a new post is actually warranted, and how to keep those two streams from colliding. Meta does not publish numeric posting thresholds, so treat every number below as a conservative store standard, not a platform rule.

Why Price Updates vs New Posts Need Separate Cadence Rules

A price change is a field edit on an existing commercial object. A new post is a new commercial object. Ranking systems, duplicate-content filters, and buyer conversation threads treat those two events differently. If your team uses one daily count for "things we did on Facebook," you will either under-merchandise aged cars or over-post the account.

What a price update actually is

A price update, done correctly, is:

• The same VIN, same photos, same description skeleton.
• A changed asking price that matches the window sticker, website, and CRM.
• Optionally a short, calm sentence in the description that the vehicle was recently repriced, without all-caps panic language.
• The same listing URL and the same message thread, so buyers who already asked "is this still available?" are not starting over.

That work should not consume a new-post slot. It is merchandising hygiene, closer to correcting a typo than to launching a unit.

What a new post actually is

A new post is a first-time listing, a relist after a true takedown, or a replacement after the original listing was removed or expired. It creates a new object, a new impression history, and a new conversation surface. It is the action that should sit under your daily posting ceiling.

If you are unsure which you are doing, ask one question: will a buyer who already messaged this VIN still land in the same thread? If the answer is no, you just created a new post, even if you thought you were "just updating the price."

Cadence Rules for Price Updates on Live Listings

Price updates should be frequent enough that Marketplace never shows a stale number, and infrequent enough that you are not twitching the listing every time the desk debates $100. The guide to editing a live listing covers field-level safety; this section covers timing.

When to edit in place the same day

Edit the live listing, do not create a new one, when:

• The desk issued a real, approved price change that is already in the DMS.
• Mileage, title status, and photos are still accurate.
• The listing is not pending, sold, or in a deal jacket.
• You are not trying to "refresh" position by deleting and reposting.

Do the edit once, in one sitting. Changing the price at 9 a.m., 11 a.m., and 3 p.m. because the manager is still negotiating with himself is worse than waiting until the number is final. Buyers who watched the listing drop three times in a day assume something is wrong with the car, not that your desk is indecisive.

How often a single unit should be repriced on Marketplace

Set a store rule, not a feeling. A conservative operating standard that many lots can live with:

1. No more than one Marketplace price change per unit per business day.
2. No public markdown until the website and window sticker already show the new number.
3. No title rewrite that exists only to advertise the drop.
4. No second listing of the same VIN while the first is still live.

If the desk wants to test a number internally, that conversation belongs in the used-car meeting, not in three successive Marketplace edits. For wording that does not look panicked, see showing price drops without looking desperate.

What not to do when the price changes

• Do not delete the listing "so it shows up as new."
• Do not clone the listing onto a second profile to "cover more eyeballs."
• Do not paste "PRICE DROP" into the title.
• Do not leave the old price in the description after you changed the price field.
• Do not treat a price update as credit toward a rep's daily new-post target. That incentive is how associates learn to kill live ads.

Cadence Rules for New Posts (First-Time and True Relists)

New posts are the activity that can look like burst posting if you bunch them. They belong under a daily ceiling per account, spread through the workday, with irregular gaps. For the broader pacing question, use how many cars a dealer can post per day as the companion playbook. This section is only about keeping new posts from being confused with updates.

Count only true new objects

Your daily new-post log should include:

• Units that have never been on this Marketplace account.
• Units whose previous listing was actually removed or expired, and you are starting over on purpose.
• Units returning to market after a deal fell through and the original listing was already taken down.

It should not include:

• Price edits.
• Photo swaps on a live listing.
• Mileage corrections.
• Description cleanups.

If your analytics mix those together, you will think you posted twenty cars when you posted eight and edited twelve. Managers then "catch up" in the afternoon and create the burst you were trying to avoid.

Spread new posts; batch the paperwork

CSV import, VIN decode, photo selection, and queue assignment can happen in a morning block. Submission should not. A conservative operating standard is to load the queue once, then let posting run one vehicle at a time with human-like delays across the day. Do not dump the aged list at 4:55 p.m. because someone remembered Marketplace during the close.

Price-update work can sit in a different window. Many stores do markdowns after the used-car meeting, then new posts through the rest of the day. That split keeps the account from looking like it launched a dozen near-identical ads in ten minutes.

A Floor Decision Tree: Update, Wait, or Relist

Give every associate the same three-way choice. Write it on the whiteboard if you have to.

Checklist before anyone hits submit on a "new" listing

• Confirm the VIN is not already live on this account.
• Confirm you are not replacing a listing that only needed a price field change.
• Confirm website, DMS, and Marketplace will show the same number.
• Confirm this submit counts against today's new-post ceiling.
• Confirm the associate is not posting from a shared login to "get around" a ceiling.

If any box fails, you are doing a price update or you are waiting. You are not posting.

How PostToMarket Automates This

The specific failure this article targets is the associate who turns every markdown into a new Marketplace object, then burns the daily ceiling on duplicates. PostToMarket keeps inventory, queue, and posting state in one place so a price change and a first-time post are not the same button.

• Inventory statuses (draft, posting, posted, sold, failed) show whether the unit is already live. A posted unit gets an edit path, not a second submit.
• AI-generated titles and descriptions, editable before posting, so a markdown does not require a panicked rewrite of the whole ad.
• Facebook photo picker so you are not cloning another unit's album to "save time" on a relist that should not exist.
• Personal and per-rep queues, with managers assigning work to associates, so price-update tasks and new-post tasks can be queued separately.
• Server-enforced daily post limits and delays, plus one-vehicle-at-a-time Chrome extension posting with human-like delays, so new posts cannot burst even if someone tries to "catch up."
• Mark as sold and archive from inventory or the queue, so a unit that left the market is not sitting next to a clone.

No tool can guarantee Facebook will distribute every listing. What this workflow does is stop the operational pattern where price updates vs new posts collapse into one messy burst.

Run Price Updates vs New Posts as Two Cadences, Not One Dump

Price updates vs new posts will keep colliding until the store treats them as different jobs. Updates keep the live catalog honest. New posts introduce units to the catalog. Mix them, and you train the platform — and your buyers — to see duplicates, stale prices, and panic titles.

If your floor still uses one instruction, "update Facebook," replace it with two: edit the live listing when the number changed, and post only when the VIN is not already advertised. Put both on a conservative ceiling, and stop giving reps credit for killing ads they should have edited.

PostToMarket holds unlimited vehicles in inventory on every plan, then posts through a paced Chrome extension instead of a 4 p.m. scramble. Starter is $59 per month for a solo seller or independent lot with one login. Dealership is $299 per month for up to 13 logins so managers can assign update work and new-post work to different people. Start your 10-day free trial with secure Stripe checkout. Cancel anytime.