QuickShip Fedex REST API

Kinetic ERP
102

Chris, from my testing there are not errors when phone numbers are blank if you have a default phone number set up in your config.

I forget where, but I’m pretty sure in QS config for facility you can toggle something or fill something out that uses a phone number of your choosing when these things are blank. Maybe the phone number to your shipping dept.

103

Thanks Utah. I wish I knew where that setting was, because both UPS and FedEx seem to be requiring a phone# for all 3rd party billing now. I found this reference in the QuickShip help:

The enhancement in phone number hierarchy reduces errors caused by missing or incomplete contact information.

The order in which the REST API searches for contact information when building the shipment payload is:

  1. Ship-To “Attention” of the Order
  2. Ship-To Primary Shipping Contact
  3. Ship-To Record Contact
  4. Sold-To “Attention” of the Order
  5. Sold-To Primary Shipping Contact
  6. Sold-To Record Contact The enhancement in phone number hierarchy reduces errors caused by missing or incomplete contact information.

The order in which the REST API searches for contact information when building the shipment payload is:

  1. Ship-To “Attention” of the Order
  2. Ship-To Primary Shipping Contact
  3. Ship-To Record Contact
  4. Sold-To “Attention” of the Order
  5. Sold-To Primary Shipping Contact
  6. Sold-To Record Contact
104

I think Utah is talking about a different phone number field. You can’t use your own for a third-party billing account.

You can use your shipping departments phone number on the label. If you don’t have the customer phone number. But that just means if they can’t deliver, they’re calling you instead of the customer.

2 Likes
105

Ahhhh. I see now… it’s third party billing that forces the phone number.

I will test again and let them know.

@spaceage I misunderstood what was happening. I didn’t test third party billing… I need to test that. And like Chadd said, it’s going to bark.

107

Which I think has been a thing for a while.

I was thinking the phone number you were talking about being required @utaylor was the customer phone number.

2 Likes
108

I’m not trying to talk about anything different than what @spaceage was trying to explain haha so sorry if I’m confused and making this more confusing.

1 Like
109

All good. This thread has covered a lot of ground.

2 Likes
110

I think I confused the topic by adding the hierarchy - that structure is valid for every shipment, regardless of carrier or how it’s being billed. The 3rd party billing phone# was what I had originally thought was causing the freighting errors, but it turned out to be due to there being no customer phone# at any level in that hierarchy.

1 Like
111

What do you mean by this specifically? Are you saying that there needs to be a phone# at some point (any point) in the hierarchy and we’ll be fine?

For example, if we are using a ship to num and it’s not the customer’s default address (blank ship to), then the ship to needs to have a phone number OR the customer has to have a ship to? Is that right, either or? And if it was just shipping to the customer, no ship to ID present, the customer has to have a phone number, is that right?

Thanks,

Utah

112

Yes, for any freighting activity with UPS or FedEx, this seems to be a requirement now. If you have a # somewhere in that hierarchy, you should be good. Regarding 3rd party & phone numbers, the 3rd party billing guide details what’s required for each billing type. Some just require a phone#, some required the full billing address and phone #.

For example, if we are using a ship to num and it’s not the customer’s default address (blank ship to), then the ship to needs to have a phone number OR the customer has to have a ship to? Is that right, either or?

Correct.

1 Like
113

But is this any change from before? You’re saying the phone number wasn’t required before for third party?

114

I didn’t start seeing these phone number errors on regular, freighted shipments until we migrated to the FedEx REST API - regardless of 3rd party billing type. We have always seen 3rd party billing phone # errors and would adjust based on the QuickShip guide.

1 Like
115

That’s the thing Chris I ran through prepaid and add scenarios with no phone number anywhere and it never errored out.

Then when I changed freight payer to third party then it complained when the ship to didn’t have a phone number.

Also, are you using a dummy third party account to test that out against sandbox apis or you testing against your actual fedex api with actual account?

116

Prepay & Add excludes 3rd party I believe - it adds the freight cost to the shipment as a Misc Charge. Third Party, FedEx Recipient, UPS Consignee…those are the 3rd party billing types. I didn’t have time to test using dummy accounts, so this was all live fire.

1 Like
117

Yeah, you couldn’t have Prepay & Add and be 3rd party.

4 Likes
118

side note… when I first read that line I read “freighting” as “frightening”… gives it a whole 'nother flavor!

2 Likes
119

It’s been both, so appropriate :rofl:!

1 Like
120

It has indeed.

121

Installing UPS Worldship certainly falls into that category…their account validation process was a disaster. Half the time it didn’t work even if you had the right credentials.

1 Like
122

I just tested it and yeah, the ship to has to have a phone number for Third Party, FedEx Recipient, and consignee when shipping through a fedex service. Not worried about testing UPS at this time.

2 Likes