Justin incorrectly fills in TTN in the order

[quote] Kupriyan Vladislav Valerievich wrote: Why is this correct TTN not shown in the order, and what kind of code does it show in the TTN? [/quote] We import the invoice number (TTN) and internal number EH (when created from OneBox, it corresponds to the process ID) that the Justin API gives us. The sticker is printed not by the TTN number, but by the internal EH number. Why they have a different TTN number printed in the sticker - you can ask Justin technical support directly

[quote] Tyndyk Maxim Vadimovich Administrator wrote: [quote] Kupriyan Vladislav Valerievich wrote: Why is this correct TTN not shown in the order, and what kind of code does it show in the TTN? [/quote] We import the invoice number (TTN) and internal number EH (when created from OneBox, it corresponds to the process ID) that the Justin API gives us. The sticker is printed not by the TTN number, but by the internal EH number. Why they have a different TTN number printed in the sticker - you can ask Justin technical support directly [/quote] By the number that is written in the box after creation, nothing can be tracked That is, I cannot send this number to the client so that he can track the delivery, also I cannot send this number to the outlet, since again it will not be tracked How can I make it so that in the box in the invoice field the TTN number is written, which is displayed on the sticker?

I assume that now you need to use the number in the form 41*****77 (9-digit) as the TTN, which they give in the number element. In parallel with this, it is necessary to change the logic of receiving shipment statuses to work with the new TTN format, because in the status receiving API they also write that the current type of TTN is outdated, but it works.

[quote] Tyndyk Maxim Vadimovich wrote: I assume that now you need to use the number in the form 41*****77 (9-digit) as the TTN, which they give in the number element. In parallel with this, it is necessary to change the logic of receiving shipment statuses to work with the new TTN format, because in the status receiving API they also write that the current type of TTN is outdated, but it works. [/quote] If it needs to be finalized - it takes 2 hours

I don’t know how it used to work at all and what TTNs were sent to customers, but I understand that now I can’t send a TTN to a client from the box, by which he can track the movement and status of his package Now everything works like this I went into the order made TTN Justin, then opened the sticker for printing From there I took the TTN number, wrote it down on the invoice and then send it to the outlet and to the client Clients come here https://justin.ua/tracking?number=41*****77 and check the status by the number (which is on the sticker) Nothing can be traced by the number that the box now issues after the creation of the TTN But this is all a "calic" option that takes a lot of time and this is all done, to put it mildly, through one place 1. It turns out that it would all work, you need to pay for revision? 2. There are no other options (what would it work like other logistics of NP and UP - the TTN code in the invoice field is correct)?

[quote] Kupriyan Vladislav Valerievich wrote: 1. It turns out that it would all work, you need to pay for revision? 2. There are no other options (what would it work like other logistics of NP and UP - the TTN code in the invoice field is correct)? [/quote] I can once again quote the text above, which describes why this happens and what is a possible solution. If you read it more carefully, you will see that your judgment that the number on the top of the sticker is the delivery note number is erroneous. This is the package number. Apparently now instead of TTN it is necessary to use the EH number, I provided the solution and assessment. [quote] Tyndyk Maxim Vadimovich wrote: We use the API https://justin.ua/api/api_justin_documentation.pdf , where, according to the documentation of paragraph "11 REQUEST FOR THE FIXING OF THE EXPRESS INVOICE" in the description of the response, it is indicated that the TTN number is given in the ttn element. But since they signed that this parameter is "obsolete" - apparently they have changed something in their architecture recently and did not notify anyone. As far as I understand, what is written on the sticker is the number of the freight unit of departure, and not the TTN. As far as I remember from personal experience of using the services of this logistics company, their TTN numbers have a 9-digit value. I assume that now you need to use the number in the form 41*****77 (9-digit) as the TTN, which they give in the number element. In parallel with this, it is necessary to change the logic of receiving shipment statuses to work with the new TTN format, because in the status receiving API they also write that the current type of TTN is outdated, but it works. If it needs to be finalized - it takes 2 hours [/quote]

In short, it's clear Let it work through one place I guess that just no one uses the functionality of creating TTN justin in OneBox Are you planning to invest in solving this problem?

[quote] Kupriyan Vladislav Valerievich wrote: Are you planning to invest in solving this problem? [/quote] I don't answer questions like this. And for investments, there was already a topic on the forum, which described the rules for their provision.

[quote] Kupriyan Vladislav Valerievich Baza.cn.ua / Integrator (FOP Kupriyan) wrote: In short, it's clear Let it work through one place I guess that just no one uses the functionality of creating TTN justin in OneBox Are you planning to invest in solving this problem? [/quote] Stop pouring shit, I'm already tired of reading this. I give you one last warning

[quote] Ustimenko Igor OneBox CTO wrote: [quote] Kupriyan Vladislav Valerievich Baza.cn.ua / Integrator (FOP Kupriyan) wrote: In short, it's clear Let it work through one place I guess that just no one uses the functionality of creating TTN justin in OneBox Are you planning to invest in solving this problem? [/quote] Stop pouring shit, I'm already tired of reading this. I give you one last warning [/quote] And where did you see "shit" why are you starting to "press"? I figured it out and it turned out that now it’s not easy to work with the delivery of Justin, you have to print, then interrupt the TTN and it’s all somehow wrong, compared to other UP and NP logisticians At the same time, they offer me to make a revision, well, it’s somehow abnormal at least, if the integration with Justin is raw, then you need to write it like that, or if I figured it out wrong, then give me more information so that I can understand from it what I’m doing wrong

[quote] Kupriyan Vladislav Valerievich Baza.cn.ua / Integrator (FOP Kupriyan) wrote: [quote] Ustimenko Igor OneBox CTO wrote: [quote] Kupriyan Vladislav Valerievich Baza.cn.ua / Integrator (FOP Kupriyan) wrote: In short, it's clear Let it work through one place I guess that just no one uses the functionality of creating TTN justin in OneBox Are you planning to invest in solving this problem? [/quote] Stop pouring shit, I'm already tired of reading this. I give you one last warning [/quote] And where did you see "shit" why are you starting to "press"? I figured it out and it turned out that now it’s not easy to work with the delivery of Justin, you have to print, then interrupt the TTN and it’s all somehow wrong, compared to other UP and NP logisticians At the same time, they offer me to make a revision, well, it’s somehow abnormal at least, if the integration with Justin is raw, then you need to write it like that, or if I figured it out wrong, then give me more information so that I can understand from it what I’m doing wrong [/quote] If you are not satisfied with the revision, wait until other clients do it or make an investment and what's wrong here I don't understand In any case, I gave the OS - take into account

[quote] Ustimenko Igor OneBox CTO wrote: and what's wrong here I don't understand [/quote] It is not normal that in order to send the TTN to the outlet you need: 1. Create it in box 2. Next print the siter 3. Then rewrite from the TTN sticker 4. Enter this code in the invoice field (remove the incomprehensible code that now comes from Justin's api) 5. And only because of this already send the TTN to the outlet and to the client Looking forward to investment!

some kind of tin - you even get lost who is the support here and who is the client)) I thought I had a complicated relationship with TP, but it turns out to be a tradition))

TP employee Justin answered me that the normal (short) TTN code also comes to the API Here is "Good afternoon. In the response to the creation of EH, there is also a short number. The field is called number" Please correct this moment https://prnt.sc/vhdsf9

Dear developers, could you correct the action that sends the invoice to the Rosette https://prnt.sc/vswiha so that in the case of Justin, it would send this invoice https://prnt.sc/vswj5s (and does this field have name in van box to substitute in SMS templates for clients?)