Freeze the listing copy before you freeze the build

Teams freeze binaries with care and then edit store listings on the day of submit. The listing is part of the version users receive. If it names a feature you pulled, or omits a limitation you accepted, the freeze is incomplete.

Treat listing copy, screenshots, and questionnaire answers as artefacts with owners, the same way you treat a candidate build. They should match the version, the languages you claim, and the limitations you are willing to ship. A screenshot from a previous freeze that still shows a removed button is not a small mismatch; it is a promise you are no longer keeping.

For teams shipping both English and Bahasa Malaysia, the two listings drift independently unless someone is named to keep them together. We have read packets where the English listing mentioned a hold on payments and the Malay listing did not. Support received the tickets the English readers never sent.

Enterprise distribution has an equivalent: the note you send to the admin who pushes the internal build. If that note is a forward of the engineering changelog, you have not briefed the admin. Write the same limitation list you would put on a public store, minus the marketing sentences.

Put listing freeze on the same calendar as binary freeze, a day earlier if the copy needs translation. The go/no-go packet should include the final text, not a reminder to “update the store later.”