Compare sales channels

Create a comparison

1. 1

   Open /app/channel-economics in an entitled workspace.

2. 2

   Enter marketplace and owned-store revenue, orders, and costs in RUB kopeks through the displayed ruble fields.

3. 3

   Calculate, review the warnings, and save a named scenario to preserve its version.

4. 4

   Change one assumption at a time and compare contribution and fully loaded profit.

Import owned-store records

1. 1

   Open /app/channel-economics/imports and upload an owned-store CSV, TSV, or Excel .xlsx order or cost file.

2. 2

   Choose the source, encoding or sheet where applicable, map columns, and inspect the preview and rejected rows.

3. 3

   Commit only after checking order IDs, dates, returns, costs, and source totals. A repeated identical upload must not add duplicate financial rows.

Prepare and check import files

1. 1

   Download the order or cost CSV template from the imports page. Order rows need order_id, line_id, date, status, sku, quantity, and gross_rub. Cost rows need entry_id, date, cost_type, and amount_rub.

2. 2

   Use a stable source ID for each data source and keep order/line IDs and cost entry IDs stable across re-uploads. Upload a file of at most 16 MB; select the intended worksheet for .xlsx.

3. 3

   In the preview, resolve rejected rows and compare the period, order count, and RUB totals with the source export before committing.

4. 4

   For a possible duplicate charge warning, compare both cost entry IDs with the source export. The warning does not remove either row or reduce the total.

5. 5

   A cost row can also match a previously committed entry from another file or source. Review the related source and entry ID, confirm the warning checkbox, and preview again if another import changed the matches before commit.

6. 6

   For a corrected cost entry, use a signed amount and inspect the correction count and file checksum in import details. Check the resulting summary against the original source again.

Compare an independent source statement

1. 1

   On the imports page, choose Orders or Costs, the source ID, and a period of at most 90 days. Select a grouping and download its control CSV template. Orders support day, order, SKU, and day + SKU; costs support day, entry, cost type, campaign, and day + cost type.

2. 2

   Enter complete control totals from an independent source export. For orders, supply at least one of gross_rub, revenue_rub, quantity, or line_count. For costs, supply amount_rub (signed corrections are allowed) and/or entry_count. The CSV must be UTF-8, at most 1 MB, and contain at most 1,000 groups.

3. 3

   Compare totals and inspect mismatches, groups missing from the import, and imported groups absent from the statement. Download the report before leaving the page; the control file and report are not stored.

4. 4

   Repeat the comparison after any correction or new import. Matching selected measures at one point in time does not certify the source statement, tax policy, return handling, missing costs, or profit.

Use Google Sheets when available

1. 1

   If the Google Sheets panel is available in your workspace, connect with the dedicated read-only authorization and choose one spreadsheet, named sheet, and bounded range. Do not publish the sheet or paste a public sharing link.

2. 2

   Refresh to create an immutable snapshot, then use the same mapping, preview, warning review, and explicit commit steps as a file import. Only the selected range enters the import pipeline.

3. 3

   A changed sheet revision creates a new snapshot. Disconnect the source when access is no longer needed; revoked or expanded authorization fails closed and requires reconnection.

Connect a store or Store API when available

1. 1

   For a supported InSales store, an owner creates a pending connection, supplies credentials through the protected review process, and verifies the initial read-only period before any recurring import is accepted.

2. 2

   For another store or shopping cart, open Store API, create a sandbox credential first, and store the one-time secret in the sending system. Sign every bounded event batch and use stable order, line, revision, and idempotency identifiers.

3. 3

   Treat HTTP 202 as accepted for processing, not as published revenue. Check receipt status and source health, reconcile the resulting order rows with the source, then rotate or revoke credentials when ownership changes.

4. 4

   Only qualified order and financial events can enter recognized revenue. Cart and checkout events are conversion observations and never realized profit.

Build first-party cohorts when available

1. 1

   Use only seller-owned opaque customer references under an approved identity domain. Never send email addresses, phone numbers, marketplace buyer identity, or free-form personal data.

