Skip to content
Interface language: English
Design / Signal

After buying a file: from order to a working download

Design delivery of a purchased digital file from order confirmation through recovery and updates.

Article language: English

Two people beside a table in front of a large circular structure overlooking a landscape.
In this article

A customer buys a decoration template and closes the confirmation tab. In the evening they return to work. They find the email, but its button opens a login for an account they never created at purchase. The file exists, the order exists, and the paper decoration remains exceptionally digital.

This fictional shop sells sets for customers to print themselves. For the customer, delivery ends only when they find the right asset and can use it. The page design should guide them through access to the purchased file, an interrupted download and a later return. An elegant product page alone does not describe that route.

Order, entitlement and a file ready to download

Map what causes an asset to become available. An order record may precede confirmation required by the shop. A file may also await manual preparation, for example for a personalised template. A “Download now” button should not appear merely because the browser returned to the thank-you page.

WooCommerce makes download availability dependent on product and order settings. The option to grant access after payment can make files available while the order is still processing, without waiting for completion. This is a rule of a particular system. Customer messaging should describe the consequence rather than transfer an internal status name without explanation.

Our example can have two clear views. One confirms receipt of the order and indicates where file information will appear. The other shows the ready set and download option. If a file needs preparation, establish the real next step. Do not replace a missing rule with an endlessly repeated “Almost ready”.

The ready-asset page should identify the order item. The customer bought the Leaves decoration in an A4 print format, so that name and variant should be visible. A generic “Download file” button for several different orders invites confusion. If a set contains several elements, show whether the button downloads the whole package or one item.

Names, format and version help identify a file on a computer later. These are also addressed in designing a download centre (in Polish). Purchase delivery additionally identifies the order and why a specific customer is entitled to download. A public library and fulfilling a purchase need different paths.

For several purchased files, do not equate one being ready with the entire order being ready. A standard set may be available immediately while a personalised card awaits preparation. Show both states beside the correct items. A customer should not mistake the missing card for an archive error merely because the main heading says “Everything ready”.

Agree the role of messages too. They may confirm an order, deliver a ready file or report an update. Shop transaction messages (in Polish) should distinguish these events in subject and body. Do not send two nearly identical thank-you messages, only the second containing the important button, without recognisable readiness information.

The process owner should know who resolves a case where the order is accepted but no file appears. The variant-to-asset link, file preparation or notification might fail. The customer page should show the confirmed state and a help route retaining the correct case number.

Before designing downloads, distinguish delivery of a copy from entry to an asset in another service. Shopify Digital Products describes an uploaded store file and a link to content hosted by a supported external provider. In the latter case, login and content permissions are configured with that provider. The purchase alone therefore does not explain the full opening route.

In our example the purchase is a printable file. If the shop instead sold access to an editable project in another service, it would need to show the required account and entry route beforehand. “Download PDF” would not fit that action. Preserve the promised asset form in the purchase summary. A customer should not discover afterwards that obtaining a copy requires another program or access to a project in another system.

Returning without an account and recovering a download

Guest checkout (in Polish) also requires a way back to the purchased asset. An account may help find history, but should not unexpectedly become a delivery condition on a route that did not anticipate one. Record how an entitled customer reaches the file after closing the first page.

In the decoration shop this might be an email linking to the specific order. The recipient should recognise the sender, set name and button purpose. If the link needs additional verification, explain that step where used. Someone unable to use the original email address needs a separate clarification route consistent with the company's actual process.

Do not design recovery as entering any order number and immediately displaying a file. A number helps find a case but need not itself establish the requester's right. The responsible team defines verification scope. The interface should show the next step without revealing another person's purchase history to a random visitor.

Shopify Digital Products documentation describes resending a message with the same links while retaining prior limit usage. Resending a message and increasing available download count are therefore different actions in that application. A shop's help screen should distinguish a lost message from exhausted access.

Aeneia conceptual photography

