slegrand.antidot

@nortom : still waiting for the “more details” we asked 3 months ago. Without this information we can’t progress.

You can send us additional details on [email protected]

There is no parameter for VAT or not in the bpost shipping manager backend.

The only thing you can do is to enter the price VAT excl. in bpost shipping manager backend and then to find a way to apply VAT afterwards, or not.

This is workaround and needs some development but there is currently not other alternative to this issue.

Hello, the plugin by itself doesn’t store any user information it is a technical interface between systems.

When an order is placed in your WP/WC platform, it forwards the customer information towards bpost systems so that it can process it and generate labels and so on.
Plugin also retrieved labels from bpost systems and store it in your WP/WC platform.

Of course, this means your WP/WC platform must be GDPR compliant and bpost systems to be as well (which if of course the case).

Hope this helps.

Considering there is no more update for several months, we can assume the issue is fixed.

Considering there is no more update for several months, we can assume the issue is fixed.

Is issue finally solved ?

No more input from the reporter, we assume the issue is solved

No more update nor feedback for months, we assume it is ok and close the ticket.

Hello the issue was fixed with plugin v2.2.3
Can you confirm it is ok now ?

Hello, some news ?

The ginroom.be website uses Magento framework.

In Magento, the integration of bpost is different than in WP/WooC, therefore; functional behaviour and technical constraints are not the same…

The bpost plugin for WP/WooC is open source, and can be adapted but this require time and effort as well as good php programming skills.

Finally: I forward your functional adaptation request to bpost, maybe they will take it into account for a plugin next release.

We understand your request.

However, we can’t call the bpost popup at step 2, before the order is indeed placed.

There are several functional and technical reasons for that.

For example: when you’ve finished in the bpost popup and leave it… the request is posted towards bpost SHM backend. If you’d go back to step 2 you would still have the ability to update the address -without going back to bpost popup- and finalize the ordering process with a data discordance between what has been sent in bpost SHM backend and where really/finally the parcel has to be delivered and is encoded in wordpress db.

Indeed, the limitation to this behavior is that, at the order recap screen, we don’t know yet how much finally delivery will cost, that’s why we indicate “as from XX”; XX being the lowest cost charged for deliveries configured in SHM backend.

kind regards, SLG

Hello, as asked previously can you please check the following :
Can you check curl’s option “CURLOPT_RETURNTRANSFER” ?
What happens once you run the PHP test file dowloaded here: https://bit.ly/2ktoDYb ?

Can you check curl’s option “CURLOPT_RETURNTRANSFER” ? What happens once you run the PHP test file dowloaded here: https://bit.ly/2ixd9D2 ?

Strange… on our test environments we do not observe this bug. We check and come back to you.