Refund & Cancellation Policy

Last updated: 23 August 2026

WPCodeForge sells digital WordPress plugins and related digital products. Because our products are digital software, they can be downloaded, installed and used without being physically returned.

This Refund & Cancellation Policy explains when refunds may be available, how cancellation works, what happens when a refund is approved, and the requirements that apply when a customer receives a refund for software that has already been supplied.

This policy is intended to be clear and fair while protecting WPCodeForge against misuse of its refund process.

Nothing in this policy removes or limits any consumer right that cannot legally be excluded or restricted under the laws of England and Wales.

1. Our General Refund Position

WPCodeForge does not generally offer refunds simply because a customer changes their mind after purchasing and receiving a plugin, except where a refund is required by applicable law or WPCodeForge expressly agrees to provide one.

This does not affect statutory consumer rights.

For example, digital content supplied to consumers must meet the requirements imposed by the Consumer Rights Act 2015. Where paid digital content does not conform to the contract, consumers may have legal remedies, which can include repair, replacement, price reduction or a refund depending on the circumstances.

We therefore assess refund requests according to the circumstances of the purchase, the applicable contract terms and the rights that apply to the particular customer.

2. Consumer Rights Are Not Excluded

Nothing in this policy is intended to exclude, restrict or override statutory rights.

In particular, a term stating that “all sales are final” cannot lawfully remove rights that a consumer has under applicable legislation.

The Consumer Rights Act 2015 provides protections concerning digital content, including requirements that digital content be of satisfactory quality, fit for a particular purpose where applicable, and as described.

Consumer contract terms must also be fair and transparent. The Competition and Markets Authority states that unfair consumer terms may be unenforceable.

Accordingly, this policy should always be read subject to applicable law.

3. When a Refund May Be Available

A refund may be available where:

• WPCodeForge is legally required to provide one.
• The digital product does not conform to the contract and the applicable legal remedy is a refund.
• WPCodeForge has materially failed to provide what was purchased.
• A transaction was made without proper authorisation, subject to appropriate investigation.
• WPCodeForge expressly agrees to a refund in the particular circumstances.
• Another applicable legal right gives the customer a right to cancel or obtain a refund.

A refund is not automatically available simply because a customer no longer wants the plugin, has changed their mind, has not used it, or has subsequently decided that it is not suitable for their particular needs, subject to any statutory cancellation rights that apply.

4. Digital Products and the 14-Day Cancellation Period

Online sales of digital content can be subject to statutory cancellation rights under the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013.

However, there are specific rules for digital content that is supplied immediately.

Where a consumer asks for digital content to be supplied during the 14-day cancellation period, the business must obtain the required express consent and acknowledgement concerning the loss of the cancellation right.

WPCodeForge will therefore use appropriate checkout wording and consent mechanisms where required by law.

This policy does not attempt to remove a statutory cancellation right where the legal requirements for doing so have not been satisfied.

5. Refund Requests Based on a Change of Mind

Where applicable law does not provide a cancellation or refund right, a change of mind does not automatically entitle a customer to a refund.

Examples can include:

• Purchasing the wrong plugin.
• Deciding that you do not need the plugin anymore.
• Deciding that another plugin would be preferable.
• Not using the plugin after purchasing it.
• Not installing the plugin.
• Purchasing the plugin before checking its published requirements.
• Discovering that the plugin is not suitable for a particular website configuration where it was otherwise supplied as described.

WPCodeForge may nevertheless consider exceptional requests at its discretion.

A discretionary refund is not a contractual entitlement merely because WPCodeForge has granted a refund in another case.

6. Refunds for Faulty or Non-Conforming Digital Content

If you believe that a WPCodeForge plugin is defective, does not work as described, or otherwise fails to conform to the applicable contract, please contact us through our contact form.

Please provide:

• Your order number.
• The plugin name.
• The plugin version.
• Your WordPress version.
• A description of the problem.
• Steps needed to reproduce the problem.
• Relevant error messages.
• Relevant technical information.