2. 2

   Register the complete source history, link eligible owned-store orders, and attribute independently supported acquisition costs. Review unmatched orders, spend, source coverage, maturity, and minimum cohort-size suppression before using CAC, LTV, or payback.

3. 3

   Use the privacy controls to export retained identity links or erase links for an opaque reference. Financial order facts remain subject to the organization's separate retention and customer-data process.

Request a grounded AI brief when available

1. 1

   Save a versioned manual scenario and select only the imported owned-order evidence and marketplace account that belong to the same workspace and period.

2. 2

   Review the evidence labels, freshness, missing-cost warnings, and source health before requesting the brief. Manual estimates, imported observations, and marketplace mart snapshots remain separate evidence bases.

3. 3

   Use the structured findings and citations to inspect the underlying scenario and source records. The brief reports the channel comparison, modeled cost structure, available CAC break-even condition, missing measurements, and a next-analysis draft from validated evidence.

4. 4

   Treat missing cohort maturity, repeat-purchase, cost, or source evidence as unavailable rather than zero. Do not treat a model selection as audited actual profit or as an autonomous pricing, tax, or channel-allocation decision.

Identity-link requests

If your workspace has a first-party identity domain, an authorized owner can export or erase the cohort identity links for a seller-owned opaque customer reference from the cohorts page. The request works for retained links even when cohort calculations are unavailable or the Channel Economics plan has ended.

The JSON download contains the stored source, order and attribution link metadata only. It does not contain the customer reference or internal pseudonym, and it is not a complete customer-data or financial-order export. Follow your organization's separate data-subject request process for other records.

Compare the channels on the same horizon

1. 1

   Use the same dates, RUB currency, recognition basis, return treatment, and fixed-cost allocation for marketplace and owned-store scenarios. Keep acquired and repeat customers separate.

2. 2

   Enter marketplace commissions and promotion costs on the marketplace side. Enter owned-store acquisition spend, payment, fulfillment, support, returns, and platform costs on the owned side. Do not subtract acquisition spend twice: if it is included in advertising, do not add it again to channel costs.

3. 3

   Change one assumption at a time: marketplace fee, owned-store conversion and acquisition cost, repeat purchases, return rate, and order migration between channels. Save versions so the baseline and alternatives remain comparable.

4. 4

   Check whether first-order contribution plus assumed repeat-order contribution covers acquisition spend within the chosen horizon. If customer count or repeat behavior is unknown, leave CAC/payback unavailable rather than assigning zero.

Interpret and recover

The calculator is a manual estimate. Imported order revenue is observed from committed files, but cost coverage and independent source reconciliation may be incomplete. Do not call a partial known-cost summary fully loaded profit.

If a total is missing, verify the period, source ID, column mapping, order status, and whether the file was committed. Corrected files retain import lineage. Confirm recognition and tax policy with your finance owner.

Original uploaded files are erased after 30 days when committed or 7 days when uncommitted. Financial rows and correction history remain; retain an independently reconciled source export under your own retention policy.

Check marketplace source health

1. 1

   From Channel Economics, open Marketplace source health. Select one connected marketplace account and the exact reporting dates, then run the check.

2. 2

   Check mart rows and days with data against the provider finance-report rows and the count linked to an archived successful provider response. A zero or incomplete count means the period needs investigation; it does not mean zero sales.

3. 3

   Review the period-mapped bank-receipt counts and every open check. A configured match or source link is not proof of an independent bank reconciliation. Correct missing source data or mapping with your finance owner, then run the check again for the same period.

4. 4

   When the workspace capability is enabled, an authorized platform finance reviewer can accept the exact account, period, evidence fingerprint, independently obtained statement checksum, reconciliation reference, difference, tolerance, and expiry. Customers cannot create or renew this qualification themselves.

5. 5

   A current accepted qualification allows that exact marketplace revenue, net profit, and bank-receipt snapshot to enter the grounded AI brief. Any evidence change, expiry, revocation, replacement, stale data, quality warning, incomplete lineage, currency mismatch, or reconciliation gap closes the path automatically.