> Zum 01.01.2024 werden die Preise für die "Bücher- und Warensendung
500" und die "Bücher- und Warensendung 1000" um jeweils 30 Cent
angehoben. Der neue Preis beträgt dann 2,25 EUR für die BüWa 500 und
2,55 EUR für die BüWa 1000. Notwendig ist die Preiserhöhung wegen stark
gestiegener Personalkosten nach dem Tarifabschluss im März 2023 sowie
durch drastisch gestiegene Preise aufgrund der Inflation.
Source: https://www.deutschepost.de/de/w/buecherundwarensendung.html
In other news: DPDHL 2022 EBIT was > 8 * 10**9 €
(which yields an EBIT margin of almost 9 % or so)
This time only variants of the existing 'Einschreiben' (registered letter)
were added, i.e. basically all existing variants are extended with
a for registered letter with reply to show receipt ('Rückschein')
variant.
NB: Those products are new to the inema service, the 'Rückschein'
feature already was available with Deutsche Post since forever, but
apparently couldn't be ordered via inema, so far.
New products are activated on 2023-07-01.
i.e. using 20220512_IMPARTNER_PPL51.csv which is distributed by Deutsche Post
via email.
NB: the update doesn't contain any price updates but 'just' removes all
'Warenpost International' products.
Apparently, those products are/were migrated to DHL.
Pricing is not going back to what it was before July 1st, 2020
but there are significant price increases - and some products
that were discontinued. This update covers "ppl_v480_PARTER.CSV"
as received from DPAG on December 1st, 2020.
i.e. VAT temporarily changes from 19% to 16% as part of the Corona
related economy stimulus package. Deutsche Post thus adjusts the prices
for a subset of their products.
i.e. some added/removed products and some price changes
The package now supports multiple price lists and selects the right
one based on the effective date suffix (if present).
This allows the user to re-generate (update) the price list in
products.json using ProdWS API, which is a separate API provided by DPAG
to obtain the product catalogue including pricing information.
Without this patch, python 2.x would abort with a famous
'ascii' codec can't decode byte ...
error. This is why I kept the file free of special characters
so far, but commit 6d2ee85a7e
unfortunately broke that assumption.
I'm sure there's a proper solution, but I really don't feel like
investing time into researching and testing that now.
When using the build_comp_addr() method 'person' argument, we need
to pass in a PersonName object, and not a string name of the contact.
Add a public build_pers_name() method to produce that PersonName object,
and use it from the example code.