> If you are trying to get CCS to work and Google keeps telling you are
> doing something wrong... Ignore Them! CCS has never worked since
> release. If you read these threads both current and past you will find
> that CCS returns inaccurate results for UPS and FedEx and Nonsense for
> USPS.
> Obviously Google does not care if they release crap.
To the best of my knowledge the recent discrepancy was caused by stale
fuel surcharge data. We are still working on matching the rates
exactly with the carrier rates you would find online.
Peng
On Jun 20, 11:44 am, "c...@gamegiants.net" <c...@gamegiants.net>
wrote:
> On Jun 20, 11:37 am, "c...@gamegiants.net" <c...@gamegiants.net>
> wrote:
> > If you are trying to get CCS to work and Google keeps telling you are
> > doing something wrong... Ignore Them! CCS has never worked since
> > release. If you read these threads both current and past you will find
> > that CCS returns inaccurate results for UPS and FedEx and Nonsense for
> > USPS.
> > Obviously Google does not care if they release crap.
+P...@google.com> wrote:
> To the best of my knowledge the recent discrepancy was caused by stale
> fuel surcharge data. We are still working on matching the rates
> exactly with the carrier rates you would find online.
> Peng
> On Jun 20, 11:44 am, "c...@gamegiants.net" <c...@gamegiants.net>
> wrote:
> > bump
> > On Jun 20, 11:37 am, "c...@gamegiants.net" <c...@gamegiants.net>
> > wrote:
> > > If you are trying to get CCS to work and Google keeps telling you are
> > > doing something wrong... Ignore Them! CCS has never worked since
> > > release. If you read these threads both current and past you will find
> > > that CCS returns inaccurate results for UPS and FedEx and Nonsense for
> > > USPS.
> > > Obviously Google does not care if they release crap.
I did some checking and it is not just the "fuel surcharge" all base
rates for Fedex and UPS are coming back too low on the range of
20-40%. Carrier Calculated Shipping shoiuld be inactivated as it just
plain returns false results! It is useless!
On Jun 20, 7:55 pm, "c...@gamegiants.net" <c...@gamegiants.net> wrote:
> USPS has no fuel surcharge and you still do not return correct values!
> On Jun 20, 3:30 pm, CheckoutDevProPeng <Checkout-Dev-Pro
> +P...@google.com> wrote:
> > To the best of my knowledge the recent discrepancy was caused by stale
> > fuel surcharge data. We are still working on matching the rates
> > exactly with the carrier rates you would find online.
> > Peng
> > On Jun 20, 11:44 am, "c...@gamegiants.net" <c...@gamegiants.net>
> > wrote:
> > > bump
> > > On Jun 20, 11:37 am, "c...@gamegiants.net" <c...@gamegiants.net>
> > > wrote:
> > > > If you are trying to get CCS to work and Google keeps telling you are
> > > > doing something wrong... Ignore Them! CCS has never worked since
> > > > release. If you read these threads both current and past you will find
> > > > that CCS returns inaccurate results for UPS and FedEx and Nonsense for
> > > > USPS.
> > > > Obviously Google does not care if they release crap.
> I did some checking and it is not just the "fuel surcharge" all base
> rates for Fedex and UPS are coming back too low on the range of
> 20-40%. Carrier Calculated Shipping shoiuld be inactivated as it just
> plain returns false results! It is useless!
> On Jun 20, 7:55 pm, "c...@gamegiants.net" <c...@gamegiants.net> wrote:
> > USPS has no fuel surcharge and you still do not return correct values!
> > On Jun 20, 3:30 pm, CheckoutDevProPeng <Checkout-Dev-Pro
> > +P...@google.com> wrote:
> > > To the best of my knowledge the recent discrepancy was caused by stale
> > > fuel surcharge data. We are still working on matching the rates
> > > exactly with the carrier rates you would find online.
> > > Peng
> > > On Jun 20, 11:44 am, "c...@gamegiants.net" <c...@gamegiants.net>
> > > wrote:
> > > > bump
> > > > On Jun 20, 11:37 am, "c...@gamegiants.net" <c...@gamegiants.net>
> > > > wrote:
> > > > > If you are trying to get CCS to work and Google keeps telling you are
> > > > > doing something wrong... Ignore Them! CCS has never worked since
> > > > > release. If you read these threads both current and past you will find
> > > > > that CCS returns inaccurate results for UPS and FedEx and Nonsense for
> > > > > USPS.
> > > > > Obviously Google does not care if they release crap.
A while back I spent some time reverse engineering the algorithms used
by UPS.com and FedEx.com. They each use slightly different rounding
rules and orders of operations, and as far as I've found there is no
public documentation of those details. I would be glad to help the
Checkout team achieve an exact match with what the official website
estimators produce. (I've also implemented USPS calculations but I
don't think our rate tables match the public ones so I don't know how
"accurate" my USPS algorithm is... might or might not be able to help
there as well.) (Oh and in case you want to know how bad the
documentation is even inside these companies, UPS's own rate
estimation API sometimes returns slightly different answers than their
public website produces... differences are usually 1 or 2 cents,
presumably due to slightly different rounding and/or order of
operations. Fun fun.) Anyway, if anyone over there is listening and
interested, just drop me a note.
Cheers,
-Ben
On Jun 20, 3:30 pm, CheckoutDevProPeng <Checkout-Dev-Pro
+P...@google.com> wrote:
> To the best of my knowledge the recent discrepancy was caused by stale
> fuel surcharge data. We are still working on matching the rates
> exactly with the carrier rates you would find online.
> Peng
> On Jun 20, 11:44 am, "c...@gamegiants.net" <c...@gamegiants.net>
> wrote:
> > bump
> > On Jun 20, 11:37 am, "c...@gamegiants.net" <c...@gamegiants.net>
> > wrote:
> > > If you are trying to get CCS to work and Google keeps telling you are
> > > doing something wrong... Ignore Them! CCS has never worked since
> > > release. If you read these threads both current and past you will find
> > > that CCS returns inaccurate results for UPS and FedEx and Nonsense for
> > > USPS.
> > > Obviously Google does not care if they release crap.
> A while back I spent some time reverse engineering the algorithms used
> by UPS.com and FedEx.com. They each use slightly different rounding
> rules and orders of operations, and as far as I've found there is no
> public documentation of those details. I would be glad to help the
> Checkout team achieve an exact match with what the official website
> estimators produce. (I've also implemented USPS calculations but I
> don't think our rate tables match the public ones so I don't know how
> "accurate" my USPS algorithm is... might or might not be able to help
> there as well.) (Oh and in case you want to know how bad the
> documentation is even inside these companies, UPS's own rate
> estimation API sometimes returns slightly different answers than their
> public website produces... differences are usually 1 or 2 cents,
> presumably due to slightly different rounding and/or order of
> operations. Fun fun.) Anyway, if anyone over there is listening and
> interested, just drop me a note.
> Cheers,
> -Ben
> On Jun 20, 3:30 pm, CheckoutDevProPeng <Checkout-Dev-Pro
> +P...@google.com> wrote:
> > To the best of my knowledge the recent discrepancy was caused by stale
> > fuel surcharge data. We are still working on matching the rates
> > exactly with the carrier rates you would find online.
> > Peng
> > On Jun 20, 11:44 am, "c...@gamegiants.net" <c...@gamegiants.net>
> > wrote:
> > > bump
> > > On Jun 20, 11:37 am, "c...@gamegiants.net" <c...@gamegiants.net>
> > > wrote:
> > > > If you are trying to get CCS to work and Google keeps telling you are
> > > > doing something wrong... Ignore Them! CCS has never worked since
> > > > release. If you read these threads both current and past you will find
> > > > that CCS returns inaccurate results for UPS and FedEx and Nonsense for
> > > > USPS.
> > > > Obviously Google does not care if they release crap.
> > > A while back I spent some time reverse engineering the algorithms used
> > > by UPS.com and FedEx.com. They each use slightly different rounding
> > > rules and orders of operations, and as far as I've found there is no
> > > public documentation of those details. I would be glad to help the
> > > Checkout team achieve an exact match with what the official website
> > > estimators produce. (I've also implemented USPS calculations but I
> > > don't think our rate tables match the public ones so I don't know how
> > > "accurate" my USPS algorithm is... might or might not be able to help
> > > there as well.) (Oh and in case you want to know how bad the
> > > documentation is even inside these companies, UPS's own rate
> > > estimation API sometimes returns slightly different answers than their
> > > public website produces... differences are usually 1 or 2 cents,
> > > presumably due to slightly different rounding and/or order of
> > > operations. Fun fun.) Anyway, if anyone over there is listening and
> > > interested, just drop me a note.
> > > Cheers,
> > > -Ben
> > > On Jun 20, 3:30 pm, CheckoutDevProPeng <Checkout-Dev-Pro
> > > +P...@google.com> wrote:
> > > > To the best of my knowledge the recent discrepancy was caused by stale
> > > > fuel surcharge data. We are still working on matching the rates
> > > > exactly with the carrier rates you would find online.
> > > > Peng
> > > > On Jun 20, 11:44 am, "c...@gamegiants.net" <c...@gamegiants.net>
> > > > wrote:
> > > > > bump
> > > > > On Jun 20, 11:37 am, "c...@gamegiants.net" <c...@gamegiants.net>
> > > > > wrote:
> > > > > > If you are trying to get CCS to work and Google keeps telling you are
> > > > > > doing something wrong... Ignore Them! CCS has never worked since
> > > > > > release. If you read these threads both current and past you will find
> > > > > > that CCS returns inaccurate results for UPS and FedEx and Nonsense for
> > > > > > USPS.
> > > > > > Obviously Google does not care if they release crap.
We just reviewed the UPS shipping rates calculated by Carrier
Calculated Shipping and they are even worse now than they were
previously. For a 68 lbs UPS shipment from 89510 to 60174 we get these
rates from Google Carrier Calculated Shipping:
Ground $28.79
3 day select $91.78
Express Saver $259.27
and the actual Daily Pickup Rates are:
Ground $45.06
3 day select $150.26
Express Saver $310.25
Carrier Calculated Shipping is TOTALLY UNUSABLE!!!!
On Jul 15, 10:37 am, DosGrandeBeans <Brian.W...@gmail.com> wrote:
It also appears that at least for UPS Carrier Calculated Shipping is
not using the <postal-code> provided in <ship-from> but is using the
destination zip in the customers account.
You can clearly see this if you submit a ccs cart and note the rate.
Now change the destination address to the same zip as the <ship-
from><postal-code> you will see that the rate is now Higher than the
original quote to another area. But again the numbers returned are
wildly inaccurate as opposed to the UPS actual daily rates.
Carrier Calculated shipping is so Buggy Google should just pull it as
IT DOES NOT WORK!!!
On Jul 25, 5:00 pm, gg <gamegia...@gmail.com> wrote:
> We just reviewed the UPS shipping rates calculated byCarrier
> Calculated Shipping and they are even worse now than they were
> previously. For a 68 lbs UPS shipment from 89510 to 60174 we get these
> rates from GoogleCarrierCalculated Shipping:
Still Broken! I thought you said it was going to be fixed today Peng!
Carrier Calculated Shipping still is returning invalid results. I am
glad Google does not write avionics or medical device software!! It is
unbelievable that Google can not write a simple shipping calculator.
To make it worse all the information is readily available from the
carriers.
On Jul 28, 12:28 pm, gg <gamegia...@gmail.com> wrote:
> It also appears that at least for UPSCarrierCalculatedShipping is
> not using the <postal-code> provided in <ship-from> but is using the
> destination zip in the customers account.
> You can clearly see this if you submit a ccs cart and note the rate.
> Now change the destination address to the same zip as the <ship-
> from><postal-code> you will see that the rate is now Higher than the
> original quote to another area. But again the numbers returned are
> wildly inaccurate as opposed to the UPS actual daily rates.
> CarrierCalculatedshipping is so Buggy Google should just pull it as
> IT DOES NOT WORK!!!
> On Jul 25, 5:00 pm, gg <gamegia...@gmail.com> wrote:
> > We just reviewed the UPS shipping ratescalculatedbyCarrier
> >CalculatedShipping and they are even worse now than they were
> > previously. For a 68 lbs UPS shipment from 89510 to 60174 we get these
> > rates from GoogleCarrierCalculated Shipping:
I just spent forever trying to search on Google for this problem and
all I kept finding was the same developers docs. I would fancy a
solution as soon as possible so I can move on with my life.
On Aug 1, 9:41 pm, gg <gamegia...@gmail.com> wrote:
> Still Broken! I thought you said it was going to be fixed today Peng!
> Carrier Calculated Shipping still is returning invalid results. I am
> glad Google does not write avionics or medical device software!! It is
> unbelievable that Google can not write a simple shipping calculator.
> To make it worse all the information is readily available from the
> carriers.
> On Jul 28, 12:28 pm, gg <gamegia...@gmail.com> wrote:
> > It also appears that at least for UPSCarrierCalculatedShipping is
> > not using the <postal-code> provided in <ship-from> but is using the
> > destination zip in the customers account.
> > You can clearly see this if you submit a ccs cart and note the rate.
> > Now change the destination address to the same zip as the <ship-
> > from><postal-code> you will see that the rate is now Higher than the
> > original quote to another area. But again the numbers returned are
> > wildly inaccurate as opposed to the UPS actual daily rates.
> > CarrierCalculatedshipping is so Buggy Google should just pull it as
> > IT DOES NOT WORK!!!
> > On Jul 25, 5:00 pm, gg <gamegia...@gmail.com> wrote:
> > > We just reviewed the UPS shipping ratescalculatedbyCarrier
> > >CalculatedShipping and they are even worse now than they were
> > > previously. For a 68 lbs UPS shipment from 89510 to 60174 we get these
> > > rates from GoogleCarrierCalculated Shipping: