ProfitVena Frequently Asked Questions

ProfitVena is an analytics and operations platform for marketplace sellers. It combines sales, returns, commissions, logistics, advertising, cost of goods, and stock to explain profit and unit economics by SKU, period, and source. See the product map and from marketplace report to real profit.

Brand owners, finance and commercial leaders, marketplace managers, analysts, and agencies. It is most useful when data is split across seller accounts and spreadsheets and the team needs one reviewable calculation.

A dashboard displays metrics. ProfitVena connects a metric to its source, period, SKU, seller account, legal entity, warehouse, and calculation policy. Profit Engine, Product 360, reports, access control, and AI explanations work on top of that context.

Wildberries, Ozon, and Yandex Market are live read-only API connections for Russian seller accounts. Yandex Market covers store identity, catalog mappings, prices, stock and turnover, and detailed orders. Other providers use file import unless their API tab is marked live. See Marketplace connections, the Yandex Market API reference, and integrations.

ProfitVena currently serves customers in Russia, and the application language is Russian. Public Help, Wiki, and this FAQ are also available in English. Commercial availability, payments, data storage, and support for another country must be confirmed before purchase.

Use the demo experience or request a guided demonstration. The demo uses synthetic data, so confirm the available datasets and reports for your marketplace and account type before purchasing.

Create a workspace, assign roles, connect Wildberries or Ozon, or prepare an Excel/CSV import, enter cost data, and reconcile the first profit calculation. Start with a short period and a few SKUs. Follow the Getting started guide.

Typical sources include sales, orders, returns, payouts, commissions, logistics, advertising, products, stock, purchases, and cost of goods. The available set depends on the marketplace, seller-account permissions, and plan. See Imports, refresh, and freshness and the marketplace data lifecycle.

No password should be sent by email, support chat, or spreadsheet. Use only the supported connection flow and the minimum API permissions. Credentials should remain in protected server-side storage, not in the browser. See Marketplace connections and security boundaries.

Freshness depends on the marketplace API, report type, source limits, import schedule, and processing state. Check the last-updated timestamp and covered period before acting. Treat a metric with no freshness indicator as potentially incomplete. See Imports, refresh, and freshness and freshness, completeness, and quality.

Compare period, timezone, currency, order status, sale and payout dates, returns, tax, commissions, logistics, advertising, and cost of goods. Then inspect freshness and the source report. Use the data-quality guide and how to investigate two reports with different profit.

Yes. The workspace model supports users, groups, roles, seller accounts, legal entities, branches, and warehouses. Server-side scope and plan limits determine which combined views each user can access. See Workspace and team and workspace boundaries.

Yes. Excel/CSV can be a controlled source. Validate the template, dates, currency, product identifiers, and duplicates. A manual file must retain provenance and pass quality checks; upload alone does not make it authoritative. See Imports, refresh, and freshness and the import lifecycle.

Profit Engine starts with revenue and includes available returns, compensation, commissions, logistics, advertising, cost of goods, tax, and configured expenses. The result is only as complete as the connected and correctly classified data. See Profit Engine and the profit model.

It measures what one sale of a specific product earns after variable costs. This makes it possible to compare products by margin and net profit rather than revenue alone. See Unit economics and what one SKU sale earns.

Product 360 brings together a product’s sales, price, discount, stock, returns, rating, content, and warnings. It is a diagnostic view, not a new data source; completeness depends on connected reports. See the Product 360 guide.

The model supports returns, compensation, commissions, and deductions. A late event can change a previously closed period, so calculations need versioning and reconciliation.

Yes, when ad spend and sales are correctly linked to the period and SKU. More orders do not necessarily mean more profit; compare ad spend, contribution margin, returns, and organic movement.

ProfitVena can show available stock, sales velocity, and stockout signals. Replenishment recommendations still require human review of lead times, seasonality, minimum quantities, warehouse constraints, and source-data quality. See Inventory and replenishment.

Forecast and scenario availability depends on the plan and data coverage. Treat every forecast as decision support rather than a guarantee: review its calculation date, horizon, confidence, source coverage, and measured error before acting. See Forecasts and scenarios, the forecast and recommendation model, and forecasting without magic.

Use Wildberries tariff analysis only when ProfitVena displays the source, version, and freshness of the applicable tariff data. If no current version is shown, verify the fee directly with Wildberries before making a pricing or margin decision. See Wildberries fees and tariffs.

ProfitVena supports saved reports, exports, schedules, and delivery flows according to the selected plan. Test a scheduled report and its delivery channel before relying on it for a critical process. See Reports, exports, and schedules and the report lifecycle.

Yes. In Channel Economics, enter revenue, orders, and costs for the marketplace and your owned store. The calculator shows contribution and profit after allocated fixed costs for each channel and their sum. This is a scenario based on your assumptions, not a verified forecast or a guarantee of advantage. See the guide and method.

Yes. Order and cost imports accept CSV, TSV, and Excel .xlsx files: map fields, inspect the preview, then confirm. Imported observations are shown separately and do not replace manual scenario assumptions. Check cost and return coverage against the sources. See the owned-store import guide.

The calculator can model acquisition from entered assumptions, but adding the two channels does not estimate customers moving between them. First-party cohorts can measure repeat behavior only in workspaces with an approved identity domain, privacy controls, complete source history, and the capability enabled. Missing maturity or customer links remain unavailable. See customer cohorts and the customer-economics method.

