<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>crimulus-dot-com &#187; package</title>
	<atom:link href="http://www.crimulus.com/tag/package/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.crimulus.com</link>
	<description>A blog; ineptly autobiographical</description>
	<lastBuildDate>Sun, 29 Jan 2012 10:20:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>USPS Shipping XML API Testing Idiosyncrasies</title>
		<link>http://www.crimulus.com/2010/05/20/usps-shipping-xml-api-testing-idiosyncrasies/</link>
		<comments>http://www.crimulus.com/2010/05/20/usps-shipping-xml-api-testing-idiosyncrasies/#comments</comments>
		<pubDate>Thu, 20 May 2010 17:55:49 +0000</pubDate>
		<dc:creator>Jeremy</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[How-To]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[application]]></category>
		<category><![CDATA[e - commerce]]></category>
		<category><![CDATA[exact values]]></category>
		<category><![CDATA[fedex]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[math teacher]]></category>
		<category><![CDATA[package]]></category>
		<category><![CDATA[package dimensions]]></category>
		<category><![CDATA[rate request]]></category>
		<category><![CDATA[RateV]]></category>
		<category><![CDATA[Statistics]]></category>
		<category><![CDATA[test]]></category>
		<category><![CDATA[United States Postal Service]]></category>
		<category><![CDATA[usps]]></category>
		<category><![CDATA[valid zip code]]></category>
		<category><![CDATA[web developer]]></category>
		<category><![CDATA[XML]]></category>
		<category><![CDATA[zip]]></category>
		<category><![CDATA[ZIP Code]]></category>

		<guid isPermaLink="false">http://www.coffeecuphalfmoons.com/?p=963</guid>
		<description><![CDATA[If you&#8217;re a web developer and happen to develop software for use in e-commerce, chances are, somewhere along the lines you&#8217;ll need or want to integrate with the big 4 shippers&#8217; (UPS, USPS, FedEx, DHL) APIs.  You&#8217;ll find right off the bat that they all offer rather robust APIs, so your options are sufficient. Then [...]]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;re a web developer and happen to develop software for use in e-commerce, chances are, somewhere along the lines you&#8217;ll need or want to integrate with the big 4 shippers&#8217; (UPS, USPS, FedEx, DHL) APIs.  You&#8217;ll find right off the bat that they all offer rather robust APIs, so your options are sufficient.</p>
<p>Then you&#8217;ll get to programming and realize that the documentation is pretty crappy, but specifically I want to address the idiosyncrasies of the USPS &#8220;test&#8221; environment.  Effectively, what USPS means when they say &#8220;test&#8221; is not a test of robustness of your application, but simply whether or not your application can build a sample request (an EXACT sample request), and send it to their server.  Yeah &#8212; it&#8217;s like asking a math teacher to write the numbers 1 to 30 on a sheet of paper (in order) before he/she can get hired.</p>
<p>The problem is, the USPS docs don&#8217;t tell you this, nor do they show you the sample request.  So, for others who are about to embark on a few hour journey finding these details on Google (or worse, emailing USPS directly &#8230;eeek) I&#8217;m going to sum up a few facts here.</p>
<p>The most laborious for me so far is the one I already mentioned above.  For a rate request, the docs show you a RateV3Request, but in testing you can only use a RateV2 request (which does not support package dimensions).  Also, you must use the zip codes 10022 and 20008 for origination and zip, as well as 10 lbs. 5 oz. for the weight, and &#8220;LARGE&#8221; for the size.  Everything else (LAUGH) you have leeway with.</p>
<p>If you don&#8217;t use these exact values, you&#8217;ll get responses like &#8220;Please enter a valid zip code for the sender&#8221; (which of course makes you think you wrote the XML incorrectly) or &#8220;The package size must be &#8216;Regular&#8217;, &#8216;Large&#8217;, or &#8216;Oversize.&#8217;&#8221; (even though you have &#8220;regular&#8221; quite clearly in the request.</p>
<p>The advice is to get to production as soon as possible, though why USPS would design things this way is beyond me, but them&#8217;s the cards, you gotta play &#8216;em.</p>
<p>I will add more here as I find them obstaclicious enough (yeah I just made up that word).</p>
<p>Amendment 1:  <em>I should add that the issues about the documentation not mentioning the &#8220;canned&#8221; requests is only applicable to the PDF documentation.  It is stated quite clearly in the HTML versions.  Go figure &#8230;</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.crimulus.com/2010/05/20/usps-shipping-xml-api-testing-idiosyncrasies/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>&#8220;How not to run an online business&#8221; » JavaSigns.com Customer Experience and Review</title>
		<link>http://www.crimulus.com/2010/01/29/how-not-to-run-an-online-business-%c2%bb-javasigns-com-customer-experience-and-review/</link>
		<comments>http://www.crimulus.com/2010/01/29/how-not-to-run-an-online-business-%c2%bb-javasigns-com-customer-experience-and-review/#comments</comments>
		<pubDate>Sat, 30 Jan 2010 04:42:19 +0000</pubDate>
		<dc:creator>Jeremy</dc:creator>
				<category><![CDATA[Personal]]></category>
		<category><![CDATA[Reviews]]></category>
		<category><![CDATA[better business bureau]]></category>
		<category><![CDATA[better business bureau of new jersey]]></category>
		<category><![CDATA[company]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[javasigns]]></category>
		<category><![CDATA[javasigns review]]></category>
		<category><![CDATA[javasigns.com]]></category>
		<category><![CDATA[javasigns.com review]]></category>
		<category><![CDATA[leway]]></category>
		<category><![CDATA[Ms. Marshall]]></category>
		<category><![CDATA[order]]></category>
		<category><![CDATA[package]]></category>
		<category><![CDATA[personal time]]></category>
		<category><![CDATA[phone]]></category>
		<category><![CDATA[phone tag]]></category>
		<category><![CDATA[review]]></category>
		<category><![CDATA[shipment confirmation]]></category>
		<category><![CDATA[sign]]></category>
		<category><![CDATA[Trish Marshall]]></category>

		<guid isPermaLink="false">http://www.coffeecuphalfmoons.com/?p=714</guid>
		<description><![CDATA[Even though my experience with this company was quite painful, long, and drug out, I&#8217;m going to attempt to keep this review short. Bottom line: Although the design and ordering process is very easy, streamlined, and simple, placing an order with this company, based on my personal experience, runs a very high risk of cumbersome [...]]]></description>
			<content:encoded><![CDATA[<p>Even though my experience with this company was quite painful, long, and drug out, I&#8217;m going to attempt to keep this review short.</p>
<p><strong>Bottom line:</strong> <em>Although the design and ordering process is very easy, streamlined, and simple, placing an order with this company, based on my personal experience, runs a very high risk of cumbersome delays, phone tag, and a major investment in your personal time.</em></p>
<p><span id="more-714"></span></p>
<p>I placed an order at javasigns.com for a sign for my car window in October of 2009.  I received an email that my order would ship soon.  I then received an email that my order had shipped on Oct. 15 and, based on the tracking number, would arrive on Oct. 19.</p>
<p>The package did not arrive, so I called &#8212; several times because I often got their answering service, even when I called during business hours &#8212; finally to speak to Trish Marshall who assured me there had been a mistake and my order would ship right away.</p>
<p>To avoid the drawn out details, that phone call process was repeated several times over the next two months, and yet no package arrived.  Finally, Ms. Marshall promised to refund my money and get the order out that day.</p>
<p>Over a week later, I did get the refund, but I did not receive the item.</p>
<p>Most customers might call the problem solved at this point, but I really wanted this sign as advertisement for my business, and I had been promised it, so I continued to press the issue.</p>
<p>Eventually, it became nearly impossible to get in contact with Ms. Marshall either by email or by phone.  Once I did reach her again, she told me there was a problem with the sizing of the sign &#8212; they were having trouble cutting it, so she asked if there was some leway on the dimensions.  We worked it out, so again she assured me my order would ship soon.  By now, it was the middle of December.</p>
<p>A week and a half later, still having received no shipment confirmation or package, I filed a complaint with the Better Business Bureau of New Jersey.  Three days later, my sign arrived.</p>
<p>Ironically, shortly after the sign arrived, I received an email from the BBB that, since my money was refunded, there was nothing they could do.</p>
<p>I will never deal with this company again because of the time and energy I had to spend to simply get the sign &#8212; a sign whose price tag was $136 and some change &#8212; but they did earn a few redemption points for honoring their promise even when they were not forced by the hand of the BBB.</p>
<p>Proceed with caution.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.crimulus.com/2010/01/29/how-not-to-run-an-online-business-%c2%bb-javasigns-com-customer-experience-and-review/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

