Cultural Identity Protocol

A platform that flattens cultures into a SKU grid is a colonial project. Kolshee is the opposite: an instrument by which marginal cultures gain superior infrastructure without losing their soul.

The first stores in the Kolshee mesh are precisely the stores no algorithm has served well: halal supermarkets, ethnic markets, regional importers, family-run butchers, immigrant-owned grocery ecosystems. These stores carry SKUs the mainstream cannot stock — seven kinds of olives, twelve kinds of rice, regional spices that exist nowhere else in the country, breads baked from recipes older than the country they are baked in.

Kolshee designates a class of SKUs as "Heritage." Heritage SKUs receive special treatment across the platform:

• ▸First-class catalog placement; never substituted with a mainstream analog.
• ▸Origin-direct sourcing through the supplier graph; provenance recorded immutably on the spine.
• ▸Cultural-calendar-aware forecasting (Ramadan, Diwali, Easter, Lunar New Year, Eid, Nowruz, Día de los Muertos, Christmas, etc.).
• ▸Protected pricing — never used as a discount loss-leader.
• ▸Native multilingual product metadata (English, Arabic, Urdu, Spanish, Bengali, Farsi, Turkish, French, more).

Every Heritage SKU carries a provenance record on the event spine: origin farm, processor, certification body, chain-of-custody timestamps. Customers and merchants can inspect this record in-app. Mainstream platforms cannot replicate this without rebuilding their supplier relationships from scratch.

Kolshee never asks a merchant to surrender their identity. The merchant's branding remains on the shelf, on the bag, and on the receipt. The Kolshee marque appears only as a small "powered by" credential. The relationship between the merchant and the customer is owned by the merchant; Kolshee is the infrastructure beneath the relationship, not the face on top of it.

• ▸No private label competes with a Heritage SKU sold by an exclusive merchant in their corridor.
• ▸No data sold to a third party can re-identify a household, a merchant, or a community.
• ▸No price suggestion may force a merchant below the Heritage floor without their explicit consent.
• ▸No SKU may be removed from the catalog purely on velocity grounds if it carries Heritage designation.

Cultural fluency in this category is not aesthetics — it is distribution. Community trust dictates which stores carry which SKUs, which suppliers get repeat orders, which payment rails are tolerated, and which platforms are accepted into the back office. A competitor with deeper capital but no cultural literacy cannot enter these stores and cannot earn shelf-level data from them. That is the moat.

• ▸Trust precedes adoption. Stores that share data with Kolshee do so because the protocol exists, not despite it.
• ▸Heritage SKUs are unforgeable inventory. Network competitors cannot reconstruct provenance retroactively.
• ▸Cultural-calendar forecasting is a defensible data product. No generic forecasting engine has the underlying ground truth.