Prepare a Shopify digital product by defining what the customer receives, how access is delivered and what the support team should do when access or a refund needs attention. Check the actual app and destination settings before publication. Use the worksheet below to connect the product promise, order record, delivery route and access decisions into one understandable process.
What is the digital product promising?
Write the deliverable in terms the customer can recognise: the file or service, its intended use and the way it will be accessed. Identify any software, account or external destination needed to use it. Keep those requirements in the product brief so the public description can explain them accurately.
Shopify supports selling digital goods alongside physical goods. Documentation. Shopify gives downloadable art, video and audio as digital-product examples. Documentation. Choose the arrangement appropriate to the actual deliverable. A downloadable file and a link to content hosted elsewhere need different operational questions. Ask who maintains the asset, who approves an update and what record identifies the version supplied to a customer.
Prepare the product description and support instructions together. If the customer needs help locating a delivery message or opening a file, the support team should know which order and asset references to request. Keep the instructions focused on the intended product rather than assuming every digital purchase behaves the same way.
How should delivery be configured?
Shopify Digital Products sends digital items automatically by default without an access limit. Documentation. Review that default against the intended customer promise before relying on it. Decide whether the item should be delivered automatically or whether a person must complete a defined review first. Record the actual choice and the conditions under which the product is ready to release.
A manually sent variant does not show its download link on the Thank you or Order status page. Documentation. Include the selected delivery method in a controlled customer-journey rehearsal. Ask the reviewer to follow the actual route the customer will use, including relevant email and order-status information. A manual process needs a named operator and an understandable handover.
Shopify Digital Products accepts product links only from supported providers. Documentation. Shopify Digital Products does not accept product links from other websites. Documentation. The Digital Products app lists its supported providers when a link is added. Documentation. Check that the intended provider is listed and the actual product URL is accepted before choosing linked-content delivery.
Purchased external-link products send the customer an email linking to a download page. Documentation. For a linked product, inspect the destination as well as the delivery page. Confirm that the approved content is available through the intended sharing arrangement and that the support owner can identify it. Keep any external account requirement visible in the product description and evaluation brief.
An original digital-delivery worksheet
Use this practical checklist for one product or variant. Fill it with the actual app, asset and order references when preparing the configuration. It is an original acceptance aid for delivery and access handling.
| Boundary | Information to specify | Question before publication |
|---|---|---|
| Product promise | File, service or external content and relevant requirements | Can the customer understand what they are buying? |
| Asset identity | Approved version and responsible owner | Which content should this order provide? |
| Delivery method | Automatic or manual route | What event makes the content available? |
| Provider eligibility | Provider listed in the app and actual URL acceptance | Is this a supported linked-content route? |
| Access arrangement | Link, count and destination sharing settings | Which control governs the customer’s access? |
| Customer support | Order reference and recovery instructions | Can staff locate the intended delivery? |
| Refund decision | Actual published policy and authorised decision-maker | What action is appropriate to this request? |
| Access change | Intended revocation or continued-access treatment | Has the relevant control been identified? |
| Update | Revised asset and affected delivery references | Who approves and verifies the change? |
Keep the business’s actual refund terms and applicable requirements with the authorised owner. The worksheet connects a decision to the operational action needed to carry it out; it does not supply invented refund periods or rights. Have the public policy and the support workflow reviewed together for the actual product.
Include an exception row for a delivery that reaches the wrong destination or a customer who cannot locate the message. Define which evidence staff need before changing access or resending information. Keep the resulting support decision connected to the order rather than only to an email conversation.
What does an access limit actually count?
Digital Products can limit how often a customer opens or downloads an asset. Documentation. The access limit applies to each received link rather than to the customer overall. Documentation. Files within a variant share an access count. Documentation. Read the configured rule in that scope before explaining it publicly. Ask the demonstrator to show the intended limit using a controlled product and customer, then compare the observed behaviour with the wording the customer will read.
Avoid treating one access setting as the complete protection model for every destination. Record which control belongs to the Shopify app and which belongs to an external hosting or content service. The support owner needs that distinction when a request involves replacing a link or changing access.
Where the product includes several files, ask how the intended customer journey uses the shared count. Rehearse the relevant sequence rather than testing only the first click. Retain the expected and observed treatment with the selected configuration version.
Hypothetical example: a refund decision requires an access review
Imagine a customer requests a refund for a product delivered through an external content link. The business makes the decision under its actual policy and requirements, then asks the support team to apply the intended access treatment. This hypothetical example focuses on the operational handover after that decision.
First choose a provider from the app’s supported list and check acceptance of the exact test URL before preparing the linked product. Record that result in the provider-eligibility row; resolve a rejected URL before the delivery or access rehearsal. Then locate the order, delivered link and external destination. Deactivating a purchased download link does not affect share links or directly saved destination URLs. Documentation. Fully removing access to an external destination also requires changing its provider-side sharing settings. Documentation. Identify the settings relevant to the approved action instead of assuming that one deactivation control affects every copy or route to the content.
Use a controlled test destination to rehearse the intended change. Check the relevant delivered link and destination access through the authorised test arrangement. Record which part was changed, what was observed and any remaining action for the external content owner.
Then consider a customer who should retain access after an unrelated support correction. The proposed workflow should distinguish that case from a revocation decision. Keep the authority and reason for each action visible so an operator does not remove useful access merely to tidy the record.
What should be checked before the product goes live?
Compare the public description, approved asset, delivery method, access settings and support instructions. Use a representative order in the appropriate controlled environment and retain the actual observations. Resolve unclear destination ownership before relying on the product for ordinary customers.
Keep provider eligibility with the Shopify payment guide. Discuss the catalogue and customer journey through online stores and web development. Get started with the deliverable, delivery route and access questions you need to support.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.