Re: [WebERP-developers] POS

[Janvl <jv...@st...>]

I see it like this:

The producttable in POS is a copy of that in the ERP,
so if you add a new product it must be done in the ERP and a sync must be
done with the POS

The customertable in POS is a copy of that in the ERP,
so if you add a new customer it must be done in the ERP and a sync must be
done with the POS

Sales made in the POS WITH an productnumber will be brought to the ERP in
batches, or through a transaction

Sales made in the POS WITHOUT a productnumber must be treated different, not
yet sure how

Sales made on a customername must somehow be linked to the customers in ERP

Stock will be maintained in the ERP, with the POS you can sell even with no
stock available,
so the inventory is better done inside the ERP.


I once had a system in the hospital I used to work that used a
"virtual-printer" to send 
transaction-records to a system for X-ray results, sent to general
practitioners. The POS has 
the ability to define the output of certain events, so maybe this would be
an option.

Working in realtime would be nice but we must consider if the work to be
done and the benefits to gain are in balance.

Kind regards,
Jan
-- 
View this message in context: http://n4.nabble.com/POS-tp1549501p1750845.html
Sent from the web-erp-developers mailing list archive at Nabble.com.