Paid Post Submissions in WordPress with WooCommerce
By Aleksan Aharonyan ·
To charge for post submissions in WordPress, you connect a front-end submission form to a WooCommerce product. The form saves the submission as a draft, sends the user to checkout to pay for that product, and moves the post to the status you chose once the order reaches Processing or Completed. Nothing appears on the site before the money clears, and you do not need custom code or a separate checkout.
The setup has three parts that have to agree with each other: a product that stands for one submission, a form that creates the post and points at that product, and a post status decision that applies after payment. Most broken setups get the third part wrong.
Key takeaways
- Set the form’s post status to Pending if a person should look at paid submissions before they appear, or Publish if payment is the only gate you want.
- While an order is unpaid the submission is a draft; only Processing or Completed releases it to the form’s status.
- Create the WooCommerce product first, so the form has something to link to and you can test the whole path.
- Test the abandoned cart, failed payment and refund paths on a staging site, because those are the ones that generate support email.
What you need before you can charge for submissions
You need WooCommerce running with a working payment gateway, a front-end form that can hold a post back until payment, and a decision about the status paid submissions should get.
WooCommerce handles the commerce half: cart, checkout, taxes, coupons, order emails and the order statuses that record whether money arrived. The submission plugin handles the content half: the form, the draft post, the categories and the redirect after submit. The link between them is a product.
Two WordPress behaviours are worth setting deliberately:
- The submitter’s role. In wp-admin, Subscribers and Contributors cannot publish, and Authors can publish their own posts. If people register on your site in order to submit, check the default role for new users, because it decides what they can do outside your form, such as deleting their own posts.
- Draft visibility. A draft is visible only to users who can edit it, so an unpaid submission cannot leak onto the front end while the buyer is still in checkout.
Decide early whether submitters need an account. Login is simpler to support and gives every post a real author; guest submissions need a guest posting option in whichever form plugin you use.
Create the WooCommerce product that pays for one submission
Create one simple, virtual WooCommerce product per submission type, priced at what you charge, and keep it out of your shop pages so it exists only as the thing the form sells.
- Name it after the outcome, not the plugin: “Standard listing submission” or “Guest post review fee” reads correctly on a checkout page and on the receipt.
- Set a fixed price. Avoid variations unless you truly sell tiers through one product.
- Mark it virtual, so WooCommerce does not ask for a shipping address for something delivered as a published post.
- Hide it from the shop catalog. Buyers should arrive from the form, not by browsing.
- Write a short description, because it appears in the cart and on the confirmation, and it is where you say what the buyer gets and when.
One product per submission type keeps order reports, coupons and refunds legible. If featured placement is a separate product, you can count upgrades without exporting line items.
Build the submission form and link it to the product
Build a form that collects everything the post needs, set its post status, then link it to the product you just created.
At minimum the form needs a Post Title field, a content editor and a way to choose categories; add a featured image field if your theme’s layout depends on one. In Front User Submit, a free plugin for frontend post submission and guest posting forms, you assemble that with a drag-and-drop form builder and place it with [fe_form id="123"] or the Front Editor block. The form builder documentation covers the field types and how they are ordered.
Linking the form to a WooCommerce product is the Pro step: you select the product in the form’s payment settings, and every submission from that form is then tied to an order for it. The paid submissions documentation lists those settings. That link needs Pro, and Professional starts at $9.99 per month or $95.88 per year for one site, with a three-day trial; the plans list the other options.
What the user sees: draft, checkout, and the post afterwards
The submitter fills in the form, the post is saved as a draft, they pay at WooCommerce checkout, and only then does the post take the status you configured.
- The user submits the form. A draft post now exists with a title, content and an author, visible to editors only.
- The linked product is added to the cart and the user goes to the cart or straight to checkout, depending on the form’s payment settings, pays, and receives the normal WooCommerce order emails.
- While the order waits for payment the post stays a draft, but the submitter can still see it. Front User Submit’s
[fe_fs_user_admin]dashboard has a Draft tab, so the user has somewhere to confirm the submission arrived instead of emailing you to ask. - When the order reaches Processing or Completed, the post moves to the form’s status.
Set the success message and redirect on the form so the checkout step is expected rather than a surprise. A buyer who pays and lands on a blank page assumes the purchase failed.
Which status the post gets on Processing and on Completed
The form’s post status is the status the post gets after payment, not before. While the order is unpaid the post is a draft; when the order reaches Processing or Completed, the plugin applies the form’s status, either Publish or Pending.
That distinction is the whole design. With Publish, a paid order puts the post live with no further input from you. With Pending, the post moves from Draft to Pending and waits for an editor, so payment clears your spam filter but not your review.
Processing and Completed both release the post. WooCommerce decides which one a paid order lands in depending on the product and the gateway, so treat both as paid and do not build your workflow around one of them.
- Pending suits anything that carries your site’s voice: guest posts, interviews, opinion. Say in the product description and the confirmation message that payment buys review, not publication, or the first rejection turns into a refund request.
- Publish suits listings and directory entries, where the content is structured, the fields are fixed and the form itself is the quality control.
The post submit settings documentation covers the status setting and the messages around it.
Test the flow: abandoned cart, failed payment, refund
Testing means walking three orders through your store: one abandoned at checkout, one that fails payment, and one that is paid and later refunded. Do those before the happy path, because a successful order is the case you will hear about anyway.
- Abandoned cart. Submit the form, reach checkout, close the tab. Check the post is a draft, that it is absent from archives and the sitemap, and that the user’s dashboard still shows it. Then decide how long unpaid drafts live and clear them from the posts list filtered by Draft.
- Failed payment. In your gateway’s test mode, pay with a card it declines. The order should end failed and the post should stay a draft. If the post moves, check the form’s product link before going further.
- Completed payment. Pay with a test card. The order reaches Processing or Completed and the post takes the form’s status. Confirm the admin notification arrives and, when the submitter has an account, so does the author notification. Guest posts have no author account, so no author email is sent for them.
- Refund. Refunding in WooCommerce changes the order’s status, but the documented release happens on Processing and Completed only. Handle the reverse by hand: set the post back to Draft or Pending when you refund, and write that into your refund policy.
- Role check. Repeat once as a logged-in user with your site’s default role, and once as a guest if you accept guest submissions. The two paths fail in different places.
Run all of it on a staging copy. A test order in your live store still sends real emails.
Pricing models: per post, per listing or featured placement
Three pricing shapes cover most paid submission sites, and each one maps to a different product and form setup.
- Per post. One product, one price, one form. Every buyer gets the same thing, which makes it the easiest model to explain at checkout and to support afterwards.
- Per listing. Charge per directory entry and collect structured detail such as address or opening hours. In Front User Submit a listing site needs Pro, because custom post types are a Pro feature, so plan for that from the start rather than outgrow the free version later.
- Featured placement. Sell a second, higher-priced product for a featured slot. Because each form links to one product, offering standard and featured normally means two forms on the same page, with the difference stated in the product names and on the receipt.
Two smaller decisions: whether you accept coupons (a coupon that brings the total to zero creates a checkout that completes without money changing hands, so test it deliberately) and whether unpaid drafts are deleted or kept.
FAQ
Does the post stay hidden until payment clears?
Yes. The submission is saved as a draft, and a draft is visible only to users who can edit it, so it cannot appear on your archive pages or in search while the order is unpaid. It moves to the form’s status only when the order reaches Processing or Completed.
Can I charge people who do not have an account on my site?
Yes, provided your form plugin supports guest posting; in Front User Submit that is a Pro feature. Depending on your WooCommerce checkout settings, buyers may also be able to check out as guests, which keeps the whole flow account-free. A guest submission has no author account, so the author notification is not sent for it.
What happens if someone pays and the post is not acceptable?
Set the form’s post status to Pending so nothing publishes automatically, then either send the post back for changes or refund the order and set the post to Draft yourself. The payment release only proves the order reached Processing or Completed; it is not a quality check.