Listing a Software
Product on Space App
Space App is a license-based / downloadable software marketplace. Every software product must be:
- Fixed price
- Paid before access
- Delivered digitally
- Instantly delivered via one downloadable artifact
Space App - Software handling
If your product can’t be paid for instantly and delivered through a downloadable artifact, it doesn’t belong on Space App for now.
Space App - Software handling
1) What you need before you list
Required info
- Product name
- Software category
- Price
- At least 1 preview image (recommended: 3–6)
- Product summary
- Product description (how it works + how to activate)
- Exactly one “Software File” (your delivery artifact) (.zip or .exe files)
Space App - Software handling
If applicable (recommended)
- Version number
- Seats / quantity (if you’re selling limited licenses)
- Platform support (Windows / macOS / Linux)
- License delivery method (see below)
2) The most important rule: your “Software File” is the
delivery artifact
Your uploaded file is the delivery artifact. It may be:
- The actual installer, or
- A license/activation file, or
- A “GET_STARTED” instructions file (recommended for SaaS / external activation)
Enforcement rules
- Exactly one file per product
- Must be downloadable
- Must not expire
- Must not require authentication outside Space App to obtain the file
Space App - Software handling
3) Allowed delivery artifact types (choose one approach)
A) Installer / Executable (best for downloadable apps)
Use when the software is directly downloadable.
Examples:
- .exe, .dmg, .pkg
- .zip (installer inside)
Space App - Software handling
Recommended ZIP layout
YourProduct_v1.0.0.zip /installer/YourProduct_Setup.exe (or .dmg) GET_STARTED.pdf/readme file LICENSE.txt VERSION.txt
B) License / Activation file (best for license-key products)
Use when the buyer receives a key or activation credential.
Examples:
- LICENSE_KEY.txt
- ACTIVATION_STEPS.pdf
- .zip with a key + README
Space App - Software handling
Example ZIP layout
YourProduct_License_Packet.zip LICENSE_KEY.txt GET_STARTED.pdf LICENSE.txt
C) Instructions placeholder (recommended default for SaaS / externally hosted
tools)
Use when access is provisioned externally (e.g., your website/app store/account activation).
Examples:
- README.txt
- GET_STARTED.pdf
Space App - Software handling
Must include
- Activation URL
- Buyer steps
- Where the license is shown (Order Details vs inside file)
- Support contact
4) Platform handling (Windows vs macOS) without
confusing buyers
Space App supports one file per product , so you have two valid options:
Option 1 (recommended): One product includes both platforms
Upload one ZIP containing both installers + a GET_STARTED file.
YourProduct_Win_Mac.zip /windows/YourProduct_Setup.exe /mac/YourProduct.dmg GET_STARTED.pdf LICENSE.txt
Product summary page must say clearly: “Includes Windows + macOS.”
Option 2: Separate products per platform
Create:
- “YourProduct (Windows)”
- “YourProduct (macOS)”
This avoids huge downloads and keeps support clean—just don’t hide the OS in the description. Either way, each product still has exactly one file.
Space App - Software handling
5) Pricing rules (strict)
Space App supports one pricing model :
- Fixed price
- Price must be > 0
Space App - Software handling
Not supported:
- Free ($0) software listings
- Custom pricing
- Negotiation
- Subscription renewals / enforcement
Space App - Software handling
6) License delivery methods (choose one)
Space App supports these delivery patterns:
• LICENSE_KEY
• ACCOUNT_ACTIVATION
• EXTERNAL_ACTIVATION_LINK
How it should appear to the buyer
- If license key exists → show in Order Details (and/or inside the file)
- If instructions exist → show + allow file download
- If external link exists → show link + file download
Space App - Software handling
Space App does not validate licenses. That’s the seller’s responsibility.
Space App - Software handling
7) Refund expectations (be transparent)
Refund rule is enforced at the order level:
- ❌ If the file is downloaded or the license is revealed → no refund
- ✅ If delivery is not completed → refund allowed
Space App - Software handling
Seller best practice: Put this plainly in your description so buyers don’t feel surprised.
8) Step-by-step: Create a software product (recommended
flow)
Your docs already define that software listings require product name, software category, version/license info, quantity/seats (if applicable), and media/files.
Use this workflow:
Step 1 — Basic Info
-
Product Name
-
Category: Software
-
Short Summary (1 line)
Step 2 — Pricing
- Fixed Price (> 0)
- Currency
Step 3 — Media & Files
- Upload screenshots (min 1, recommended 3–6)
- Upload 1 delivery artifact file (installer / license packet / instructions)
Step 4 — Details
- Platforms supported (Windows/macOS/Linux)
- Version
- License delivery method
- Activation steps (short)
Step 5 — Review
- Confirm the buyer can complete install/activation without contacting you
- Confirm the file is accessible and does not expire
Space App - Software handling
9) Do’s and Don’ts (to avoid rejection)
✅ Do
- Explain clearly what the buyer receives after payment (installer vs key vs activation link)
- Include a GET_STARTED file inside the ZIP for clarity
- State platforms supported + system requirements
- Make activation steps simple and explicit
❌ Don’t
- Don’t require negotiation or “message seller for access” (not supported)
Space App - Software handling
-
Don’t upload multiple separate files (one-file rule)
-
Don’t use expiring links or access that disappears
-
Don’t list software you don’t have legal rights to sell (you’re responsible for resale rights)
Space App - Software handling
10) Example “high-trust” software listing
Title: “InvoicePro Desktop — Windows + macOS Bundle” Price: $29. Platforms: Windows 10/11, macOS 12+ Delivery: Instant Download (1 ZIP) Includes: Installer(s) + GET_STARTED.pdf + LICENSE.txt Activation: License key shown in Order Details + inside ZIP