When resending, show the destination address to the extent appropriate for that route. A typo at purchase can send further messages to the wrong place. Changing the address is a different action from resending, however. It requires appropriate entitlement verification and confirmation of the new contact under shop process. Support should see whether data was corrected or delivery merely repeated. The user then receives a specific account of the help provided, rather than “resent” without changing the cause.

Likewise distinguish an expired link, a deactivated link, an exhausted limit and a download error. These are not four ways to say “try later”. Expired entitlement may need support to restore it. A connection error may call for returning to the same available item. The message must follow the confirmed state the system can actually recognise.

Before starting, state applicable limits. If access has an expiry, show it beside the asset and in the relevant message. If there is a count limit, establish what consumes it in the solution used: starting a request, completing a transfer or opening a link. A customer should not discover only after an interruption that an unsuccessful attempt was counted.

In our fictional route a person opens the message on a phone but wants to print from a computer. This needs a considered handoff of a task to another device (in Polish), preserving a recognisable order and asset. Buttons should not suggest that opening a page on a phone completed a download to a computer.

Do not replace access to a purchased file with a general link for everyone without explanation. Conscious sharing design (in Polish) distinguishes an address for authorised people from wider circulation. Post-purchase help concerns recovering the correct asset for the buyer. A quick workaround can change the audience while apparently solving only one message problem.

With Aeneia Design, you can discuss the order page, message and download-recovery route and agree on the scope of their design. Real shop settings and examples of exceptions provide material for that discussion. The aim may be to describe available actions on buttons and agree with support on a delivery method for the purchased set.

What was downloaded, and what is available after a correction?

Clicking a button starts a download attempt. It does not confirm that the file reached the selected folder or opened in the required program. A page can show the start and instructions for finding it in the browser, but a completion message needs an appropriate basis. Do not write “Your set is already on your computer” when the page knows only about a click.

MDN describes the Content-Disposition header, which indicates display in the browser or download as an attachment and may suggest a filename. This is a server-response setting. Design should distinguish buttons opening a preview from those starting delivery of a copy, and test the solution's actual behaviour.

For acceptance of a test order, also open the downloaded package. The Leaves set should contain the correct sheets and instructions if included in the purchased item. Record the version and variant compared. Do not treat a technically successful transfer of the wrong set as successful delivery. The customer did not order any arbitrary file with a valid extension.

If the package has three elements, acceptance should cover each: cover, printable sheets and instructions. Opening the cover PDF does not confirm the sheets and separate instructions are present. A test record can state which items were opened, on which device and what was compared with the offer. If one item fails, the help route should retain the set and faulty filename. The team can then correct the asset rather than ask the customer to recount the entire purchase.

A change to an asset after purchase needs a known rule. Does a corrected file replace the earlier one under the same access? Is it a new separately granted item? Should the buyer be informed? These are fulfilment decisions for the particular offer, not conclusions to guess from an “Add file” button in a dashboard.

WooCommerce distinguishes changing an existing file row from adding a new one: the former updates links for past purchases; the latter does not automatically grant them a new download. According to its documentation, changing an existing row preserves expiry and remaining download count. Consider these details when designing updates in that system.

If the shop fixes a template error, replacing a file alone may not resolve a customer whose access expired or was exhausted. The team needs a route to deliver the current version under agreed rules. A correction notice should lead to an asset the recipient can actually open rather than another access-denied message.

Include a customer who downloaded the old version and someone who has not started in an update trial. Record the expected result for each. Also prepare an earlier message opened after the asset changes: which version should its address lead to? This tests the actual correction flow. Checking only a newly generated button in an admin panel misses old links still in buyers' inboxes.

For multiple editions, show which was downloaded and what the current button leads to, within data the shop has. An internal server history does not always say whether a customer retained and opened a particular copy. Help recognition through name and version without attributing knowledge of later work on another person's device to the system.

For acceptance, choose a guest order, close the initial tab and return to the file as the buyer would. Then test a lost message and an available correction. Delivery works when the recipient reaches the right asset with their entitlement preserved. Only then can they get on with the paper instead of studying the shop's organisation.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear