CodeCanyon RnB - WordPress Plugin

How to Configure CodeCanyon RnB for Rentals and Bookings in WooCommerce

CodeCanyon RnB is best understood not as a standard booking form, but as an extra layer of logic on top of WooCommerce: it adds the Rental Product product type, links the product to inventory, calculates pricing by day or by hour, blocks unavailable periods, and sends the order into the store's regular cart flow. This guide focuses on the practical workflow rather than marketing copy: what to prepare before installation, which settings to verify first, how to create a rentable product, and how to confirm that the calendar, pricing, deposit, locations, and checkout all behave as expected.

This walkthrough is useful for sites that rent out equipment, vehicles, costumes, rooms, consultation slots, and similar services where the customer chooses a date, time, pickup location, add-on resources, or number of participants. We will move from the plugin structure to a working setup: first the WooCommerce foundation, then inventory, pricing, availability, the product page, quote requests, order validation, and troubleshooting common issues.

All exact tab names and field labels are kept as they appear in the documentation and interface. If your version of the plugin shows tabs in a different order or hides some fields, follow the logic rather than the layout: first create the reference data and inventory, then attach them to the product, and only after that test the front end and the order flow.

How the Plugin Works and Where It Fits into WooCommerce

The key feature of RnB is that it does not replace WooCommerce or create a separate order system alongside your store. The plugin adds a new product type for rentals and bookings, then relies on WooCommerce's built-in mechanisms: the product page, cart, checkout, order statuses, emails, taxes, and payment methods, as long as those are correctly configured on the site itself. That means you should think of it as an extension of WooCommerce's product model, not as a standalone calendar service.

RnB works with several layers of data. The first layer is the product itself, which the customer sees on the site. The second is inventory: the actual units, sizes, models, categories, or resource variants that can be booked. The third is the booking logic: dates, times, weekends, buffer days, minimum and maximum duration, and available hours. The fourth is the money layer: base price, hourly price, discounts, deposit, paid resources, location pricing, or per-person pricing.

If you mix up these layers, the setup quickly turns chaotic. A common mistake is creating a separate WooCommerce product for every physical unit. In RnB, the better approach is to create one product and attach multiple inventory items inside it. For example, if you have three identical bicycles, you need one product called "City Bike," not three separate product pages. Inside the inventory, you can store the specific units, quantity, price, availability, and related options.

This approach is especially useful when one public-facing product has several internal variations. A dress may come in multiple sizes, a car may have several trims, a piece of equipment may support extra attachments, and a consultation service may be offered by different specialists. RnB lets you model these variations through inventory, resources, people, categories, locations, attributes, and features. The main idea to remember is this: inventory controls availability, while the product controls how the offer appears to the customer on the site.

What Happens to the Order After the Customer Clicks Book Now

When the customer selects dates, times, quantity, locations, and extra options, RnB calculates the price and adds the rental product to the WooCommerce cart. From there, the order follows the store's normal path. That is convenient because you do not have to rebuild payment methods, email notifications, and tax logic just for bookings. The downside is that if your cart, checkout, payment gateway, or site caching is unstable, the issue will show up in the booking flow as well.

That is why implementation should not stop at checking whether the calendar appears on the product page. A test order all the way to the confirmation step is mandatory. That is the only reliable way to see whether dates, locations, deposits, participants, resources, and the final amount actually make it into the cart. If a parameter is visible on the product page but disappears in the cart or email, the root cause is likely in the interaction between RnB, WooCommerce checkout, the theme, and third-party plugins, not just in a single form field.

Who RnB Is Best Suited For

The plugin works best for sites that sell not just a "service on a calendar," but a rentable item or temporary access to a resource. That could include car rentals, bicycle rentals, dress rentals, tool rentals, equipment rentals, sports gear, venues, photo studios, event equipment, or consultation slots if they are handled as WooCommerce products. In these cases, the key requirement is not just reserving time, but tying the booking to a specific inventory item, rental period pricing, a deposit, and optional add-ons.

If your business revolves around doctors, technicians, employees, offices, scheduled services, and reminders, a specialized appointment plugin may be a better fit. Those tools are usually stronger when it comes to staff schedules, notifications, and recurring appointments. RnB is stronger where the main question is "which item, for how long, under what conditions, and at what price."

What to Check Before Installation and First Launch

