Changing a Design Mid-Season Without Splitting the Store

Somebody spots a typo. A new coach wants the mascot updated. A sponsor is added. Whatever the cause, a design changes while a store is running, and now two versions of the same item exist — one worn by the families who ordered early, one by everybody after.

The short answer: decide first whether this is a correction or a new version, because they call for opposite handling. Then change one thing at a time, with a written record of which file is current.

Correction or new version?

This is the whole decision, and it is worth ten minutes before anything is edited.

A correction fixes something that was wrong: a misspelled name, an incorrect year, the wrong colour. The earlier items are defective in a way that was nobody's choosing, and the previous file should stop being used immediately.

A new version is a deliberate change to something that was not wrong: a refreshed mark, an added element, a different arrangement. Both versions are legitimate, and the earlier one is not a defect.

The difference drives everything downstream. A correction raises the question of what happens for people who already received the wrong thing — a question for the organization and its provider, since what is possible depends on how the items were made. A new version raises no such question, but does raise the question of whether both remain available.

Write down which one it is before proceeding. Almost every mid-season mess starts with this left ambiguous.

Do not overwrite the old file

The most damaging habit is replacing the artwork file in place, under the same name.

Once that is done, there is no way to tell which version any given order used, no way to reproduce the earlier one, and no way to answer "is this the current art?" — the question the next coordinator will ask first.

Keep both files, with distinct names that say which is which and when each became current. Artwork is part of the brand record, and keeping a team store on-brand is exactly what a lost or ambiguous file undermines: mid-change is when a file goes missing.

Record, in one place: which file is current, from what date, what changed, and who approved it.

Decide what happens to what is already listed

A change mid-store leaves listings in an inconsistent state, and every option is defensible as long as it is chosen.

• Replace everywhere. Only the new version is available from now on. Simplest, and the right answer for a correction.
• Run both. Each is listed separately and clearly distinguished. Honest, but it needs naming that makes the difference obvious.
• Close and reopen. Stop ordering, make the change, restart with one version. Disruptive, and sometimes the cleanest for a substantial change.

If you run both, the naming does all the work. A store showing two items that look nearly identical with nothing in the name to separate them produces orders nobody can interpret. Extend the existing naming pattern to cover versions rather than inventing something ad hoc — then write the pattern down alongside the rest of the store's rules, the way product names and descriptions sets out.

Tell people, once, plainly

Anyone who ordered before the change will notice, at distribution if not before. A short message when the change is made costs far less than the conversation at the pickup table.

Say what changed, when, which items are affected, and what someone should do if they have a question. Do not state what will happen about already-ordered items unless that has actually been decided and confirmed — an unconfirmed reassurance is worse than an acknowledgement that the question is open.

Write down why

Six months later, somebody will find two versions of a design and no explanation, and will have to guess which is current. That guess is how a superseded file gets reused.

The record needs four things: what changed, when, why, and which file is current. It belongs with the rest of the operating record that passes to whoever runs the store next, as the handoff guidance describes. It is a paragraph, and it is the difference between knowing and guessing.

Frequently asked questions

What is the first thing to decide when a design changes mid-season? Whether it is a correction to something wrong or a deliberate new version. They are handled oppositely, and leaving it ambiguous causes most of the difficulty that follows.

Should the old artwork file be replaced? No. Keep both with distinct names and a record of which is current from when. Overwriting removes any way to tell which version an order used or to reproduce the earlier one.

Can both versions be sold at the same time? Yes, if they are named so a buyer can tell them apart. Two nearly identical listings with indistinguishable names produce orders nobody can interpret later.

What do we tell people who already ordered? What changed, when, which items are affected, and who to ask. Do not promise anything about replacements unless it has been decided and confirmed, since what is possible depends on how the items were produced.

What should be recorded? What changed, when, why, and which file is current. Without it, the next person finds two files and guesses — which is how a superseded design gets printed again.