Currently translated at 78.7% (52 of 66 strings)
Translated using Weblate (Thai)
Currently translated at 100.0% (176 of 176 strings)
Translated using Weblate (Thai)
Currently translated at 100.0% (176 of 176 strings)
Translated using Weblate (Thai)
Currently translated at 100.0% (19 of 19 strings)
Translated using Weblate (Thai)
Currently translated at 100.0% (50 of 50 strings)
Translated using Weblate (Thai)
Currently translated at 100.0% (84 of 84 strings)
Translated using Weblate (Thai)
Currently translated at 100.0% (117 of 117 strings)
Translated using Weblate (Thai)
Currently translated at 100.0% (117 of 117 strings)
Added cost and count to reports
- Added cost in temp table, reports at bottom of page and in each
summary and detailed report
- Added count in all the reports
- Renamed some report fields name to make it generic and consistent
across views
- Fixed few issues here and there
- Adjusted some code indentation
NOTE: Proper translation of word Cost is required in all the languages
but English
Improved Items suggestion
- Added select to restrict results fields
- Added distinct in suppliers instead of the array match
- Added $is_deleted in model part but is not still effective
Add copyright statements in COPYING license file
- Added jekkos and FrancescoUK / daN4cat
Other people that contributed should add their statements.
Finished task
1. User can add stock location in config page. Adding format is StockA,StockB,StockC for example
2. Item page, there is no more quantity column show in cert table. The quantity tracking is integrated in inventory detail
3. Receiving page, There is a stock location for user to select before receiving or returning stuff
4. Sale page, There is a stock location which is for user to select a stock location they sell from
Remain task
1. Requisition work flow
2. Language editing
3. Remove unuse code
PS
database.sql script merged with current ospos one
remaining problems in reporting (sale_type to add in sales_temp query?)
data model should be refactored to allow more genericity for custom item locations (2+)
inventory tracking should be adapted to use multiple locations (instead of duplicating items for different locations)