Before installing CodeCanyon RnB, prepare the site so that plugin issues do not get mixed up with ordinary WooCommerce problems. At a minimum, you need a working WordPress site, an active WooCommerce installation, currency settings in place, cart and checkout pages configured, store emails enabled, and a theme that correctly renders the single product page. If WooCommerce still cannot complete a simple test order with a regular product, fix that first and only then add booking functionality.

The official CodeCanyon page may list compatibility with current WordPress and WooCommerce versions, but on a real site you still need to account for the theme, cache, page builder, payment gateways, and third-party cart extensions. Booking depends on dynamic data: the calendar requests availability, the cart stores the selected period, and checkout must preserve metadata. Aggressive caching, JavaScript optimization, and custom product templates can all affect that chain.

Minimum Test Environment

For the initial setup, it is best to use a site copy or a separate staging store. This is not just a formality. RnB creates a new product type and adds its own inventory reference data, so installation introduces new menus, tabs, and meta fields. On a staging copy, it is much easier to understand which data appears, which theme templates are affected, and which settings can be safely moved to production.

• Make sure a regular WooCommerce product can be added to the cart, checked out, and trigger an email to the administrator.
• Temporarily disable aggressive JavaScript bundling and deferred loading during the first test if they have caused issues with forms or the cart before.
• Confirm that the product page is not built entirely with a custom template that hides the standard Product data box or the add-to-cart form.
• Prepare one simple product for testing: no complex coupons, no custom shipping methods, and no extra checkout plugins.
• Decide in advance what the first scenario will be: daily rental, hourly rental, rental with deposit, rental with location selection, or quote request.

If the site is already processing live orders, do not enable the new workflow for all products right away. Create one test Rental Product, hide it from the catalog or restrict access to it, configure it fully, and only then repeat the structure for other items.

What Not to Do at the Start

Do not try to enable every feature on day one. RnB has a lot of settings: different pricing plans, buffer days, paid resources, deposits, participants, locations, maps, quote requests, translations, and global and local rules. If you turn everything on at once, it becomes much harder to understand which field is changing the final amount or why the calendar suddenly became unavailable.

A practical order is this: start with a simple daily rental product, then set up inventory and availability, then pricing, then extra fields, then deposit and locations. Only after the basic order flow works should you add the map, quote request, partial payments, or add-ons.

Installing CodeCanyon RnB and Running the First Admin Check

The installation process is the same as with a typical commercial WordPress plugin: in the admin panel, open Plugins, choose to add a new plugin, upload the plugin ZIP file, and activate it. The RedQ documentation notes that the full CodeCanyon package contains a separate archive named woocommerce rental and bookings.zip; that is the file you should upload to WordPress, not the full package with documentation and extra files.

After activation, check whether RnB or Inventory menu items appear in the admin panel and whether the product editor lets you choose the Rental Product type. If WooCommerce is not installed or not active, the plugin cannot function as a store extension. In that case, restore WooCommerce first, verify its pages, and only then try activating RnB again.

First Validation After Activation

Do not jump straight into configuring dozens of products. Open Products and create a new product with a simple name. In the Product data box, select Rental Product. If that type is missing, the plugin is either not activated correctly, conflicting with the current environment, or the product editing screen has been altered by another extension. At this stage, do not look for a CSS fix. First make sure the product type appears in the standard WooCommerce admin interface.

1. Create a test product and select the Rental Product type.
2. Save it as a draft so RnB has time to generate the related fields and tabs.
3. Check the inventory, pricing, and settings tabs inside the product data box.
4. Open the global settings at WooCommerce -> Settings -> RnB Settings.
5. Return to the product and confirm that local settings can be selected independently from the global ones.

Short version: after installation, you should see not just a menu item but a working Rental Product type inside WooCommerce. If that type is visible, you can move on to the core data model: inventory.

Inventory as the Foundation of Availability, Resources, and Rental Variants

Inventory is the most important layer in RnB. RedQ's documentation directly ties product availability to inventory items: if you have multiple physical units or several variations of one offer, they should be defined in inventory and attached to the rental product. This same layer is also where you connect resources, people, deposits, attributes, features, pickup locations, and return locations.

Imagine a dress rental business. The public-facing product might be called "Aurora Evening Dress," while the inventory inside that product defines sizes S, M, and L. Each size can have its own availability and related parameters. Or take a car rental scenario: the product "BMW i8" might include several actual vehicles with different characteristics, and the customer selects an available one for the requested dates. This structure reduces the risk of double booking and makes the product page easier to understand.

How to Create Basic Inventory