Where appropriate, WPCodeForge may first attempt to provide a fix, update, repair or replacement.

The Consumer Rights Act 2015 provides statutory remedies for faulty digital content, including repair or replacement and, in appropriate circumstances, a price reduction or refund.

We will not require a customer to waive statutory rights as a condition of receiving a remedy required by law.

7. Compatibility Issues

WordPress websites can contain numerous variables, including:

• WordPress versions.
• PHP versions.
• Themes.
• Other plugins.
• Hosting environments.
• Server configurations.
• Security systems.
• Caching systems.
• Content management configurations.

A plugin not functioning correctly in a particular environment does not automatically establish that the plugin is defective.

Where you report a compatibility problem, WPCodeForge may investigate the issue and request reasonable diagnostic information.

Where the problem is caused by WPCodeForge software failing to conform to the applicable contract, the remedies available under applicable law will apply.

8. How to Request a Refund

Refund requests should be submitted through our contact form.

Please include:

Subject: Refund Request

and provide:

• Full name.
• Email address used for the purchase.
• Order number.
• Product purchased.
• Date of purchase.
• Reason for requesting the refund.
• Relevant information supporting the request.

Providing a clear explanation helps us determine whether the request concerns a statutory right, a technical problem, suspected unauthorised activity or a discretionary refund request.

9. We May Ask for Information

WPCodeForge may reasonably request information needed to assess a refund request.

Depending on the circumstances, this may include:

• Proof of purchase.
• Order information.
• Technical information.
• Evidence of the reported problem.
• Information about how the plugin was used.
• Confirmation of the affected website.
• Other information reasonably necessary to determine whether a refund is appropriate.

We will not request information that is unnecessary for assessing the request.

10. What Happens When a Refund Is Approved

When WPCodeForge approves a refund, the customer must cease using the refunded product and remove it from the relevant website or websites, unless we expressly agree otherwise in writing.

This is an important condition of accepting a discretionary refund and, where applicable, forms part of the agreement under which the refund is provided.

The customer must not:

• Continue using the refunded plugin.
• Keep the refunded plugin installed.
• Continue receiving updates or support under the refunded purchase.
• Use a refunded licence to operate the product.
• Copy the plugin for continued use.
• Transfer the refunded plugin to another person.
• Continue using the product on another website.
• Retain access to a paid service that has been refunded where the service has been terminated.

A refund is not intended to provide the customer with permanent access to paid software without paying for it.

11. Removal of Refunded Software

If you receive a refund for a WPCodeForge plugin, you must remove the refunded plugin and its associated WPCodeForge code from websites on which you are no longer entitled to use it.

Where technically applicable, this may include:

• Deactivating the plugin.
• Uninstalling the plugin.
• Removing the plugin files.
• Removing associated licence keys or activation data.
• Removing copied or modified versions used under the refunded licence.
• Removing the software from staging or development environments where continued use is not permitted.
• Ensuring that authorised copies are no longer being used.

Where a plugin has created configuration data or website content, removal of the plugin does not necessarily mean that unrelated website data must be deleted.

12. Refunds and Licence Termination

Unless WPCodeForge expressly agrees otherwise, approval of a refund terminates the customer’s paid licence to use the refunded product.

The customer must therefore stop using the product once the refund is processed.

If the product was licensed on a subscription basis, the refund may also result in termination of the relevant subscription, licence or entitlement as specified in the applicable product terms.

13. Software Verification and Licence Enforcement

WPCodeForge may operate technical systems designed to verify licences, activations and authorised use of its products.

Where technically and lawfully appropriate, these systems may identify information relevant to whether a plugin remains activated or is being used under a valid licence.

The purpose of such systems is to help protect WPCodeForge’s software from unauthorised use, piracy and misuse of refunds.

A customer who has legitimately received a refund is expected to cooperate with the termination of the refunded licence.

14. Continued Use After a Refund

If a refund is granted and you subsequently continue using the refunded product without a valid licence, WPCodeForge may treat that use as unauthorised use of its software.

