When to run a listing batch

Run a listing batch when aged metal needs truthful ads and the desk is ready to review drafts — not when you want the OS to publish by itself. The default pool is available units sitting 30 days or more. Oldest days-in-stock go first. Sold units stay out. The batch writes listing_copy drafts into Approvals. It does not post to Cars.com, Autotrader, or Facebook.

Listing Studio’s “Draft aged copy” control and the AgentOS cron job aged-listing-drafts both use that same rule. Cron can fire on a rooftop-local schedule (the seed job is 07:00). autoSend and autoPublish stay false. A person still opens each draft, edits the facts, and decides whether it goes out.

Keep batches small enough to review. Copy batches cap at 25 units; photo batches cap at 17 (a full gallery). Prefer available + aged unless you explicitly pick stock numbers. Pending can be included when you mean it; wholesale is a desk call; sold is never a listing target.

Price lines follow the unit card. Asking prints only when inventory has a price. Otherwise the draft says “see store.” The batch will not invent MSRP, APR, or a monthly. If the card is thin, the draft stays thin — that is correct.

Photo batches only include units that already have lot stills. No still, no photo job. Do not substitute a catalog hero to fill the gallery. After the batch lands, work the HITL queue the same day so aged units do not sit behind a pile of unreviewed drafts.

Skip the batch when inventory is wrong (bad YMM, missing stock, leftover sold rows) or when nobody is on Approvals. A scheduled job is not a reason to lower the integrity bar. Batch is a queue-builder for this rooftop’s aged units, still HITL.