Overview
With Article Requests, you request information specifically per Article or supply source (Supplier-Article relationship) – not just per Supplier. The dedicated entry Requests → Article Requests provides a separate Request type for this. The responses are prepared as a comparison matrix and can be applied in bulk to the properties of the supply source.
What this means in practice:
Requests at Article/supply source level instead of only at Supplier level
Each Supplier only sees their own Articles or supply sources
AI-assisted filling (if activated): Suppliers upload a data sheet, certificate or Excel file, and the table is pre-filled automatically
Responses are reviewed as a matrix and applied to the supply source via a bulk action – with value history
What problem does this feature solve?
Procurement and compliance often work at Article level: conformity information, specifications or origin data relate to the individual Article from a specific Supplier. If such information is only collected at Supplier level, the link to the specific Article is missing – the data has to be compiled via email and Excel and transferred manually.
Typical use cases:
Request PPWR information per packaging Article from the affected Suppliers
Document REACH/RoHS conformity at Article level per supply source
Capture long-term supplier declarations (SSA) and preferential origin per Article
Collect Article specifications, food contact or chemical information in a structured way
Prerequisites
Article Requests are enabled for your account by Tacto (AI-assisted filling is activated separately)
Articles, Suppliers and supply sources (Article × Supplier) are available in Tacto
Supplier Contacts are maintained (for sending)
Relationship to Supplier Requests
Article Requests do not replace Requests at Supplier level – both Request types exist side by side
A single Request does not mix questions at Supplier and Article level. If both are needed, send two Requests
Permissions & access
Access via the Requests area in the SRM module
No new roles – existing Request permissions apply (read access to supply sources, attributes and Contacts is also required)
Suppliers access exclusively via the magic link, only see their own supply sources and do not write any properties themselves – applying values is always done by procurement