we seem to be stuck a little with this mainly because the etimate budget (estimated $500) is only funded partially ($115.-) so far
@cpurbaugh@Muzzy@fkardame@sellisjr you all ave expressed certain interest in this feature and at least some of you where down for a contribution … Any reason that made you stop?
we are ready in terms of specs and platform for the funding … so let’s go ahead everybody. I am not prepared to just bury this project.
@anand I now you are super busy with release of ERPNext 7 these days supposedly. Still it would be great whether you find a minute to comment on the question raised 2 or 3 post earlier regarding integration of subwarehouses in the main code or adding up to it with a custom App from your perspective?
@ramielian, sorry to bother you, but do you have any news regarding your contribution? @cpurbaugh@fkardame@Muzzy@sellisjr , guys we really should start moving further with the project, please consider donating if you want this feature to get implemented.
Thanks.
@strixaluco am actually having financial problems at the moment and i cannot even go back to my work country due to visa issues and insufficient funds… so any contributions to me would be very appreciated
Hello, Even though the client has not yet replied I have gone ahead with $50 for this project now, We would have been more financially supportive but situation is extremely difficult for now.
Hope few others also pitch in and someone creates the codes.
That’s great, @Muzzy! Thank you for contribution. @cpurbaugh, thanks for update. There is definitely a difference between what you’ve written in the thread on the Bountysource and specifications draft, made by @vrms, so I assume you might want to commit some changes to the draft.
by the way … this is the job I have posted. There is one interested party so far
and it would be great whether someone from Frappe Pvt. @anand, @rmehta, or anybody else from the core team could comment on the question whether from your point of view this feature would be integrated in the core (which I think is the way to go) or rather be added as an external App.
Indeed, our company intended to sponsor development and to have the feature in the core and it’s great to know that Frappé team shares this point of view. @vrms, thanks for creating the job listing. I think at this point, as @anand confirmed intentions to have the sub-warehouses feature in the core, you can explicitly tell mr. Maroof Ibrahim from Maven Solutions that the code has to be merged upstream. From my humble experience, service providers expect to develop the code for standalone instances by default, not for upstream branch.
Also please check if you agree with my pull request to specifications.
Thanks.
It’s not quite relevant to actual topic, but I’d like to ask community if we can solve the problem with stock in transit within current campaign too?
For sure it’s nothing about sub-warehouses, but if there is a demand to cover “in transit” issues, we might expand campaign.
It will help as a temporary workaround, but as @jchakma pointed, it’s probably not standard. Let me describe the whole situation.
We have substantial amounts of items being constantly moved from one warehouse to another and we’d like to keep records of each dispatch and track them. It will be good to have list of items, customer name, date and time and postal tracking number per each dispatch.
I’m not sure which part of “Stock” module this functionality should be related to, that’s why I’m asking for opinions. Apologize if it’s too offtopic.
can we trade a commitment (which time wise maybe does not have to be same as 7 release date) from your side against the funds available ($165.- at this point in time)?
