ResellPortal Docs
Back to Software Usage
Docs » Software Usage » Storefront (Client Self-Service) Flow

Storefront (Client Self-Service) Flow

Last updated Apr 25, 2026

The other way the white-labeled plugin gets generated is when a client buys it directly from your storefront. The client picks their own branding during checkout — you don't have to be involved. This is the workflow most resellers prefer because it scales without per-client effort.

What the client experiences

  1. Client visits your storefront and clicks WordPress Plugin Installer Pack (or whatever you've named it on your storefront)
  2. They pick a billing cycle
  3. The checkout form asks them to enter:
    • Plugin Name — what their plugin will be called
    • Description — short summary of what it does
    • Author Name — the brand the plugin appears to come from
    • Logo URL — link to their logo
    • Their domain — the WordPress site the plugin will install on
  4. They pay (Stripe Connect, PayPal, etc. — based on what you have configured)
  5. The system generates the plugin and emails the ZIP to the client
  6. You receive a copy of the same email for your records

What you set up first

For the storefront flow to work, you need:

  • WordPress Plugin Installer Pack enabled in your storefront — go to Whitelabel Settings → Storefront and ensure it's toggled visible
  • A retail price set for each billing cycle — Monthly/Quarterly/Bi-Annual/Annual
  • A payment method connected — Stripe Connect (recommended) or manual payment options for the client to use
  • Your branded email configured — so the plugin delivery email comes from your domain, not appserviceportal.com

What happens behind the scenes

  1. Client submits the order — payment is processed through Stripe Connect (or whichever method)
  2. The system validates the form fields (the URL is reachable, the domain is valid)
  3. Wholesale is deducted from your wallet
  4. Build job is queued; finishes within 5–15 minutes
  5. Email goes out to the client with the ZIP attached
  6. Same email is BCC'd to you for records

If a build fails

Common reasons:

  • Logo URL doesn't load — the build aborts and the client gets an error email asking them to provide a different URL
  • Domain is malformed — same; client is asked to correct
  • Wallet runs out mid-build — extremely rare, but possible. Top up immediately, then open a ticket and the team will manually retrigger.

The client's payment is held until the build completes — if the build can't complete after multiple retries, the payment is automatically refunded.

Tips for the storefront flow

  • Add example values to the form — clients often submit "Logo URL: my-logo" instead of a real URL. Set placeholder text and add a tip in your storefront copy.
  • Include a "we'll send install instructions after" line on your storefront — manages expectations. Then actually send your own install email after the system's plugin email.
  • Test the flow yourself first — buy your own plugin with a different email to see the full client experience end-to-end.
  • Bundle with hosting — selling "Hosting + Plugin Pack" as a single package converts better than selling them separately, since the client sees the value of having a fully managed WordPress site.