One Store belongs to the selected team. Start it with a name, public address, currency, and optional description. The overview then lists what remains before the Store can be public: settings, a ready payment account, products, and shipping when physical products require it.

Store settings contain the public name, address, description, contact email, currency, shipping origin country, shipping policy, and returns policy. Currency and public addresses become constrained after publication or commerce starts so historical orders and shared links remain understandable.

Team admins can review and edit the Store name, description, contact email, shipping origin, and policies in the native app. Currency and the public address remain read-only there when the Store is live. Before publication, the Store address and currency can also be changed in native. Team admins can also review and add shipping zones, publish or unpublish the Store, and review payment readiness from the native app. Starting or continuing payment setup opens Stripe-hosted onboarding; identity and payout details do not pass through Magpie.

Connect the team's existing Stripe payment account. Store uses one-time direct charges and does not apply the Supporters recurring fee. The connected seller owns the charge and remains responsible for tax, refunds, disputes, shipping, and customer support.

Publish only after testing a product, cart, eligible shipping method, and checkout. If payments later become restricted, the storefront can remain visible while checkout is unavailable.

Store has no custom theme editor. The public storefront uses Magpie's Store template. For a setup item that stays incomplete after its requirement is met, Contact support.