Le 16/08/2015 23:39, Cédric Krier a écrit :
Hi,
I will maybe have the opportunity to start working on a simple POS module
for Tryton. As I already explained many times, I think extending the
sale object is wrong because the workflows are too much different.
Also for me, a POS should work with tax included price as bases, it
should not create shipments nor invoice by default.
So the idea is to have a quite simple object with only:
- order number
- employee
- shop
- lines (product, quantity, unit price (tax included), price)
The price will come from a new list price tax included on the
product.
It will have a button to add payments registered as lines on it:
- journal
- amount
with change line created on cash journal.
may be able to differentiate the types of payment: cash, credit card,
check ...
Once it is fully paid, the order will create:
- an account move for the sale (on account define in the
configuration)
- stock moves from shop location to customer
But this default workflow could be modified by requesting an invoice, if
so the party will be requested. This request should be possible on
already paid POS order.
Of course the account move generated by the POS order should be the same
as the one generated by the invoice.
The design should be take into account such possible extension:
- using a wizard to add lines
- allow to request a shipment (included back-order)
- support for sale_extra and sale_promotion
- fidelity card
The design should not care about price list, nor grouping modules.
I think it could be the foundation for more complex POS using specific
UI (like a web base).
Did I forget something? Or do you see a use case that could not be
supported?
Thanks,
--
Christophe
http://adiczion.com
