Optimise the repeat shop
Everything about grocery points the same way. The customer is rebuying a list, usually on a phone, usually in a hurry.
So previous orders, favourites, fast add and a search box that tolerates how people actually type are worth more than anything on the homepage. A grocery site that makes the weekly shop take fifteen minutes instead of twenty-five has done the single most valuable thing available to it.
Accuracy is an operations problem
No amount of integration makes a system report stock the shop floor has not counted correctly. If local accuracy is poor, the storefront will faithfully sell things that are not there.
That makes cycle counting, pick discipline and store process part of the scope of any serious grocery commerce project, even though none of it is software. We would rather say that at the start than deliver an integration and watch the substitution rate explain the problem.
Where this sits
This is unified commerce with a demanding operating model, built on a storefront from eCommerce development, and dependent on integration work for stock, picking and slot capacity. If the model is rapid delivery rather than a scheduled weekly shop, that is Q-commerce.