In a typical setup, you first create the reference data that will later be selected inside inventory. That includes pickup locations, return locations, resources, participants, deposits, attributes, and features. Then you open the inventory tab in the product and add one or more inventory items. Older RedQ documentation highlights an important nuance: after adding the first item, you may need to save or update the product and then expand the inventory item to see the fields for attaching all the related parameters.

1. Create the reference data you actually need for the first product in the RnB or Inventory menus: resources, deposit, locations, features, and other relevant parameters.
2. Open the rental product and go to the inventory tab.
3. Add an inventory item, give it a clear name, quantity, and basic details.
4. Save the product, then expand the inventory item and attach the required reference data.
5. Repeat the process for each physical unit, size, model, or variation that must be bookable separately.

How to verify the result: the public product page should display either an inventory selector or the related booking fields, and a booked period should be blocked specifically for the selected unit. If nothing changes on the product page, check whether the inventory item is published and actually attached to the product.

Resources, People, and Deposits: What Belongs in Inventory

In RnB, a resource is a paid or meaningful add-on to the rental. For a car, that could be a child seat, GPS unit, or extra tire set. For a photo studio, it might be lighting, a backdrop, or an assistant. For equipment rentals, it could be an attachment, a consumables kit, or an accessory. A resource makes sense when the customer needs to choose it on the product page and the final price or order contents should change as a result.

The Person block fits scenarios where price or capacity depends on the number of adults, children, participants, or guests. RedQ documents it as an inventory taxonomy that can be paid or unpaid. Do not use it as a substitute for a standard product quantity field if your business only needs a simple quantity selector. It is intended specifically for cases where "people" are part of the booking logic: tours, consultations, rooms, events, or group services.

Deposits in RnB are also attached through inventory. You can use them for security holds on expensive items, damage deposits, or a mandatory amount that the owner later returns manually or through an external process. Do not promise automatic refunds unless that workflow is configured separately. On the customer-facing side, it is safer to phrase it neutrally: the deposit is added to the order total, and the refund process should be described in the site's rental terms.

Pickup and Return Locations

Pickup and return locations in RnB are separate inventory reference items. The documentation explains that the location name appears in a dropdown on the product page, while the description may be shown in the cart, checkout, order details, and email. This is a practical detail: if the customer needs to see the address, pickup point, parking instructions, or service desk information, do not leave the description empty.

If a location has an extra cost, only add it where the customer can clearly understand the reason for the surcharge. For example, "Warehouse Pickup" may be free, while "Airport Delivery" may carry a fee. After setup, test not only the product page but the cart as well: the location fee should be reflected in the final amount, and the selected address should appear in the order details.

Pricing and Calculation Rules: How to Avoid Confusing Customers and Admins

In RnB, pricing is not limited to a single WooCommerce field. The plugin supports multiple calculation methods: a general daily price, day-of-week pricing, monthly pricing, day ranges, hourly pricing, hour ranges, and duration-based discounts. That is one of the plugin's strengths, but it is also where unpredictable totals show up most often if the store owner enables multiple rules without a clear hierarchy.

Start not with "what pricing types are available," but with "how does the customer buy time." If the rental is always billed by the day, you do not need an hourly rate. If customers typically rent equipment for 2 to 4 hours, a daily price may get in the way. If weekends have higher demand, day-based pricing or separate availability rules may be the better fit. If long rentals should be more cost-effective, use day ranges or duration discounts.

Basic Pricing Models

A general rate is the easiest model for customers to understand: one day costs a fixed amount, and the total is multiplied by the number of days. Day-of-week pricing is useful for businesses with different demand on weekdays and weekends. Monthly pricing helps when seasonality follows the month but does not require a separate add-on. Day ranges work well for package offers, such as one rate for short rentals and another for extended periods.

Hourly logic requires more care. RedQ's documentation notes that hourly pricing applies to bookings shorter than a full day, and the Single Day Booking setting affects how short bookings are calculated. If your site sells rentals by the hour, first confirm that no setting is forcing short bookings to be billed as a full day, and only then add hourly ranges.

Duration Discounts and the Pitfall of Matching Range Limits

In RnB, discounts are configured by day range and can be either fixed or percentage-based. This works well for weekly rentals, long-term hire, or encouraging multi-day orders. But the documentation includes an important warning: do not set the same value for the minimum and maximum number of days within a single discount range. If you need a discount for one exact duration, test the current behavior of your plugin version on a staging copy before applying that rule to a live product.

