Sign in
CorpiFind Technical Knowledge Base

Platform Documentation & Trade Standards

Guides to the catalogue, requests for quotes, customs terms and the API.

Platform Architecture & Verification Methodology

CorpiFind is a sourcing platform for food, feed and aquaculture inputs. It turns a technical sourcing need into a structured request and a shortlist of catalogue products, and explains each match. Official datasets (registers, trade statistics, tariff schedules) are added through approved pipelines and shown with their source and date; until then the pages that need them say so.

Exporter KYB & Entity Resolution Standard

A facility record, once official registers are loaded, reflects what the register says: a licence and, where applicable, an EU approval number. A licence proves that a facility is licensed, not that it sells a given product or will accept an order. Supplier-submitted claims are not independently verified today.

HS and GTİP Codes as Evidence

CorpiFind shows HS and GTİP codes only as evidence with their source, never as a classification it asserts for your goods. Duty rates and origin-preference rules (such as the EU–Türkiye customs union and EUR.1 arrangements) appear only once official tariff schedules are loaded, with their source and date. Until then, confirm the classification, duty and origin documents with your customs broker.

Logistics and Cold Chain

CorpiFind does not publish freight rates, transit times or landed costs it cannot source. Agree Incoterms, packaging, temperature requirements and documents with the supplier and your forwarder in the RFQ; route estimates will appear only when sourced rate data is loaded.

Proforma contract generation & document verification

Commercial terms follow ICC Incoterms 2020, and the platform can generate a proforma invoice and a customs dossier from an accepted quote. CorpiFind does not hold or move money: settlement runs directly between the parties on the terms the proforma records.

API & Cryptographic Notarization Ledger

Trade documents can be given a SHA-256 fingerprint and checked against a local notarization record, so a later copy can be compared byte for byte with what was notarized. There is no public API yet; the endpoints described in earlier drafts of this page are not available.