How refunds are handled on BuildRightWeb.
This page explains how BuildRightWeb handles refund and return requests for plugin purchases and related digital products sold through the site. Because the site now focuses on digital plugin sales and related WordPress work, this policy is built around digital delivery, customer access, account-based downloads, and licensing-related products.
Effective date: April 7, 2026
What’s on this page
The goal is to be fair, clear, and practical.
BuildRightWeb sells digital WordPress-related products such as plugins, and may also offer related support, setup help, or custom implementation services. Because plugin purchases are digital and may involve immediate access to downloadable files, customer account access, and licensing-related functionality, refunds are handled differently than returns for physical products.
The goal of this policy is to set expectations clearly while still leaving room to handle genuine problems fairly.
There is usually no physical “return.”
Plugins and similar products sold through BuildRightWeb are digital goods. Once a purchase is completed, the buyer may receive immediate access to downloads, account-based fulfillment, licensing-related activation, or support-linked access.
Because of that, there is usually not a traditional return process where an item is physically sent back.
Most real problems should be handled through support before refund assumptions.
If the issue is installation trouble, setup confusion, compatibility questions, or uncertainty about how the plugin is meant to be used, the first step should usually be support. A lot of refund requests can be resolved faster and better by clarifying setup, scope, or expected behavior.
Refunds may be reviewed in situations like these.
- Duplicate purchase: you were accidentally charged more than once for the same product.
- Accidental purchase: the order was made in error and the request is made promptly before meaningful product use or abuse occurs.
- Broken delivery or access issue: you paid but did not receive proper access, download fulfillment, or expected account-linked delivery, and the issue cannot be resolved reasonably.
- Severe technical failure: the plugin is materially unusable in the intended supported context and the issue cannot be resolved through normal support effort.
- Other clear fairness situations: where a refund makes sense based on the actual circumstances and site records.
Changed your mind after access was delivered
If the product was delivered properly and the purchase was completed intentionally, a later change of mind does not automatically create refund eligibility.
You expected custom work from a plugin purchase
Buying a plugin is not the same as hiring BuildRightWeb for custom implementation unless that was explicitly included in the order.
Compatibility assumptions outside stated scope
If a customer assumes the product will behave beyond its intended scope, supported context, or stated description, that alone does not guarantee a refund.
Duplicate charges should be reported quickly.
If the same customer is charged more than once for the same plugin purchase by mistake, reach out as soon as possible. Genuine duplicate purchases will typically be reviewed quickly and handled accordingly.
Fast contact matters.
If you made a genuine accidental purchase, contact BuildRightWeb promptly. Requests made quickly and in good faith are much easier to review than requests made long after files, account access, or product use have already occurred.
Technical problems should usually go through support first.
If the issue is that the plugin is not working as expected, the first step should usually be contacting support with enough detail to review the issue properly. That may include the website environment, WordPress version, WooCommerce version, screenshots, error details, or a description of what the plugin is doing versus what you expected.
If the issue is fixable, explainable, or caused by environment-specific conflict rather than a true product failure, support may be the proper solution instead of a refund.
- Installation or setup confusion
- Plugin conflict or environment-specific issue
- Scope misunderstanding
- Custom implementation need rather than plugin defect
Custom work is different from plugin-only purchases.
If BuildRightWeb is hired separately for custom development, implementation, consultation, debugging, or related project work, refund handling may differ from plugin sales. Time, labor, discovery, diagnosis, and implementation effort may not be refundable once that work has begun or been delivered.
Separate agreements may override this general page.
If a custom project, proposal, invoice, statement of work, or separate written agreement includes its own refund, cancellation, milestone, or payment terms, those more specific terms should control that service relationship.
Use the site’s support or contact flow and include enough detail to review it.
If you believe a refund should be considered, contact BuildRightWeb through the site’s contact or support process and include enough detail to identify the order properly.
- Your name and email used during checkout
- The product purchased
- The purchase date or order details
- A short explanation of the issue
- Any relevant screenshots or technical details if the issue is functionality-related
Approved refunds are generally sent back through the original payment path.
If a refund is approved, it will usually be processed back through the original payment method or payment provider used during checkout, subject to that provider’s timing and rules.
Product access may be removed after refund.
If a refund is issued for a digital product, related access may be limited, revoked, or removed, including download access, account-linked product fulfillment, or licensing-related use connected to that refunded purchase.
Please contact support before escalating a payment dispute.
If there is a problem with a purchase, the best first step is to contact BuildRightWeb directly and give support a chance to review it. Unnecessary chargebacks on properly delivered digital products can create account, access, and dispute complications that are harder on everyone than handling the issue directly first.
Abuse of refund requests, fraudulent claims, download-and-refund behavior, or similar misuse may lead to denial of the request, revocation of access, or additional protective action where appropriate.
Questions about a purchase or refund request?
If you need help with a plugin order, accidental purchase, duplicate transaction, access issue, or refund-related question, use the site’s contact or support flow and include enough information to identify the order.