From 09fd0369bb588066c8f92f98d693180b26545493 Mon Sep 17 00:00:00 2001 From: Lance Edgar Date: Sun, 19 Oct 2025 10:11:22 -0500 Subject: [PATCH] Add WorkflowsOrders --- WorkflowsOrders.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 WorkflowsOrders.md diff --git a/WorkflowsOrders.md b/WorkflowsOrders.md new file mode 100644 index 0000000..9c51bde --- /dev/null +++ b/WorkflowsOrders.md @@ -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.