Platform Data Partnership LOI Template
Internal draft template for Finn and Vera.
As of 2026-04-15.
Use Case
Use this as the fastest path to capture commercial intent after a first or second platform conversation. Keep it short. The goal is to lock:
- who the counterpart is
- what data is in scope
- what BuyWhere is allowed to do with it
- what happens during the pilot
Template
Parties
This Letter of Intent is between:
Partner:[Legal entity name]BuyWhere:[BuyWhere legal entity name]
Effective date: [DATE]
Purpose
The parties intend to explore a pilot data partnership under which Partner will provide BuyWhere with access to certain catalog data for use in BuyWhere's product indexing, normalization, discovery, and referral infrastructure for AI shopping experiences.
Pilot Scope
- geography:
Singapore - initial category scope:
[CATEGORY / ALL SG CATALOG / NAMED SELLERS ONLY] - expected delivery method:
[CSV / JSON feed / API / SFTP] - target pilot launch date:
[DATE] - pilot term:
90 daysunless extended in writing
Minimum Data Fields
- product identifier or SKU
- title
- price
- product URL
- image URL
- category
- stock or availability status
Optional but preferred:
- brand
- barcode or GTIN
- seller identifier
- variant data
- promo flags
Permitted Use
During the pilot, BuyWhere may ingest, normalize, deduplicate, cache, index, and display partner-provided product metadata within its services for search, recommendation, and referral use.
Restrictions
Unless otherwise agreed in the definitive agreement:
- BuyWhere will not resell the raw feed as a standalone dataset.
- No exclusivity applies.
- Neither party is granting production SLA commitments under this LOI.
Commercial Intent
The parties intend in good faith to negotiate one of the following structures in a definitive agreement:
- fixed annual data license
- fixed integration fee plus annual renewal
- revenue share on attributed commerce
- hybrid minimum guarantee plus upside revenue share
Pilot economics, if any: [NO-FEE PILOT / SGD AMOUNT / REV SHARE TEST]
Success Criteria
The pilot will be evaluated against:
- successful feed or API integration
- agreed field coverage and data quality
- refresh cadence achieved
- discoverability and referral reporting
- mutual agreement on expansion economics
Confidentiality
This LOI and any non-public commercial, technical, or legal information exchanged in connection with it will be treated as confidential.
Non-Binding Effect
Except for confidentiality and any expressly binding clauses, this LOI is non-binding and is intended only to record present commercial intent pending a definitive agreement.
Signature Block
[Partner name / title / signature / date]
[BuyWhere name / title / signature / date]
Finn Checklist Before Sending To Vera
- named legal counterparty confirmed
- pilot scope written narrowly enough to win internal approval
- no exclusivity language
- no implied uptime or support SLA
- data rights language allows caching, normalization, and display
- Kai has confirmed the minimum field list is feasible