Paid products are in private beta
Anyone can use a Digital Product to deliver a free resource. Paid checkout is currently available by invitation while Reroute completes the private beta.
Use a Digital Product Block to deliver files or an external resource after a free submission or paid checkout. This guide covers Product, Checkout, Confirmation, testing, and the records created after completion.
Choose free or paid delivery
Decide what the visitor is exchanging before you open the editor.
| Product | The visitor provides | Where the result appears |
|---|---|---|
| Free | Their email and any checkout details you request | Audience as a Response and Contact |
| Paid | Their checkout details and payment | Sales as an Order |
A free product is useful for a lead magnet or resource you want to distribute widely. A paid product is for a finished offer with a price, buyer access, and an order record.
Add the Digital Product Block
Open the page editor, select Add block, then choose Digital Product.
The editor has three stages: Product, Checkout, and Confirmation. Work through them in order because each stage answers a different visitor question.
- Product describes what the visitor receives and contains its delivery.
- Checkout collects the information needed to complete the exchange.
- Confirmation controls access after completion and the delivery email.
After these stages are complete, test the public route as a visitor.
Screenshot to add: Digital Product editor stages
Show Product, Checkout, and Confirmation in the editor navigation with a completed product visible in the preview.
Open: /app/page
Framing: editor stages and product preview
1. Describe the product
Give the product a name a visitor can understand without the surrounding post. Add a short description that answers:
- what is included;
- who it is for; and
- what someone can do with it after they open it.
Choose Free or Paid. For a paid product, set the price and connect payments when prompted. The paid Block remains hidden from the public page until payment setup and the required product details are complete.
Avoid inflating a simple download with vague claims. A useful description such as “12 Lightroom presets for warm indoor portraits, with an installation guide” gives the buyer something concrete to judge.
Screenshot to add: Product details and delivery settings
Show a concrete product name and description, free or paid selection, and the file or external-link delivery controls.
Open: /app/page
Framing: Product stage
2. Add the delivery
Upload files directly or provide an external link. A product can contain up to 10 files, which is useful when the download needs a guide, template, and supporting assets.
Use names that still make sense after the files reach someone’s Downloads folder. portrait-presets.zip is easier to recognise than final-v4.zip.
For an external resource, test the access rules in a private browser window. A link to a document that still requires your own account permission is not a working delivery.
3. Keep checkout focused
Email is required so Reroute can identify the recipient and send access. Add other fields only when they change how you fulfil or support the order.
For example, a name can make support more human. A long set of marketing questions creates work for the visitor without improving delivery.
A free product submission does not automatically subscribe the Contact to future marketing. If ongoing updates are part of the offer, ask for that consent clearly through a Subscribe signup.
4. Write the confirmation
Confirmation has two jobs: reassure the visitor that the exchange worked and make access easy.
Keep the on-screen message direct. Tell them the product is ready and where else the delivery was sent. Then check the delivery email so its subject, button, and support details describe the same product.
If the product uses an external link, the access button should open the final resource rather than an intermediate page that asks the buyer to search again.
Screenshot to add: Checkout and confirmation settings
Show the required email field, one optional field, the confirmation message, access button, and delivery email controls.
Open: /app/page
Framing: Checkout and Confirmation stages
Test the complete route
Open the public page and complete the product as a visitor. Preview alone cannot confirm the full submission, payment, and delivery path.
For a free product:
- Submit an email address you can recognise.
- Open the product from the confirmation screen.
- Check the delivery email and every file or external link.
- Find the submission under Audience in Responses and Contacts.
For a paid beta product, use the test process provided with your invitation. Confirm checkout, receipt, buyer access, and the Order under Sales before sharing the Block publicly.
Screenshot to add: Public product checkout and delivery
Show the product before checkout, its confirmation state, and the delivery opened successfully. Use test product and account data.
Open: /[slug]
Framing: three-step visitor sequence
Understand what Reroute records
A free delivery creates a Response and resolves the email to a Contact on that page. The Contact is recorded as not subscribed unless they separately gave marketing consent. Free deliveries do not create Orders.
A paid checkout creates an Order under Sales. The Order is the operational record for the buyer, payment, and product access. During the private beta, the Reroute platform fee is 10% on Free and 5% on Creator, in addition to payment processing fees.
Payment operations such as refunds and disputes are handled through the connected Stripe account. Use Reroute Sales to identify the order and Stripe to complete the payment action.
Manage orders and buyer access covers the Sales list, Order details, buyer recovery, and Stripe payment actions.
Screenshot to add: Audience and Sales records
Compare the Response and Contact created by a free product with the Order created by a paid test product.
Open: /app/contacts/responses, /app/contacts, and /app/sales
Framing: relevant record details with fictional data
If something looks wrong
The Block is in the editor but not on the page. Complete the required Product fields. Paid products also need payment setup before they can appear publicly.
The delivery email did not arrive. Check the email address used in the test, then confirm the delivery is attached and the email is enabled in Confirmation. Also check spam or promotions folders.
A free download is missing from Sales. Free products create Responses and Contacts under Audience, not Orders.
A buyer cannot open an external resource. Test the destination in a private browser window and change its sharing permissions at the source.
A paid product is unavailable. Paid checkout is invitation-only during the private beta. You can publish the product as free or wait until paid access is enabled for the account.
Check the product
- The name and description state what the product contains and who it is for.
- Every file has a recognisable name and every external link has open access.
- Checkout asks only for information needed to deliver or support the product.
- The confirmation screen and email lead to the same delivery.
- A public test appears in Audience or Sales as expected.
If the product should be delivered after an Instagram comment, connect this guide to Set up an Instagram auto-reply. If you want to understand the Contacts created by a free delivery, read Collect responses and build your audience. For paid private-beta transactions, continue with Manage orders and buyer access. For help choosing and validating the offer, read Launch your first digital product.