Seller Management

Marketplace Seller Management

A marketplace grows on its number of active sellers, not its number of sellers. A seller who registers and never adds a product adds nothing. That is why seller management is not a registration form but the design of a life cycle stretching from application to continuity.

The path tracked from application to first sale
6-step onboardingThe path tracked from application to first sale
Sellers grant limited access to their own team
Role-based permissionsSellers grant limited access to their own team
Dispatch speed, cancellations and complaints are tracked
Performance scoreDispatch speed, cancellations and complaints are tracked
Commission and limits change with the tier
Tier systemCommission and limits change with the tier

What Is Seller Management Really About?

A marketplace grows on its number of active sellers, not its number of sellers. A seller who registers and never adds a product, or who disappears after the first order, adds nothing. That is why seller management is not a matter of a registration form but the design of a life cycle stretching from application to first sale and on to continuity.

The first critical point in that cycle is onboarding. The more documents you ask a seller for, the more trust you gain and the lower your completion rate falls; the balance between the two has to be struck per seller type. For an individual seller, identity and contact verification is usually enough, while a business seller is asked for a tax certificate, signature circular and sub-merchant registration. Asking both the same form wears out both sides.

The second critical point is measurement. What matters is not how many products a seller has added but how long they take to dispatch, how many orders they cancel and how many complaints they receive. Once these indicators become a performance score you can write automatic rules: if the score drops, lower their listing priority; below a certain threshold, stop them taking new orders. In PazaryeriSoft these rules are defined from the workflow editor.

The four things that shape the cycle

  • Document balance

    More documents raise trust but lower the application completion rate; it should be split by seller type.

  • The right metric

    Dispatch speed, cancellation rate and complaint count should be measured, not product count.

  • Tier incentives

    Good performance sticks when it is rewarded with a commission discount and visibility.

  • Automatic intervention

    A warning, restriction or suspension is applied automatically by workflow when a seller falls below a threshold.

Onboarding

Six Steps From Application to First Sale

The drop-off at each step is measurable; the step that loses the most is usually document upload.

  1. The application form is filled in

    The seller type is chosen and the fields for that type open up. An individual seller is asked for basic details and contact verification, a business seller for company details and tax registration.

  2. Documents are uploaded and reviewed

    Documents such as the tax certificate, signature circular and trade registry record are uploaded. The review happens in the application queue in the admin panel; the seller is notified about any missing document.

  3. A payment account is set up

    The sub-merchant record is opened at the payment institution and its approval status is tracked in the seller panel. No payout can be made until this step is complete.

  4. The store is set up

    Store name, logo, description, and return and shipping policies are entered. The store page is published on its own URL and opened to search engines.

  5. The first products are added

    One by one, or in bulk via XML/Excel. Category-specific field templates make sure the right data is collected on the very first product; products pass through moderation.

  6. The seller goes live

    Once approval is complete, the store and its products become visible. Order notifications, the shipping flow and the earnings screen open up in the seller panel.

Division of Powers

What the Seller Does Themselves and What the Administrator Controls

When this split is clear the support load falls; the seller does not have to call you for every small thing.

What the seller can do in their own panel

  • Adding and editing products, bulk import and stock updates
  • Tracking orders, generating shipping labels and managing return requests
  • Answering buyer messages and product questions
  • The commission breakdown, earnings and withdrawal request screen
  • Buying campaigns, coupons and promotion packages
  • Store settings, holiday mode and defining a shipping policy
  • Defining role-based authorised users for their own team

What the platform administrator controls

  • The application queue, document review and the approve/reject flow
  • Assigning seller type, tier and commission agreement
  • Product moderation and publication rules
  • Performance score thresholds and automatic intervention rules
  • Complaint, ticket and dispute management
  • Suspension, restriction and account closure
  • Per-seller revenue, commission and earnings reports
Modules

Modules That Come Ready in Seller Management

Application and Approval Flow

A form that changes by seller type, document upload and multi-step approval. On a rejected application the reason is passed back to the seller.

Organisation Hierarchy

Branch, dealer or agent accounts can be defined under a parent company; reporting is available separately at every level.

Role and Permission Management

The seller grants limited permissions to their own team: roles that only see orders, only add products, or can reach the finance screen.

Performance Score

Dispatch time, cancellation rate, return rate, complaint count and average rating are turned into a single score.

Seller Tiers

The tier determines the commission rate, the earnings waiting period, transaction limits and badges. Transitions can be automated.

Automatic Warning and Suspension Rules

Thresholds set up with workflows: a warning if the score drops, a new-order restriction or suspension below the threshold.

Seller Notifications

Instant notifications for new orders, messages, low stock, an approaching dispatch deadline and earnings payouts.

Store Page and Showcase

A store page published on its own URL; featured products, the store rating and the return policy are visible.

Seller Reports

Revenue, commission, earnings, product performance and period-on-period comparison. A separate view on both the seller and administrator sides.

FAQ

Frequently Asked Questions

The questions asked most often about seller management design.

This is a question of balance: the more documents you ask for, the more trust you gain and the lower your application completion rate falls. That is why it should be split by seller type. Identity and contact verification is usually enough for an individual seller; a business seller is asked for a tax certificate, signature circular and trade registry record. You define from the admin panel which document is mandatory for which type, and the seller is notified automatically about anything missing.
Yes, role-based authorisation works at seller level too. The seller can define limited roles for their team: a warehouse operative who only sees orders, a content manager who only adds products, or an accountant who can reach the finance screen. Growing sellers therefore do not have to share a single account, and who did what is visible in the audit trail.
Instead of metrics that look good but do nothing, such as product count, it uses indicators that directly affect the experience: dispatch time, order cancellation rate, return rate, complaint count and average buyer rating. These indicators are weighted and turned into a single performance score. You decide how the score is calculated and where the thresholds sit.
Yes, by writing rules in the workflow editor. The typical design is graduated: when the score falls below a certain threshold a warning notification goes to the seller, if the decline continues their listing priority is reduced, and at a critical threshold they are closed to new orders or the account is suspended. You define the threshold and waiting period for each step; interventions are recorded in the audit trail.
Tiers keep sellers on the platform because they turn performance into a concrete advantage. Each tier can carry a different commission rate, a different earnings waiting period, a different transaction limit and a badge. A new seller is given a long wait and a narrow limit; a seller with a clean history gets the reverse. Tier transitions can be automated against the performance score.
Yes, the organisation hierarchy supports it. The parent company sits on top and branch or dealer accounts attach to it; sales and earnings reports can be taken at both sub-account and parent level. This structure is used in scenarios such as chain stores, estate agencies and producer cooperatives.

Let's Plan Your Seller Design Together

Let's work out your onboarding steps, your document requirements and your performance thresholds.

Setup support · Role-based authorisation · 24/7 support