A purchase record should help you reconstruct the agreement, not overwhelm you with screenshots. The useful collection is small: the product you selected, the conditions attached to it, the seller’s confirmation and the payment reference. Keep those pieces together while keeping credentials and unnecessary financial information separate.
This is a filing method you can adapt to any digital purchase. It does not determine a refund right or replace the seller’s actual terms.
Save the offer in context
Keep the page or message that identifies the specific product and complete quoted amount. Include the currency, term and any conditions that affected your choice. A tightly cropped price badge is weak evidence if the surrounding page explained that the figure was a monthly equivalent or applied only to a particular edition.
Give the file an ordinary name you will recognise later, such as the seller, product and order date. If the quote changes before purchase, keep the accepted version easy to identify. A folder full of similarly named images can be surprisingly hard to interpret when a question arises months afterwards.
Link the order and the transaction
Save the order confirmation with its reference, then retain the payment provider’s own transaction record. These documents serve different purposes. The order explains the product; the transaction explains the money event. A common reference or a short private note can connect them without merging them into one vague receipt.
Where the names differ, keep the explanation of the billing relationship. If a store handles a software purchase and a service seller handles viewing access, create separate entries. A later question about an app feature should not be sent with an unrelated service receipt merely because both were purchased on the same evening.
Keep the handover useful and private
Account handover material may contain sensitive information. Preserve what you need using an appropriate private storage method, but do not duplicate passwords into every document. A purchase register can point to the secure location without exposing the secret itself.
For support records, save the question, response and any reference that identifies the conversation. Keep enough context to distinguish an acknowledgement from a decision. If you received a revised arrangement, note which earlier message it replaces; otherwise an old instruction may look like the current one when you search your files.
Make the folder easy to close
At the end of the transaction, add a short plain-language note: what was bought, what remains unresolved and where future account or billing questions should go. This makes the record useful without repeatedly opening private financial pages.
Review the folder before sharing anything. Remove unrelated conversations and redact details the recipient does not need. You can retain originals privately while sending a limited copy. The objective is not to collect the largest possible archive, but to preserve a clear chain between the offer, your selection and what actually happened.
Useful answers
Should I keep every screenshot I took while shopping?
Keep the versions needed to understand the accepted offer and any later correction. Label irrelevant or superseded material clearly.
Can I put the service password in the receipt filename?
Avoid that. Use a non-sensitive order label and keep credentials in a separate private location.