Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New mandatory datas for shipping outside EU #27

Open
zangra-dev opened this issue Feb 10, 2021 · 10 comments
Open

New mandatory datas for shipping outside EU #27

zangra-dev opened this issue Feb 10, 2021 · 10 comments

Comments

@zangra-dev
Copy link

Hello,

We received an email from bpost telling us that more details will be mandatory for shipping outside EU.
If the datas are not completed from March, the shipments will not be possible anymore.

The requirement datas are the details of item send in the parcel (quantity, description, origin, HS Code, item's value, item's weight).
There is a way to config those datas and send it by the API ?

Is it corresponding to the lines : $order->addLine( new Line("Article description", 1) ); ? Or something totally different ?

With a little research, I found a postmen api doc explain the items details : https://docs.postmen.com/bpost.html?sdk=php#item
You think you can add it to your api ?

Thanks in advance for you answer

@zangra-dev
Copy link
Author

Continue my search and refind the official bpost api doc.
The parcelContents is a object link to "International" like the CustomInfos

Here is the xml code from the doc

<international:parcelContents>
    <international:parcelContent>
        <international:numberOfItemType>2</international:numberOfItemType>
        <international:valueOfItem>200</international:valueOfItem>
        <international:itemDescription>t-shirt ARMANI L  WINTER 2020</international:itemDescription>
        <international:nettoWeight>400</international:nettoWeight>
        <international:hsTariffCode>61091000</international:hsTariffCode>
        <international:originOfGoods>US</international:originOfGoods>
    </international:parcelContent>
    <international:parcelContent>
        <international:numberOfItemType>4</international:numberOfItemType>
        <international:valueOfItem>425</international:valueOfItem>
        <international:itemDescription>Gloves leather ARMANI L WINTER</international:itemDescription>
        <international:nettoWeight>500</international:nettoWeight>
        <international:hsTariffCode>420329</international:hsTariffCode>
        <international:originOfGoods>IT</international:originOfGoods>
    </international:parcelContent>
</international:parcelContents>

I will work on my fork in speed (our new release is for March so not much time ^^') and propose a PR with a clean code for the parce contents after the rush

@zangra-dev
Copy link
Author

After a day of work, i extend the Box/International the Box/CustomsInfo/CustomsInfo and create the Entity ParcelContent

The XML for the CustomInfo is correctly generated.
this is the XML in the doc for the customInfo (bpack integration manual v 3.3.21.pdf on p. 51)

<international:customsInfo>
    <international:parcelValue>625</international:parcelValue>
    <international:contentDescription>Ipad 6</international:contentDescription>
    <international:shipmentType>GIFT</international:shipmentType>
    <international:parcelReturnInstructions>RTS</international:parcelReturnInstructions>
    <international:privateAddress>false</international:privateAddress>
    <international:currency>USD</international:currency>
    <international:amtPostagePaidByAddresse>12.50</international:amtPostagePaidByAddresse>
</international:customsInfo>

And this is my XML generated

<international:customsInfo>
    <international:parcelValue>8956</international:parcelValue>
    <international:contentDescription>lamps</international:contentDescription>
    <international:shipmentType>GOODS</international:shipmentType>
    <international:parcelReturnInstructions>RTS</international:parcelReturnInstructions>
    <international:privateAddress>true</international:privateAddress>
    <international:currency>USD</international:currency>
    <international:amtPostagePaidByAddresse>5</international:amtPostagePaidByAddresse>
</international:customsInfo>

But the currency and PostagePaid is not set in the shipping manager... And same thing for the ParcelContents...
I have sent a email to bpost to ask how and what to do to have a correct setting...

But if you have an idea of what to do ... I take it with pleasure
(tag you @aselvais @shubinont @Cryde @kouinkouin to be sure you will see the messages, sorry if you are not involved in the project )

@kouinkouin
Copy link
Member

Hi,

First, thanks to contribute on the library!

I'm checking it with bpost and come back asap (I hope tomorrow).

@kouinkouin
Copy link
Member

I retrieved the official doc of the bpost api : https://bpost.freshdesk.com/support/solutions/articles/4000037653 (I will add the link in the readme).
The library has some delays compared to the API.

@zangra-dev
Copy link
Author

I don't know if they have done a correction during the night but this morning everything is working, the currency is correctly set like the PostagePaid and all Parcel Content are ok

If you want to see the additions I've done there is the 3 commits (I don't make a PR because in our fork there is all work about the International Pugo except if you want it)
zangra-dev@05c0cf9
zangra-dev@e9bb967
zangra-dev@590d7c2

@kouinkouin
Copy link
Member

Nice! I will check globally the library in the next weeks (before March ;-) ).
I will check your (old :-/ ) PR for Int. Pugo too.

@eroctra
Copy link

eroctra commented Aug 29, 2022

@kouinkouin Any update on this?

If I recall correctly it's not yet possible to provide the EAD fields (quantity, description, origin, HS Code, item's value, item's weight,...) in shipments. We received the following notice from Bpost a couple of days ago:

As of 1st November 2022, under customs decision, parcels without EAD can be send back to sender without any carrier intervention nor compensation.

By using the version 5, you will also get the possibility to use (if available in your contract) our latest products and options. The Shipping Manager webservices under version 5 will be unsupported and decommissioned as from November 1st 2022.

The library uses version 3 correct?

@kouinkouin
Copy link
Member

Hi @zangra-dev .
Sorry, really, for my absence.

Can I cherry-pick yours 3 commits (by keeping the author of these commits!) and make a release?
Did you do some things concerning the International shipping?

@zangra-dev
Copy link
Author

Hello @kouinkouin
Of course you can ;)

Yes I've done some work for the International shipping, but with extends (International, CustomsInfo) and a new one , ParcelContent .
You can download the files with this link ;) https://we.tl/t-7qB13PQGF9

@kouinkouin
Copy link
Member

You can download the files with this link ;) https://we.tl/t-7qB13PQGF9

BpostAPI_Entity_Extends.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants