The trick here is to realise that perhaps it is not actually a business problem if the data on the read side is eventually consistent (ie old data)?
For the bank, the bank can actually make money on overdraft fees when the balance is negative.
But, as a developer it may feel weird to not always use the 100% up-to-date value.
secondly, the inventory value in your database is an approximation of the actual value in the warehouse shelf. Things might have been damaged, lost, misplaced or stolen. So the actual value in the warehouse and in your database will never be 100% accurate.
So, I would ask the business if this is really a requirement?