[TYPO3-commerce] change order in backend

[Falk Kühnel]

Hi Ingo!
>> Just an idea.
>> Since there are two important status informations, where one is payment 
>> status (unpayed, partially paid, etc) and the other one is order state 
>> (open, packaging, shipped, partially shipped, etc), should those not be 
>> seperate values, which can be changed seperately for any order?
>>     
>
> You can setup different structures of folders, so it could be
> open
> packaging
>   - payed
>   - not payed
> ..
>
> But normally you would have one clear workflow for handling the orders, 
> so such a complex structure is not needed.
>   

Well, if you offer different payment and shipping options, this is true. 
You can have prepaid, cash on delivery, or invoice. All the payment 
states are similar, but they gets handled differently. So you would need 
a complex folder structure, which in my oppinion is not useful. 
Secondly, the states do not get preserved. I cannot see, when the 
changes occurred. When was a package packed, when has it been marked 
payed, etc. Those states should also have a comment field, where 
additional information can be stored.

> Orders are saved fixed, have a look at tx_commerce_order_articles. For 
> statsicts reasons we have included a reference to the  original article.
>   
I have not seen that. Thanks. Since the customerinformation in the order 
was not saved but only referenced, i overlooked this bit.

>> And third, i think orders should be changeable in the backend more 
>> easily. Like add remove products, change addresses, etc.
>>
>> Is any of that being worked on? Or is it not wanted for any reason. (If 
>> so please elaborate).
>>     
>
> As I mentioned before, this is quite complex, since you have to take in 
> account, that you might inform the customer or change the billing on a 
> external system.
>
> Before stating this, we have to make a clear workflow what should happen 
> we a order is changes, like a "used case diagram".
>
>   
>> If not, i am willing to get to work on that.
>>     
>
> If you could do the use case diagram, this would be fine. Actual it's 
> planing before programming ..
>   
If nobody is working on this, i will try to get something done. Is there 
a wiki or the like where features can be proposed and discussed and be 
prepared for programming?

Best regards
Falk


-- 
cogitatio - Ihr kompetenter Medienpartner
Falk Kühnel
Am Lappenweiher 3
53127 Bonn

Tel: 0228-369 369 9
Fax: 0228-369 369 6

post at cogitatio.de
www.cogitatio.de

UStId: DE224965781