Track17

  • Resolved Jonas

    (@gnuworld)


    3 years, 10 months ago

    Hi

    We have set up a custom shipping provider with their own tracking link, and this is working fine in WooCommerce. All works as expected.

    However, we also use a customer support platform (Re:Amaze) and this pulls in order information via WooC Rest API. The info it pulls in reflects the correct tracking number for orders and it states the correct shipment provider but all the tracking links now point to https://t.17track.net/en#nums={trackingnumber} instead of to the custom tracking links we have set up and which are working in WooC. itself.

    Is there any reason that something different would be retrieved via the Rest API than what we are seing reflected in WooC ?? My colleague said it used to be working fine up until a while ago.

    • This topic was modified 3 years, 10 months ago by Jonas.
Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Zorem

    (@zorem)

    Hi, you will need to check with Amaze why they use Track17 links, it might be something on their end.
    May I ask which shipping providers you use as custom, we will be happy to add any provider to the AST providers list..

    Thread Starter Jonas

    (@gnuworld)

    Hi @zorem OK will do.

    We use “RAM Couriers” who are one of the big South African courier companies.

    Tracking link format is: https://www.ram.co.za/Track/%number%

    Plugin Author Zorem

    (@zorem)

    Can you share a tracking number example?

    Thread Starter Jonas

    (@gnuworld)

    @zorem HHBT776453

    Please also note that I spoke to Re:Amaze support and they said that https://t.17track.net is a link that they use as a fallback when there isn’t a tracking url provided.

    They say they just pull in data from WooC and that they took a look and can see that the custom_tracking_link field is empty.

    So they for example got this payload:

    {“id”=>4190906, “key”=>”_wc_shipment_tracking_items”, “value”=>[{“tracking_provider”=>”cp-ram-couriers”, “custom_tracking_provider”=>””, “custom_tracking_link”=>””, “tracking_number”=>”HHBT776453”, “tracking_product_code”=>””, “date_shipped”=>”1620345600”, “products_list”=>””, “status_shipped”=>”1”, “tracking_id”=>”dfe4a77087583b284fda794c75eebc8b”}]}

    Is the plugin not pushing the custom tracking link through?

    Plugin Author Zorem

    (@zorem)

    Hi,
    ??We added RAM to the AST shipping providers list, please sync the shipping providers list on the AST plugin settings.

    To sync your shipping providers list, go to WooCommerce > Shipment Tracking > Shipping Providers, and on the top-right, click on Sync Providers icon. (more about Sync providers on the AST documentation)

    Thread Starter Jonas

    (@gnuworld)

    Hi @zorem

    Thank you, I have synced and switched over but the issue remains. As per my last comment the “custom_tracking_link”=>”” field is seemingly still empty because re:amaze is still using its fallback link.

    It retrieves the correct provider and the correct tracking code, but not the tracking link.

    Can you check if your plugin is in fact populating the correct tracking link for the WooC Rest API?

    Plugin Author Zorem

    (@zorem)

    Hi, We do not provide the option to pull the tracking link info from the WooCommerce API. You can request for this feature and provide all the necessary details of how it works and what you need on the AST features board here

    Plugin Author Zorem

    (@zorem)

    Hi Jones, we did some research, we will have the option to pull the tracking link from the WooCommerce API available in the next version of the AST Pro.

    Thread Starter Jonas

    (@gnuworld)

    OK, thanks for the update

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Track17’ is closed to new replies.