The Real Story Behind Cracker Barrel’s Firing Of Brad’s Wife After 11 Years Of Service

9:52 AM EDT 3/31/2017 by Lainee M., Celebeat Reporter

Bradley Reid Byrd from Indiana left a simple query on Cracker Barrel's official Facebook page to know why the store fired his wife. Surprisingly, the question caught the attention of several followers who got interested on the reason behind his wife's firing. Since then, Brad's question became an internet sensation and people are obsessed to know the answer. But what really happened to Brad's wife?

Brad's wife, Nanette, has reportedly served Cracker Barrel for 11 long years as a retail manager. However, the store decided to let her go back in February that made Brad not so happy. So, he took to his personal Facebook page to inform his friends about his wife's firing. He also requested his followers to ask the company on their Facebook page why they fired his wife.

After almost a month, Brad followed up by posting, "why did you fire my wife?" on Cracker Barrel's Facebook page. Many followers seemed to be intrigued by what really happened so they, too, demanded an answer from the store. This gave birth to hashtags #bradswife and #justiceforbradswife.

However, just recently, Brad updated his Facebook page to ask followers not to harass the local Cracker Barrel stores in their respective areas as per a report by Chicago Tribune. The man made it clear that the local restaurants from other cities have nothing to do about his wife's situation. He also asked followers to direct their concerns to the corporate office of the store.

Brad didn't know that his simple question will turn out to be an internet sensation. Facebook and Twitter users made fun of the issue and even created memes against Cracker Barrel who fired Brad's wife after 11 years of faithful service. They also came up with a Change.org petition that aims to gather signatures to support Brad's wife, Fox News Insider reported.

The real reason why Cracker Barrel fired Brad's wife remains a mystery as of this posting. The company refused to comment since the issue started, apparently.