WPCodeForge may take reasonable and lawful steps to protect its intellectual property and enforce its contractual rights.

Depending on the circumstances, this may include:

• Disabling the refunded licence.
• Revoking activation credentials.
• Blocking further updates.
• Suspending support associated with the refunded purchase.
• Contacting the customer to request removal of the software.
• Requesting payment for continued authorised use where a valid contractual basis exists.
• Seeking recovery of losses or other sums that are legally recoverable.
• Taking further legal action where appropriate.

Important distinction regarding continued billing

WPCodeForge will not treat a refund as giving automatic permission to charge a customer indefinitely.

If continued use after a refund results in a valid contractual charge, licence fee or other legally enforceable payment obligation, the applicable terms will determine what amount is payable.

WPCodeForge will not use this policy as a basis for imposing arbitrary, disproportionate or undisclosed penalties.

This distinction is important because consumer contracts must be fair and transparent, and terms that impose excessive cancellation charges or create a significant imbalance may be considered unfair.

15. We May Request Proof of Removal

Where reasonably necessary to verify compliance with the terms of an approved refund, WPCodeForge may request reasonable evidence that the refunded software has been removed.

For example, we may ask you to confirm:

• The plugin has been deactivated.
• The plugin has been deleted.
• The relevant website no longer contains the refunded software.
• Any unauthorised copy has been removed.

In a genuine dispute, WPCodeForge may request reasonable technical evidence relevant to the specific issue.

We will not require unnecessary access to your website, hosting account, server or personal information merely to process an ordinary refund.

16. Failure to Remove Refunded Software

If a customer refuses to remove refunded software despite being required to do so under the applicable refund arrangement, WPCodeForge may contact the customer to seek resolution.

Depending on the circumstances, continued unauthorised use may constitute a breach of the applicable licence or contractual terms and may also raise intellectual-property issues.

WPCodeForge may pursue remedies available under applicable law where necessary.

Any legal action will be considered on the facts of the individual case and will not be taken merely because a customer has exercised a genuine statutory right.

17. We Will Not Penalise Legitimate Refund Rights

A customer will not be penalised merely for exercising a genuine statutory consumer right.

For example, WPCodeForge will not refuse a legally required remedy solely because the customer has asked for one.

Likewise, this policy does not prevent a customer from relying on statutory rights that apply to faulty or non-conforming digital content.

The purpose of the refund and licence provisions is to prevent a customer from obtaining a discretionary refund and then deliberately retaining the commercial benefit of paid software without authorisation.

18. Fraudulent or Abusive Refund Requests

WPCodeForge takes deliberate refund abuse seriously.

Examples of potentially abusive conduct may include:

• Deliberately providing false information to obtain a refund.
• Claiming that a purchase was unauthorised when it was knowingly authorised.
• Obtaining a refund and deliberately continuing to use the refunded software.
• Obtaining multiple refunds through deceptive means.
• Repeatedly purchasing and refunding the same product while retaining access.
• Distributing a refunded plugin to third parties.
• Using a refunded licence on additional websites.
• Attempting to circumvent licence restrictions after a refund.
• Making fraudulent representations concerning the removal of software.

Where WPCodeForge has reasonable grounds to suspect fraud or deliberate abuse, we may investigate the matter and take proportionate and lawful action.

19. Chargebacks and Payment Disputes

If you believe that a payment was made incorrectly, please contact WPCodeForge before initiating a payment dispute where reasonably possible.

This gives us an opportunity to investigate and resolve legitimate problems.

A payment dispute does not automatically give a customer a right to retain software without a valid licence.

Where a payment is reversed or charged back and the transaction is subsequently determined to have been valid, WPCodeForge may seek appropriate remedies available under the applicable agreement and law.

Nothing in this section prevents a customer from exercising a genuine statutory or card-provider right.

20. Duplicate Purchases

If you accidentally purchase the same WPCodeForge product more than once, contact us as soon as possible.

We may review duplicate transactions and, where appropriate, refund a genuine duplicate purchase.

