Hey everyone!
Thanks for pitching in on the discussion. @JayRam, when I asked the question my thinking was along the lines of what @bkm has stated.
Some good news, I’ve been hard at work the past 7 days trying to integrate Unicenta oPOS an open source POS with ERPNext v12. I decided to use Myddleware because I needed a quick solution, in hindsight learning/working with Frappe/Python on a connector would have been a better solution (portable/replicable) and probably taken just as much time.
I also changed the POS to SambaPOS because it has a far better UX and database structure (not too normalised/fragmented). I think its a better solution even though it is no longer open source. It has a very fair once-off price of $250.
The major downside is that SambaPOS runs on MS SQL.
Here’s what I’ve been able to do:
- Sync Customers
- Sync Tables
- Sync Item Groups and Items
- Sync Sales Invoices with
- Included Sales Invoice Items
- Sales Invoice Payments
Here’s what I need to do:
- Automatically mark invoices as Paid, they’re coming in as drafts even if I set the status to Paid
- I’m thinking of creating a script for this
- Deduct sales stock from ERPNext
- Considering my current skills and time I’m thinking of creating BOMs (Recipes) in SambaPOS and sending these as Stock Issue Entries to ERPNext.
- No production is necessary because the Kitchen will get a printout Order from SambaPOS
- Non production Items, like drinks, will either have a 1-to-1 Recipe (preferred for its simplicity)
- OR be deducted via the normal Update Stock mechanism in Sales Invoice. While Kitchen items will be non-stock items deducted with the same Stock Issue transaction type described above.
Please recommend any improvements if you think any of this can be done better.