The connectors are implemented as separate workspace-controlled capabilities. Where enabled, Google Sheets creates read-only revisioned snapshots, InSales uses reviewed read-only credentials, and Store API accepts signed versioned events. Each source still requires mapping, review, and reconciliation before financial publication. If the control is absent, use an accepted CSV or Excel export. See connected channel sources.

CAC divides attributable acquisition spend by acquired customers; contribution LTV uses cohort contribution per customer; payback is the first period where cumulative contribution reaches CAC. Missing denominators, spend, identity links, or cohort maturity produce unavailable values rather than zero. See CAC, cohorts, LTV, and payback.

No. Cart and checkout events describe the funnel. Recognized revenue requires qualified order and financial events under the configured status and recognition policy; contribution also requires supported costs. An accepted API batch is not automatically a published financial result. See Store API events and revenue recognition.

When included in the plan, ProfitVena AI can answer questions about profit, stock, products, and marketplace changes, prepare briefings, and connect a conclusion to a metric, period, and source. Results depend on the data available in the workspace and never enable autonomous account changes. See the ProfitVena Intelligence guide and AI that can be trusted in seller analytics.

Yasnora provides the managed AI layer used by ProfitVena. Start uses limited Yasnora usage and functions; Growth uses the full supported Yasnora feature set; Business uses hybrid routing, keeping routine work on Yasnora and sending selected advanced intents to YandexGPT. ProfitVena checks access, workspace scope, quotas, permitted context, and evidence before every route. See ProfitVena AI and Yasnora architecture.

No. AI is enabled automatically for an active or trialing subscription when the selected plan includes it. Cancellation, expiry, overdue status, or a subscription pause removes or suspends access. Temporary unavailability can occur when the quota is exhausted, required data is missing, or the AI service is unavailable.

An answer should use permitted ProfitVena evidence and identify source, period, currency, freshness, and confidence. Missing or stale evidence must be disclosed rather than invented, and the user should be able to open the source report. See AI evidence and confidence and the AI evidence model.

Yes. Incomplete data, wrong cost inputs, provider delays, ambiguous questions, or model generation can produce an error. Review source reports before changing prices, budgets, replenishment, assortment, or financial plans. See AI evidence and confidence.

No. ProfitVena AI provides analysis, recommendations, and alerts; it does not make autonomous changes to marketplace accounts. Any sensitive action must show a preview and require explicit user confirmation. See Recommendations and alerts, AI governance, and controlled actions.

Data processing follows the applicable ProfitVena policy and customer contract. ProfitVena sends only the context permitted for the requested function. Customers with additional compliance requirements can request written details about processing services, purpose, retention, deletion, and model-training restrictions. See Privacy and data security.

Current plans, prices, and limits come from ProfitVena’s managed catalog. Plans may differ in users, seller accounts, SKUs, reporting, AI credits, support, and other entitlements. See Plans, trial, and billing, plans and entitlements, and the current pricing page.

A trial is offered only for plans marked as trial-eligible in the current catalog. Its duration, limits, payment-method requirement, and end-of-trial behavior are shown immediately before activation and take priority. See Plans, trial, and billing.

They come from a managed, versioned catalog and may vary by plan version or billing period. The pricing page and in-product subscription screen are authoritative.

ProfitVena uses YooKassa for payment processing. Paid access activates after payment is confirmed. Never send a card number, CVC, bank password, or SMS code to support.

Cancellation and refund handling follows the terms shown at checkout, applicable law, and service status. Use the official support channel with the order reference, never full card details.

One AI credit equals one successful request. The monthly allowance is shared across subscription workspaces and resets on the first day of each month (UTC). Failed or refused requests are not charged. Other quotas cover users, seller accounts, SKUs, refreshes, exports and schedules. See plans and entitlements.

ProfitVena currently serves customers in Russia. Customer and marketplace data is stored and processed in Russia. Specific retention periods, processing services, and contractual requirements are confirmed during onboarding. See Privacy and data security, security boundaries, and the security page.

Access is scoped by organization, workspace, role, permission, and data boundary. Server-side checks apply to analytics, reports, and AI context. Teams should still review members and revoke unused sessions regularly. See Roles and access control and the identity and access model.

Available controls include password protection, separate sessions, device lists, login history, security events, password change, and sign-out-all. MFA/WebAuthn is not currently listed as a generally available customer feature. See Account and security.

Use the official connection flow, grant minimum permissions, and revoke unused access. Credentials should remain outside the browser and must not appear in logs or staff-facing screens. Rotate the marketplace key immediately after suspected exposure. See Marketplace connections.

ProfitVena provides API documentation, exports, events, and integration capabilities. Public API access and quotas depend on the plan. Availability of a specific BI or ERP connector is confirmed before connection. See Integrations and API.

Use the Support tickets guide and the shared ProfitVena support center. For telephone contact, call +7 (495) 133-86-88. Include workspace, period, marketplace, SKU or report, error time, and a safe request ID. Never attach passwords, API keys, complete personal-data exports, or payment credentials.

Provide the report name, period and timezone, marketplace and seller account, SKU, expected and actual value, last refresh time, a redacted screenshot, and request ID. Remove marketplace tokens and unnecessary buyer personal data. See Troubleshooting and the error model.