Do not use discounts as a substitute for transparent pricing. If the customer sees a "per day" price but then gets a complicated total in the cart with no explanation, trust drops quickly. It is better to enable price information display where appropriate for the product and verify that the labels on the product page are clear. RnB includes display, label, and pricing information settings for exactly that purpose.

Deposits, Partial Payments, and Customer Expectations Around Money

A deposit adds a separate amount to the booking, but the legal and operational meaning of that deposit depends on your business. Your site should explain it clearly in the rental terms: when it is charged, when it is returned, who checks the product condition, and how the customer learns the final outcome. In the RnB interface, the deposit may be mandatory or optional, but customers should never be left guessing why the order total is higher than the base rental price.

If you use partial payments or Instance Payment, first test the standard workflow without coupons or unusual payment gateways. Only after that should you enable coupons, extra payment methods, and tax logic. Pricing issues are hardest to troubleshoot when a single order includes a discount, deposit, resource, location fee, tax, and coupon all at once.

Local and Global Settings: Which Fields to Change First

RnB includes both global settings and product-level local settings. The documentation describes a simple hierarchy: global values serve as the default for all products, while local settings on an individual product take priority when enabled in the product card. This is helpful when most products should behave the same way, but some items need their own dates, labels, restrictions, or layout.

A practical approach is to set the global baseline first, then enable local settings on the first test product only where a different outcome is actually needed. Do not make every product local "just in case." A month later, it will be difficult to understand why one product shows time fields, another hides them, and a third calculates the rental period using a completely different logic.

The Display Tab: What the Customer Should See

The display tab controls which fields appear on the public product page. The goal here is not to overload the form. If every rental uses the same pickup and return point, the customer does not need two separate location selectors. If rentals are calculated only by day, the time field can be hidden. If the product is rented as a single unit with no quantity choice, the quantity field may be unnecessary.

• Show pickup and return dates if the customer chooses the booking duration.
• Show time fields if pricing or availability genuinely depends on hours.
• Enable quantity if the customer can book multiple units of the same product and your inventory setup supports that.
• Enable quote requests if the final amount depends on manual review, a long rental term, delivery, or a custom service combination.

After changing the Display tab, open the product in incognito mode or in another browser. Testing while logged in as an administrator can hide issues related to cache, sessions, or permissions.

The Labels Tab: Where Localization Matters

RnB lets you change field labels from the admin panel. That is better than editing templates or hunting for strings in the code. For any localized site, make sure to review the labels for dates, time, locations, resources, deposits, the booking button, and minimum and maximum rental period errors. Even if some strings have already been translated automatically, read them carefully anyway: machine translation may be technically understandable while still feeling awkward to customers.

The button label should match the action. For a standard booking flow, "Book Now" works well. For a rental with payment, something like "Complete Rental" may fit better. For a quote-based workflow, "Request a Quote" is more appropriate. Do not mix "Book Now," "Request Quote," and localized labels in the same form unless the English elements are fixed system labels in your plugin version and cannot be changed.

The Conditions Tab: Period Rules, Buffers, and Weekends

This tab contains the settings that have the strongest effect on availability and final pricing: date format, time format, maximum lateness, late-hour surcharge, single-day booking, minimum and maximum duration, initially blocked dates, pre-booking and post-booking buffers, time interval, allowed hours, booking layout, and weekends.

Buffer days matter especially for physical rentals. If a dress needs to be cleaned after return, equipment needs to be checked, or a car needs to be prepared, add buffer days before or after the booking. That way, the calendar will not allow the next customer to book the item immediately next to the previous order. Test buffers in the calendar itself, not just by reading the setting label: create a test booking and confirm that the neighboring dates become unavailable exactly the way your business needs.

The Validations Tab: Time Limits and Required Fields

Validation protects the form from incomplete or impossible requests. The documentation includes a notable nuance around daily opening and closing hours: if you want to allow bookings up to a certain time, you may need to set the maximum to one minute later than the actual intended boundary. This is exactly the kind of setting that should never be left untested. If you want to accept bookings from 08:00 to 22:00, verify the edge slots, not just the middle of the day.

Quick summary of this section: global settings define the store-wide standard, while local settings handle exceptions for a specific product. After every questionable change, test the public product page, the cart, and the order itself, not just whether the field saved in the admin panel.

Practical Example: Setting Up a Bicycle Rental with Location and Deposit

