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

Edit previous stock entries - feature request #410

Open
odingalt opened this issue Jul 8, 2015 · 4 comments
Open

Edit previous stock entries - feature request #410

odingalt opened this issue Jul 8, 2015 · 4 comments

Comments

@odingalt
Copy link

odingalt commented Jul 8, 2015

Feature request.

Adjust previous stock entries. We have been entering parts for months just to get up and running with the system. We thought it would be nice to take advantage of the average price feature.

Or

Allow rolling window (6 month?) where average price only includes recent purchases.

Or

Option to disable average price feature.

Unfortunately we have entered many stock with price of $0.00, causing the average calculation to be wrong forever.

Also, if there is a sudden increase in a component price due to market shortage, it will not reflect nicely under average price. (If we purchase parts for $1.00 for 5 years, then suddenly a supply disruption causes price to $2.40 per part, this isn't realy reflected by the average price, the huge purhase history will cause the average price to float nearer the $1.00 and mislead).

So I guess I don't see much use for the average price under current software.

I did add price for a stock entry, but because all previous entry were $0.00, now my average price is $0.25 for a component that costs $1.00, and I cannot edit the previous entry. So now I have incorrect pricing permanently showing in the summary screen.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@kbembedded
Copy link

I have also run in to this dilemma, and have solved it by just deleting and recreating the part. Its not a big deal for me because, while I do have stock that I keep, its ultimately pretty low volume and I do not so much care about the history.

I find a combination of the first to to be most appealing after thinking about it. The ability to adjust previous stock entries would be a great way to fix mistakes while a rolling window would better reflect the real average price of current stock. The rolling doesn't need to be a time based window, it could be stock based.

For example.
Add 20 pcs at $0.10/ea
Add 20 pcs at $0.15/ea
Add 20 pcs at $0.09/ea
Remove 10 stock. It removes from the oldest stock, so now the average would be calculated using 10 pcs @ $0.10/ea, 20 @ $0.15/ea, 20 @ $0.09/ea Avg. is now 50 pcs at $0.116/ea
Remove 30 stock, again removing from the oldest. Average is now 20 total pcs at $0.09/ea

@DIYsciBorg
Copy link

I too encounter this a lot. What I do is to find the 0 value items and make FULL DUPLICATES, then correct the price in the Initial inventory fields at the bottom of the part data, as copy in the inventory count from the original. I then go back and delete the 0 value item.

My suggestion for the future software would be one (or both?) of the following:
1: Average price calculator ignores all 0 entries.. this includes the initial stock, as well as stock adjusts.
2: Always pull the pricing data from the distributor field and "auto fill" stock adjusts. Let the user tweak them but at least get them in the ballpark. Better yet, add a pull down to the stock adjust which presents all distributors and bulk rates. If you have a sack of 100 pieces from digikey, and you had entered the data when you placed the order, then you should just need to select Digikey, 100pcs 82 cents per piece.

@Drachenkaetzchen Drachenkaetzchen added this to the 1.0 milestone Oct 16, 2015
@Drachenkaetzchen Drachenkaetzchen modified the milestones: 1.1, 1.0 Mar 14, 2016
@Drachenkaetzchen Drachenkaetzchen modified the milestones: 1.3, 1.2 Jan 17, 2017
@Drachenkaetzchen Drachenkaetzchen modified the milestone: 1.3 Sep 3, 2017
@baradhili baradhili added this to the future milestone Jan 17, 2020
@baradhili
Copy link
Collaborator

Overall we need a better way to handle "Average Price" it seems to cause no end of FRs

@baradhili
Copy link
Collaborator

Linked to #302

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants