You can sell Framer templates using an external checkout and deliver the template's remix link after payment. Create a clearly named product, prepare a delivery document containing the remix link and setup instructions, and connect the appropriate buying link to your sales page. If you also sell through the Framer Community, your checkout must meet its specific submission requirements.
This guide is for template designers who have a finished product and need to connect the sale to a usable copy of it. It covers the difference between a preview and a remix link, the delivery package, checkout selection and the checks to complete before launch. PayRequest can handle the digital product and its attached delivery file; the buyer uses Framer to copy and edit the template.
Choose Your Framer Sales Route First
Selling from your own Framer website and selling through a Community listing are related but separate routes. On your own website, you choose how to present the offer and link its buy button. For a Community listing, Framer specifies what the external checkout must provide. Do not assume that any public catalog or product URL qualifies.
Framer's Community payment requirements say the destination must lead directly to payment, identify the product and matching price, be public without a login before purchase, and include a clear refund or cancellation policy. Framer leaves payment processing and product delivery to the seller. Check the current requirements when submitting your product.
A preview URL serves a different purpose: it lets someone inspect the design. Framer's template publishing guide covers the submission materials and review process. Preparing a working checkout does not mean your template has been approved. Keep the listing review and payment setup as separate items in your launch notes.
If your immediate goal is selling from an existing personal site, begin there. Our Framer payment-button guide covers placing the link. This article concentrates on the paid template, delivery document and buyer handoff, so you can use the same prepared product wherever an appropriate checkout link is accepted.
Package the Remix Link as a Usable Product
The buyer needs a way to create an editable copy, not merely view your demo. Framer explains the distinction in its template usage guidance. Prepare the correct remix link for your release and check its destination before putting it in a delivery document. Avoid distributing an editor invitation or an unrelated preview link.
For a worked example, imagine a fictional product called Studio Portfolio v1. Its delivery file is Studio-Portfolio-v1-Start.pdf. The first page identifies the template, provides the remix link and explains what the customer should do next. Later pages describe replacing example images, checking responsive layouts, obtaining support and understanding what the purchase includes.
Use this original delivery outline as a starting point. Replace every bracketed item with your actual product information before uploading it:
| Part of the delivery document | Information to include |
|---|---|
| Product identity | [Template name], [release version], [delivery date] |
| Access | [Remix link for this release] and an explanation of the copy action |
| Requirements | Framer account and any publishing features the buyer must arrange |
| First edit | How to replace the example text, images and contact details |
| Purchase scope | Included pages, assets, usage terms and support scope |
| Help | Seller contact and the order reference to include |
Check the exported PDF itself. A link that worked in your writing tool can be missing or incorrect after export. Use descriptive linked text and also make the destination easy to identify. The file should remain understandable to someone who never saw your original sales conversation.
Only include assets you are entitled to distribute. If a preview uses demonstration photographs or fonts that are not included, explain the difference before purchase. State separately whether your service includes customization. A template download should not accidentally promise a completed custom website or a paid Framer hosting plan.
Create the Digital Product in PayRequest
Create the offer through PayRequest digital products, attach the approved PDF and set its name, currency and price. A ZIP can be useful if the purchase contains additional distributable files, but a single starting document is often clearer for a template whose editable version is accessed through a remix link.
The current PayRequest product model associates a delivery file with the product. Its download system supports PDF and ZIP files and order-related download access. Review the expiry and download allowance you configure through file delivery, then describe the actual access terms. Do not promise unlimited downloads if you configured a limit.
Copy the public product URL generated by PayRequest rather than constructing an address yourself. The product-specific route resolves the selected product before rendering the payment page. This gives you a useful starting destination for an external buy button, but the final customer experience still depends on your product, page and provider configuration.
Keep the listing and checkout recognizable as the same offer. For the fictional portfolio template, use Studio Portfolio v1 in both places, show the same preview image and state the same currency. If you have a separate customization package, give it a separate description and destination so a buyer can tell what they are purchasing.
Check the Checkout Before Connecting a Community Listing
Open the exact destination in a private browser window. Confirm that a visitor can identify the template and proceed with payment without browsing a general catalog or signing into the seller dashboard. Check the displayed price and seller policies. These observations matter more than whether the address happens to contain the word checkout.
The following review separates a public link from a Community-ready purchase route. It is a worksheet for your configured product, not a statement that PayRequest is an approved Framer integration or that a specific listing has passed review.
| Check | Expected result | If it fails |
|---|---|---|
| Destination | The intended template is already selected | Copy the specific product URL |
| Purchase route | Buyer reaches payment without unrelated navigation | Review the route before submitting it |
| Access | No seller login is needed to start purchase | Replace any dashboard or private link |
| Offer | Name, price and currency match the listing | Correct the stale offer |
| Policy | Refund or cancellation information is clear | Add the applicable seller policy |
| Delivery | Confirmed order leads to the correct release | Correct the attachment or delivery setup |
If your page introduces an extra product-selection step, do not submit it as a direct checkout merely because it works from your own site. Use a destination that meets Framer's requirements. This guide does not claim that an arbitrary PayRequest account configuration will pass Community review.
For your own Framer website, link the buying button to the reviewed product destination and publish the change. Keep the preview action separate from the purchase action. “Preview the template” should open the demonstration; “Buy Studio Portfolio” should lead to the offer that delivers its editable copy.
Verify Payment and Template Delivery Separately
A public-page check confirms where a link leads. It does not confirm a successful charge or delivery. Complete an authorized purchase check using your configured payment flow, then follow the buyer's order and download route. Record what happened rather than marking the whole journey complete after seeing the product page.
For the example product, the meaningful final outcome is opening Studio-Portfolio-v1-Start.pdf and following its remix link to the intended template. Compare the delivered document with your approved release. If it points to a previous version, fix the attachment even if the payment amount and order status are correct.
PayRequest's current download controller separates viewing the download landing page from the action that transfers the file. A visit alone does not consume the download allowance; the download action checks expiry and allowance. That distinction helps when investigating a buyer who opened an email but has not yet downloaded the document.
Delivering a PDF with a remix link does not create a native Framer entitlement or prevent the link from being copied. Download controls govern access to the delivery file, not every later use of its contents. Explain the product's usage terms and provide a support route instead of describing this as copy-proof protection.
Set Expectations for Updates, Support and Costs
Write down what happens when you release version two. Does an earlier buyer receive it, keep the original release or purchase an upgrade? Do not imply that replacing a file automatically updates every Framer project previously created from the template. The buyer's copy and your delivery package are different things.
Make support equally concrete. For example, you might help with opening the document and accessing the template while offering design changes separately. State your actual policy rather than copying this example. Include a contact method and ask customers to provide an order reference, not sensitive card information.
PayRequest pricing currently lists a Free plan with a 2% fee per successful payment, capped at €25 per transaction, plus payment-provider fees. For an illustrative €49 template, the platform percentage is €0.98 before provider fees and other applicable costs. Framer publishing costs and your support time are separate considerations.
Start with one release and one complete buying route. Create your PayRequest product, attach its starting document and review the customer experience before promoting it. For a Community submission, also complete the direct-checkout review above; for an existing site, connect the reviewed destination to its buy button.
Editorial note: AI assisted with this article and illustrative cover. Product routing and file-delivery behavior were reviewed in PayRequest code on 11 September 2026. The portfolio product and worksheets are original examples. No live purchase, Framer approval or customer sales results are claimed.