ForjioHuudisIdentityPlugipayPaymentsStorlaunchE-commerceFulkrumaFulfilmentRiplloMarketingLinkSnapShort URLsPawpadoGPU streaming
Storlaunch Docs
⌘K

Storefront

Plugipay family portal: storefront

The Storefront page (/dashboard/storefront) is where you configure the public-facing shop your buyers visit. A workspace can have multiple storefronts — useful for serving different brands or markets from the same back office — but most merchants run one.

This page covers configuring a single storefront: name, domain, theme, currency, policies, and the auto-generated public site.

What a storefront is

A storefront in Storlaunch is the combination of:

  • A public URL where buyers shop
  • A theme (colors, typography, layout)
  • A currency for display
  • Policies (returns, shipping, terms, privacy)
  • A linked product catalog (workspace-scoped by default; can be filtered)

The product catalog is workspace-level, not storefront-level — one product can appear on multiple storefronts. The storefront chooses which products to surface.

Identifier: store_01H….

Configuring a storefront

Name and subdomain

Two fields define the storefront's identity:

  • Store name — what buyers see in the browser tab, on receipts, in the cart, on emails. You can change this any time without breaking links.
  • Subdomain — your storefront URL on the Storlaunch platform: <subdomain>.storlaunch.forjio.com. Lowercase, alphanumeric + dashes, 3-32 characters.

Changing the subdomain creates a permanent redirect from the old one for 30 days, then the old one is freed. We do this so external links keep working through the transition.

Custom domain

Once you've moved past the subdomain, attach your own domain at Settings → Domains:

  1. Add a domain (e.g., shop.example.com).
  2. We show you a DNS record to add at your registrar.
  3. Once the record is verified, Storlaunch issues a Let's Encrypt certificate and starts serving the storefront on that hostname.

Apex domains (example.com without a subdomain) work too, but require an A record — we'll show the IP. Most merchants use a CNAME on a subdomain like shop.example.com.

Verification can take a few minutes depending on your DNS provider's propagation. We'll auto-retry every 30 seconds for an hour, then surface a "verify now" button you can click manually after fixing any record issues.

Currency

Pick the currency the storefront displays prices in. Defaults to IDR.

This is a display currency — it determines the symbol, decimal convention, and rounding. The underlying product price is stored in the same currency; Storlaunch doesn't auto-convert.

Multi-currency stores (showing the same product in IDR and USD) is on the backlog but not shipped. For now, run separate storefronts in different workspaces if you need parallel currencies.

Theme

The Theme tab lets you adjust:

  • Primary color — used on buttons, links, and accents.
  • Background and surface colors — the base palette.
  • Font — system, Inter, Roboto, or one custom Google font.
  • Logo and favicon — uploaded via the workspace's image uploader.
  • Hero layout — centered, split, or video.

Changes preview in real time in the right panel. Click Publish to push them live.

The auto-generated storefront is a Next.js app rendered on Storlaunch's infrastructure — you don't host anything. If you outgrow the theme system and want to build a fully custom storefront, see SDKs — you can render whatever you like and just consume the Storlaunch API for products, carts, and checkout.

Policies

The Policies tab has four free-text markdown fields:

  • Returns & refunds
  • Shipping policy
  • Terms of service
  • Privacy policy

Each gets a public page on the storefront and is linked from the footer and the checkout. Empty policies are hidden — we don't show empty pages.

Storefront pages

Under Pages you can add custom pages (About, Contact, FAQ) with markdown content. They appear in the storefront's navigation according to the order you set.

This is intentionally a minimal CMS — deep custom content lives better in a separate marketing site or your blog (which can live under Marketing → Blog, backed by Ripllo).

Going live

Storefronts start in draft mode: visible only to you (the merchant). The "Publish" toggle at the top of the storefront settings flips it to live.

Before publishing, check:

  • At least one product is published.
  • Payments are configured (auto-provisioned Plugipay is enough to start; you'll be in managed mode).
  • Returns and shipping policies are written if you sell physical goods.
  • A custom domain is verified (optional but recommended before pointing traffic).

What buyers see

The auto-generated storefront has six core pages:

  • Home — hero, featured products, recent products.
  • Catalog (/products) — the full catalog with filters.
  • Product detail (/products/<slug>) — full description, variants, add-to-cart.
  • Cart (/cart) — line items, totals, checkout button.
  • Checkout — powered by Plugipay's hosted checkout. The buyer leaves your domain briefly and returns after paying.
  • Order status (/orders/<id>) — post-checkout, includes the receipt, fulfilment status, and (for digital products) the download link.

Buyer-side authentication is OTP-based — see Auth → Sign in → Buyer sign-in for the flow.

Multiple storefronts

To run more than one storefront in the same workspace:

  1. Settings → Storefronts → New storefront.
  2. Pick a different subdomain.
  3. Decide whether to share the product catalog or filter it.

Common reasons to run multiple:

  • B2B vs B2C — wholesale prices on one, retail on the other.
  • Brand split — two product lines with different aesthetics.
  • Region — even when you can't multi-currency, you can run a second store with localized copy and pricing.

Orders, customers, and refunds are still workspace-scoped — the storefront is a presentation boundary, not a data boundary.

Next

  • Products — populate the catalog.
  • Orders — what happens after a buyer checks out.
  • Portal tour — back to the dashboard overview.