Navigation

Getting Started

IntroductionQuick Start

Business Setup

What's Business?Launch a BusinessWebApp DeploymentUpdates and ModulesCustom DomainCredits & Top-upsAI AgentPromoteTeamSettingsApp Terms

Money

MoneyDashNex CreditsDashNex MoRStripe StandardFind Your OrdersTransactionsBalancesPayoutsConversionTransfers

WebApp Modules

OverviewProductsOffersCheckoutsCouponsEmbeddable CheckoutLifecycle EventsDunningPayment MethodsContactsOpt-in FormsEmail BroadcastsEmail LibraryAutomationsTransactionalInboxPages ManagerMenu ControllerMedia LibraryinstraCHATAppearanceAgent SettingsAgent SourcesAgent Q&AConversationsMCPOAuth2 ServerUpcoming Modules

Developers

Developers programReserve a module nameGet startedSubmit for reviewPublish your listingSales, fees and refundsDev moduleDashNex CLIDashNex Code
Developers

Submit for review

Submit a version with dashnex module submit, what In review means, how to fix a rejected version and resubmit it, and how approved new versions are released automatically.

Submitting a version

Run this in your app folder:

dashnex module submit [name]

The command checks packages/[name], builds the module and submits it for review. The module's status becomes In review.

The version must be higher than the last one you submitted. If it isn't, you see:

Bump the version (run pnpm version patch in packages/[name]) and submit again.

Submitting a version stops the reservation clock for good, so review time and rejections never expire your name. See Reserve a module name.

In review

The module page shows the submitted version and its date. There is nothing to do while you wait.

If the module already has a live version, it stays on sale during the review. The module page shows Live · v1.0.1 and v1.1.0 In review.

Rejected

The module page shows "Version 1.0.0 was rejected" and the way to resubmit, as numbered steps:

  1. Fix the issues. The reviewer's issues are shown in full right under the step. Use Copy to paste them into an AI agent.
  2. In the module directory, run pnpm version patch.
  3. Run dashnex module submit [name].

The issues are shown only for the current rejection. They disappear once you submit a newer version.

A rejected newer version never affects the live one: the live version keeps selling, and the page shows v1.1.0 Rejected next to it.

Approved

When DashNex approves the first version, the module shows Approved · v1.0.0 and the Publish panel opens. Complete it in Publish your listing.

New versions

Bump the version and run dashnex module submit [name]. A new version goes through the same review as the first.

When it is approved, it is released automatically. There is no second Publish, and your pricing, support, documentation and sales page settings carry over.

  • New installs always get the latest approved version.
  • Existing installs get it as an update: the module card in their App shows Update vX, and they apply it with an app redeploy.

Activity

After the first submission, every module page has an Activity table with the columns Date, Activity and Details. It keeps one permanent record per event:

  • Each submission and its result, for example "2 issues reported".
  • Publish and unpublish.
  • Every listing change.

Records stay for reference. The issues themselves are not stored in Activity; see Rejected.

Related guides