Selling the same design twice

In this trade, exclusivity is frequently the largest part of what a buyer pays for. It is also the part most easily lost, not through dishonesty but through filing. A design that has been sold does not stop existing in the collections you already sent, and nothing in those files knows the sale happened.

Every studio understands this in principle. The reason it keeps happening anyway is that the mechanism is invisible: no alert fires, nothing is deleted, and the mistake usually surfaces months later, in front of the buyer who paid to be the only one with it.

What exclusivity actually means when you sell it

It is worth being exact, because “exclusive” on an invoice can mean several different things, and the differences are where accidents live.

• Outright buyout. The design leaves your collection entirely. It goes wrong when it stays in the archive you show, because removing it was a manual step nobody did.
• Exclusive licence, one application. You may sell it for a different application if the contract says so. It goes wrong when the second buyer’s use overlaps and neither of you notices until production.
• Exclusive licence, one territory. You may sell it elsewhere. It goes wrong because territory rarely maps onto where finished goods actually end up.
• Non-exclusive. You may sell it as often as you like. It goes wrong when the buyer believed it was exclusive because nobody said otherwise.

Notice that only the first is a filing problem. The rest are agreement problems, and no software fixes those. What software can fix is the first, and it is the one that occurs most often.

The four ways it slips

• The old file keeps circulating. The collection you sent in February is still in four inboxes, and one of those buyers opens it in September.
• The archive was never updated. Removing a sold design means editing a folder, a spreadsheet and a PDF. Under deadline that happens later, and later becomes never.
• Nobody owns the record. If an agent also sells your work, or a colleague sends collections too, the sale lives in one person’s memory or inbox.
• The design changed shape. A recolour or a variant is filed as a different piece, and its relationship to the sold original is only in your head.

None of these require anyone to behave badly. They are all consequences of a collection existing in more than one place at once.

You cannot recall a file. Once a collection has left as an attachment, the only accurate copy is the one you never sent.

What actually prevents it

The fix is structural rather than procedural, and the distinction matters: a procedure is something you must remember at your busiest moment, which is exactly when you will not.

• One place the collection lives. Not a canonical copy among sent copies. The only copy, at an address, which is what buyers open.
• Sold status attached to the design, not to a document. Recorded once, applying everywhere the design appears.
• Withdrawal that happens on its own. When a design is taken, it stops appearing for other buyers without you editing anything. The buyer who bought it keeps seeing it, because it is theirs.
• A record you can check. Who saw what, and when. Not for suspicion, but for the ordinary business of answering a question about a design from eighteen months ago.

The last point is the one studios underrate. Most exclusivity trouble is not a dispute; it is an inability to answer a simple question with confidence, in front of someone who is paying for certainty.

What this is worth

The cost of getting it wrong is rarely a lawsuit. It is a converter who quietly stops treating you as a first call, which is a slow, unattributable loss. In a trade that runs on relationships and repeat seasons, being the studio nobody has to double-check is a commercial position, not an administrative one.

One caveat worth stating plainly: the four forms above describe common trade practice, not law. Terms vary by contract and by country, and anything that matters belongs in writing with someone who knows your jurisdiction.

Withdrawing sold work automatically is one of the reasons MyDesignDeck exists. It is a setting, not a discipline.