Comments (4)
This is exactly what I need.
from django-bom.
This is really a feature that I need as well. A few months ago I started implementing warehouses, but I didn't finish it yet (lack of time, as usual ...)
I have cleaned and rebased my local branch today (rebased on my master branch, which also contains the seller preference: see #84). I will push this branch on my remote repo, so the change could be already accessible for tests and critics.
Here's how I imagine this implementation :
- Add the ability to create warehouses.
- Add the ability to put parts in warehouses (from the part management pages).
- When parts are added to a warehouse, the price can be either calculated from the seller price (in that case, the preferred seller part), computed from the subparts, or set manually.
- On the part specifications, the estimated price would be split to display:
- The estimated price of parts that must be purchased
- The price of parts that are in warehouses
- The estimated total price (sum of the two prices above)
- The warehouse details that show the parts, quantity, unit price (or avg unit price if relevant), and total price of parts contained in the warehouse.
Is it (roughly) how you imagined this feature @mpkasp @DasBasti ?
from django-bom.
@ks156 lack of time, sounds familiar :) Thanks for putting these great thoughts together. Definitely sounds roughly how I imagined this feature. Here's some hopefully constructivev feedback:
Add the ability to create warehouses.
Probably need all CRUD operations / views
Add the ability to put parts in warehouses (from the part management pages).
Thinking about this UX & when a user would want to add parts to a warehouse. Probably a few scenarios:
- They recceive a single order of a single part, probably easy to go to the part management page to add more parts to a warehouse
- They receive an order of multiple parts (E.g. an electrical BOM of 20+ components). Probably some other faster method to import multiple parts from a single view would make more sense?
- Also need to think about when parts move between warehouses, and removed from inventory.
Of course we could talk about part disposition, and combining parts into subassemblies instead of removing them, but we probably don't need to get that fancy for the initial implementation
When parts are added to a warehouse, the price can be either calculated from the seller price (in that case, the preferred seller part), computed from the subparts, or set manually.
Sounds pretty good. Maybe a seller part could be selected from a list, and defaulted to preferred?
On the part specifications, the estimated price would be split to display...
Cool!
The warehouse details that show the parts, quantity, unit price (or avg unit price if relevant), and total price of parts contained in the warehouse.
I guess this is the "R" part of the Warehouse CRUD views. Sounds good to me. Did you consider the ability to update part quantity / price, move parts to different warehouses from here as well?
Generally, it'd be nice if the UI & UX of the inventory feature is out of the way if users decide not to use it, but in the right places if they do decide to..if that makes sense.
from django-bom.
For now, I'm thinking this is a whole different product, possibly a great "sibling" product to IndaBOM. I'm willing to re-visit this in the future, but closing this for now.
from django-bom.
Related Issues (20)
- Add picture to component in detail view
- 500 Internal Server Error on Updating Subpart quantity
- Part class is being ignored in search settings
- Add link to seller part HOT 1
- Is there a way to define a seller (supplier) part number ?
- Notes about running from git with mysql
- RecursionError: maximum recursion depth exceeded while calling a Python object on Python 3.8 HOT 3
- Add manufacturer part and seller part during parts/boms csv import HOT 3
- unit cost and NRE cost not populating on seller part editing form
- Sellers informations should be revision dependent HOT 8
- Part Temperature Range HOT 1
- Variants HOT 2
- Create a manufacturing order
- Manage ellipsis is often off the right of the window and required scrolling HOT 1
- Upload / Import a full BOM
- Add a link field to a manufacturer part HOT 1
- `django.contrib.admin.sites.NotRegistered: The model User is not registered` when User model is not yet registered in admin
- Add option to cache to `part_revs` loop in the dashboard template
- Update reference to User model in Organization and UserMeta models to `settings.AUTH_USER_MODEL`
- API
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from django-bom.