On 2015-08-17 10:52, Axel Braun wrote: > Am Montag, 17. August 2015, 10:05:17 schrieb Cédric Krier: > > > > > 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. > > > > > > Why a new/different price list? > > > As we need to show the tax amount (by tax category) on a sales slip, and > > > for the keeping it simple, why not reuse the existing sales price list? > > I'm not sure about what you are talking but if it is about the "list > > price" field on the product, we can not use this one because it is tax > > excluded. > > And whats the point in adding up the tax internally? It has to be collected > anyway, as confirmed by Korbinian
Because you are saling tax included and marketing wants nice price. > > > > - stock moves from shop location to customer > > > > > > I think in general the goods issue is sufficient, a delivery process is > > > not > > > required. We just may need the address of the customer, e.g. for a food > > > delivery service or similar, when the customer does not pick it up in the > > > shop, but it is being delivered. > > > > If there is a delivery then it is a shipment. > > I feel for a POS it would be overengineered to have a shipment process. > Usually the customer walks away with the goods. That's why I put it as an extra feature (re-read my email). -- Cédric Krier - B2CK SPRL Email/Jabber: [email protected] Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
