For a warehousing system, stay away from NoSQL, use SQL, unless you want to make your life very difficult.

You need an ACID-compliant with row-level locking when dealing with stock and something fully transactional, SQL gives you that out of the box, NoSQL databases with their distributed nature usually doesn't have this and you have to add extra highly-configured plugins to get it working.

Also, you'll probably need to generate reports and the requirements for different reports will probably change, SQL makes reporting easy, with NoSQL you'll probably need to write code every time you want to do a quick report.

Also see this post: devmag.io/post/1454/moving-from-relational-to-nos…

For a nice hybrid, have a look at MariaDB, it has SQL and NoSQL support.

There is no easy answer, unless we know your exact requirements. Each different database (SQL as well as NoSQL) has its pros and cons. I suggest you read this book: NoSQL Distilled: A Brief Guide to the Emerging World of Polyglot Persistence -- it will give you a lot of insights into choosing the best DB for your app. The book even suggests that you could use different DBs for different parts of your app.

What are the requirements you have to fulfill?

Because there is no nosql database out yet which suits all the needs.

On nosql-database.org you can find a list of nosql databases which are categorized by type of data structuring.