SSpark ERP

Marketplace

A marketplace for what developers build on Spark ERP.

The registry mechanism (`erp registry publish` / `erp registry install`) is real and already used by the CLI. A public catalog of third-party listings has not launched yet — this page shows the shape the marketplace will take, honestly marked as pre-launch rather than filled with invented listings.

Pre-launch

There is no public catalog to browse yet. What is real today: any tenant can publish a package to its own registry and install it (`erp registry publish`, `erp registry install`, `erp registry list`, `erp registry mine`) — the publishing pipeline below is not a mockup, it is the real flow that mechanism runs through.

Categories

What a listing will show

Every published item — once the public catalog is live — will carry the same fields, so comparing two listings is always apples to apples.

Name & Developer

Who published it, and under what name.

Category & Compatibility

Which marketplace category, and which platform/module versions it works with.

Version

Semantic version, with a changelog per release.

Screenshots

What it actually looks like installed, before you install it.

Features

What it does, in plain language.

Pricing

Free, one-time or subscription — stated up front.

Reviews

Verified-installer reviews only, once there is real installer traffic to review.

Security

What the security review checked before publish.

Install

One action, from a tenant's own admin console, via `erp registry install`.

Example listing shape (illustrative — not a real published package)

Example: India Payroll Pack

Country Pack · HCM · India

v1.0.0 (illustrative)

  • PF
  • ESI
  • Professional Tax
  • TDS
  • Statutory Reports

Shown to illustrate the card shape only — this is not an installable package today.

Developer publishing flow

From a developer account to a published, security-reviewed listing.

  1. Create Developer Account
  2. Create Application
  3. Build
  4. Test
  5. Submit
  6. Security Review
  7. Publish
erp registry publish <packageId> <version> --type plugin \
  --name "My Package" --author "Your Org" --license MIT

Build something worth publishing.

Start with the CLI and the docs — the registry commands are ready whenever your package is.

Developer HomeCLI Reference