There is no fixed rate for adapting contracts to the aluminium product passport, and that is not because no one knows. The amount is mainly determined by your own situation: how many contracts you have running with suppliers and customers, who draws them up, and how many of them already contain a provision on supplying product data. For one company that is one paragraph in an existing template, for another it is a series of separate conversations per customer.
The bill therefore depends less on the product passport itself than on the way your company already handles purchasing and sales contracts. A company that works with fixed general terms usually adds one provision that applies to all contracts at once. A company that writes customized contracts for each customer or supplier must essentially review each contract individually, and that directly affects the number of hours a lawyer or contract manager spends on it.
What drives up the bill or limits it
The number of contracts that need to be reviewed is the first factor, but not the only one. Whether it is a new contract or an amendment to an existing contract makes a difference: an amendment is usually faster to draw up than a completely new document. Also relevant is who does the work. An internal lawyer does not charge an hourly rate, but does consume time that could otherwise be spent on something else. An external firm works with an hourly rate that varies widely, and that rate increases as the subject matter becomes more specific and more coordination is needed with technical colleagues who know which data is actually exchanged.
What will actually be in the text
The core of such a provision usually covers three things: who supplies which data, in what form, and when that must happen. In addition, it is often stipulated what happens if the underlying product changes, and who the point of contact is if something needs to be adjusted. The more precisely that is already described in an existing contract, the less time it takes to sharpen it. Companies that already have their contract structure in order usually experience this part as a minor addition; companies that do not yet have that face broader questions that have nothing to do with the product passport itself.
Where costs are often underestimated
Two components are often forgotten when estimating costs. The first is liability: what happens if a supplier provides incorrect data that ends up in the passport. The second is the handling of data that is exchanged, and whether personal data is involved. For that last point, it is useful to first review which data is actually needed; on the page on privacy and data it is explained how this is handled when compiling a passport. If you clarify this in advance, you prevent a contract from having to be reopened later.
Getting an indication before you call a lawyer
Before you invest time and money in adapting contracts, it is often useful to first know where your company stands: what role you have in the chain, and which data goes with that. With a few questions that provide an immediate indication you get insight into that, without this already starting a legal process. That helps in the conversation with a lawyer, because you then already know which parts are relevant for your contracts and which are not.
The boundary between the platform and your contract
Alupas.eu compiles the passport on the basis of the data you or your supplier provide, hosts it for ten years, and supplies the QR data carrier. Drawing up or adapting your own purchasing or sales contracts falls outside this; that remains work for yourself or your lawyer. On the page explaining where the information comes from states how that delivery proceeds in practice, and in the knowledge base with topics per situation sorted out you will find the related questions about delivery and role allocation.
Would you like to know first what actually changes for your company before you have a contract adapted? Do the free quick-scan or browse through the knowledge base to see which section fits your situation.