Replacing techTRACK carrier code
under review
Edward Aguiar
Merged in a post:
Wrong carrier name being sent in payload
A
Akash Bhalla
For GTAGSM/Chitchat integrations carrier sends consolidator_actual_carrier_name "GTAGSM" but Techtrack sends carrier name as ChitchatsV2. We need
GTAGSM carrier code.
Edward Aguiar
Akash Bhalla another option then would be to split the ChitChat carrier and define a new carrier - "GTAGSM - ChitChat". We would need to do some work on our end first, but then you will need to explicitly select the GTAGSM carrier.
A
Akash Bhalla
Edward Aguiar So what you mean is it will be a new configuration altogether and we need to disable Chitchats and turn on this one ? or within this configuration we can just select the carrier name
A
Akash Bhalla
Edward Aguiar any update on this ? Can we get on a call to understand this?
Edward Aguiar
Akash Bhalla kash Bhalla We’re expanding the techTRACK API to include additional fields specifying the actual carrier and service for the carrier performing the delivery. These fields will only be populated for consolidator carriers, so you’ll need to check them in addition to the existing ones. We can’t change the default behaviour because other customers rely on it today. Does this approach meet your needs?
A
Akash Bhalla
Edward Aguiar but if the new fields are going to populate details for only the consolidator carrier, not other regular carriers, that is going to be a problem as we drive our shipment emails and other analytics queries based on the carrier name field, and I would not want to complicate things in that flow. I would rather suggest if it's possible to have the logic below.
If it's a consolidator carrier, pass the carrier doing the delivery into the new field.
If it's a regular carrier, pass the regular carrier name into the new field.
This way will although we will have a new field but that field will have all information in it, and we do not have to look for different fields for different carriers.
Edward Aguiar
marked this post as
under review