Now let's walk through a concrete working scenario. The goal is to create a product called "City Bike" that can be rented by full days, lets the customer choose pickup and return locations, adds a helmet as a paid resource, includes a deposit, and blocks one day after return for condition inspection. This example shows the full RnB mechanics in action: product, inventory, pricing, extra options, calendar, cart, and order.

Goal and Preparation

The target is a public product page where the customer selects rental dates, sees available options, chooses a helmet, selects a pickup point, sees the deposit, and proceeds to the WooCommerce cart. Before you begin, make sure WooCommerce can already process a standard order and that RnB is active and showing the Rental Product type.

Starting Data for the Example

• One WooCommerce product: "City Bike."
• Three inventory units: "Bike-01," "Bike-02," "Bike-03," or more user-friendly names.
• One base daily price and a rule that prevents bookings shorter than one day.
• A paid resource called "Helmet."
• A deposit that the customer pays during checkout.
• Two pickup/return locations: warehouse and pickup point.
• One post-booking buffer day for bike inspection.

Setup Steps

1. In the RnB or Inventory menu, create the resource "Helmet" and set its price if it should increase the final total.
2. Create a deposit in the inventory section. If the deposit is required, do not make it optional on the public product page.
3. Create pickup and return locations. Include the address, opening hours, and a short instruction in the description, because that description may appear in the cart, order, and email.
4. Create a WooCommerce product, select the Rental Product type, and fill in the title, description, product image, and standard catalog data.
5. In the inventory tab, add three items, save the product, then expand each item and attach the resource, deposit, and locations.
6. In the pricing tab, choose a daily rate and set the base price for the inventory.
7. In the product's local conditions, set the minimum duration, maximum duration, one post-booking buffer day, and weekends if the rental business is closed on specific days.
8. In the display tab, enable the pickup and return date fields, and keep time hidden if the rental is billed only by day.
9. Publish the product and open it on the front end of the site.

After publishing, test the form. The customer should not see the internal complexity of your inventory model. Instead, they should see a clear path: choose a rental period, optionally choose a variation, resource, and locations, review the calculated total, and click Book Now. If the form feels too complex, go back to Display and hide the fields that are not needed for the first scenario.

Order Validation and Expected Result

Place a test order. Select a period, add a helmet, choose different pickup and return locations, proceed to the cart, and review the contents. The cart should show the selected dates, extra parameters, and the final amount. Then complete the order using any safe test method available on your site and open the order in the WooCommerce admin panel.

The expected result is an order that includes the rental product, rental period, locations, resource, deposit, and the correct final total. After the order is placed, the booked dates should become unavailable for that same inventory item. If the calendar still allows the same period beyond the available quantity, check the inventory assignment, quantity, order status, and any known issues related to cancellations or availability restoration.

A Detail That Often Breaks the First Test

If location data does not appear in the cart or email, check the location description and the inventory assignment. RedQ's documentation emphasizes that the location name is used in the dropdown, while the description appears later in the order flow. An empty description can make it look like the information "disappeared," even though the selection was made correctly on the product page.

Advanced RnB Modes: Quote Requests, Map, Calendar, and Translations

Once the basic rental flow is working, you can enable more advanced modes. Only turn them on when they solve a real business problem. Quote requests are useful for non-standard orders, the map helps with location selection, Google Calendar supports operational scheduling, and translations help localize the form and calendar. Every extra mode adds a dependency, so each one should be tested separately.

Using Quote Requests Instead of Direct Booking

Request For Quote is useful when pricing depends on manual review: delivery, long rental periods, rare configurations, corporate rentals, large events, or custom service combinations. RedQ's documentation describes two levels of activation: globally for all rental products through WooCommerce -> RnB Settings -> Display and locally for an individual product through the Show Quote Request checkbox in the product settings.

The practical purpose of this mode is to replace immediate checkout with an inquiry that the administrator reviews separately. If you enable it, test three things: whether the button appears on the product page, whether the customer sees a quote request section in their account, and whether the request reaches the administrator. For the admin email settings, the documentation points to WooCommerce -> Settings -> RnB Settings -> General, where you can define RFQ Admin Email and RFQ Admin Name.

Map Mode and Location-Based Layout

For delivery scenarios, vehicle rentals, or businesses with multiple pickup points, map mode may be useful. RnB documentation ties it to enabling Google Map in the global settings and adding an API key. The product settings may also let you choose between a standard layout and a modal layout, which older documentation refers to as Uber-like. This mode makes sense when the customer truly needs to choose or view a location on a map, not just read an address.

