Package products for delivery

Packaging decides how buyers receive a product. Ordinary file products deliver as downloads. Sulu Market processes and validates the two Blender-native kinds so they flow straight into buyers' Blender installations: extensions through the extensions repository, assets through the online asset library. This page is the packaging contract for both.

Blender extensions

Upload a standard Blender extension archive: the ZIP from Blender's extension tooling (for example blender --command extension build in your source directory).

What the pipeline enforces:

• The archive must contain exactly one blender_manifest.toml. Zero or multiple manifests are rejected.
• The manifest `id` is permanent. It becomes the product's immutable extension identity, and every later version must keep it.
• The manifest `version` must match the product version the archive attaches to.
• Fill the standard manifest fields Blender requires: schema_version, id, version, name, tagline, maintainer, license, and blender_version_min (plus blender_version_max, tags, website, copyright, and permissions where relevant).
• If the extension ships native code or Python dependencies, declare platforms and bundle wheels. Buyers only see builds for their platform.
• The server re-validates every archive with pinned Blender 5.2 tooling and normalizes it before publication. A manifest Blender would reject never reaches buyers.

Test the artifact, not the source tree

Install the exact built ZIP through Install from Disk in a factory-startup Blender before uploading. You test byte-for-byte what buyers receive after review.

Blender assets and asset libraries

Asset products accept two source shapes. Either becomes entries in every buyer's remote asset library:

Single .blend

One .blend file with your marked assets. Everything referenced must live inside it: run File → External Data → Pack Resources before saving. A single external reference (unpacked texture, linked library, on-disk cache) fails the upload with an external-dependency error.

Asset-library ZIP

A ZIP with the standard Blender asset-library layout:

• one or more .blend files (subfolders are allowed)
• exactly one blender_assets.cats.txt catalog map at the archive root
• optionally the textures those blends reference, as ordinary image files (.png, .jpg, .exr, .hdr, .tif, .tga, .webp, .bmp, .dds)

Nothing else is allowed: no scripts, executables, nested archives, or symlinks, and at most 2048 entries. This is Blender's local asset-library folder structure, zipped.

Mark the assets

The pipeline publishes only data-blocks marked as assets. Everything else is supporting data. Right-click the object, material, node group, world, or other data-block and choose Mark as Asset. Use Blender's stock asset types. Types behind Blender's experimental extended-asset-browser flag are rejected.

Organize with catalogs

Buyers browse by catalog. Assign every asset to one in the Asset Browser catalog tree. In a ZIP bundle, each asset's catalog must exist in the root blender_assets.cats.txt or the asset is rejected. Catalogs stay separate per product, so names never collide with other sellers.

Previews and metadata

Every asset needs a preview: Blender's generated one, a custom one, or the processor's automatic render when none is stored. Author metadata in Blender's asset details panel. Description, author, license, copyright, and tags reach the buyer's Asset Browser.

Compatibility

Asset processing currently runs pinned Blender 5.2, and library entries report Blender 5.2 compatibility. Save source files with a 5.2-compatible feature set.

Verify like a buyer

Process and publish

Upload the source to the product version and let processing finish. The delivery state shows when artifacts are ready.

Set up the buyer integrations

In a clean Blender profile, add your own asset library or extensions repository.

Check the buyer experience

Confirm previews, catalogs, names, and metadata read as intended. Install or import into an empty scene and render.

• Selling: Storefront setup, listings, orders, payouts, and publishing.
• Buyer setup: How buyers connect the asset library and extensions repository.
• Seller terms: The current policy for eligibility, fees, and listing requirements.