Selling Content with Pay Per View
Any post in your Content Hub can be sold on its own. Set a price, publish it, and clients pay once to unlock it. This article covers what you need in place, how the money reaches you, and what happens when a sale goes wrong.
What you need before you can sell
You need a connected Stripe account. It is the same account that already takes your paid bookings, paid forms and store payments, so if you have connected Stripe before you are ready.
If you have not, the Pay Per View card in the post editor stays closed and offers you the Stripe connect flow instead. Save your post first, because connecting opens Stripe in the same window and unsaved changes are lost.
Setting a price
Open a post, choose Pay Per View in the Access section, and type your price.
The currency is your store currency, taken from Plans & Pricing. It is shown rather than chosen, so every paid post in your hub uses the same one.
There is a floor. Stripe will not take a payment below a small minimum, which varies by currency, and the editor tells you the lowest price it accepts before you try to save. Set a higher price, or make the post free.
How your client pays
Clients unlock paid posts in the client portal on the web. They see what the post includes, the price, and a tick box confirming the purchase is not refundable, then they go to Stripe Checkout to pay by card, Apple Pay or Google Pay.
The mobile app never shows a price or a buy button, and it does not link across to the portal either. Both are App Store policy, and they are what keep Apple and Google out of the transaction.
What a locked post on a phone does say is where to go. Under the padlock it reads "Your coach sells this post separately. Go to your client portal in a web browser to unlock it.", so your client is not left guessing.
Access does not expire. Once a client has bought a post it stays theirs.
Where the money goes
Payments go straight to your own Stripe balance and pay out on your normal Stripe schedule. Foodzilla takes the same commission on a content sale as it takes on the rest of your store, and your rate is shown in your store settings. Stripe charges its usual processing fee on top.
Tax
The price you set is what you receive, and tax is added on top at checkout. Collecting sales tax or VAT is yours to handle. Stripe Tax runs on your own connected account and follows your own registrations, so nothing is added until you switch it on in your Stripe dashboard.
Refunds and chargebacks
There is no refund button in Foodzilla. Refund a content sale the same way you refund anything else, from your Stripe dashboard.
Foodzilla then follows what you did in Stripe:
- A full refund withdraws the client's access to that post, and the sale comes off the post's sales count and your content revenue.
- A partial refund leaves access in place. The client keeps what they bought and you have handed some of the price back.
- A chargeback also withdraws access, at the moment the money leaves.
A client whose purchase was refunded or charged back can buy the post again later if they want it.
Once a post has sold, its price is fixed
After the first sale you can no longer change a post's access type or its price. Changing either would take back something a client paid for, or rewrite what they agreed to pay. If you need a different price, archive the post and publish a new one.
For the same reason, a post that has sold cannot be deleted. Archive it instead: everyone who paid keeps it, and it comes off everybody else's Content Hub.