File № SCN-2026-01 / B · Marketplace economics
Exhibit B · Proof surface · access after written request
SKU-level marketplace economics — proof surface after qualification.
Reconciled per-article profit from raw Yandex.Market cabinet exports — fees, logistics, storage, ad boost, and cost of goods applied at SKU level. A deployed annex to the same engine described on the dossier cover — not a self-serve product page.
Yandex.Market is live; Ozon and Wildberries are scoped under co-development contract on the same architecture.
Hosted app access follows written request, scoping review, and scoped pilot under NDA.
Terms of access
Three steps from written request to reconciled output.
- 1
Written request
Industry, export workflow, and what margin truth must look like — fit is confirmed in writing before scoped access under NDA.
- 2
Redacted exports under NDA
Raw XLSX from the seller cabinet: "Finances → Reports → Payments for period" plus storage, boost, and cost-of-goods files. Scoped after qualification.
- 3
Reconciled exhibit output
Per-SKU P&L — marketplace fees, logistics, storage, ad boost, and COGS in one reviewable view. Period comparison included.
What the exhibit shows
Row-level economics the signatory can reconcile.
Per-SKU profit, not aggregate margin
Every article has its own profit and margin line — a row in the file, not a dashboard summary.
Sale date vs. payment date, handled
Marketplace exports split the same order across multiple files and time windows. The report reconciles them so the chosen period is the period delivered.
Fees, logistics, storage, boost
All marketplace services and promotional costs applied at the SKU level, not smeared as a flat percentage across the catalogue.
Period comparison
Month-over-month deltas per SKU — where margin is quietly drifting while revenue still looks fine.
Where this stands, honestly
- —Deployed on real seller files. Access is gated — request access to qualify for the hosted app.
- —Pricing (in RUB) is documented on the Russian seller page for the self-serve path; enterprise scope is agreed in writing after scoping review. A call is optional once fit is confirmed.
- —Ozon and Wildberries variants are under co-development contract — same engine, different fee models. Marketplace operators should request access to scope the variant.
Optional call only after fit is confirmed.