Before enabling the map, make sure your standard pickup and return locations already work without it. If basic location selection is not being saved correctly, the map will not fix that. It simply adds another layer: an external API, a key, domain restrictions, script loading, and possible optimization conflicts.

Google Calendar and Booking Oversight

Google Calendar integration is not necessary for every site. It is useful when the administrator or team actively works in a calendar outside WordPress and wants to see orders in a familiar schedule view. RedQ documentation describes the setup through Google Developers Console, including project creation, enabling the Calendar API, creating credentials, setting the redirect URI, and saving the configuration in WooCommerce. Do not add this integration just because it sounds attractive. It requires careful setup of an external service.

If calendar visibility is critical to the business, test more than just order creation. Also test status changes, cancellations, repeat bookings, and the site's time zone. On high-volume sites, it may be more practical to use dedicated calendar add-ons from the RnB ecosystem, but those should be evaluated separately and not mixed into the basic setup of your first product.

Interface Translation and a Useful Localization Video

RnB contains many customer-facing strings: dates, buttons, messages, location labels, resource names, and validation errors. Some labels can be changed through the Labels tab, some through global settings, and some may require translation files or tools like WPML or Loco Translate. The official RedQ support page includes a translation video specifically for RnB that helps clarify how its strings are handled.

What matters in that video is not a general product overview, but the practical localization layer: which strings can be changed through settings, which require translation files, and why automatic translation still needs manual editing afterward. That directly addresses questions like "how do I translate the RnB calendar" and "why is the booking button still in English."

Usage Scenarios: How to Adapt RnB for Different Rental Models

The same RnB feature set plays out differently across different businesses. For vehicle rentals, locations, maps, deposits, and inspection buffers matter. For costumes and dresses, sizes, features, post-return cleaning, and a clear deposit explanation matter more. For equipment, quantity, compatible resources, pickup instructions, and protection against overlapping orders are critical. For consultations or classes, time, participants, duration limits, and emails take priority. That is why, after the basic setup, you should not duplicate a product mechanically. First define the actual workflow, then choose the fields.

A good adaptation process starts with a simple table in the administrator's working document: what the customer selects, what affects price, what must appear in the order, what must block the calendar, and what staff need to see after payment. That helps you avoid turning on unnecessary fields. If the scenario does not involve multiple pickup points, you do not need locations. If there are no paid accessories, resources can stay disabled. If the product is always rented by full day, do not show time fields until you actually launch a real hourly product.

Vehicle and Equipment Rentals

For transportation rentals, three things usually matter most: availability of the specific unit, the pickup location, and the time gap between orders. In RnB, that translates into inventory, locations, and buffer days or hours. If a car or bike must be inspected after return, use Post Booking Block Days or a similar rule to close the period after the booking. If the item needs preparation before pickup, add a pre-booking buffer. That kind of buffer is best explained in the rental terms: the customer does not see the internal reason, they simply notice that the nearest date is unavailable.

For transportation, it can also be helpful to separate location pricing from distance-based pricing if those fields exist in your version and are actually used. But do not enable the map just because it looks modern. A map makes sense when location choice affects routing, delivery, pricing, or customer expectations. If all rentals are handled from a single warehouse, a normal address in the location description is enough.

Validation for Transportation Rentals

Place two consecutive orders for the same item. The first should occupy the period, and the second should either show it as unavailable or reduce the quantity available. Then cancel the first order on a staging copy of the site and check how availability is restored. If restoration is not automatic or depends on order status, document that clearly in your team's operating procedure.

Clothing, Costumes, and Size-Based Products

In clothing rentals, it is important not to lose track of size, condition, and cleaning turnaround. Sizes are best modeled as separate inventory items or features, depending on whether each size needs its own availability. If size M is booked, size L may still be available. That means a size that affects the calendar should not be stored as a simple text feature with no link to inventory.

In this type of scenario, the deposit should usually be mandatory if the business genuinely uses a damage security deposit. On the public product page and in the rental terms, explain that the deposit is not an extra rental price, but is handled according to the store's policies. RnB will include the deposit in the order calculation, but the refund itself usually remains an operational procedure handled by the site owner or by external payment logic.

Validation for Clothing Rentals

Select one size, place an order, and then try to place the same order again for the same period. Next, choose another size. If the other size should remain available, make sure it is connected to a separate inventory item. If all sizes are blocked at the same time, your inventory structure does not match your real stock.

