-
Notifications
You must be signed in to change notification settings - Fork 10
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
Rethink how products and producers are handled #17
Comments
Yeah, that's a good idea. We would need to rethink how stuff are handled in general if we want to have multiple collectives use the tool. So : Here is a dependency thing :
And we might even want to have multiple prices for the producers, in a way that would make the evolutoin of the prices traceable. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, they're part of the delivery, but we might want to put them in a separate location, like it's done for groups, so that we don't have to copy them on every delivery.
If we do this, we might want to enable / disable them on a delivery basis.
Also, when we do this, we might want to keep a record of the prices and availability of the products, related to a delivery, but I'm not sure how we should handle this.
Ideas?
The text was updated successfully, but these errors were encountered: