Skip to main content

Reading the Current Seller Workbench

The current Partner Portal is an operations workbench, not a complete analytics suite. Read each number according to its source and do not turn an empty, unavailable, or estimated field into a business conclusion.

Start with Seller Readiness

Seller Readiness is the authoritative pre-order checklist. It combines:

  • business profile and operator verification;
  • Stripe payout setup and seller agreement acceptance;
  • shipping profile/rule setup;
  • first submitted and approved listing;
  • approved stock that can route to fulfilment.

Work the first incomplete seller-owned step. An operator-owned review state is a queue, not a signal to resubmit repeatedly.

Dashboard

Use the home dashboard for current action queues and seller-scoped operational summaries. Treat a card according to its state:

StateInterpretation
Value with a timestamp/sourceA current snapshot under the displayed contract.
Zero with a known sourceA valid zero for that period.
Empty or “not computed”No usable snapshot yet; it does not prove zero demand or zero risk.
UnavailableThe required source or semantic contract is not active. Do not estimate it from another card.
Suggested actionA navigation aid. Confirm the underlying record before acting.

Listings

This is the current source for listing status, stock, curation feedback, and listing readiness. Prioritise Needs Action in this order: rejected or changes requested, out of stock, incomplete, draft, low-score, then low stock.

A listing-readiness score helps find incomplete product data. It is not a search rank, conversion forecast, or external market benchmark. Any competitor Pricing Signal is non-operational until the source-backed pricing contract is activated; see Pricing Intelligence.

Orders

The current page is the Tracking workbench. It supports per-line accept/reject, seller dispatch, eligible labels, and a tracking timeline. It does not expose the older multi-tab returns, disputes, analytics, BOPIS, or communication dashboards.

Read status as workflow state, not financial settlement. A delivered order still has a separate eligibility, policy, approval, and payout record path. See Order Management.

Shipping

Current shipping summaries are based mainly on stored labels and their costs. Total shipments or average label cost can be meaningful when rows exist. Carrier-grade on-time, delay, and delivered-performance cards may be unavailable until event history and promised-delivery truth are present.

Seller dispatch SLA currently measures acceptance to shipping-label purchase. It does not measure carrier transit time. See Shipping Setup.

Financial Records

Use Financial Records for seller-scoped transactions, fees, settlement records, tax views, and exports that the portal exposes. Keep these concepts separate:

  • customer payment capture;
  • seller earnings/liability;
  • payout eligibility;
  • approved Stripe transfer;
  • bank arrival.

A recurring calculation is not the same as a guaranteed bank payout cadence. Your applicable agreement and portal records, not an old dashboard example, control. See Payment Processing.

Ratings and private feedback

The current shopper contract shows a rating and count only when eligible verified-purchase customer ratings exist. Editorial or mixed scores, review text, and seller replies are not public. Review data visible to a seller is an operational signal; do not promise that a response or template will publish. See Ratings and Customer Feedback.

Deferred analytics

Dedicated Analytics, Performance, Inventory Forecasting, Pricing, Quality, Search Insights, review analytics, campaign, and marketplace-intelligence portal routes are not currently supported portal workflows. If cached reporting is enabled later, an empty result means “no usable computed snapshot”, not “the measured value is zero”.

Daily operating rhythm

  1. Clear order lines needing action.
  2. Resolve product curation, completeness, and stock blockers.
  3. Confirm shipping rules and failed/partial label batches.
  4. Read messages, returns, or disputes through their actual available paths.
  5. Reconcile Financial Records; escalate unexplained differences before changing a payout or accounting assumption.