Docs/sell
Reviewed 2026-07-14
Markdown
BetaBuy & sell · Guide

Start and operate a Mobazha store

Prepare a store that a buyer can understand, pay, and receive from through one tested journey.

Prepare your storeEstimated time6 minutes
Trust, applicability, and sourcesMobazha v0.3 release candidate

Start with the store journey

The objects a Mobazha seller operates

ObjectSeller responsibilityProduct boundary
Store / NodeIdentity, policy, capabilities, orders, and business-state authorityThis is not merely a visual storefront or a channel account.
StorefrontBrand, navigation, presentation, domain, and audience viewSeveral storefront or channel views may reuse store-owned commerce state where supported.
Listing revisionBuyer-visible promise: product shape, options, price, media, terms, and fulfillment eligibilityA later revision must not silently change an accepted quote or order.
Supply and availabilityWhether a purchasable combination can actually be fulfilledInventory, provider supply, service capacity, and option labels are separate facts.
Collection and discountMerchandising and price adjustment rulesThey organize or transform an offer; they do not own order state.
Shipping profileDestination eligibility, service, rate, estimate, and evidence requirementsA listing is not purchasable for a destination until a valid fulfillment path exists.
Payment capabilityA backend-advertised and operator-ready payment pathA parsed Token or provider name alone is not readiness.
OrderAccepted terms, payment state, fulfillment obligation, recovery, and completionThe backend remains authoritative even when the order is presented in another channel.

Before opening a store

  • Choose self-hosted operation or an optional managed service.
  • Configure payment methods supported by your backend and region.
  • Publish delivery, return, refund, and dispute terms that buyers can inspect.
  • Review the final quote and all recipient amounts before accepting an order.

What Mobazha does not decide for you

A seller remains responsible for product legality, tax, fulfillment, customer support, and any seller-defined charges. Mobazha provides commerce software and verifiable transaction flows; it does not make every operator one legal entity.

Store readiness checklist

  • Set a recognizable store identity, operator contact path, locale, currency display, and domain where applicable.
  • Create complete listings with accurate variants, inventory or availability, media, price, and shipping eligibility.
  • Configure shipping profiles, delivery estimates, return conditions, and fulfillment evidence before accepting orders.
  • Enable only payment methods that the backend advertises and that the store is operationally ready to monitor and settle.
  • Test the full buyer journey on the same deployment, capability set, and device classes customers will use.

Order operations

  • Review the order, quote, payment state, buyer instructions, and fulfillment obligation before confirming.
  • Do not infer payment completion from a screenshot, message, or Agent statement; use the backend's verified payment state.
  • Record shipment or delivery evidence using the order flow rather than relying on an external chat alone.
  • Handle cancellation, refund, dispute, and completion through the allowed state transition for the current order.
  • Retain policy, quote, payment, fulfillment, and communication references needed for support or dispute review.

Choose how to operate