Publish Your First Product

This guide takes a new store from nothing to a product in review, all in your browser. To do the same from your agent, follow Publish a Product from Your Agent.

• A product that works as described and meets the listing standards
• A way to deliver it, such as a package of up to 250 MB, a key or access link that every buyer receives, or both
• Images that show the product, as JPG or PNG files
• A Stripe account that can accept payments, which Who can sell on Kurodyne? describes

How are products delivered? explains what buyers receive.

A package is one ZIP file with the files buyers use, including readable source for any code. Check these requirements before building it:

• Keep the ZIP file within 250 MB and include up to 10,000 files and folders in total.
• Keep the extracted files within 500 MB in total.
• Keep the ratio of extracted to compressed file sizes at or below 100:1 across the package and 200:1 for each file.
• Leave the ZIP file unencrypted, with no password protection.
• Use regular files and folders with portable names. Kurodyne rejects symbolic links, paths outside the package folder, and conflicting filenames, including names that differ only in letter case. Names can't contain <, >, :, ", \, |, ?, or *, or end in a period or space. Avoid Windows device names such as CON or NUL, with or without an extension. Keep each file or folder name within 255 bytes and its full path inside the ZIP file within 1,024 bytes.
• Build the ZIP file from a plain folder with Packager or your system's compress command. ZIP files with comments aren't accepted. git archive adds a comment when archiving a commit or tag, and GitHub source ZIP downloads include one too.
• Exclude blocked file types, including executables, installers, disk images, system libraries, and Windows batch or PowerShell files. The blocked extensions are .exe, .msi, .scr, .com, .bat, .cmd, .vbs, .vbe, .wsf, .wsh, .jse, .wsc, .ps1, .psm1, .psd1, .hta, .cpl, .app, .deb, .rpm, .dmg, .pkg, .run, .apk, .ipa, .dll, .so, .dylib, .sys, .drv, .ocx, .lnk, .pif, .reg, .inf, .iso, .img, .vhd, and .vmdk. File and folder names can't end in any of these extensions. Remove blocked files, and rename or remove matching folders, such as example.com.
• Include product files. A top-level README and license or notice files alone don't satisfy the submission check.

Buyers read a root README.md or README.txt on the product page before they buy, so it can show a short excerpt of the deliverable. Keep purchase-only links, keys, codes, and passwords out of it. If the product includes third-party material, follow Third-Party Notices for Code You Sell to prepare THIRD_PARTY_NOTICES.md and the required license files.

Build the ZIP file from the package folder's contents, not the enclosing folder, so the README and notices stay at the ZIP file's top level. macOS Finder and many Linux file managers hide names that start with a period, such as .env.example or .gitignore, so selecting the visible contents leaves them out. Show hidden files before you select (in Finder, press Command-Shift-Period), then deselect or remove anything buyers shouldn't receive, such as a working .env, a .git folder, or .DS_Store files.

To use the Packager, open the folder, select the files and folders inside it, and drop those into Packager. A dropped folder becomes a folder inside the ZIP file. Check that Packager's file list matches the package folder. Name the archive and select Download.

For code products, use A README Template for Code You Sell to document requirements, setup, configuration, and updates.

For a skill package, follow How to Sell Claude Skills for a downloadable example, installation checks, and a listing that states the buyer's requirements.

Skip this step for a product that delivers only a key or access link.

Your Stripe account must be based in Canada, Hong Kong, New Zealand, Singapore, or the United States. Who can sell on Kurodyne? covers the other seller requirements.

1. Open Seller Console from the account menu.
2. Select Connect Stripe and complete Stripe's setup. Stripe returns you to the Console.

You can create a product once Stripe is connected, and submit a new product for review once your Stripe account can accept payments. Kurodyne lists an approved product in the Catalog while your Stripe account can accept payments. If Stripe needs more information, the Console's Diagnostics shows a View Stripe account button.

Select New product in the Console, or New Product on the Console's Products page. The Product Editor opens a private draft and shows the listing standards. The draft saves automatically as you work.

