Bloomberg News

JD.com Loss Widens as Costs Increase in First Results After IPO

August 15, 2014

JD.com Inc. (JD:US), the Chinese online retailer with a business model similar to Amazon.com Inc. (AMZN:US), reported a wider loss because of higher costs in its first set of financial results since going public three months ago.

The net loss (JD:US) widened to 582.5 million yuan ($94.8 million) in the three months ended June from 28.3 million yuan a year earlier, the Beijing-based company said in a statement today. The loss was projected at 257.2 million yuan, the average estimate (JD:US) of six analysts compiled by Bloomberg.

JD.com’s initial public offering that raised $1.78 billion in May has enabled the company to spend on warehouses, delivery vehicles and technology as it steps up competition to larger rival Alibaba Group Holding Ltd. Tencent Holdings Ltd. (700), which bought a stake in JD.com in March, is giving users of its instant messaging applications easier access to the e-commerce partner and generating traffic.

JD.com and Alibaba have different business models. JD.com follows a model similar to billionaire Jeff Bezos’s Amazon.com where the company manages inventory and sells products such as home appliances, books and clothes directly to consumers while Alibaba provides the platform that brings buyers and sellers together. Alibaba is preparing for an IPO that could be the largest in U.S. history.

Tencent, Asia’s largest Internet company, in March agreed to buy a 15 percent stake in JD.com and then folded its e-commerce businesses into the venture.

To contact Bloomberg News staff for this story: Edmond Lococo in Beijing at elococo@bloomberg.net

To contact the editors responsible for this story: Michael Tighe at mtighe4@bloomberg.net Subramaniam Sharma, Aaron Clark


Steve Ballmer, Power Forward
LIMITED-TIME OFFER SUBSCRIBE NOW

Companies Mentioned

  • JD
    (JD.com Inc)
    • $25.44 USD
    • 0.04
    • 0.16%
  • AMZN
    (Amazon.com Inc)
    • $312.97 USD
    • -2.36
    • -0.75%
Market data is delayed at least 15 minutes.
 
blog comments powered by Disqus