Add Tracking URL as input field (next to Tracking ID)

Gaston.La.Brick

I did a suggestion in the past (upvoted 8 times, but closed without implementation) to be able to input the full tracking link instead of a tracking number, where the URL is determined by the shipping method (= carrier) and the URL format for the tracking link is determined by BrickOwl website.

Initially, my request was because I use generic shipping methods ("large parcel", but use different carriers for different countries). This results in a tracking link using the wrong carrier.
The workaround suggested by Lawrence, was to create shipping methods for all carriers, change the shipping method after the order was placed to the correct carrier. A somewhat cumbersome, but still manageable workaround.

Today, a customer asked "where is my order" (note: that line is the actual full message of the customer, no more, no less). I did enter the tracking code to the order and made sure the correct carrier is selected.
But the tracking link is not correct. The customer sees a (Dutch) landing page, where he has to enter the tracking code, the destination country and hit "submit". After that step, the tracking is shown.
For a non-Dutch speaking customer, this might be too much. Even when the language wouldn't be a barrier, I like to be as customer friendly as I can and avoid extra steps by the customers.

My suggestion - for another reason as the previous time: please allow us to either add a Tracking ID and/or a full tracking URL to the order. It would make it easier for both buyer as seller, and probably for the technical maintenance of BrickOwl too (as it avoids to maintain all different carriers and their tracking URL formats).

Lawrence

We did change the field length so I think you can just paste the entire tracking link into the tracking field if you want to do that

Gaston.La.Brick

Aha, nice, will try that.

Gaston.La.Brick

Sadly, not a solution.
Please have a look at the effect when I enter a URL.
The URL is stripped (on the right) from all non-alfanumerical characters.
The clickable link still goes to the generic (in this case PostNL) carrier track and trace link.

(Tracking ID obfuscated by intent :-))

Gaston.La.Brick

Wouldn't it be a solution to check if the Tracking ID starts with "https" and use that a the clickable link under the text "See full tracking"? (and maybe don't mention the carrier name)

Vosblokjes

It would even be better if BO made the correct link automatically
PostNL uses a uniform URL for it:
https://tracking.postnl.nl/track-and-trace/<Tracking ID>-<country code>-<postcode>

for example (these aren't real data, these examples will give a parcel not found)
https://tracking.postnl.nl/track-and-trace/3SOPKA513123456-NL-9405ZZ
https://tracking.postnl.nl/track-and-trace/RT123312345NL-US-93123-5456

I think that PostNL decides the language shown based upon the location of the visitor (not sure), otherwise one can choose 1 of 4 different languages very easy.

Gaston.La.Brick

If the tracking link can be correctly formed based on the ID : great.
I do think this is hard to maintain for all carriers. Even the same carrier in different countries (PostNL is available in Netherlands and in Belgium, but are different organizations) can have different formats of tracking links.

So for me, I would like a generic solution where I can just enter the tracking link as I want it, and it will be displayed as a clickable link.

Lawrence

We have now made further changes, so you can use an entire URL that the customer can then click, please let us know if that works as intended

SavioryBricks

Works it great for us! Perfect implementation, thank you!

Gaston.La.Brick

Hi @Lawrence ,

I've tested it with a recent order.
I tried updating the tracking id with this value, as it's the correct tracking link for an order using Belgian postal services (bPost):
https://track.bpost.cloud/btr/web/#/search?lang=fr&itemCode=323235049165191000&postalCode=1070

It seems the part after the # symbol got stripped.
After experimenting a bit with the URL, it seems indeed a problem with the processing of the hashtag character.
Also, it seems only the first parameter of the querystring (the part after the ? character) is retained. All following querystring parameters get stripped. Maybe due to the ampersand character?

I hope this test feedback is useful for you?

Lawrence

@Gaston.La.Brick Thank you for reporting that, that should now be fixed

Gaston.La.Brick

Excellent, verified the correct working now.

Thank you!