I drafted this email out to a colleague:
When you refer to multi-location support, do you mean multiple retail locations? For example, a retail company (like Wal-Mart) will want to track their sales and accounts for each location, as well as the aggregate reports. My "Uplink" software has physical location support, addresses, equipment inventory, dynamic floor plans, but no product inventory. I might be able to tie it in, but I'm not very comfortable with the inventory accounting model. Alternatively, locations could be microcosms of a large accounting system, almost like several smaller companies making up a larger one. I believe the data model I've got going now can support this type of functionality. Or I had also thought that multi-locations simply meant being able to access the software over a network (a given for me, and one of the reasons why I've had a tough time embracing Quickbooks). In all these cases, user management is key. The user management system I have in place, as well as the company management system is very flexible. One installation of the software can support multiple users obviously, but also several companies, and has the capability to allow administrators to seamlessly traverse through the companies they are managing or servicing. Another complaint I have about Quickbooks is how different it is to the traditional models of accounting I learned. I agree about accountability, double entry accounting has survived not only because it enables error detection, but because it can also divide up tasks (and transactions) into separate departments to try and prevent fraud.
Those were mostly my random thoughts, I'd like to send a clearer email.
