Merchandiser Assistance Mobile App

Software tool for merchandisers I want an app that helps merchandisers find the items they merchandise. The app must accurately display the locations of each item no matter how small or big it is through either its article number or its barcode. I want the app to be able to link to multiple company databases but never without the proper authorisation from the company itself. It must only pick up items once scanned in by that companies stock controller and must work in synchronisation with the company system to track where the stock is at all times up until it is scanned by the till point. Once checked out by the till point, it must no longer display where the item is. The app must be able to work seamlessly with whatever company system it comes into contact with. Your job will be to figure out a solution as to how this must done in the best way possible. As I don't work hand in hand with these companies in any way, I would like the person I hire to be able to showcase their skills by finding solutions by tackling these problems. The best solution I can think of would be to send a request using data to the companies servers whereby someone else would need to give permissions to the system you design but feel free to tackle this problem in any way you think would be best. With this way at least their IT department or whoever can see who the request is coming from and they can investigate for themselves to test whether the request is safe or not to provide permissions to and ask me directly as to what this is or if the request really came from me or not. Since I work in a company with a lot of security measures, tight budgets and overseas partnerships, I wont be hard to find and since I've been there for a while, the right people will know where to find me. I might consider just asking someone to point me to their IT department though to liaise with them on whether this idea would be safe to implement into their company system and what can possibly be done to work on the initial architecture to improve on it. That's where you come in. Also, nothing physical must be implemented or introduced to any of these stores. A lot of these companies dont want to spend money because it comes with a lot of risks to their security and expenses. Some of them are under mergers and partnerships with other companies as well which for the company could lead to a lot of paperwork, etc. This idea must only use a smartphone and data. Picture this, I walk into the store. I open my phone and go to the app. I send a request. The company acknowledges I do in fact work there based on a different app on my phone which can verify that I have in fact had a history of logins tied to this company. It does another fact check with its own system and find out I have a ID under their system with fingerprints and an employee number. Once the system acknowledges I work here, Im given access to information pertaining to me being a merchandiser. As there are multiple merchandisers working under the same brand at a time, the architecture needs to focus on sorting out which info is relevant to which merchandiser and know which products they merchandise. For this the UI must list each product according to the companies information on what stock they handle, not other merchandisers stock or info. Along with stock count info, the stock must be able to be found, even if hidden in layers upon layers of stock. It must also display a basic interface when locating items, mainly to accommodate for current limitations on smartphone technology and space. But the system architecture behind it must be complex enough to find a needle in a haystack. I want this app to also be used whether online or offline. Online should only really be to connect with cloud services of the company and to display the most to date info the company has with relation to the stock. Offline should really be to display any info the merchandiser needs to see that isn't necessary to be updated like the last info seen before it went offline, dispo docs of that merchandiser, etc. Preferably anything that can be seen at a moments notice and sensitive info that needs the permissions of a manager to change if required. Your architecture in this aspect must be built on requesting permissions from the manager in certain aspects and be able to send it to the right departments manager as there are many while also later focusing on not trying to overwhelm the manager with too many requests from multiple merchandisers at a time while also trying to take into account of emergencies whereby the information needs to be accessed as fast as possible in cases whereby the manager may not readily be available to give the ok to such permissions but the merchandiser might be aware that something is not adding up and needs someone with the right authority to give the ok to such action. The ideal I can think of for this idea would be to initially have multiple copies of the same info in certain instances like for example, one being to the merchandiser and then one that's sent to the manager. The manager reviews the information on his end and oks the request for a count and the access is given to the merchandiser to do a recount. If the information checks out, the manager maybe comments that "everything's ok, false alarm" but if the system conflicts with the count, the manager checks to see what could be the issue. Maybe the merchandiser counted incorrectly or maybe there's something wrong with the system. If the manager finds that something is not adding up, he takes further action on his side. When the manager sits with two copies of the same report, one must list the original, uneditable report and other, the editable report. When opened, it must preferably display the two side by side showcasing which info the merchandiser counted that isn't adding up with the system's by highlighting the information showing which info doesn't add up with the originals. Problem is, I want the idea to be that