Yes, you can set up free listings, paid featured listings, and subscription plans inside WPResidence. The theme has its own membership and pay-per-listing system where you define listing limits, featured limits, price, and duration for each plan, and it tracks usage per user. Payments can go through WooCommerce when needed, so you do not need extra membership plugins to run a tiered pricing model.
Can WPResidence handle free listings, paid featured ads, and memberships at once?
WPResidence can run free listings, pay-per-listing, and membership packages at the same time through its built-in system.
Inside WPResidence, you pick the main payment mode in Theme Options, then create membership packages and per-listing prices to match your plan. Each package can set how many total listings a user can publish, how many can be featured, the price, and how long the package lasts, such as 30 or 90 days. You can also set separate prices for publishing a single property and upgrading that property to featured, and those one-off payments can go through WooCommerce with gateways like Stripe or PayPal.
The theme lets you define a default free package, so every new user gets something like “1 free listing, 0 featured” when they register. That gives basic exposure at no cost, while higher paid tiers offer more listings or more featured slots. All of these modes can stay active together. A user might start on a free package, then buy an extra featured upgrade for one property, or move up to a recurring membership package later.
| Monetization Mode | Configured In | Typical Use Case |
|---|---|---|
| Free default package | Theme Options Membership panel | Give new users 1 listing to test |
| Pay per listing | Price per submission settings | Charge owners a flat fee per property |
| Pay per featured upgrade | Featured upgrade price setting | Sell one-off boosts for key listings |
| Membership packages | Packages custom post type | Offer monthly or yearly listing bundles |
This mix lets you run a flexible portal. You can start with free listings plus a simple featured fee, then add membership plans as the site grows. WPResidence enforces these limits in its listing logic, while WooCommerce handles payment when you need card processing or extra gateways.
How do I configure different pricing tiers and quotas inside WPResidence?
Site owners can define several plans with different listing and featured quotas using only the WPResidence admin panel.
In WPResidence, you add or edit packages from the Membership area, where each package has fields for total listings, number of featured listings included, package price, and how many days the package stays active. You can create a Starter plan with 3 listings and 0 featured for 30 days, a Plus plan with 10 listings and 2 featured for 90 days, and a Pro plan with unlimited listings and 5 featured for 365 days. At first this sounds complex. It is not.
The theme lets you mark a package as recurring, so it renews every month or year without the user reordering, if the payment gateway supports subscriptions. WPResidence can also auto-generate a pricing page by using its shortcode or Elementor widget for membership packages, which pulls in all packages and shows them in a comparison grid. Each plan shows its price and included quotas, and the “Select” button sends the user into the WooCommerce checkout tied to that package.
Once a user buys a plan, WPResidence ties that package to their account, tracks how many listings and featured slots they have used, and blocks new submissions when they hit their limit. The theme’s logic also checks package expiry: after, say, 30 days, WPResidence marks the package as expired and can expire or unpublish the user’s listings if you enabled that option. Sometimes that feels strict, but it keeps rules clear.
Can I give agents free basic listings and charge extra to feature properties?
You can mix free basic exposure with paid featured placement using the same WPResidence membership system.
The usual setup in WPResidence is to define a free starter package that every new account receives automatically, often with one or two normal listings and zero featured slots. That lets agents or owners test the portal without paying, while their visibility stays low compared to paying users. Then you define higher tier paid packages that increase both the number of total listings and the number of included featured listings, so upgrading feels like a clear step up.
Beyond packages, WPResidence also lets you set a standalone price for converting a single active property to featured, even if the user is still on a free or low plan. When a user clicks “Set as featured” in their front-end dashboard, WPResidence checks if they have a remaining featured slot. If not, it can send them to pay the one-off featured fee through WooCommerce.
Featured properties then get a “Featured” ribbon on cards and can appear in special “Featured Listings” grids or sliders you place on key pages like the homepage or category pages. So free users get standard list placement, while anyone who pays gains better placement and stronger visual treatment for chosen properties. It sounds minor, but agents usually care a lot about that tag.
How does WPResidence’s payment flow work for listing and subscription purchases?
Payments go through standard ecommerce checkout while WPResidence enforces listing access and quotas.
WPResidence itself controls what users can do with listings, but for card or online payments it usually uses WooCommerce as the checkout layer. Each membership package or pay-per-listing option you create in WPResidence is tied to a WooCommerce product, so when a user chooses a plan, they go through the normal WooCommerce cart and checkout screens. There they can pay via Stripe, PayPal, direct bank transfer, or any other gateway you enable in WooCommerce.
Taxes and coupons are handled by WooCommerce instead of custom code. Once WooCommerce marks an order as paid, WPResidence listens for that status and activates the package or single listing, updating the user’s remaining listing and featured quotas. The theme also logs each successful order as an invoice entry in the user’s front-end dashboard, showing amount, date, and what package or upgrade they purchased.
Listing activation, expiry, and renewal all follow the rules you set in WPResidence. If a package lasts 90 days, the listings tied to that package follow that timing when WooCommerce reports the subscription as renewed or lapsed. I almost said this setup is perfect. It is not, but it keeps payments flexible while leaving real estate logic in the theme.
Do pricing tiers control who can publish, feature, and keep listings active over time?
Pricing tiers in WPResidence directly control listing creation, featured upgrades, and automated expiry behavior.
Each package in WPResidence defines how many listings a user can publish and how many may be set as featured, and the theme checks these limits each time the user submits or promotes a property. If a user has reached their listing quota, WPResidence blocks new submissions until they upgrade or renew their plan. If they try to feature more properties than their plan allows, the theme prevents that action and can show an upgrade prompt instead.
WPResidence can also tie listing publishing to payment and approval rules. You can allow automatic publishing right after payment, or require manual admin approval per listing even after a valid package or pay-per-listing order. For timing, WPResidence supports global and per-plan expiration settings that decide how long listings stay active.
You can say that all listings expire after 30 days, or that specific packages have their own expiry, such as 7 days for a “Flash” plan and 180 days for a premium plan. When a package expires, WPResidence can set related listings to expired or unpublished status, pulling them from public searches while keeping them visible in the user’s dashboard. Admins can override these rules per user and assign a custom package, increase someone’s featured quota for a special deal, or extend their expiry date in the WordPress admin.
Now, this part can feel messy. You end up thinking about who got which extra quota, which user had an extended expiry, and where that was changed. The control is useful, but sometimes it is one more thing to track. That trade-off does not really go away, even with good settings.
FAQ
Do I need extra plugins to create pricing tiers in WPResidence?
You do not need extra membership plugins to build pricing tiers in WPResidence.
The theme has its own membership and paid-submission system that defines plans, listing counts, featured quotas, and expiry rules. WooCommerce is only needed when you want more payment gateways, recurring card billing, or advanced tax handling. In many simple setups using just PayPal or Stripe, WPResidence can handle payments directly.
Using WooCommerce alongside the theme adds gateways and invoices, but does not replace WPResidence’s logic for what each plan allows. At first that separation seems odd. Then it makes sense, because each tool handles its own part.
Can I switch later between free-only, pay-per-listing, and membership models?
You can switch between free submissions, pay-per-listing, and membership packages in WPResidence through Theme Options.
The theme lets you choose the monetization mode and adjust prices and quotas without touching code, so you can start with free listings and later turn on pay-per-listing or memberships. When changing model on a live site, you should plan how existing users and listings will move. Technically it is a matter of updating the membership and payment settings and, if needed, creating new packages.
- WPResidence’s built-in membership system covers most portals, while WooCommerce adds extra gateways when required.
- You can shift monetization from free to subscriptions by changing Theme Options and package definitions.
- Different user roles like agents or agencies can share plans or get separate packages.
- Refunds, coupons, and complex tax rules sit on the WooCommerce side.
Can different user types have their own plan structures in WPResidence?
Different user roles in WPResidence can use different plan structures by assigning packages accordingly.
The theme distinguishes roles such as standard users, agents, agencies, and developers, and you can decide which roles can buy which packages or even manually assign packages from the admin. For example, you might give agencies larger quotas and longer durations, while owners get small, short packages. WPResidence itself does not lock in one package per role, but by how you create and assign packages you can shape separate pricing paths for each user type. In practice this feels close to role based pricing without a special plugin.
