Thanks for the suggestion. Unfortunately I'm not in front of a system where I can run up POS at the moment, so forgive me if this is a question/comment that would be easily resolved with some experimentation...
In my scenario, my customer requests a product I do not have in stock. I need to
a) Record that Customer A has ordered X quantity of product Y
b) Record any deposits paid by the customer (most of the time this is nil)
c) Generate a purchase order for the product(s) - usually consolidate orders a couple of times a week
d) When the stock arrives from the supplier, identify the products that fulfil customer orders, and notify the customer
Note, at this time there is no online interaction with my customers (all face-to-face or via phone).
Generally, I have gone down the path of creating a Sales Order for (a) because it lets me do (b), and it automatically generates the necessary requirements that makes (c) straightforward. (d) still requires a bit of manual scanning, and it would be great if I could run a report that reconciles purchase shipment receipts against sales orders (or if the Facility receive shipment flagged that received items fulfil orders).
I don't use manually entered Requirements for (a) because I can't directly associate a requirement with a customer. To do this, I need to have a Request, but I find the use-model for Requests a bit cumbersome. Besides, I can't do (b) with Requests/Requirements.
As to Shopping Lists, to the best of my knowledge there would be no Requirements generated if I created a Shopping List for the customer - is that correct? Also, I cannot record any deposits (b).
I'll be the first to admit that I might have missed something in the "correct" use of Orders/Requirements/Requests/ShoppingLists, but it seems that creating the Sales Order is the "right" thing to do to allow me to efficiently handle (a)-(d). If I'm right about that, then what I need is the ability to start the Sales Order in Order Manager, and finish it in POS.
Happy to be corrected, as always.