Apply to sell in a community market
Submit one eligible market application, understand its current membership state, and take only the transition that state allows.
Trust, applicability, and sourcesMobazha v0.3 release candidate
Before you start
- Sign in as the seller responsible for the intended store and product groups.
- Open the selected market and confirm its identity, operator, seller-entry mode, seller-review mode, and catalog mode.
- Treat market membership as a discovery and curation relationship. Approval does not transfer store, listing, quote, payment, or order authority to the market.
- Continue only when the deployment exposes the market's seller page and the market allows self-service applications.
Apply to the market
- Open the market's Sell entry, normally
/marketplace/{slug}/sell. - Read the displayed seller-entry, review, buyer-access, and catalog rules before selecting products.
- For a curated catalog, select at least one product group owned by the current seller. A group may be eligible even when it currently contains zero items. An open catalog can permit submission without a selected group.
- Review the selected groups and submit once. The submit control remains visible but disabled while the request is in flight.
- Read the returned membership state. Automatic review may approve immediately; manual review normally records an applied state pending an operator decision.
- Return to the same seller page for review updates. A notification can lead to this page, but the current application and membership record determine the status.
Understand the current state
| State | What the seller can conclude | Available next action |
|---|---|---|
| No application | No current self-service application is recorded | Select required groups and submit if the market permits self-service |
applied | The application exists and is awaiting a decision | Keep selection locked; withdraw if the product offers that action |
approved | The market accepted the seller under its current policy | Inspect which groups and listings are visible; market approval does not prove order readiness |
rejected | The application was declined | Read the decision reason where provided; reapply only when the current policy exposes submission |
left | The seller withdrew or left | Reapply when the current policy permits it |
suspended | The operator has suspended participation | Do not reapply through self-service; follow the market operator's published review route |
Selections remain locked while the application is applied, approved, or suspended. This prevents a local draft from silently changing the groups attached to an active membership state.
Expected result and verification
The seller page should show one current application and membership state for the selected market and seller context. Verify the market identifier, store or seller identity, selected product-group identifiers, review mode, and current status after a refresh.
For an approved seller, separately verify that the intended groups or listings are visible in the market and that a buyer handoff still resolves to the correct seller-owned backend. Membership alone does not prove availability, price, payment readiness, or fulfillment readiness.
If something fails
- If submission is disabled in a curated market, select at least one eligible product group and verify it belongs to the current seller.
- If the market is invite-controlled, do not repeatedly submit API requests; use the operator's published admission route.
- If submission or withdrawal returns an unknown result, refresh the current application before retrying. A delayed response may already have changed membership state.
- After rejection or
left, submit a new application only when the page makes it available. A suspended seller cannot self-serve a new application. - If the notification and seller page disagree, use the refreshed membership record and report the stale notification with sanitized identifiers.