Feature #8

Make order statuses dependent on each other

Added by Rick Glunt over 2 years ago. Updated 2 months ago.

Status:Closed Start date:01/18/2010
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:- Spent time: -
Target version:2.1

Description

In order to create a proces flow, the order statuses need to be made dependent on each other. This will allow for more order control.

History

Updated by Rick Glunt over 2 years ago

well
consider that each market has it own rules

for example for one customer we have this workflow inside virtuemart (this step are if everything check goes fine)

new -> pending -> payment check -> ok payment -> stock check -> ok stock -> wip -> ok wip -> shipped

so indeed there are certain ACTIONS that need to be defined in aset of rule in order to choose between which status they have to happen

e.g. a user could decide to have the order mail send only after ok payment status

Updated by Rick Glunt over 2 years ago

Status should easily be added or removed, this is how client of mine works.
(New)-+-> Pending ---+ | V | >Processing - | | | | V | > Confirmed --> Cancelled > Refunded | | -----> Shipped ------------------->(End)

Updated by Rick Glunt over 2 years ago

Correct; the intention is to add the option in the order status edit screen to create status dependencies. By default there will of course be a standard flow, something like: (New)-+-> Pending ---+ | | | | V |
> Confirmed --> Cancelled -> Refunded | |
----> Shipped ------------------->(End)
with options to change/remove dependencies/order statusus.

Updated by Rick Glunt over 2 years ago

this invokes a relation model that should be created by the user too
i mean, every business has different logic. for sure we can deploy a default behaviour but imho we must give to the user the possibility to change this behaviour

Updated by Urs Brülhart about 1 year ago

  • Target version changed from 1.6.0 to 2.1

Updated by Ondra Spilka 2 months ago

  • Status changed from New to Closed

Also available in: Atom PDF