Improvement: Allow automatic approval of proposed products

[Guilherme-B]

Configurable product approval workflow for vendor-submitted products

Summary

Currently, when vendors create new products, they always require administrator approval before becoming available. While this is a sensible default for many marketplaces, it can become a significant bottleneck during vendor onboarding, especially when vendors need to import or create a large catalog of products.

In MercurJS v1, vendors could create products directly without requiring manual approval, which made the onboarding experience much smoother.

It would be great if this behavior could be made configurable through the Admin panel.

Proposed solution

Add marketplace-level configuration options such as:

• Allow vendors to create new products (On/Off)
• Require admin approval for vendor-created products (On/Off)

This would support the following workflows:

Vendor product creation	Admin approval required	Behavior
Disabled	N/A	Vendors cannot create products.
Enabled	Yes	Vendors can propose products, which require administrator approval (current behavior).
Enabled	No	Vendor-created products are automatically accepted (MercurJS v1 behavior).

Benefits

Different marketplaces have different moderation requirements.

For curated marketplaces with a relatively small number of trusted vendors, requiring approval for every new product creates unnecessary friction and significantly slows down onboarding.

For open marketplaces, the existing approval workflow remains an excellent default.

Making this configurable would allow MercurJS to support both use cases while preserving the current behavior by default.

Thanks for considering this feature!

[vholik]

There is a feature flag product_request for this: https://github.com/mercurjs/mercur/blob/main/packages/core/src/feature-flags/product-request.ts

[vholik]

Hey. You can use createProductsWorkflow productsCreated hook to update products status from proposed to published. Or you can utilize product_request feature flag and send published status in the request body.

We kept the proposed-products flow as the default because most marketplaces need some verification of master products.