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

Supporting price negotiations based on a DPP for a product that will be produced in the future #43

Open
zachzeus opened this issue Mar 26, 2024 · 2 comments
Assignees
Labels
Product Passport Issues related to Product Passport

Comments

@zachzeus
Copy link
Contributor

Some product claims may not be fully resolvable when the negotiation between buyer and seller is occurring. Is there a method that should or could be added to the protocol that will allow suppliers and consumers the ability to price the value of claims in the future.

@monkeypants
Copy link

DPPs are at the SKU or batch/item level. I think this question relates to proposed items or proposed batches where the items are known in advance.

For example: if I am negotiating a contract for future sale, I might make a basket of claims (and provide evidence) based on the information currently available, which the buyer uses to negotiate a price. When the sale is struck in the future, a different version of the basket of claims might be available. As a buyer, I will want to specify "same or better" for some claims.

The DPP link resolver may need access to the history of product passport versions. A DPP may need a reference "supersedes" the previous version of the DPP in a chain.

@zachzeus
Copy link
Contributor Author

@monkeypants - what does it mean to close this issue? Is there an example of how we might use a DPP to address this?
This technique may also be useful for some of our circularity and 'late arriving data' scenarios.

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

No branches or pull requests

2 participants