Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add store accounts #2

Closed
UplandsDynamic opened this issue Jan 28, 2019 · 1 comment
Closed

Add store accounts #2

UplandsDynamic opened this issue Jan 28, 2019 · 1 comment
Assignees
Labels
backend Issue includes backend elements development funded Development funded though client, bounty or donation enhancement New feature or request merged to master work on this issue has been merged to master ui Issue includes UI elements

Comments

@UplandsDynamic
Copy link
Owner

UplandsDynamic commented Jan 28, 2019

#Preliminary scope

Backend

Add database for each 'store manager' user. Change stock xfer process to add units to store database, rather than simply delete from warehouse database (as currently the case). Add a 'stocktake' process to calculate a report, as detailed below.

Database schema

Duplication of warehouse database schema, with exception of:

+ 'opening_stock' column
+ 'closing_stock' column
+ 'xfer_price' column (unit price of stock as xferred)
+ 'selling_price' column (current unit price of stock as sold in the shop)
- 'unit_price' column

Report generation

Recorded data

  • Opening stock (opening_stock as of datetime of last stocktake)
  • Closing stock (closing_stock as of datetime 'now' at current stocktake process)

Processed data

Values for each line

a) Differential for all sales & loss (opening_stock - closing_stock)
b) Xfer price value for all units lost or sold ((opening_stock - closing_stock) * xfer_price)
c) Selling price value for all units lost or sold ((opening_stock - closing_stock) * selling_price)
d) Differential between total xfer price & total selling price, for a line ( (c) - (b) ) *See note (1)

Values for total store

e) Total xfer price value of all stock lines sold or lost since last stocktake process (Σ(b))
f) Total selling price value of all stock lines sold or lost since last stocktake process (Σ(c))
g) Total differential for all stock lines, between xfer price & selling price (Σ(d)) *See note (1)

Database maintenance processes

  • Following completion of stocktake process, closing_stock data is copied to opening_stock, then emptied.

UI

Build a dedicated UI for store databases, to allow store managers to:

  • View their own store's stock holding record
  • Submit a stock count (closing_stock) & trigger the generation of stocktake reports

Notes

  1. Whilst the differential may be indicative of a store's sales performance, it cannot be considered "profit", because actual sales, shrinkage and loss (both known and unknown) are not recorded. Therefore, the differential is not synonymous with sales and profit in this model. It may merely suggest that, had the differential consisted entirely of sales at the selling price - with no units being subject to loss or shrinkage - the differential would have been representative of "store profit" under those improbable circumstances.
@UplandsDynamic UplandsDynamic added the enhancement New feature or request label Jan 28, 2019
@UplandsDynamic UplandsDynamic changed the title Add store databases Add store accounts Jan 30, 2019
@UplandsDynamic UplandsDynamic self-assigned this Jan 30, 2019
@UplandsDynamic UplandsDynamic pinned this issue Jan 30, 2019
@UplandsDynamic UplandsDynamic added assigned Work has been assigned to individual(s) premium feature This is a premium feature that is not offered as part of the free community edition in progress Work on this issue is in progress labels Jan 30, 2019
@UplandsDynamic UplandsDynamic added planned Work on roadmap, commencement pending ui Issue includes UI elements backend Issue includes backend elements and removed in progress Work on this issue is in progress premium feature This is a premium feature that is not offered as part of the free community edition labels Jan 30, 2019
@UplandsDynamic UplandsDynamic added in progress Work on this issue is in progress and removed planned Work on roadmap, commencement pending labels May 29, 2019
@UplandsDynamic UplandsDynamic added merged to master work on this issue has been merged to master and removed assigned Work has been assigned to individual(s) in progress Work on this issue is in progress labels Jun 26, 2019
@UplandsDynamic
Copy link
Owner Author

Released in version 4.0.0

@UplandsDynamic UplandsDynamic added the development funded Development funded though client, bounty or donation label Jun 26, 2019
@UplandsDynamic UplandsDynamic unpinned this issue Oct 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Issue includes backend elements development funded Development funded though client, bounty or donation enhancement New feature or request merged to master work on this issue has been merged to master ui Issue includes UI elements
Projects
None yet
Development

No branches or pull requests

1 participant