Equipment, Tools, and Accessories

Equipment rentals often need resources such as batteries, tripods, attachments, carrying cases, or protection kits. In RnB, a resource can be made paid and shown on the product page. But a resource should not replace separate inventory if the resource itself is limited and can run out. For example, if you have two battery kits for ten cameras, that resource needs especially careful testing: does it track availability, or does it only add cost?

In this kind of setup, it also helps to display features and attributes that help the customer choose the product: power, size, compatibility, weight, or included items. But do not overload the form with technical characteristics that play no role in the choice. The product page should guide the customer toward booking, not turn into a static spec sheet with no action path.

Consultations, Classes, and Services with Participants

If RnB is used for consultations or classes, the main risk is choosing the wrong type of logic for the job. The plugin can work with hours and participants, but it does not replace a dedicated staff scheduling system. For a simple case like "one service, one time slot, limited number of people," RnB may be enough. For a more complex schedule involving multiple specialists, shifts, rooms, and reminders, appointment plugins are usually a better comparison point.

If you still use RnB for this purpose, keep the form short: date, time, participant count, clear pricing, and contact details at checkout. The Person fields make sense when the number of adults, children, or guests affects pricing or capacity. After setup, test the edge values: minimum, maximum, zero, unavailable times, and repeat booking of the same slot.

Updates, Production Rollout, and Risk Control

RnB has evolved actively over time, and its changelog includes fixes related to compatibility, the calendar, deposits, calculations, RFQ, translations, and interactions with add-ons. That is a good sign of active support, but every update still needs to be tested before it reaches a live store. Booking logic is highly sensitive to order data: if an update changes time calculations or inventory structure, the issue can affect both real money and real availability.

Before updating, create a backup of both files and database, then repeat your test set: a simple daily order, an hourly order, an order with a deposit, an order with a location, an order with a resource, a cancellation, and a repeat calendar check. Do not publish these test dates on the site, but keep the checklist in your internal operating procedure. If the site is large, create a dedicated hidden product such as "Booking Test" so you can quickly validate a new version.

How to Move a Configured Product from Staging to Production

It is best to move not only the product itself but also the related reference data: inventory, resources, deposit, locations, attributes, and features. If you transfer only the WooCommerce product card, some dropdowns may end up empty. After the transfer, open each inventory item and make sure the related values are still selected. Then save the product and place a test order in the production environment using a safe method.

If you use demo data imported from the package, do not leave demo products in the live catalog. They are useful as learning material, but they may contain placeholder prices, locations, text, and images. Study one demo product as a reference, then build your own product with real names and real conditions.

Which Changes Require Dedicated Testing

• WooCommerce updates, because they can affect the cart, checkout, orders, taxes, and sometimes front-end JavaScript.
• Theme updates, especially if the theme overrides the single product template or the booking form styles.
• Enabling caching and optimization, because the calendar and cart depend on dynamic data and sessions.
• Changing pricing rules, because overlapping daily, hourly, discount, and deposit logic can produce unexpected totals.
• Adding a payment gateway, because order status may affect booking locks and downstream processing.
• Enabling RnB add-ons, because they extend the same order object, calendar, inventory, or product page.

If a problem appears after an update on only one product, do not roll back the entire site immediately. Compare the global settings with that product's local settings, check the related inventory items, and repeat the scenario on a copy of the product. In many cases, the real cause is not the update itself, but an old local rule that became visible after a calculation fix.

Safe Enhancements and Integrations That Do Not Break the Plugin Core

Enhancing RnB is safest when you begin with settings, translations, theme-level changes, and small reversible tweaks. Do not edit the plugin files directly: updates will overwrite your changes, and a mistake in pricing or availability logic can affect real orders. If behavior needs to change, first look for documented settings and filters, then use a child theme, a small custom plugin, or Code Snippets.

A CSS Tweak for a More Readable Booking Form

If your theme makes the RnB fields too cramped, you can add a small CSS tweak in a child theme or the standard custom CSS section. This does not alter pricing calculations or checkout behavior. Before applying it, open the product page, inspect the classes used in your version, and adjust the selectors if needed.

.rnb-cart,
.redq-rental-booking {
  max-width: 760px;
}

.rnb-cart label,
.redq-rental-booking label {
  font-weight: 600;
  margin-bottom: 6px;
}

.rnb-cart input,
.rnb-cart select,
.redq-rental-booking input,
.redq-rental-booking select {
  min-height: 44px;
}

