.png.022b5452a8f28f552bc9430097a16da2.png)
Inform-All
-
Posts
610 -
Joined
-
Last visited
-
Days Won
2
12 Followers
About Inform-All
Recent Profile Visitors
9,987,064 profile views
Inform-All's Achievements
-
Good to hear it's working for you now. I'm not familiar with that DHL module, so i don't know what HS code field your DHL module specifically requires. I would assume the DHL module has some kind of documentation on how to pass the HS code?
-
At the moment, this module does not offer that functionality. As it is a paid, community-supported module, you are welcome to contact me privately if you would like a quotation.
-
Let me know what problems you have with this module, and i am more then happy to help. (even though i guess you simply posted this to promote your own *paid* module)
-
The module uses an override in order to function. But it seems that another module you already use, also uses the same override. Usually you can simply merge these overrides, but you would have to do this manually. Mostly anyone with some programming skills could easily do this for you. You could also send me a PM, then i could assist you with this.
-
When you download something from Github it automatically renames it to the branch you download it from, and in this case that is the "main" branch. But to answer your question, yes the version from Github and the first post of this topic are still the latest. I would advice you to simply download the the zip file from the first post.
-
Thanks to the generosity of community members, the module has now been updated in the first post of this topic. This new version introduces an additional module configuration option that allows you to choose which address (shipping or invoice) should be used during checkout.
-
Hi, thanks for your question! At the moment, the DNI field in PrestaShop is a completely separate field, and this module doesn’t interact with it or perform any kind of validation on it. The module only works with the VAT field, so combining both into a single field unfortunately isn’t something it can handle. I understand the need for a unified identifier field, especially with the upcoming requirements in 2026, but this would require changes outside the scope of the module. If you have any other questions, feel free to ask in a private message!
-
This error happens when you have made too many requests to the VIES database. This error is something my module cant and never will fix for you. We do keep already validated addresses in the database so we don't have to double check. This is usually a sign that your shop simply makes to many addresses ( or saves them, and the vat hook will recheck it ). This error happens often when bots create spam accounts. So, no matter what module you will use, your server IP is overused according to the vies database.
-
Great to hear that it’s working well for you! I’m not sure I completely understand your question. The module simply adds validated VAT customers to the group you’ve selected in the module settings — it doesn’t remove them from any existing groups. So, if your shop has a default customer group set, new customers will still be added to that group upon registration. The module just adds an additional group for validated VAT customers. And the "with taxes" label is only (potentially) changed after the first address creation. So unless you have a registration page that adds the address the module simply cant know yet.
-
I am afraid that this is a limit from the VIES database itself. This is a problem outside of the VatChecker module. And it's actually the same problem you asked me before in July (here)
- 219 replies
-
- 1
-
-
- intra-community
- vies database
- (and 2 more)
-
The VAT checker applies 0% if a filled in TAX number is correct. But i have also made a (free) module what you are looking for. The SAME PRICE module allows people to always have the same price no matter what tax rule is applied for the destination country.
-
What Prestashop version are you using? Can you uninstall your VatChecker module completely and then reinstall it? (only the modules settings should be set again, the rest will be fine) Are you using a custom theme, and did the theme change?
-
Sorry for my late response, can you provide more information on what you are doing. Also screenshot for the test address and information (better idea to send this in a private message).
-
Updated the module (first post of this topic and Github) for Prestashop 9 compatibility.
-
Just added Prestashop 9 version in the first post and on Github. Feedback is welcome
