Vendor Terms

Vendor Terms

Closed-beta legal boundary: Founder-prepared draft for closed-beta readiness. Lawyer/CA review required before paid/public production. PGI Hub has no approved live payments, GST invoicing, vendor payouts, escrow, public marketplace launch, automated supplier award, or production legal approval under this pack.

1. Master Overview and Boundary

These Vendor Terms govern vendor participation in PGI, including vendor claim workflows, business profile management, capabilities, rates/offers, stock, lead times, certification claims, contact governance, RFQ responses, profile correction, takedown, suspension, and supplier labels. They bind vendors, suppliers, manufacturers, distributors, service providers, team members, and representatives using PGI.

PGI does not guarantee buyer leads, buyer conversion, ranking position, RFQ volume, quote acceptance, payment, delivery success, legal compliance, tax treatment, or supplier performance. PGI is not a broker, escrow provider, payment intermediary, payment aggregator, merchant-of-record, customs broker, freight forwarder, insurer, or guarantor.

2. Operational Definitions

• Vendor Claim Request means a request by a person or business to control, correct, or manage a PGI vendor profile.
• Vendor-Submitted Data means business details, contact governance settings, capabilities, processes, materials, product categories, part aliases, certifications, rates/offers, stock, lead times, shipping terms, and RFQ responses submitted by or for a vendor.
• PGI Researched Profile means a supplier profile derived from public, third-party, internal research, provider/API, or buyer-supplied sources and not necessarily claimed or verified.
• Claimed means PGI has allowed a vendor representative to manage a profile after a claim workflow; it does not equal verification.
• PGI Verified means PGI has completed a defined verification process supported by retained evidence. The label must not be used without evidence.
• Contact Hidden means vendor contact fields are not broadly visible and are governed by access controls.

Platform Informational Inferences means outputs generated, derived, normalized, classified, ranked, estimated, compared, summarized, or otherwise presented by PGI using platform logic, user-provided data, vendor-provided data, public-source data, third-party data, provider/API data, AI-assisted analysis, rule-based logic, or internal procurement intelligence methods.

Platform Informational Inferences are not professional, engineering, legal, tax, logistics, insurance, customs, financial, or procurement advice. They are decision-support outputs only. The buyer, vendor, or contracting party remains exclusively responsible for independent validation before relying on such outputs for commercial, technical, legal, tax, logistics, compliance, or contractual decisions.

3. Authority to Represent Business

A vendor user represents that they are authorized to act for the relevant business, supplier, manufacturer, distributor, service provider, or organization. A vendor must not claim a competitor, impersonate a supplier, submit false certifications, publish unauthorized contact data, or represent capability, stock, pricing, lead time, quality, tax, or logistics terms without authority.

4. Unclaimed and PGI-Researched Profiles

PGI may present unclaimed supplier records as Potential Supplier, PGI Researched, Not Yet Claimed, Not PGI Verified, and Contact Hidden. These records are decision-support only and can be corrected, suppressed, claimed, reviewed, or removed under vendor correction and data-quality procedures.

Unclaimed supplier records must not be described as approved, partnered, verified, guaranteed, certified, or endorsed by PGI.

5. Vendor-Submitted Data Responsibility

Vendors are responsible for keeping profile data accurate and current. Dynamic commercial data, including rates/offers, stock, lead times, freight basis, MOQ, GST/tax basis, and availability, should carry freshness metadata. Dynamic data older than 7 days can be flagged as stale, downgraded in confidence, or hidden from high-trust comparison workflows.

Certification claims must be supported by accurate evidence. PGI may request evidence, hide unsupported claims, downgrade verification labels, or remove claims that appear misleading or stale.

6. Contact Governance

Vendors control contact details subject to PGI's Contact Hidden Policy, buyer workflow rules, privacy controls, and anti-scraping protections. PGI may hide, suppress, or rate-limit contact exposure to prevent misuse, scraping, unsolicited outreach, privacy violations, or ungoverned buyer-vendor communication.

7. RFQ Response Obligations

Vendors responding to RFQs must clearly state price basis, tax/GST treatment, freight inclusion/exclusion, incoterms, MOQ, lead time, validity period, inspection/certification status, deviations, assumptions, and exclusions. A quote that excludes GST, freight, packing, warranty, testing, tooling, or delivery must explicitly state that exclusion.

8. Verification, Ranking, and No Guaranteed Leads

PGI may use labels, data-quality warnings, freshness indicators, response-history signals, category/process/material fit, location, certifications, and confidence scores for supplier discovery and ranking explanations. No vendor receives guaranteed buyer leads, guaranteed RFQs, guaranteed ranking, guaranteed visibility, guaranteed sales, or paid placement in organic ranking under this closed-beta pack.

PGI organic ranking must not be based on commission, billing plan, paid status, sponsored status, credits, or PGI commercial relationship unless a separate clearly labeled advertising/sponsored policy is professionally reviewed and implemented.

9. Correction, Removal, Takedown, and Suspension

PGI may correct, hide, suspend, remove, or place a vendor profile or field in review when data is inaccurate, disputed, unsupported, stale, misleading, unsafe, abusive, privacy-invasive, or inconsistent with platform rules. Vendors may request correction or removal through the Vendor Correction Policy and support/grievance route.

10. Product UI and Acceptance Mapping

Related Documents

• vendor-data-policy
• contact-hidden-policy
• vendor-verification-policy
• marketplace-labels-policy

Review Status

Founder-prepared draft. Lawyer/CA review required before paid/public production.

Paid/public production readiness: Not approved. Lawyer/CA/payment-provider/founder review required.