GithubHelp home page GithubHelp logo

Comments (9)

ngolatka avatar ngolatka commented on July 4, 2024

At the moment I don't really understand the purpose of manually entering a tracking number when DHL will generate one anyway.

Are you using the custom tracking number like an order reference? If yes, there's a separate API field for that.

from dhl-shipping-m2.

in-session avatar in-session commented on July 4, 2024

In this case, for example, if a validation fails and we have to initiate the dispatch manually, we create a label in the DHL portal which is then added manually if necessary. If the validation then works, a second label is created. It is then not possible to simply remove the label. After removing the automatically generated label, a new one is created. Here it would be desirable to check whether a label is already stored and then to prevent the automatic generation.

from dhl-shipping-m2.

ngolatka avatar ngolatka commented on July 4, 2024

Thanks for the explanation! It looks like the double tracking numbers are rather the symptom of the underlying issue, which seems to be a somewhat strange workflow.

You wrote

if a validation fails and we have to initiate the dispatch manually [...] If the validation then works, a second label is created

This sounds to me like you corrected some error in Magento (e.g. a mistake in the shipping address) after already creating the label manually in the DHL portal. Then you triggered the label creation in Magento again. If that is correct, why did you create the label in the DHL portal anyway, instead of doing everything in Magento?

Generally speaking, you should not create a label in the DHL Business Customer Portal and also in Magento. It should only be one or the other – preferably in Magento, so our extension can handle everything, all the correct events get triggered, etc.

from dhl-shipping-m2.

in-session avatar in-session commented on July 4, 2024

We have the labels generated automatically with batch processing, i.e. we do not trigger them per order. In this case you are right that we have corrected the address, as in the other Usses. The label was then generated automatically. We have now tried to delete the automatically generated tracking number as there are now two of them. However, a new one is then generated immediately and we have no way of preventing this in this case. The customer now always receives two tracking numbers.

from dhl-shipping-m2.

ngolatka avatar ngolatka commented on July 4, 2024

Ok, but then the question still remains: why don't you simply correct the address in Magento and use the batch process again?

If the timing is critical, you could also trigger the label creation for the affected order(s) in Magento, not having to wait for the next run of the cronjob.

To me, that makes the most sense. Just don't manually create the label in the DHL portal at all. Do everything in Magento via our extension to prevent things getting mixed up. That is the way it's supposed to be done.

Or is there anything preventing you from doing it like this? I'd really like to know.

from dhl-shipping-m2.

in-session avatar in-session commented on July 4, 2024

The problem is that due to the use of some payment service providers like klarna, the address can no longer be changed once the order has been submitted:

image

We therefore have no way of correcting the address data.

from dhl-shipping-m2.

ngolatka avatar ngolatka commented on July 4, 2024

I have to admit that I'm a bit confused.

You wrote

In this case you are right that we have corrected the address, as in the other Usses. The label was then generated automatically.

That sounded to me like you were indeed able to edit the address later. If you can't correct the address in Magento, then you should never get a DHL label via our Magento extension.

But to shorten this: would it be easier if you disabled this option? Then the cronjob would not touch the failed shipments again. You could of course still retry them manually in Magento.

image

from dhl-shipping-m2.

in-session avatar in-session commented on July 4, 2024

That sounded to me like you were indeed able to edit the address later. If you can't correct the address in Magento, then you should never get a DHL label via our Magento extension.

No, I have changed this within the database. But I will contact Klarna again to see if they can reactivate the edit button for the delivery address.

Thanks for your suggestion, I have now deactivated the checkbox and will continue to monitor this.

from dhl-shipping-m2.

ngolatka avatar ngolatka commented on July 4, 2024

I have changed this within the database.

Ah, I see. Would it then be possible to simply not create a label in the DHL portal, but do it in Magento through our extension, after you made the correction in the DB?

from dhl-shipping-m2.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.