USPS Server Meltdown
m2pc writes "The US Postal Service is experiencing major server issues for its shipping API web services. After spending about an hour debugging my own eCommerce software for a client, I found the problem was with the USPS shipping servers being unavailable. Further research showed that message boards for OS Commerce and other e-Commerce packages are filling with posts from angry users who are experiencing crashing Web store applications and frustrated customers. Developers are scrambling to find interim solutions, from hard-coding fixed price shipping, to 'rolling their own' shipping calculation APIs based on the USPS Fixed Rate Zone Tables, to disabling the USPS option altogether. One user reported yesterday that a call to USPS yielded the response 'we expect it to be down all day.' As of 9:20 AM PST the service is still unavailable."
Sounds like the USPS is just angling to get some of that federal bailout money! Oh wait...
And that's what you get for writing e-commerce packages that rely on 3rd party sites for basic functionality...
Don't say I didn't tell you so...
My blog
"Neither snow nor rain nor heat nor gloom of night stays these couriers from the swift completion of their appointed rounds"
But the computers will!!!
Provide a web service, apparently.
When servers go down, the best idea is to Slashdot them.
Only a really terrible developer would hit a web services API and not code for it to fail. No one should expect a third party service to be up 100%. The apps should fail gracefully. Anyone finding their e-commerce software handling this situation poorly should find another package.
If a store offers only the USPS delivery method and the web service is down, the user could be directed to call the sales number to place their order. If the store offers other deliver methods the store front could instruct the user that USPS isn't currently available and they must choose another method.
Developers: We can use your help.
Answer:
Because he wrote it without any error handling, nor the ability to report issues with third party sites back to the eCommerce site administrator.
an again my great tax dollars at work!!!!! Shoot guess they are going to increase taxes again to fix it...
If the log rolls over we'll all be dead!
god man Slashdot is becoming pretty dark with all this apocalyptic foreshadowing.
I don't mean the USPS, I mean the people using their service.
They never thought this might fail?
This is sure to piss off a lot of people being between that Thanksgiving and Christmas period. Lets hope nobody that ordered me something is having problems.
"I don't have to think. I only have to do it. The results are always perfect, but that's old news." - Meat Puppets
...but not through server crashes, apparently. :-)
-- http://ninthagenda.com/
This is a great example of why SAS (Software as a Service) in its current form will eventually fail. The very nature of the Internet is to be disconnected and stateless. If there is no guaranteed delivery at the 5 - 9's level (99.999%), then how can business expect to depend on the service? Mind you, I don't have a better model, but we had better come up with one if we intend to continue using the Internet for commerce!
thats rhe slashdot effect for ya! :P
I was trying to figure out why one of my Christmas cards to an address got delivered while another one to a different person at the same address got returned marked "VACANT." I called the national number, and the rep I talked to tried to look up the address and said, "Oh, our system is down." But she was still able to give me the number of the PO I needed, so I got my answer from them.
I work at a small used bookstore and we use USPS's own Shipping Assitant program for labels, and I had to do weverything by hand the past two days because the program was whining about some connection error. Lol.
USPS has IT people? Oiy veih I can imagine that job.
It would probably snailmail patches to all the vendors connecting to their site ;-)
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
Try it. Go to a USofA-based commercial site and check the shipping charges for your purchase.
Most of the sites are offering free shipping. I'm guessing that these two items are related.
Our website has been suffering from time outs and dropped connections to the UPS rate calculator web service as well since yesterday. Seems to be intermittent, refreshing the page seems to help and it will eventually connect. Luckily none of our customers see the problem as our sales tools are all internal. Happy Holidays!
TODO: Insert witty sig
The government can't even manage to keep a simple web service online, and people still believe that it would be wise to let them control health care. Once they can handle the trivial, they should be allowed to move onto bigger things.
You don't make the poor richer by making the rich poorer. - Winston Churchill
I came in yesterday morning to find the USPS module non-functional. Worse, the only working option was DHL overnight - and in case you've missed the news, DHL is now about an order of magnitude worse than the post office for domestic delivery. Even for places they say they can do next-day delivery to, actual delivery can take more than a week.
Why? Because they hand it off to the post office rather than deliver it themselves. Why it takes the post office a week to deliver it when I can get it there in two days by sending it by priority mail myself is a mystery. In any case, DHL's out of the (US) domestic game entirely next month.
My site was up last time I checked, but if the USPS option goes down again, I think it's time for a 'free economy shipping' promotion. No messy rate tables to deal with!
After I indirectly purchase a Ford, Chevy and Chrysler at the same time with my already paid tax-dollars - guess I'll be throwing more cash at the USPS computer infrastructure. I think I have some old blade servers with a single working power supply in the shroud you can have instead of my tax money.
An unexpected error occurred. An exception occured in module:
USPS
at address: 0x1234 Main St., Hometown USA, zc=0x10001
posting anonymously to cover my ass... We upgraded to MySQL 5.1 last week. We had some major table corruption and no backups. Sadly, no one will be fired or even reprimanded for any of this major cluster fuck.
So that's why I haven't been getting any orders from my website.
The company I work for provides a hosted e-commerce shopping cart solution, SEO-Cart, which supports the USPS Web Tools. Of course the first call coming in for the day was from a client using USPS and having incorrect shipping prices being calculated for their store.
I went ahead and called USPS and the lady who answered was quite rude and explained to me that they had a Worldwide outage which affected other applications than just their Webtools API, and also that they hire a 3rd party company to handle their Webtools API software. She couldn't provide any other information at all and I told her a company of that size should have some sort of fail over plan in place to prevent them from being down as long as they have been. I was really disappointed in the fact she didn't even ask me for my name, phone number, or company by time the conversation was over, but she was probably being bombarded with phone calls all day.
After figuring out that USPS was completely down, I looked through our fail over code and found the following equations seem to come close to the USPS pricing:
National shipping: [cart-weight]*1.6+3.00
International shipping: [cart-weight]*1.6+15.00
These also include pricing for insurance.
After tweaking the fail over pricing code to this, it seemed that everyone using USPS were happy with the results. We also had to decrease the connection timeout set for the request to the USPS Webtools API which was also slowing things down.
The Webtools API seems to be both up and down today, with some orders having shipping prices directly from USPS and others having the fallback pricing. Either way, hopefully their IT department learns from this and also provide us information as to what exactly went wrong.
On that note, this is a prime example that I use when speaking to prospects about the advantages of using a hosted shopping cart solution rather than a licensed/free download solution. Besides the obvious IT benefits that you get with a good hosted shopping cart solution, hosted shopping cart software is typically a centralized application that can provide quick updates to problems like these. Of course this is assuming that the prospect is serious about their online store and doesn't want to handle technical support themselves.
To be fair, what sort of "backup" calculation would you have done here, short of reverse-engineering the USPS algorithm for calculating shipping rates?
I'm not usually a rabid free-market libertarian, but this here can be seen as a result of the fact that the USPS isn't really beholden to its customers. Can you imagine FedEx or UPS being afflicted by such an issue? And, if they were, would they blow off inquiries with a glib, "We expect the servers to be down for the rest of the day?" Of course not, because, for FedEx, UPS, DHL, et. al. such an outage directly affects the health of the organization. If people can't calculate shipping rates, they can't ship, and if they don't ship, the company doesn't make money. The close linkage between revenue and working services tends to put more impetus behind keeping things working and making sure that they get fixed quickly if they do happen to go down.
We all know what to do, but we don't know how to get re-elected once we have done it
That's why I use Virgania Horsen's Pony Express.
"We shall grapple with the ineffable, and see if we may not eff it after all." - Douglas Adams
Serves em right for not producing a Mac version. :)
This explains why my Christmas sales are in the toilet. I'm glad I took a break and decided to read Slashdot. I've had fairly good luck with my OSC connection directly into USPS. Guess not now, huh?
"Here's what's happening. You're starting to drive like your Dad..." - Red Green
Why don't more companies just use the old "Shipping & Handling" charge to cover the costs of shipping without having to calculate the rate the the USPS is going ot charge them. Charge a fee that is close to what you expect to pay. Over on a few and under on a few, but should even out at the end.
Spelling and Grammar errors have been added to this post for your enjoyment
I currently cannot sign up for a rebate, because MSI's rebate center REQUIRES the address to be verified by USPS, and for 2 hours last night all I was getting was Gateway Not Responding or Server not found errors. they better get it back up by my rebate deadline or I will be pissed.
Oh, and I am already upset that they wont send the rebate to a PO Box, because my street address has never been in the USPS database due to our town requiring us to use their PO Boxes.
To be fair, what sort of "backup" calculation would you have done here, short of reverse-engineering the USPS algorithm for calculating shipping rates?
A store can charge whatever they want for shipping. So if they know how much it costs on average to ship their products, they can simply charge everyone that flat rate. Or if they sell something simple, they can charge one simple rate per quantity. Or they could cache the last rates they charged and reuse those. Or they could offer everyone free shipping and eat it as the cost of doing business with the USPS.
Developers: We can use your help.
The post office can't do it for 50 cents either. Through various agencies, some less obvious than others, that cost is a subsidized cost.
Because it's no longer reliable enough. The S&H charges change based on too many values for the few factors (carrier, size, weight, destination, type of delivery, timing of delivery, etc.), and things change. So it's not a necessarily easy calculation to perform.
Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
Retail customers expect to check out knowing the full price they will be paying, including shipping. This means that you HAVE TO calculate shipping during order placement (checkout). You're asking for customer service headaches if you have to manually charge shipping after the customer has already (they thought) completed the order.
So your only option, if you don't want to rely on a third-party server for shipping costs, is to have your shopping cart do its own calculations.
A work that expires before its copyright never enters the public domain and thus enjoys eternal copyright protection.
how about logging when the damn service is down???
"Neither snow nor rain nor heat nor gloom of night stays these couriers from the swift completion of their appointed rounds"
But the computers will!!!
You do realize that this has never been the motto or creed of the USPS.
It is taken from the courier service of the Persian Empire. See Wikipedia.
--
This is not the sig you are looking for... Move along...
Forget the cigarettes - they are taxed way to heavily on the federal and state level. Well, unless they "fell off a truck".
"But this one goes to 11!"
Apart from the trouble reported in this /. article which I found occuring on one of the existing sites I wrote yesterday (simply because there were no USPS prices being returned, no error, but took about 30 seconds to work out what happened), USPS simply sucks ass.
Here's why:
Some time ago, they had an API to get rates, it was called RateV2.
Then they "updated", and now have RateV3.
RateV3 is the only specification published.
To get access to the Rate API servers, you must first test your implementation against thier testing servers successfully, when they see that they let you on the production server....
Thier testing servers only work with a limited version of RateV2.
So, in order to use the USPS API, you must:
Write to the now unpublished RateV2.
Test that RateV2 on the test servers.
Ask USPS to allow you to use Production (and get the keys etc) because you have successfully tested.
Write completely new code against RateV3.
Test that RateV3 on the production servers.
And if you try and show the USPS staff the logical problem in this process, they will reply "I can not put you on production servers, until you have done three successful tests on the test servers".
NZ Electronics Enthusiasts: Check out my Trade Me Listings
If TFSummary is to be believed, the least they could do is make sure the app didn't crash on bad data returned from an API. There is NO excuse, ever, for a crashing bug in an online store app like that. There's no problem with the USPS servers being funky, there's a problem when people programming dependent apps somehow didn't at least plan on it ever happening.
My blog. Good stuff (when I remember to update it). Read it.
It doesn't take a brain surgeon to look at a postal rate schedule - the postal service does provide them for all shipping services with clearly marked zones to figure out how much to pay for postage.
The California EDD (Employment Development bureau that handles unemployment) www.edd.ca.gov signup website and their phone systems are literally non-responsive.
Maybe more people are filing for unemployment than trying to get their stuff shipped.
To be fair, what sort of "backup" calculation would you have done here, short of reverse-engineering the USPS algorithm for calculating shipping rates?
Its called looking up the rates in the domestic mail manual, and interfacing a scale to calculate the rate. It's not that hard, but it takes time.
Seems to me that a program that crashes rather than degrading gracefully when a remote network resource becomes unavailable needs a bit of work.
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
Can you imagine FedEx or UPS being afflicted by such an issue?
Having worked in IT for one of them this year... yes, without question, yes.
The same has been true with the USPS since 1970. Their entire budget is financed by people buying stamps and other services. They don't get a dime of taxpayer money.
If you reply, do so only to what I explicitly wrote. If I didn't write it, don't assume or infer it.
and if the livelihood of my business depended on it you better be damn well sure I'll have my application ready to crunch each of these factors manually in determining shipping cost...it's terminally stupid to do otherwise...
...in bed
The call from the User to the parent poster m2pc could not have been a fun one. But some interesting Ah-Ha's can be gleaned from this event. "Try-Catch-Finish" can be a troubling paradigm, but when your user employs the administrative technique of MBH, ( Management By Hysteria ), having your program tell you what its inputs were, and what the response was from the "other guy's" server in a nice log file can be; satisfying. This problem could have been reduced further by having the program email any nonstandard messages from the offending server to the maintainer of the software. These two little tricks have made me more Pro-Active, than Re-Active when it comes to spending time on problems, and it keeps customers longer.
The zones are clearly marked but determining which zone you are shipping to is not. They are based on distance from the originating ZIP Code so the application must use Postal Explorer to generate the zone chart ahead of time. (For now, it happens to be working.) And in the case of non-flat-rate Priority Mail, there's a huge price difference between zone 4 (zone and weight only) and zone 5 (zone and weight *OR* zone and size).
Herodatus (sp) , not the Post Office.
The Post Office's motto is "the price of stamps just went up".
Except, they get to charge an exorbitant amount for their stamps and services by prohibiting competition - a luxury that Fedex and UPS do not have. (If you think their costs are reasonable, then why is there a law the prohibiting Fedex/UPS from charging below a certain amount?)
My brother accidentally ordered a 120 foot HO scale rail road set with the foam peanuts individually packaged.
He got confused and put in Amazon.com HQ as the shipping address.
Also he used Discover card.
Is this a DOS attack and should I report him?
The fact that some people seem to think this is a *big thing* really shows USPS has been doing a decent job. Failure happens to the best of us. ( Except for you of course. )
I give them a tentative A+ despite the current issue. Hell, they get a C baseline for trying.
Really? it was that reliable? I would call that a government success -- assuming failure is a good metric, I know I do.
Crap, I twisted my brain again while talking government. As you were, whilst I untie this flawed logic... Can I get some help here? Its choking me.
I think you underestimate just how much I just dont care.
I'm seeing a lot of aspersions directed at developers for this problem. While it is reasonable that an unquoteable carrier condition should not be a showstopper in a sales situation, there is considerable follow-on logic and heuristics to be considered before taking next steps when a preferred shipping carrier cannot be used.
Also, in my experience, client reliance turns out to be a pretty good forcing function on web service provider SLAs, because ultimately it's someone's ass if business is at stake.
Back to the USPS, though.
A USPS outage is particularly problematic for e-commerce as, for most US domestic shipments, it is the cheapest "go-to" service. "Falling back" to UPS or FedEx, while an appealing concept to a software developer, often means triple the shipment costs (on lighter parcels) which you have to assume is going to be a dealbreaker on a sale of commoditized mass market goods, which is the whole point. So you're not doing yourself a favor there.
So, when USPS fails, you can use another carrier and hope your customer doesn't mind; defer the shipping computation (good luck closing a deal with a "TBD" shipping price); or estimate the USPS shipping yourself. Let's look at what's involved in the last, most practical option.
USPS rates are a non-linear, discontinuous function of parcel dimensions, parcel weight, parcel shape (is it a box or a guitar case?), parcel density (lead or feathers), and requested service level. And of course, origin and destination location, which USPS wraps as a "zone" (misleading because it's not really a target "zone" but rather a distance + complexity metric).
Zones:
USPS publishes domestic rate tables but getting their consolidated zone map (so you can actually use the rates) is a $50 CD purchase let alone the code needed to parse it and the time needed to maintain the zone calculation code. Let's simplify and say you're shipping from a single location so you only need one zone map, though. Then you're only on the hook for annual zone revisions/additions.
Rates:
Simple spreadsheet lookup, right?
OK, but you did make sure that you were properly calculating the Priority Mail balloon rate on your huge box that weighs 1 pound, right?
And did you check whether your goods qualify for the machineable local or intra-BMC Parcel Post rate?
Do you ship internationally? Please be aware that the weight limit to Greece for Express Mail International shipments is subject to change, as is the maximum length + girth of your parcel, and about 800 other limitations. But I trust you're on top of all the DMM and IMM changes because you have nothing better to do then re-invent the USPS API in your free time. Oh, and these rates are not available in spreadsheet form, and it's a completely different zone map.
And that's just for one carrier.
Consider that many carriers don't publish their rate tables in a consumable form, unless you consider a glossy annual rate PDF with fancy typesetting, a consumable form, and want to take the time to scan them or hire a data entry monkey to do so (and test to make sure they didn't fat finger anything).
I think we forget why web services were such a Good Idea, or at least the practical limits of software development principles in the face of a finicky customer with money to spend.
So while there are no extra points awarded to shopping carts that just timed out ignorantly, also consider the burden that the USPS has placed on clients for those developers trying to do the "right thing" among competing priorities, including, say, tools for selling and marketing rather than determining whether the Canada postal code that the customer entered is in a region that is not eligible for ground shipment because it's iced over this time of year.
Seriously, why does anyone's checkout SW need realtime synchronous connection to the shipper? Why can't it be asynchronous with a local cache of the relevant data?
Synchronous is just dumb. Most other Internet applications don't work that way. DNS is a great example of data being cached everywhere, yet still centrally update-able. E-mail is another great example of quick communication w/o requiring a synchronous connection.
I can't believe that a small shipping application couldn't be left locally with each partner that provides cached rate information and handles the API whether or not USPS/UPS/whomever is up to manage it.
My favorite quote doesn't fit into 120 characters. Now no one will like me.
> To be fair, what sort of "backup" calculation would you have done here, short of reverse-engineering the USPS algorithm for calculating shipping rates?
Algorithm:
1. Remove USPS options from shipping menu.
2. Leave UPS and Fedex in place for people to calculate shipping.
3. if 2 does not exist provide a phone number for people to call for order completion.
4. If phone is disconnected, use a fixed flat rate shipping charge.
there, not so hard eh ?
No, that's always been that way. I was unemployed for like three months in the last 6 years. I tried to file for Unemployment and I got no response. Since then I consider the amount they take out of my check every month to cover "Unemployement" to be simple theft. The money is not theirs and they do not hand it out responsibly according to the intent of the law. The California EDD is a total sham and a total failure!
~Sticky
//TAG IT 65536+1
Oh come on! When you make such an outrageous claim like this, back it up with a reference please. Last time I bought my forever stamps, they were 42 cents a piece. Good fucking luck getting a price anywhere near that in private industry. Sure, I can have a great web-server if I'm like FedEx and charge $30 to mail an envelope. Of course, every time the postal service wants to ask for more money to have updated services like eCommerce whatever, congress complains.
Americans are pathetic sometimes -- they expect their government services to do as well as private industry, yet they don't give them the ability to charge what private industry charges. Amtrak is a similar situation, Amtrak is expected to be cash flow positive, yet they are not allowed to own their own tracks, those are owned by the freight companies, whereas their main competitors run on highways that are paid for completely by the taxpayer and gas taxes, or operate out of airports also funded by taxpayers.
Gentlemen! You can't fight in here, this is the war room!
The US Postal Service is experiencing major server issues for its shipping API web services. After spending about an hour debugging my own eCommerce software for a client, I found the problem was with the USPS shipping servers being unavailable.
Others have said it, but I'll say it again because I like the beat this philosophy into everyone's head at work:
IMPLEMENT FAULT TOLERANCE.
If a service, internal or external, doesn't work right... make sure that your customers are still mostly satisfied.
It would be IMPOSSIBLE to experience "major server issues" if your damned eCommerce software was designed smartly.
Point the finger all you want. But at the end of the day, this failure is YOURS.
Web services go down, go bad, get attacked, or become unreachable. Plan for it.
"Americans are pathetic sometimes -- they expect their government services to do as well as private industry, yet they don't give them the ability to charge what private industry charges. Amtrak is a similar situation, Amtrak is expected to be cash flow positive, yet they are not allowed to own their own tracks, those are owned by the freight companies, whereas their main competitors run on highways that are paid for completely by the taxpayer and gas taxes, or operate out of airports also funded by taxpayers."
Welcome to municipal broadband. Oh wait!
Shai Schticks:"You don't make peace with friends, you make peace with enemies"
And that's what you get for writing e-commerce packages that rely on 3rd party sites for basic functionality...
Don't say I didn't tell you so...
Oh man! My faith in open source software is shaken to it's core.
Shai Schticks:"You don't make peace with friends, you make peace with enemies"
I remember at my previous workplace that one of the vendors techs was working at post office also. They were work on DEC (now HP) Alpha servers and that was in 2001. I don't know if those servers are still in use but those servers where great back then but are definitely showing there age now if they are still in use.
A zone chart subscription in a clearly documented format is available for $50 a year here:
http://www.usps.com/ncsc/addressmgmt/zonechart.htm
We use it for our rate calc, in fact it's all local based calculation since the rate tables are public:
http://www.usps.com/prices/downloadable-pricing-files.htm
I understand that using the API means no work when there is a rate change, but the rates change 1-2 a year with 60 days notice. Not a huge deal.
-aaron
I've got to say that tracking shipments via USPS has always been crapped when compared to DHL or FedEx. USPS never shows the shipment as having ever done anything but left the facility and then magically shows up at my doorstep with no stops along the way which would be believable if it didn't take 6 days.
then why is there a law the prohibiting Fedex/UPS from charging below a certain amount?)
Oh come on! When you make such an outrageous claim like this, back it up with a reference please.
Actually, I think the law says they can't charge less than the LARGER of $3.00 or twice the postal rate, unless they have some type of guarantee time for delivery where the price falls as the time extends.
Doing a quick comparison on their websites, it will cost me roughly 2.5 times as much via Fedex and UPS than the post office to send a 1 pound package across town, if I drop it off at the self-serve shipping center, and it is picked up by the receiver at the shipping location.
If I have them pickup from me, and deliver, it's about 3 to 4 times more than the USPS.
If I want to send a postcard through UPS or Fedex it's going to cost a HELL of a lot more than the USPS... I'll pay more to mail it across the country on low-priority just in the FUEL surcharges let alone the actual base rate & fees.
But they still have a government-issued monopoly on all non-urgent mail. It is actually flat-out illegal to mail a non-urgent letter via UPS or FedEx: that "Extremely Urgent" text on the UPS boxes is not a marketing ploy.
Because of this monopoly, the analogy, I think, still stands.
From my experience, this is common. Even worse than it being down is when it starts returning malformed headers, etc. It's really not fun. FedEx and UPS are no better, particularly with their development servers. It's YOUR time and labor, so they really don't care.
the USPS has a sheet you can get that gives the approximate cost of shipping based on weight. so a backup solution with hardcoded values should be able to tell you that weights between 1 and 2 pounds will cost you between 2 and 3 dollars to send. Not as exact as 1.16 lbs costs 2.32, but it's close enough. no need to reverse engineer anything.
Really now.
Atleast you are honest.
I am very small, utmostly microscopic.
Charge a fee that is close to what you expect to pay. Over on a few and under on a few, but should even out at the end.
That works only as long as your shipping volume is relatively low. If its not, then even small discrepancies in shipping costs can result in the books not balancing, as that "negligible difference" isn't really so negligible when its multiplied by hundreds or thousands of packages.
We all know what to do, but we don't know how to get re-elected once we have done it
I fully agree on that point. At the very least, the application developer ought to have returned a well-formed error message stating something to the effect of, "Sorry, the postal service's servers are down, so we can't calculate your shipping at this time."
We all know what to do, but we don't know how to get re-elected once we have done it
You have a point.
I used to work for a company that shipped $40 million/year to residences and charged flat rate shipping for almost half of it. Every month we hit within .5% of the actual cost to ship. Whenever the disparity exceeded a certain dollar value in a given week, we added or subtracted 5 cents from the shipping charge for the next week.
It wobbled back and forth like that for years, until one week when we had a sale on 40 pound ferrite cores.
Then we added 10 cents.
The larger your shipping is, the more you can absorb discrepancies if you know already know how much your inventory costs to ship and know where your customers are.
Sure, I can have a great web-server if I'm like FedEx and charge $30 to mail an envelope.
If FedEx is charging you $30 to mail an envelope:
FedEx Ground is the only REAL comparison to the mail service if you're going to base it off 42 cent stamps. Ground from where I'm at covers most of the STATE in one day, and a good portion of neighboring states. It takes me 2 to 3 days to get an envelope to my parents 3 hours away.
Compare apples to apples, please.
Disclaimer: I have worked for FedEx in the past, and have a somewhat unfortunate detailed understanding of how the pricing works.
"To be fair, what sort of "backup" calculation would you have done here, short of reverse-engineering the USPS algorithm for calculating shipping rates?"
I'm sorry, we are unable to calculate your USPS shipping cost at this time. Would you like to:
1) Accept the shipping without knowing the cost.
2) Select a different shipping option.
3) Have us contact you when we know your shipping cost.
4) Accept shipping up to a selected amount and have us contact you if the actual amount is higher?
5) Cancel your order for now, leaving these items in your shopping cart so you can order them later.
It's that simple.
The same has been true with the USPS since 1970. Their entire budget is financed by people buying stamps and other services. They don't get a dime of taxpayer money.
How did you ever get modded +5 informative with that load of bull?
The total funding for the Postal Service in the administration's 2005 budget is just over $61.7 million.
Appropriation, fiscal year 2004 $65,135,000
Appropriations, 1999 $100,195,000
etc, etc
When information is power, privacy is freedom.
I help a friend of mine fill orders on his Hobby Shop Website yesterday, and couldn't complete any shipments on USPS "Click N' Ship" site. When you would submit new addresses, the apps would reject OUR return zip code, saying it was invalid (even though it had worked fine for months beforehand). Today, you would have to keep resubmitting information after the site would initially reject it, but then accept on second try. Or you would get no shipping options after submitting a new shipping address. You would go back and then forward and it would work... Very frustrating....
You're messin' with my Zen Thing, man.....
So does FedEx Ground charge less than 42 cents to send an envelope, or did you just kind of skip the main point?
If you mod me Overrated, you are admitting that you have no penis.
Here you go. From HR 6407 - Postal Accountability and Enhancement Act of 2006, section 503 "PRIVATE CARRIAGE OF LETTERS" :
You can google for "USPS monopoly privilege" and "USPS monopoly law" and get quite a screenful on the subject.
Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
Sounds like the idiots at USPS switched their from their rock solid COBOL green screens to Winders... Now they qualify... for the federal bail out funds...City Bank was hacked got a bail out, Pentagon was hacked...IMF was hacked (got a bail out), world bank hacked(got a bail out)....all because they use Widnows....The IMF sent their 40 servers to MS to figure out.....
I work for an e-Commerce company and the USPS API did the same thing last year. It gets overwhelmed and can't handle the volume. If you have a decent shopping cart software, set your rates to backup for USPS and you should be fine.
Please don't humanize the morons around me. It makes me very uncomfortable.
I said it was the closest, not a price match. Take a look at the area of next day delivery service you get from FedEx Ground (or UPS for that matter, they're almost identical). Compare that to where you can send something next day USPS.
The post had 2 parts. One, that comparing $30 express service to 42c envelope service through the USPS was a useless comparison ( at least compare USPS priority services) and two, that the USPS is much slower in getting those 42c envelopes delivered than even the cheaper FedEx services, which means you have to add that value judgment into the equation.
They could have returned to the pre-computer shipping practices to figure out the shipping rate: rolling dice, consulting the Oracle, checking tea leaves, or sacrificing a goat.
Oh no, wait, they didn't do that. They either used a fixed rate or a rate based on the product price range, looked up in a five-row table.
The shipping api is down, however the rate calculator is available. We provide the rate calculation engine to the folks that provide the shipping api. The shipping api offers numerous services and we are just one of them.
If you require domestic rates calculations, as received by ShippingAPI.dll, you can access our rate engine directly.
Accessing the rate calculator api is very similiar to how you access this functionality from the shipping api.
Getting started:
A simple demo site that will allow you to learn/test a subset the API:
http://postcalc.usps.gov/domSDK/SDKXMLtest.asp
XML over HTTP Application access:
http://postcalc.usps.gov/SdkXml.aspx
Documentation is available but I do not have a publically available site to post this on. If a site is available, just let me know and I will post the SDK documentation there.
Let me know if I can help.
Adrian Griffith
ManTech Information Systems & Technology
Project Manager, USPS Postal Explorer and Rate Calculators
adrian.griffith@mantech.com
There are companies out there that provide API based local products to act as a primary. This allows integrators to use the Web API as a backup.
(Shameless Plug Warning)I recommend ProShip by Best Way Technologies http://www.bestwaytech.com/proship. But there are other "acceptable" alternatives out there
Carriers, such as USPS, FedEx, UPS and DHL, can change their rates, services and algorithms quarterly. It is often easier and cheaper to offload said responsibilities to a third party.
More of my thoughts
I guess this will be the point where the guy who installed the Linux system gets fired and they put in a more common and vendor supported Windows or Unix system.
The shipping api is down, however the rate calculator is available. We provide the rate calculation engine to the folks that provide the shipping api. The shipping api offers numerous services and we are just one of them.
If you require domestic rates calculations, as received by ShippingAPI.dll, you can access our rate engine directly.
Accessing the rate calculator api is very similiar to how you access this functionality from the shipping api.
Getting started:
A simple demo site that will allow you to learn/test a subset the API:
http://postcalc.usps.gov/domSDK/sdkdemo.htm [usps.gov]
For programmatic access use the XML over HTTP Application:
http://postcalc.usps.gov/SdkXml.aspx
Documentation is available but I do not have a publically available site to post this on. If a site is available, just let me know and I will post the SDK documentation there.
For web site access:
Domestic Retail - http://postcalc.usps.gov/
International Retail - http://ircalc.usps.gov/
Domestic Business - http://dbcalc.usps.gov/
Let me know if I can help.
Adrian Griffith
ManTech Information Systems & Technology
Project Manager, USPS Postal Explorer and Rate Calculators
adrian.griffith@mantech.com
I know that it's not direct-linked, but is it wise to get anything like this within 100 feet of Slashdot? Could we end up turning "down for the day" into "down for the week?"
Somewhere, someone is finding a way to report that this is good news for the economy. Someone else is finding a way to say that the use of USPS instead of FedEx is bad news for the economy.
That's Darl McBrides to you at a cost of US 699: Imagine the savings!
So does FedEx Ground charge less than 42 cents to send an envelope, or did you just kind of skip the main point?
Does the postal service charge a Fuel Surcharge? Is FedEx's Fuel Surcharge MORE than 42 cents? I don't think ANY law here is the issue. If it was then FedEx wouldn't be charging any Fuel Surcharges. Why do they do this? To maximize the profits. The postal service does NOT charge a fuel surcharge, never has. Even without this "Law" I venture to say that the likes of FedEx and UPS would STILL be more than USPS because they need to make a PROFIT. Postal Service needs to SUSTAIN. Profit for the postal service means GROWTH, not Shareholders getting rich. After all the Shareholders of the Postal Service are the American People. Right?
Paul Gardner http://www.csandm.com/