The treatment of duplicate purchases may depend on whether the licences have been activated or used and on the circumstances of the transaction.

21. Unauthorised Transactions

If you believe that someone has used your payment method without your permission to purchase a WPCodeForge product, contact us promptly.

We may request information reasonably necessary to investigate the transaction.

Where appropriate, we may also recommend contacting your payment provider.

22. Refund Processing

Where WPCodeForge agrees that a refund is due, we will normally return the money using the same payment method used for the original transaction, unless applicable law or the customer’s express agreement provides otherwise.

For statutory refunds concerning digital content, the Consumer Rights Act 2015 provides that a refund must be made without undue delay and, in the circumstances covered by the Act, within 14 days from the date the trader agrees that the consumer is entitled to a refund.

The time taken for funds to appear in an account may also depend on the payment provider or financial institution.

23. Refunds Do Not Transfer Ownership of the Software

A refund does not transfer ownership of WPCodeForge’s intellectual property to the customer.

WPCodeForge and its licensors retain all applicable intellectual-property rights in the software.

Where a refund terminates the customer’s licence, the customer must cease using the software in accordance with the applicable licence terms.

24. Third-Party Products

This policy applies to products and services sold by WPCodeForge.

If you purchase a third-party product through an affiliate link, marketplace or external provider, that provider’s refund and cancellation policy may apply instead.

WPCodeForge cannot guarantee or control the refund policy of an independent third-party provider.

25. Business Customers

Where a purchase is made by a business or another customer acting wholly or mainly for purposes relating to its trade, business, craft or profession, different legal rights may apply from those available to consumers.

The contractual terms applicable to the transaction will govern, subject to applicable law.

Nothing in this policy is intended to create consumer rights for a business where those rights do not apply.

26. Subscriptions and Recurring Payments

Where WPCodeForge offers a subscription or recurring payment product, the relevant product page and checkout will specify the applicable subscription terms.

Cancellation of a subscription normally prevents future renewal charges but does not necessarily create a right to a refund for an already completed billing period.

Any statutory cancellation rights that apply will continue to apply.

Subscription arrangements must also comply with applicable consumer-protection requirements. Current CMA guidance notes that additional rules concerning subscription contracts are expected to come into force in Spring 2027, so WPCodeForge will update its processes as applicable requirements come into force.

27. Cancellation Before Supply

Where a customer has a statutory right to cancel before digital content is supplied, the cancellation will be handled in accordance with the applicable legislation.

Where digital content is supplied immediately, WPCodeForge will use the legally required consent and acknowledgement process where applicable.

UK government guidance confirms that businesses supplying downloadable digital content must obtain the customer’s required express consent and acknowledgement concerning the loss of the 14-day cancellation right before supplying the content in the relevant circumstances.

28. Legal Rights Take Priority

If any provision of this policy conflicts with a mandatory legal requirement, the mandatory legal requirement will prevail.

The remaining provisions will continue to apply to the extent permitted by law.

This policy does not attempt to:

• Exclude statutory consumer rights.
• Exclude liability that cannot legally be excluded.
• Impose an unlawful penalty.
• Create an automatic right to charge a customer indefinitely.
• Prevent a customer from exercising a lawful cancellation right.
• Prevent a customer from obtaining a legally required remedy.

29. Changes to This Policy

WPCodeForge may update this Refund & Cancellation Policy when necessary.

Updates may be made to reflect:

• Changes to products.
• Changes to licensing arrangements.
• Changes to payment systems.
• Changes to subscription arrangements.
• Changes to refund procedures.
• Changes to applicable law.
• Changes to consumer-protection requirements.
• Changes to how digital products are supplied.

The Last updated date at the top of this page indicates when the policy was most recently reviewed or amended.

30. Contact Us

For refund and cancellation enquiries, contact:

WPCodeForge
Bristol, England
Contact: Contact form

Please include your order number and the reason for your request where possible.

WPCodeForge is owned and operated solely by James William Steven Parker.