A catalog helps quickly compile an initial list of manufacturers, but a product listing should not be treated as ready-made proof of compliance with the procurement requirements. The description may be abbreviated, outdated, or insufficient to identify a specific model. Therefore, information found through the search should be compared with the procurement documents, the manufacturer's data, and the documents that the supplier is prepared to provide upon delivery.
First, identify the product
Check whether the listing data makes it possible to identify the product unambiguously. Names such as “personal computer” or “server” without a model, configuration, and component list provide little information. For complete equipment, it is important to determine whether the entry refers to the entire product or only to an individual component.
- Which manufacturer is listed, and do the organization's name, taxpayer identification number, and address match the counterparty's details?
- Is there an exact model, part number, version, or configuration designation?
- Which processor, storage devices, memory, interfaces, and peripheral devices are included?
- Are the operating system, preinstalled software, and their licensing terms specified?
- Can the catalog information be linked to the manufacturer's passport, manual, or specification?
For preliminary market analysis, it is useful to search for Russian computer and electronic equipment. This is an information catalog of products based on open GISP data. The listings help compile a list of manufacturers for subsequent requests for documents and commercial proposals. The accuracy of the information, model specifications, and delivery terms should be clarified with the manufacturer; the presence of an entry does not confirm compliance with the technical specifications of a particular procurement.
Compare the listing with the procurement requirements
A match in the general category name is not enough. Create a table with the columns “requirement — value in the listing — supporting document — discrepancy.” Separately note parameters that are absent from the open data. Ask the customer to clarify whether equivalent characteristics are acceptable, how ranges and phrases such as “not less than” are compared, whether a specific form factor is required, which interfaces are mandatory, and what is included in the delivery package.
If the procurement documentation contains requirements concerning the origin of the products, registry information, or supporting documents, check whether they apply specifically to this procedure. The presence of an entry in itself does not guarantee compliance with the technical specifications, product quality, legality of the delivery, or successful participation in the tender.
Request confirmation from the supplier
- Which manufacturer and exact model will be specified in the contract, delivery note, and product passport?
- Is the proposed configuration current, and have any components been replaced since the listing was published?
- Who provides the warranty, where is repairs performed, and what is the procedure for submitting a claim?
- Which documents confirm the specifications, origin, and rights to the software?
- Can you obtain a sample of the labeling, serial number, and bill of materials before shipment?