• Details: Add the Title, Description, Category, Product type, and Price (USD), a whole-dollar amount from $5 to $500. Under Public requirements, list the software, runtime, account, or service buyers need.
• Images: Add at least one image that shows the product. The first image is the main image.

• Files: Upload your package. The Package checklist shows what Kurodyne found, including your README and any notice files.
• Keys: To deliver a key or access link, turn on Key delivery, choose the Delivered value, enter the Key value, and describe the Access requirements shown on the product page. Every buyer receives the same value.

A product needs a package, key delivery, or both. With key delivery on, the package is optional.

Test the files, links, and keys buyers receive. If you uploaded a package, download it from the Product Editor's Files section and test that copy.

In the Product Editor's Release section, enter a Release label, such as 1.0, and the Private usage instructions buyers see only after purchase. Release notes are optional for the first release.

The Kurodyne Commercial License defines how buyers may use your product, including for personal, internal business, and commercial projects.

1. Open Review in the Product Editor and select each listed item to go to its field and fix it. The checklist keeps the last saved requirements visible while your changes save. If Stripe payments aren't active, select View Stripe account in the Review section and finish Stripe's setup.
2. When the Review section shows Ready to submit, select Submit for review. If Submit for review is unavailable, the message above it explains what to do next.
3. Select the checkbox to authorize Kurodyne to grant the license on your behalf and confirm the seller warranty in the Terms, then select Submit for review.

The Product Editor shows In review and stays locked until review finishes. On the Products page, the Review column shows In review. When review finishes, it shows the decision:

• Approved: The product is listed in the Catalog while your Stripe account can accept payments.
• Changes requested: Follow Fix a Listing That Needs Changes.
• Rejected: The decision is final. You can delete the product or create a new product to try again. The Product Editor shows its automatic deletion date.

How does listing review work? covers review and the standards it applies.

• New Product is unavailable: Your store has no connected Stripe account. Connect Stripe in the Console first.
• Stripe payments not active: A new product can be submitted once your Stripe account can accept payments. Select View Stripe account in the Console's Diagnostics and finish what Stripe asks for.
• Review limit reached: Too many of your products are in review. Wait for a review to finish, then submit.
• Unpublished product limit reached: Only products that have never been published count, including those with Draft, Changes requested, In review, or Rejected status. Delete one with Draft, Changes requested, or Rejected status, or wait for one in review to be approved. Rejected products also count until Kurodyne deletes them after the automatic deletion date.
• The package contains a blocked file type: Check both file and folder names for the extension named in the error. Remove blocked files, and rename or remove matching folders, such as example.com for .com, then rebuild and upload the package. Check the blocked extensions in Prepare Your Package before choosing what to include.
• The package is password protected: Remove password protection and encryption, rebuild the ZIP file, and upload it again.
• The package contains rejected entries: Rebuild the ZIP file from a plain folder of regular files and folders. Remove symbolic links, avoid paths outside that folder, resolve conflicting filenames, and rename files and folders that break the name rules in Prepare Your Package before uploading again.
• This package couldn't be read: Rebuild the ZIP file from the package folder with Packager or your system's compress command, then upload it again. ZIP files with comments, such as those git archive and GitHub source downloads create, aren't accepted.
• The package has too many files or folders: Remove unneeded files and folders until their total is within the 10,000 limit, then rebuild and upload the package.
• The files inside this package add up to more than the limit: Remove files until the extracted total fits the limit shown in the error, then rebuild and upload the package. The standard limit is 500 MB.
• This package expands far beyond its compressed size: Remove highly compressible files, then rebuild and upload the package. Check the compression limits in Prepare Your Package.
• The package needs product files: Add the files buyers use, then upload the package again. The top-level README and license or notice files alone don't satisfy the submission check.
• The package is blocked by security checks: Upload a replacement package. Contact Kurodyne support if you think the check is wrong.
• The package is too large: How large can a product package be? explains how to request a higher limit.

While your product is in review, choose how buyers can reach you in Settings under Buyer support, such as Kurodyne Relay or your own channels.