Independent research · Source-linked guidance
Home / Maintain releases / Retire a listing without accidentally removing old buyers’ files
Practical guide

Retire a listing without accidentally removing old buyers’ files

Last materially reviewed 2026-09-27

Quick answerSeparate selling visibility, purchase options and underlying files before retiring any part of the catalogue.
What to know

Name what should end

You may want to stop new sales, remove an option or replace a file. Those are different actions. Write down which behaviour should change and what previous buyers should retain before opening controls. A retired product is not automatically a cancelled customer entitlement.

What to know

Check the documented consequences

Payhip distinguishes deleting a variant from deleting its assigned file. Existing buyers can be affected differently. Read the current help and inspect the actual package rather than assuming a delete button only changes the public listing. Do not experiment with removal on a live product to discover the consequence.

What to know

Preserve the record

Keep the old description, manifest, revision and any continuing support commitment. A private archive helps investigate past purchases; it is not a substitute for legitimate customer access. If a replacement is offered, explain whether it is a correction, a new product or an optional upgrade.

What to know

Verify the narrow outcome

After an authorised change, check that new-sale visibility and historical-access expectations match the intended plan. Do not infer both from one dashboard label. If the platform cannot support the required arrangement, seek a clear provider answer before destructive changes rather than improvising with public file links.

What to know

An original working example

Prepare a before-and-after note with three rows: visible to new buyers, available as a purchase option, and files available to previous buyers. Describe the desired result in each row before touching the store. A fictional retirement may set the first two to no while retaining the third under the existing promise. If the provider does not document the required combination, ask a narrow question before deleting anything. Preserve a rollback or continuity plan where the service supports one. Do not call a private backup a complete customer-access solution; it helps your investigation but does not itself give an entitled buyer a usable download.

Continue when useful

Next: Keep a revision log that helps old and new buyers

Record what changed, which files changed and who needs the correction; a new date alone is not enough.

Open Keep a revision log that helps old and new buyers →
Keep exploring

Related guides

Keep a revision log that helps old and new buyersRecord what changed, which files changed and who needs the correction; a new date alone is not enough.Map each purchase option to its filesA variant is an entitlement choice: verify what each option delivers, not just how its label looks.Plan a store move without losing the purchase storyA new store does not automatically inherit old orders, access rights or communication permissions.

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Digital product variants — Merchant documentation · help.payhip.com · Merchant-controlled · checked 2026-09-27
  2. Adding a digital product — Merchant documentation · help.payhip.com · Merchant-controlled · checked 2026-09-27