Operate a Vendorzo marketplace

Available in: Marketplace only.

Marketplace adds seller operations to the shared catalog and order workflows. The customer-facing product can be shared while offers, seller ownership, inventory, fulfillment, policy, and settlement responsibilities differ by workflow. Confirm the owner shown on the affected record before acting.

Find the marketplace workspace

The Sellers & Marketplace area can include:

• Sellers, Seller Types, Seller Approval Queue, and Seller SLA Queue for seller account and approval work.
• Marketplace Settings, Marketplace Campaigns, Policy Versions, and Category Access for marketplace configuration and eligibility.
• Support Cases, Seller Feedback, Commercial Profiles, and Seller Identity Changes for seller-specific follow-up.
• Digital Asset Queue, Service Booking Queue, and Purchase Orders for edition-specific service and fulfillment work.
• Privacy Requests and Legal Disclosures for requests that require the responsible privacy or legal owner.

Visible pages depend on edition and permissions. If an item is absent, confirm those prerequisites rather than changing edition flags or granting broad access.

Safe marketplace operating sequence

1. Review a seller application in the approval workflow and follow the verification process configured for the marketplace.
2. Confirm seller eligibility and category access before enabling a listing.
3. Check that the offer references the intended shared product and variant. Review seller, price, availability, commission, and fulfillment ownership before publishing.
4. Monitor order, inventory, and seller service work in the queue that owns the issue. Do not resolve a seller-owned problem by editing the shared catalog record unless that is the approved workflow.
5. Reconcile order changes, returns, commission, settlement evidence, and payout status through the configured financial controls.

Review service bookings

Use the Service Booking Queue for confirmed customer bookings. Check the service offer, customer, and scheduled slot before acting. Mark a booking complete only after the service was delivered; use No-show only after confirming the customer did not attend. These actions require the configured multi-factor authentication step-up and record a booking event. Completion can also schedule a review request, so check the communication policy for the installation. A booking status or settlement entry is not proof that a seller was paid.

Create a slot only for the intended service offer. Its start time must be in the future and within the offer's configured booking horizon. Use the configured capacity and time zone, then confirm the slot is visible before making the service available to customers. If the queue or action is missing, check the Marketplace edition and seller permissions before changing access.

Use this as an ownership check, not as a promise that every installation supports every handoff. Confirm the seller and fulfillment owner on the affected record before proceeding. An order or settlement status alone does not prove that a payout was released.

Seller identity, privacy, legal, and payout decisions can have financial or regulatory consequences. Follow the responsible owner's procedure and preserve the audit trail. This public guide does not replace the marketplace's approved policy or financial review process.

Merchant installations do not include seller operations. Marketplace is an additive edition; changing an edition setting alone does not install its package or perform a supported downgrade. Check edition selection and compatibility before an edition change.

For seller access and audit history, see Manage administrators and access. For an uncertain order or provider result, use Troubleshooting and reconcile with the provider before retrying a financial action.