Hi @dizzaineris,
Thank you for taking the time to share your feedback. I’m sorry to hear that the plugin did not meet your expectations.
The invoice document itself is fully available in the free version, including both the PDF invoice and the electronic invoice (e-invoice), with support for standards such as UBL and CII. Many users are able to include all legally required information using the available settings.
That said, we would genuinely like to understand your specific situation better. Could you please let us know which information you were unable to add to the invoice and why it was mandatory for your use case? With a bit more detail, we can help determine whether there is a setting you may have missed, a possible workaround, or an area where the plugin could be improved.
Your feedback is very appreciated and helps us improve the plugin for everyone 🙂
Hello, @yordansoares Yordan Soares
Shop VAT Number can only be added to the invoice template with a paid plugin. Without this number the invoice is not valid in our country.
Thanks for the clarification, @dizzaineris:
We’ve discussed this internally with the team and agree that you raised a valid point.
As a result, we’ve decided to remove the display settings for both the VAT number and the CoC number from the Professional extension. Instead, these values will now only be shown when the fields are actually filled in. This improvement will apply to all users, not just paying customers, helping to streamline the experience and avoid the confusion you highlighted.
In the meantime, if you need to display your VAT number while using the free version, you can do so by adding a line such as VAT number: 0123456789 in the Shop Additional Info field, that you’ll find in your WordPress Dashboard > WooCommerce > PDF Invoices > “General” tab, within the Shop Information panel.
This will ensure the VAT number is still visible, even though there is currently no dedicated display setting in the free plugin.
We understand that having a specific field but needing to rely on a general information field to display its value isn’t ideal from a user-experience perspective. This approach is therefore intended as a temporary workaround until the next release.
I’ll keep you posted as soon as this change has been implemented!
