Trove Boutique Curated Intelligence
Piece III · Trove Provenance · Issue №07

Trove Provenance.

A working graph linking every SKU to materials, makers and origin — surfaced naturally inside the buying flow, never exiled to a virtue-signal page nobody visits. Auditable. Queryable. Refused where we cannot evidence the claim.

The graph

Three sub-graphs. One queryable surface.

Materials
Every SKU linked to its material composition.
Fibres, woods, metals, ceramics, dyes. Each node carries provenance attributes — species or alloy, source region, certification where claimed. Where a claim is unevidenced, the edge is annotated "unverified"; the merchant sees the gap and the customer never sees a hollow assertion.
Makers
Every SKU linked to the people who made it.
Workshop, atelier or factory. Country, region, scale. Independent maker, third-generation house, manufacturer-of-record. Where the merchant has direct relationships (most do, in boutique retail), the edge is dense and well-attributed.
Origin
Every SKU linked to the place it comes from.
Region of raw material, region of assembly, region of finishing. Country-of-origin notations that mean something — not the regulatory minimum, the working answer.
In the flow

Surfaced where it's relevant, silent where it's not.

The single most common provenance mistake in commerce is the badge. A round green badge on the product card linked to a separate page that nobody opens. We do not do this. Provenance information appears inside the product description where it earns its place — the origin of the oak in a chair, the dye-house behind a textile, the specific atelier responsible for the assembly. Where the information is not interesting for that piece, it is simply not surfaced. The customer encounters relevance, not signposting.

For categories where provenance is a category-wide concern (sustainable fashion, food, wood objects, hand-made textiles), Trove Provenance also generates a brief, evidence-grounded summary at the top of the category page. The summary is short, specific, and silent on anything we cannot evidence.

Pilot result · three boutiques · twelve months Across three pilot stores in different categories, surfacing provenance naturally moved conversion up by 4–6% on the relevant categories. Crucially, return rates dropped in parallel — customers buying with full information return less. The conversion lift is the easier number to publish; the return-rate drop is the operationally significant one.
The schema

Open · versioned · ours.

The Provenance schema is open. Versioned, documented, available in the Library. We use it ourselves; we encourage merchants to use it directly when they import third-party data; we are entirely happy for competitors to use it. The point of an open schema is that the data outlives the platform, and the merchant's investment in provenance data is not held hostage to a vendor choice.

Schema entityRequired fieldsVerification
materialtype, source_region, certification?Direct, supplier-attested, inferred
makername, country, scale, relationshipDirect, public-registry, inferred
originraw_region, assembly_region, finish_regionDirect, customs-record, inferred
claimstatement, evidence_link, statusVerified, unverified, refused
audit_eventtimestamp, actor, prior, posteriorImmutable log

Provenance Schema v1.2 is the current version. Earlier versions are archived and remain queryable; migration tooling is included with the atelier slot.

What we will not do

Three refusals, not negotiable.

Greenwash
We will not publish a sustainability claim we cannot evidence. The merchant sees the gap; the customer sees silence rather than a hollow assertion. Some merchants find this uncomfortable. The ones who don't end up with stronger brands.
Aggregate-and-pretend
We will not aggregate poorly-evidenced supplier statements and present the aggregate as a proven fact. Where the underlying claims are weak, the aggregate is annotated to match — even when the optics are unflattering.
Two-tier provenance
There is no premium-tier where evidence is treated more loosely. The Provenance discipline is one discipline; the audit log is one log. No client account can override a "refused" claim into a public assertion.

Apply for an atelier slot