BuyWhere BD Commercial Pricing And Terms
Internal working doc for Finn and Athena.
As of 2026-04-15.
Objective
Lock a pricing model and default commercial terms that can be used immediately for:
- anchor merchant alpha deals in Singapore
- one platform data partnership pilot with Carousell, Shopee, or Lazada
This package is designed to maximize speed to first booked revenue without promising production-grade SLAs that the product cannot yet support.
Recommended Anchor Merchant Offer
Offer Name
Alpha Access Partner
Commercial Structure
| Component | Default |
|---|---|
| Onboarding fee | SGD 4,000 one-time |
| Monthly platform fee | SGD 1,500/month |
| Initial term | 3 months |
| Included catalog size | Up to 10,000 active SKUs |
| Feed refresh cadence | Daily preferred, weekly minimum |
| Overages | Custom after 10,000 SKUs |
Why This Should Be The Default
- low enough to close with a design-partner motion
- high enough to matter commercially
- easy to explain without usage-based complexity
- three-month minimum creates booked revenue quickly
At default terms, one signed merchant is worth SGD 8,500 in first-term contracted revenue.
Six merchants at default terms would equal SGD 51,000.
Recommended Packaging By Segment
| Segment | Best fit | Default commercial package |
|---|---|---|
| Mid-market catalog merchant | 1,000 to 10,000 SKUs, wants AI visibility | SGD 4,000 onboarding + SGD 1,500/month |
| Large catalog merchant | 10,000 to 50,000 SKUs, stronger reporting asks | SGD 7,500 onboarding + SGD 2,500/month |
| Strategic platform or marketplace | 100,000+ listings, schema/API work, legal review | pilot first, custom economics in definitive agreement |
What The Merchant Gets
- product feed mapping and ingestion support
- catalog normalization into BuyWhere schema
- product inclusion in BuyWhere search and recommendation surfaces
- referral-ready outbound links where supported
- monthly summary reporting on indexed SKUs, clicks, and top categories
- named BD owner during alpha
What We Should Not Promise Yet
- guaranteed GMV uplift
- guaranteed conversion rates
- enterprise uptime SLA
- custom dashboards before a signed expansion agreement
- real-time sync unless Kai explicitly confirms support
Default Merchant Terms
Contract Structure
- order form plus short MSA is preferred
- if legal overhead is slowing the deal, use a paid pilot letter plus data processing appendix
Payment Terms
- invoice on signature for onboarding fee
- invoice monthly in advance for platform fee
- payment due
Net 14 - late payment pauses feed processing after written notice
Data And Usage
- merchant retains ownership of source catalog data
- merchant grants BuyWhere the right to ingest, normalize, index, cache, and display product metadata for discovery and referral use
- BuyWhere may use aggregated performance data for internal analytics and board reporting
- no resale of raw merchant feed without explicit written approval
Pilot Scope
- Singapore catalog only unless explicitly expanded
- core fields: SKU, title, price, URL, image URL, category, stock status
- optional fields: brand, GTIN/barcode, attributes, promo flags, variants
Service Language
Use this language consistently:
BuyWhere is providing alpha-stage infrastructure access and implementation support. Features, refresh timing, and reporting may evolve during the pilot.
Termination
- either party may terminate for uncured material breach
- convenience termination allowed with
30 daysnotice after initial term - on termination, BuyWhere stops refreshing the feed and removes merchant-owned data from customer-facing surfaces within a commercially reasonable period
Recommended Platform Partnership Starting Position
For Carousell, Shopee, or Lazada, do not lead with a revenue share debate. Lead with a pilot that proves:
- data transfer method
- schema quality
- refresh cadence
- attribution path
- legal comfort on usage rights
Preferred Pilot Position
| Term | Starting point |
|---|---|
| Pilot term | 90 days |
| Geography | Singapore first |
| Data scope | category-limited or seller-limited if needed |
| Economics | pilot can be no-fee if it unlocks access quickly |
| Expansion trigger | broader catalog scope, higher refresh cadence, or API access |
Definitive Agreement Options After Pilot
| Model | When to use |
|---|---|
| Fixed annual data license | platform wants predictable economics |
| Fixed platform integration fee + annual renewal | best for operational simplicity |
| Rev share on attributed orders | only if attribution path is accepted by both sides |
| Hybrid fixed minimum + upside rev share | best long-term option if trust is established |
Approval Flags For Vera
Loop Vera before agreeing to any of the following:
- exclusivity
- MFN pricing
- limits on data caching or normalization that break the product
- indemnity beyond standard mutual carve-outs
- sub-processor restrictions
- service credits or hard SLA language
- resale rights for raw data
Suggested Talk Track
- BuyWhere is the catalog layer for AI shopping agents.
- The first goal is accurate product inclusion, not a heavyweight enterprise integration.
- We can onboard via feed or API with a narrow Singapore pilot.
- The pilot is structured to validate discoverability and data operations, then expand.
Close Criteria For Week Of 2026-04-15
- Athena aligned on default anchor merchant package
- Finn uses one commercial default instead of custom pricing per prospect
- Vera reviews the approval flags before external redlines start
- Kai confirms the minimum required feed fields and supported import paths