Create reusable products under Monetization, upload storefront images and download files, activate when payouts are connected, and link buyers to /products/{slug}. After checkout, buyers re-download files from Account → Library. Use the Products block to list active products on any page, or attach products to paywall gates.
Create a product
Open Monetization in the organization sidebar (after payouts setup, or from the setup card).
Click New product.
Choose a site (storefront host) or leave the product org-wide so every site in the organization can sell it.
Enter a name and slug — the slug becomes the public URL segment (/products/your-slug). Slugs are unique per site; org-wide slugs are unique across the organization.
Choose One-time or Recurring billing. Recurring subscriptions require Stripe card payments — PayPal checkout does not support subscriptions. Recurring products can set monthly/yearly cadence and an optional intro discount percent.
Set a price and currency.
Save as draft while you finish assets, then Activate when you are ready to sell.
Open any product from the list to edit it in the two-column editor: storefront images on the left, pricing and files on the right.
Storefront images
Upload one or more 3:4 portrait images for the public product page carousel — the same crop the storefront page and Products block use, so the editor preview matches what visitors see.Click Add image to open the org asset browser: pick existing library media or upload new files without forcing a re-upload. Images attach to the product by URL; removing one here only drops the link if other content still references the same file.
Images from the library store as canonical /api/media paths and render signed in the editor and on the live storefront (product page, Products block, Product Showcase). See How media URLs work.
If a product has no images, the page still renders with title, description, and price.
Download files
Attach the files buyers receive after purchase (PDFs, ZIPs, audio, and so on):
Each file can be up to 200 MB
Uploads go directly to private storage — the browser PUTs bytes to a signed URL, so large files do not pass through the app server
Files are optional — a product can sell access only (for example, unlocking a gated page) without a download payload
Files are never exposed on the public product page — buyers access them only after checkout through their signed-in Library (see below).
Buyer library
After checkout, signed-in buyers open Account → Library in the Aveiro account portal to:
Your products — entitled downloads with one-click Download buttons (files are served through short-lived signed URLs)
Purchase history — site name, date, amount, and payment status for past orders
Buyers who are not signed in during checkout get an account automatically; returning visitors can sign in and open Library from the account menu at any time. Gated pages unlock in place on the site — the Library focuses on downloadable files and purchase records.
Retiring is reversible — useful when you pause sales without deleting history.
Public product pages
Each active product on a site resolves at:
https://your-site.example/products/{slug}
The page shows images, title, description, price, and a Buy button. Checkout runs through Stripe on your connected account.
For EU digital content, buyers must acknowledge the no-refund / withdrawal waiver checkbox before checkout starts — the product page enforces this before redirecting to payment.
Fourthwall merchandise uses /shop/{handle} instead, so both catalogs can coexist on one site.
Customize the product page
When you create a product scoped to a site, Aveiro automatically creates an MDX page under Pages → products in the site editor. The page includes a locked Product Showcase block that renders images, price, and checkout from your Monetization settings.
You can add headings, copy, FAQs, testimonials, or any other components above or below the showcase, then publish the site as usual. The showcase block itself stays fixed — you cannot drag, delete, duplicate, cut, or edit its source. Pricing, images, and download files always come from Monetization → Products.
Visitors see the published snapshot of the product MDX page — edits in the site editor reach the storefront only when you publish the site, the same as any other page. A product page that has never been published falls back to the hardcoded layout. Embedded <Media> and <Carousel> blocks in the MDX body store canonical /api/media paths and are signed on read for live visitors and for members in the editor preview — see How media URLs work.
Org-wide products and older site-scoped products without a content file keep the standard hardcoded layout at /products/{slug} until you add a custom page manually.
To edit a product page, open the site editor, go to Pages → products, and select the product slug. Publish when your surrounding copy is ready.
Products block
In the site editor, open Components → General and insert Products:
Lists this site's active products (newest first)
Layout: grid or column, with configurable columns and max count
Toggle title and price on each card
Each card links to that product's /products/{slug} page
Unlike Store collection (Fourthwall), there is no external collection handle — the block always reflects your Aveiro product catalog.
Paywall gates
Products are reusable. Page and collection settings let you pick existing products for a paid gate instead of creating a one-off offer:
Enable a paid gate and select one or more products (any-of — buying any selected product unlocks access).
Publish the page when the gate and product are both live.
The paywall preview in the editor loads the same product details visitors will see at checkout.
Discount codes
Under the product list, Discount codes lets you create checkout codes buyers can type on a paywall:
Field
Notes
Code
2–32 characters — what the buyer types
Kind
Percentage off or fixed amount (fixed codes need a currency)
Product scope
All products, or one product only
Redemption limit
Optional cap on total uses
Expiry
Optional end date
A code's value and kind cannot change after creation — buyers may already have been quoted it. Retire a code and issue a new one instead. The paywall validates the code server-side and shows the reduced price before checkout; an invalid code is rejected explicitly rather than ignored. Intro discounts on a product and a checkout code combine into one reduction measured against list price.
Checklist
Step
Verify
Payouts connected
Monetization → Payouts shows charges enabled
Product active
Status tag reads Active in the product list
Site published
Editor publish menu — page and site settings as needed
Smoke test
Open `/products/{slug}`, complete checkout, confirm download or gate unlock
