Add WorkflowsOrdersDelivery

WorkflowsOrdersDelivery.md

@@ -0,0 +1,23 @@
+# Pick-Up / Delivery
+
+At some point the product and the customer must unite, either by the customer visiting the store to pick it up or by the organization delivering (or shipping) the product to the customer.  It's assumed in any case that the customer is aware of their order's current status.
+
+## The Basics
+
+ 1. The product is physically united with the customer.
+ 1. The customer pays any remainder owed on the product, or is billed.
+ 1. Objects' statuses are updated and events are logged.
+
+## Pick-Up vs. Delivery
+
+If the product is held in the shop to await customer pick-up, eventually it will be up to the customer to actually do that or else risk their product being returned to the vendor or placed on the shelf for general sale, etc.  When they come in, they will be given the product which has been held for them.
+
+TODO:  Some shops may deliver or otherwise ship the product to the customer.  Unfortunately this is not the current focus, so there's no documentation for now.
+
+## Payments / Invoicing
+
+If some outstanding balance is owed on the product, the customer will either be expected to pay it (e.g. at the POS) at the time of pick-up (or e.g. COD at the time of delivery), or else they will be invoiced/billed for it.  However it is possible that the product will have already been paid for in full, in which case nothing special must happen.
+
+## Point of Sale Transactions
+
+It may be desirable to relate line items within a POS transaction to the OrderProducts they represent, for workflow purposes.  If the POS software in use is *not* Rattail (which it currently cannot be), such an association could be tricky to achieve.  I'm waiting to document this until further discussion.