Title: WRONG LINK WHEN USING J&T
Last modified: August 5, 2022

---

# WRONG LINK WHEN USING J&T

 *  Resolved [mikzeng](https://wordpress.org/support/users/mikzeng/)
 * (@mikzeng)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/wrong-link-when-using-jt/)
 * Hi,
 * When we use J&T singapore, the links all send customers to J&T id. This is very
   bad for them as we are receiving many complaints. How can this be rectify? Thank
   you.

Viewing 1 replies (of 1 total)

 *  Plugin Author [Zorem](https://wordpress.org/support/users/zorem/)
 * (@zorem)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/wrong-link-when-using-jt/#post-15890236)
 * Hi [@mikzeng](https://wordpress.org/support/users/mikzeng/),
 * J&T Singapore doesn’t have a direct link with the tracking number. You need to
   enter the tracking number manually in it.
 * You can use [TrackShip For WooCommerce](https://wordpress.org/plugins/trackship-for-woocommerce/).
 * Thanks

Viewing 1 replies (of 1 total)

The topic ‘WRONG LINK WHEN USING J&T’ is closed to new replies.

 * ![](https://ps.w.org/woo-advanced-shipment-tracking/assets/icon-256x256.png?rev
   =2166296)
 * [Advanced Shipment Tracking for WooCommerce](https://wordpress.org/plugins/woo-advanced-shipment-tracking/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/woo-advanced-shipment-tracking/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/woo-advanced-shipment-tracking/)
 * [Active Topics](https://wordpress.org/support/plugin/woo-advanced-shipment-tracking/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/woo-advanced-shipment-tracking/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/woo-advanced-shipment-tracking/reviews/)

## Tags

 * [wrong link](https://wordpress.org/support/topic-tag/wrong-link/)

 * 1 reply
 * 2 participants
 * Last reply from: [Zorem](https://wordpress.org/support/users/zorem/)
 * Last activity: [3 years, 10 months ago](https://wordpress.org/support/topic/wrong-link-when-using-jt/#post-15890236)
 * Status: resolved