See the replies still needed
Identify requests waiting for a response or clarification, without piecing together a status from separate messages.
Purchasing and export · Machinery
From a purchased part to an assembly: bring requests, product references and supplier replies together. Give purchasing and export a shared view of the work.
Explore the free betaFree beta · Access by invitation
One request. Replies and evidence together.
Less piecing things together
One supplier replies about the shaft, another about the housing. UrsprungWert keeps each request, response and open question together so your team can see what still needs attention.
Identify requests waiting for a response or clarification, without piecing together a status from separate messages.
Select the products covered by the request. Article references help your team check whether the reply covers the right scope.
Record the assessment alongside its supporting documents so another team member can understand the decision.
Every component has a reference. Every decision has context.
From the first request to the recorded decision.How it fits your work
Select the supplier, products and period you need. A clear request makes the response easier to place.
Collect the declaration and supporting documents with the request. Keep questions in the same context.
Review which components and periods are covered, clarify open points and record the decision.
An illustrative workflow example
A declaration arrives for a coupling. It is unclear whether it includes the version your team requested.
Your team finds the request and response together, clarifies the reference and records the resulting decision with the case.
An illustration, not a customer case study.
Before you begin
What UrsprungWert supports. And what stays your decision.
Yes. Select the relevant products and use clear article references. Your team then checks whether the response actually covers the scope requested.
No. UrsprungWert organises supplier declaration collection and review. Preference calculation and independent determination of the physical origin of goods are outside its scope.
No. You can manage suppliers, products and requests directly in the web interface. Import is an optional starting aid, not a prerequisite for the workflow.
Yes. In the planned pricing model, the plan does not cap the number of imported records. Use in requests counts towards the relevant allowances. Technical file and processing limits still apply.
The supplier is responsible for its statements. Your team assesses the response and decides whether to accept it. UrsprungWert organises this process and does not independently confirm the physical origin of goods.
Access is currently restricted to invited teams. There are no plan charges during beta and no automatic conversion to a paid plan.
Plans based on suppliers used are planned, including a permanent free plan. Paid plans are not active yet. The separate pricing overview shows the current proposal.
The planned rule releases a slot after 30 days of explicit retirement once open work is resolved. Reactivation during the wait cancels the release. This pricing rule is not yet an active technical restriction in the beta.
Start with your team
No plan charges during beta. No automatic paid conversion.
Access is currently restricted to invited teams. If you already have an invitation, you can sign in. No payment details are requested.
View planned pricing and allowances