Add WorkflowsOrders
parent
2af2c5d454
commit
09fd0369bb
1 changed files with 21 additions and 0 deletions
21
WorkflowsOrders.md
Normal file
21
WorkflowsOrders.md
Normal file
|
|
@ -0,0 +1,21 @@
|
|||
# Orders Workflow
|
||||
|
||||
The following notes apply to the "order system", i.e. customer/special/case orders - *not* purchase orders (although they may be involved).
|
||||
|
||||
Also see the [[http://packages.python.org/Rattail/rattail.ext.orders.html|"orders" extension docs]] for its API, and notes on the [[orders schema design|SchemataOrders]].
|
||||
|
||||
## Life Cycle
|
||||
|
||||
The order process can differ wildly between organizations. The following is to be considered a rough list of events which will probably occur throughout the life of a given order.
|
||||
|
||||
* [[Initiation|WorkflowsOrdersInitiation]] - All orders must start somewhere
|
||||
* [[Buyer Claim|WorkflowsOrdersBuyerClaim]] - Somehow it must be determined that a buyer will be purchasing product to fulfill the order (if needed).
|
||||
* [[Receiving|WorkflowsOrdersReceiving]] - Somehow the product will arrive from the vendor.
|
||||
* [[Delivery|WorkflowsOrdersDelivery]] - Somehow the product and the customer will be united.
|
||||
|
||||
## Deviations
|
||||
|
||||
Things can always go unexpectedly. Below are some of the various ways in which an order might deviate from the normal life cycle:
|
||||
|
||||
* [[Manual Updates|WorkflowsOrdersManualUpdates]] - Sometimes you simply must override the workflow.
|
||||
* [[Purging|WorkflowsOrdersPurging]] - Sometimes orders may become stale and need to be purged.
|
||||
Loading…
Add table
Add a link
Reference in a new issue