Thanks @Scott and @Jacques for putting these for brainstorming. I couldn't share right examples for recommendation that sales data is necessary to have in the system, when we are actually doing the sales in business.
I believe whenever doing sales, logging should be there. It might be possible that, for some reason the data not seems useful for certain situation. Thanks again! Rishi Solanki Sr Manager, Enterprise Software Development HotWax Systems Pvt. Ltd. Direct: +91-9893287847 http://www.hotwaxsystems.com www.hotwax.co On Thu, Aug 31, 2017 at 1:42 PM, Scott Gray <scott.g...@hotwaxsystems.com> wrote: > It's also used for pricing rule and promotion capabilities. > Laybys/layaways, rainchecks and purchases on account also would benefit > from the order model. > > If POS were extended to hospitality that would also rely on an order model. > > Regards > Scott > > On 29/08/2017 23:29, "Arun Patidar" <arun.pati...@hotwaxsystems.com> > wrote: > > > Hello All, > > > > In POS system, order immediately fulfill and come directly in 'Completed' > > status. Also, there is no shipping address, billing address, shipping > > method requires in POS. And even no inventory reservation takes place, > only > > items issuance is done. > > > > IMO, In the current system, the POS order detail is stored for the > > following reasons > > > > - To manage inventory issuance information > > - To store the customer information > > - To track the total sales amount > > > > > > I am thinking to remove the dependency of POS sales with Order data > model. > > Alternatively, we can simply create Invoice and item issuance record > only. > > This will reduce the system load for managing POS sales. > > > > It is possible that I am missing any important scenario that needs Order > > data model. Please let me know your thoughts on this. > > > > > > > > -- > > Thanks & Regards > > --- > > Arun Patidar > > Manager, Enterprise Software Development > > > > HotWax Systems Pvt Ltd. > > > > www.hotwaxsystems.com > > >
