Blog:'s Four-Year ERP Nightmare

Blog:'s Four-Year ERP Nightmare, the upstart unafraid to battle e-commerce goliath Amazon, has become semi-famous because of its brash and highly quotable leader, CEO Patrick Byrne, who once explained a US$14.2 million third-quarter loss to investors this way: "My bad."

The online retailer has also drawn notice for its gimmicky advertising campaigns: "The Big O" and "It's all about the O."

The latest publicity for, however, has been all about "Uh-oh."

This week, executives announced they were restating earnings for a five-and-a-half-year period, dating back to 2003. All told, the accounting mistakes during the period had lead to a $12.9 million reduction in revenue and a $10.3 million increase to cumulative net loss.

The culprits behind all this mess? An overly aggressive CEO and a problematic Oracle ERP rollout that started back in 2005.

I'll spare you the financial accounting reasons for the restatement, and let a sampling of Byrne's explanation to shareholders sum it up: "The short version is: when we upgraded our system, we didn't hook up some of the accounting wiring; however, we thought we had manual fixes in place," he wrote. "We've since found that these manual fixes missed a few of the unhooked wires."

Looking back through's short history, it appears that the ERP implementation has been nothing but trouble. The strife started in 2005. That's when Byrne's "my bad" mea culpa over the US$14.2 million loss was further exacerbated by a customer service meltdown related to the hurried Oracle ERP rollout.

"I bit off more technology projects than my colleagues could chew," Byrne told investors at the time. "The last bite, an ERP implementation, was one bite too many, and we choked on it."

Overstock's transition from a homegrown ERP package to the new Oracle system, which was rushed to completion before the 2005 holiday shopping season, left it unable to tell customers the status of their orders or to provide any shipping information, reported The Register's Ashlee Vance in late October 2005. The result:'s customer tracking systems were down for nearly a week. "In total," Vance added, "it's a shocking display for a supposed Internet-savvy retailer meant to compete with the likes of and eBay."

Byrne, in the 2005 note to shareholders, remained resolute. "We anticipated that a small number of background processes would fail, but we had more trouble than expected," Byrne wrote. "Rather than pass the problem to the customer in the form of bad service, we ate the cost by doing a great many things manually that would normally be done automatically."

Things didn't get any better in 2006. In November, in another letter to investors, Byrne wrote "The IT problem that developed last September...has had lingering effects that ran well into this year," reported The Register's Vance. "In fact, while we viewed it internally as a 2005 Q4 to early 2006 Q1 problem (which is what it was technologically), I see now that, in terms of affecting customer behavior, it was more of a 2005 December to 2006 April problem.

"It has taken an enormous amount of work to recover," Byrne added, "but our operations and infrastructure are now healthy and strong."

Join the CIO Australia group on LinkedIn. The group is open to CIOs, IT Directors, COOs, CTOs and senior IT managers.

Join the newsletter!


Sign up to gain exclusive access to email subscriptions, event invitations, competitions, giveaways, and much more.

Membership is free, and your security and privacy remain protected. View our privacy policy before signing up.

Error: Please check your email address.

Tags Oraclecustomer serviceERPsoftwareearnings restatementOverstock.combusiness applications

Show Comments