.rnb-cart .booking-pricing-info,
.redq-rental-booking .booking-pricing-info {
  margin-top: 16px;
}

After adding the CSS, test the product on both desktop and mobile widths. If the classes do not apply, do not start blindly escalating selectors with !important. First inspect the form HTML in your version and keep only the rules that actually improve readability.

A Filter to Prevent Zero-Cost Bookings

The RnB developer documentation describes the rnb_allow_free_booking filter, which lets you control whether free bookings are allowed. This is useful for stores where a zero total may be acceptable in a demo product but should never go through in the live catalog. Below is a safe adaptation for Code Snippets or a small custom plugin. Replace the product ID with your own.

add_filter('rnb_allow_free_booking', function ($allow, $cost, $product_id) {
    $protected_products = array(123);

    if (in_array((int) $product_id, $protected_products, true) && (float) $cost <= 0) {
        return false;
    }

    return $allow;
}, 10, 3);

How to test it: on a staging copy of the site, temporarily set the product price to zero, try to submit a booking, and confirm that free booking is blocked for the specified ID. Then restore the normal price and test a regular order. Rolling back is simple: disable the snippet. Do not use this filter to hide pricing bugs. If the amount unexpectedly becomes zero, fix the rate, inventory, or discount first.

A Practical Approach to Caching and Optimization

WooCommerce sites often use page caching and script optimization. For rental workflows, that is a sensitive area: the calendar, availability, cart, and checkout all depend on a dynamic session. A safe approach is to exclude rental product pages, the cart, checkout, and the account area from full-page caching, and to avoid deferring critical calendar scripts until you have tested them. This is not an official RnB integration with any specific cache plugin, but a general best-practice precaution for WooCommerce scenarios with dynamic availability.

The sequence is simple: first test the product with no aggressive optimization, then enable optimization one rule at a time and repeat date selection, add-to-cart, and checkout after each change. If the calendar stops opening or dates become unavailable for no clear reason, roll back the last rule and add an exclusion for the rental page.

How to Validate the Result After Setup

Validation should follow both the customer journey and the admin workflow. The customer side answers the question, "Can someone select and pay for a rental without errors?" The admin side answers, "Does the team see the correct data and can they manage the order properly?" If you only test the form on the product page, it is easy to miss a problem in the cart, email, or availability restoration.

Customer Journey

1. Open the product in a private window so you are not using the admin session.
2. Select an available period, resource, quantity, deposit, and locations if those fields are enabled.
3. Verify that the price changes predictably and matches the selected rate.
4. Click Book Now and confirm that the product is added to the cart.
5. In the cart, review the dates, times, locations, resources, deposit, and total.
6. Complete a test order and check the confirmation page.
7. Return to the product page and confirm that the booked period is blocked or that available quantity has decreased.

Admin Workflow

In the WooCommerce admin panel, open the order and make sure it contains all required booking metadata. Then open the RnB calendar or report view if you use that screen and confirm that the order appears there. If Google Calendar integration is enabled, check whether an event was created and whether the time period matches.

Test cancellations separately. Users have reported issues around availability restoration after canceled orders, so for a live site you need to know exactly how your version and your workflow behave. If cancellation does not automatically free the slot, do not promise customers immediate availability after cancellation until you have confirmed that behavior through testing or an update.

A strong validation set looks like this: one test order, one repeat attempt for the same period, one cancellation, one follow-up calendar check, one customer email, and one admin email. That will uncover real problems much faster than reloading the product page ten times.

When CodeCanyon RnB Is the Right Choice

CodeCanyon RnB works especially well on sites where WooCommerce is already the foundation of sales and the new workflow revolves around renting an item for a period with locations, deposits, and optional resources. It is not the easiest plugin for a simple one-click appointment form, but it offers a detailed rental product model: inventory, availability, pricing, buffer days, locations, quote requests, calendar integrations, and local rules for specific products.

Before launching it in production, follow a short path: one test Rental Product, one inventory item, one pricing rule, one order, one cancellation, and one email. Then add resources, deposits, maps, discounts, and integrations. That sequence reduces risk and makes it much easier to understand which setting is responsible for which result.

If the logic fits your store after testing, you can download CodeCanyon RnB, install it on a staging copy of the site, and build your first real rental workflow. The key is to evaluate not just the appearance of the form on the product page, but the entire path through the order, email, calendar, and availability restoration.