Put the first action first
Open with a plain instruction such as which document begins the process. Follow it with a compact file list and the current revision. Avoid starting with several pages of promotion, social links or a demand to join another service. The buyer has already purchased; the readme should help them use that purchase.
Separate the product from the process
Describe file extraction, format selection and support independently from the pattern’s creative instructions. A seller may need to explain different print layouts, but this guide does not supply or validate the actual pattern settings. Put product-specific requirements in the correct document and ensure the readme points there accurately.
Make help recognisable
State the store name, support address and useful order information to include. Ask for the minimum needed to identify the transaction; never ask a customer to email passwords, full card details or unrelated identity documents. A screenshot of a problem should omit payment information and private download tokens.
Keep it consistent
Compare the readme’s file names, version and support route with the product listing and receipt. When one changes, inspect the others. A readme cannot replace an accessible product description or rescue files that were never assigned to the purchase. It is a small navigation aid, not evidence that the entire buying journey works.
An original working example
A compact original outline is: “Start here”, “Your files”, “Choose a format”, “Current revision” and “Help with this purchase”. Under “Your files”, explain the purpose rather than repeating the extension. Under “Help”, list the order reference and product revision that make a question actionable. Do not include private credentials or a universal customer download link. Read the outline on a narrow screen and check whether its first action remains visible without scrolling through promotional material. If the readme must explain a complicated workaround, reconsider the package structure first; a long instruction document can conceal a simpler problem in how the files were grouped.
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.
- Adding a digital product — Merchant documentation · help.payhip.com · Merchant-controlled · checked 2026-09-27
- Customer did not receive email — Merchant documentation · help.payhip.com · Merchant-controlled · checked 2026-09-27