Pattern Update Checklist for Multiple Storefronts

A corrected pattern is ready for customers only when the revised file reaches the places where they obtain it. If you sell through multiple storefronts, treat the update as a small release: one approved file, one version label, and a checklist of destinations.

You can manage this with a spreadsheet. The essential step is recording what has actually been published rather than relying on a remembered upload.

Prepare the release before uploading

1. Confirm the issue and which sizes or sections it affects.
2. Have the replacement instruction checked.
3. Update the source document and its version label.
4. Export the PDF and inspect the affected pages.
5. Write a short correction summary and list affected versions.
6. Save the approved file in a clearly named release folder.

Use an unambiguous name such as Meadow-Cardigan-v1.2.pdf. Avoid using several files called “final.” Keep a copy of the previous release so you can answer questions from customers working from it.

Use one row per destination

This is an example checklist, not a list every designer must use. Include only your actual sales channels. If a retailer controls its own downloads, record that you have sent the update and leave the destination pending until it is confirmed.

Ravelry already offers an update process. Its customer update guide describes notifications and access to updated files. Use the features available in each channel; an extra tracker need only record completion.

Check the file the customer receives

An upload confirmation is useful, but verify the download when your storefront provides an appropriate preview or test method. Check the version label and corrected page in that copy. If you cannot verify a destination, record it as unverified rather than complete.

The same applies to translated or alternate-format files. If only the English PDF was corrected, do not imply that every format has changed.

Write a useful customer update

State the pattern, new version, affected sizes or pages, and where to get the updated file. Explain whether the change corrects an error or clarifies wording. Avoid a vague “please download again” message that leaves someone halfway through a project unsure whether they need to act.

The errata template provides a structure for that explanation. Keep customer messages aligned with the public correction record.

Leave an auditable end point

Record the release date and completed destinations. If one channel remains pending, give it a next action. This is especially useful when an assistant handles uploads while you or a tech editor verify instructions.

ErrataDesk is an early-access concept for this manual issue-to-release workflow, planned at $9 per designer per month with one pattern free. It does not automatically publish to storefronts or write corrections. Send an inquiry to discuss availability and your current process. No payment is collected through the inquiry form.