A Preorder Is a Version Promise

Set the promise first

A preorder is a public promise that a specified product will be available on a stated date or window. Before opening it, freeze the working title, contributor display, format, identifier, description, and expected release date in a launch sheet. Mark each field as confirmed or provisional.

For a hypothetical guide, do not advertise “fully illustrated” while maps are still being commissioned. Say only what the scheduled edition can plausibly contain.

Control file changes

Name the submitted file and cover version. Keep a list of changes after preorder goes live: typo correction, new foreword, revised publication date, or new illustration. Update every reader-facing record that the change affects; do not assume a single dashboard updates all channels.

Plan the difficult date

Work backward from the release date through proof approval, conversion, metadata review, and partner lead time. If the date moves, communicate the change plainly and preserve the reason in the internal record.

Specific production checks

Send a preorder test link to someone outside the production team and ask them what they believe they will receive, on what date, and in what format. If they cannot answer from the listing, revise the description and format labels. Avoid calling a provisional cover “final” until it is approved.

Create a release-day checklist that includes turning the preorder asset into the final listing, checking purchase links, and comparing the delivered file with the promised version. If an essential change slips, publish a short factual update rather than silently hoping readers do not notice.