Product images, videos and documents should live with the product, not in Dropbox, email and the website's media library. SKULaunch's DAM stores assets linked to each product, with metadata and versions, so the right image reaches every channel.
The problem
Assets end up scattered: supplier folders, shared drives, the ecommerce platform, someone's desktop. Nobody knows which image is current, which is approved for marketplaces, or which datasheet is the latest. Every channel upload starts with a search, and the wrong image regularly goes live.
Before and after
An illustrative example for a product's assets.
Before: where the files are
Main image on the website, two angles in a supplier Dropbox, the datasheet in an email from 2023, the lifestyle shot "somewhere on the drive".
After: in the SKULaunch DAM
- Main image, angles, lifestyle shot, video and datasheet stored against the product
- Metadata on each asset: type, angle, channel use
- Previous versions kept, current version marked
- Links published with the product to every channel
How it works in SKULaunch
- Bring assets in. Upload, import from suppliers or link from existing locations.
- Link to products. Assets are attached to the products they belong to.
- Describe them. Use configurable asset types and metadata for angle, use and channel.
- Publish with the product. Asset links go out with product data to each channel.
Organise assets around products, not folders
Folder structures break down as soon as a product belongs in two places. Linking assets to product records, with metadata describing what each one is, means the question "what is the main image for this SKU on this channel" always has one answer. Folders become irrelevant.
What changes
One place for every asset, linked to the right product and version, published consistently.
Common questions
Is the DAM included?
The DAM is available as an add-on.
Which file types are supported?
Images, video and documents such as PDFs.
Can suppliers add assets?
Yes, through the supplier portal.
See the DAM platform page, supplier uploads, and finding images.

.avif)