Half your listing copy is a setting somewhere else

Write a listing and you will produce two kinds of sentence without noticing the difference. The first kind is a judgement: this leather softens with use, this is the one to buy if you cycle to work. Nobody can falsify it by changing a setting. The second kind looks exactly the same on the page and behaves nothing like it — it reports a number that is configured elsewhere. Dispatch in two working days. Returns for thirty days. Six bars to a box. Free delivery over a threshold. Each of those is a reading taken off some other screen at the moment you wrote the sentence, and then frozen.

The drift is silent by construction

Nothing about changing the original tells you the copy exists. You go into the shipping profile because a courier changed, you move two days to four, you save, and the job is done — the profile is the thing that governs what actually happens, so changing it is the whole fix as far as the system is concerned. The sentence on the listing is in a different tool, written months earlier, and it is now wrong. There was no error, no warning and no diff; a settings page does not know what you once typed about it.

That asymmetry is what makes this a different problem from an ordinary typo. A typo is wrong the moment you make it, and somebody notices. A readings sentence is right when you write it and becomes wrong later, which means the one moment anybody was paying attention to it has already passed.

Which of your sentences are actually settings

Worth going through your own listing once with this question: if I changed something in the admin tomorrow, would this sentence become false? The usual culprits:

• Dispatch and delivery times — set in a shipping profile, written in the description, and usually quoted again in an FAQ answer.
• Return and exchange windows — a policy field that also appears in prose, often with a different number because one of them was updated.
• Stock and availability language — 'only a few left', 'made to order', 'back in stock weekly'. Inventory moves daily; the sentence does not.
• Quantities and bundle sizes — six to a box, three colourways, a set of four. These change when packing or supply changes, and the copy is rarely part of that decision.
• Price-conditional offers — free shipping over a threshold, a discount above a quantity. The rule lives in a promotions engine and the sentence lives in your description.
• Anything about your own process that is really a tool setting — how many photos you shoot, how long a video is, how long somebody has to raise a problem.

That last one is ours, and this post exists because we failed it. On 20 October 2026 an audit of this site found six operational settings written into twenty-two of our own public pages, including the homepage — the longest film we will render, the sizes a photo set comes in, how long you have to report a render that does not match your product, how many reference photos one shoot accepts, the catalogue batch ceiling, and the free preview. All six were accurate. None of them was checked by anything. Each is a number an operator can change on an internal page in two seconds, with no deploy, no diff and nobody reading the copy afterwards.

The fix is not an audit, it is a smaller surface

The instinct is to schedule a review: read all the copy every quarter and fix what has drifted. That works for about two quarters and then stops, because it is a separate job that competes with everything else and produces nothing visible when it finds nothing. The durable version is to reduce how many places a number can appear.

• Prefer the platform's own field over a sentence. Dispatch time, returns, stock and shipping thresholds all have structured fields on every major platform. The field is rendered from the setting, so it cannot drift, and search engines read it in preference to your prose anyway.
• Where you must write it in prose, write it once. One canonical sentence, in one place, linked to from everywhere else rather than restated. Two copies of a number will eventually be two different numbers.
• Attach the re-read to the change, not to the calendar. Keep a short note beside the setting itself — 'also stated on the product description and the FAQ' — so the person moving the number is the person who fixes the sentence, at the moment they already have it in mind.
• Where a number is genuinely load-bearing, make the disagreement loud. We now fail our own site build when a published sentence and the setting behind it disagree, which converts a silent drift into something that cannot ship.

Why this costs more than it used to

A stale number used to be wrong only on your page, and only until somebody noticed. That is no longer the shape of it. Product copy is lifted — into search result snippets, into shopping surfaces, into the answers assistants generate when a shopper asks whether a shop delivers in time for a birthday. Those copies are made on a schedule you do not control and cached for a while after that, so a sentence you corrected this morning can keep being quoted for weeks.

The practical consequence is that the window in which a wrong number is only your problem has closed. It becomes somebody else's quotation quickly, and the correction travels slower than the mistake did. That raises the value of the boring discipline above more than it raises the value of writing better sentences.

A short test before you publish

Read your listing one line at a time and mark every sentence that would become false if you changed a setting tomorrow. For each one, answer two questions: is there a structured field that could carry this instead, and if not, where else on my site is this same number written? If the answer to the second is 'I am not sure', you have found the thing that will go stale. It will not announce itself when it does.