Most businesses that make or sell products accumulate thousands of files about them: product photographs, renders, drawings, datasheets, installation guides, manuals, certificates, brochures, logos and videos. They are created by different people over many years, saved in shared drives, email attachments, laptops, designers’ systems and website platforms. Then a distributor asks for high-resolution images of twenty products, a tender requires the current datasheet and certificate for each item, or the website needs refreshing, and someone spends days searching, guessing which version is current and wondering whether the business has the right to use a photograph at all.
Those files are business assets. They cost money to create, they support sales and they carry obligations: technical documents must be current, images must be used within their licence terms, and people in photographs may need to have given consent. Managed well, they make marketing faster, help distributors sell, reduce errors in technical information and protect the business from avoidable legal and reputational risks. Managed badly, they waste time and expose the business to using outdated or unlicensed material.
This article explains how to organise a product image and document library: what belongs in it, how to structure and name files, which information to record about each asset, how to manage versions and approvals, how to track usage rights, how to share assets with others, which tools suit different businesses and how to keep the library useful over time. It is general information for small and medium businesses, not legal advice.
What belongs in the library
A product asset library holds the approved files that describe products and the brand, in forms people can use. Typical contents include:
- Product images: studio photographs, application and lifestyle photographs, renders and detail shots.
- Technical documents: datasheets, dimensional drawings, specifications, installation and operating instructions, maintenance guides and safety information.
- Compliance documents: test reports, certificates, declarations and approvals, where they can be shared.
- Marketing material: brochures, catalogues, case studies, presentation templates and social media graphics.
- Brand assets: logos in vector and raster formats, colour specifications, fonts where licensed, and brand guidelines.
- Video and animation: product demonstrations, installation videos and short clips for social media.
The library should hold masters and approved derivatives. Master files are the highest-quality originals, such as raw camera files, layered design files and vector logos. Derivatives are versions prepared for particular uses, such as web images, print-ready PDFs and email-sized files. Keeping masters separate means new derivatives can always be made without loss of quality.
Engineering source files, such as CAD models and drawing originals, usually belong in an engineering data system with its own revision control. The asset library should hold the released outputs, such as PDF drawings and approved renders, and link to the engineering record rather than duplicate it.
Structure: organise around how people search
Most people looking for an asset start with a product. A structure built around products, rather than around departments or file types, therefore suits most product businesses.
| Level | Example |
|---|---|
| Product family | Pumps |
| Product or model | P200 series |
| Asset type | Images, Datasheets, Manuals, Certificates, Drawings, Video |
| Status | Current, Archive |
Brand assets and general marketing material sit in their own sections. Keep the folder structure shallow, typically no more than four or five levels, because deep structures make files hard to find and paths too long for some systems.
Folders alone cannot serve every way people search. A distributor may want all images of products for the mining industry; a designer may want all application photographs taken outdoors. Metadata, described below, handles those cross-cutting searches without duplicating files.
Naming files consistently
A consistent naming convention makes files identifiable even when they are copied out of the library. A useful pattern combines:
- Product code or SKU, which links the file to the product record.
- Asset type, such as image, datasheet or manual.
- Description or view, such as front, installed or detail.
- Version or revision, for documents that change.
- Language or region, where relevant.
For example: P200-datasheet-rev-C-en.pdf or P200-image-front-white-bg.jpg.
Practical rules help:
- Use lower case letters, numbers and hyphens, and avoid spaces and special characters that some systems handle badly.
- Put the most important identifier, usually the product code, first so files sort together.
- Use dates in year-month-day order, such as 2026-10-09, so they sort correctly.
- Never use “final”, “new” or “latest” in a file name; they become untrue quickly.
- Keep the convention short enough that people follow it.
Metadata: what to record about each asset
Metadata is information about each file that makes it searchable and tells people whether and how they can use it. A practical set for most businesses includes:
| Field | Purpose |
|---|---|
| Product code and name | Links the asset to the product |
| Asset type | Image, datasheet, manual and so on |
| Status | Draft, approved, superseded or withdrawn |
| Version or revision | Identifies the current document |
| Owner | The person responsible for keeping it current |
| Approved by and date | Shows that it has been checked |
| Creator | Photographer, designer or author |
| Rights and licence terms | Who owns it and how it may be used |
| Expiry date | When a licence, certificate or approval ends |
| Model or property release | Whether consent has been obtained where needed |
| Keywords | Industry, application, setting and other search terms |
| Language or region | Market the asset is intended for |
Keep the mandatory fields few, perhaps five or six, and make the rest optional. A library with a long list of mandatory fields that nobody completes is worse than one with a short list completed consistently. The data readiness is a business habit article explains why agreeing conventions early and assigning owners matters for any business data.
Versions and approvals
Technical documents are the highest-risk part of the library, because an outdated datasheet, drawing or installation guide can lead to wrong orders, failed installations or safety problems.
Good practice includes:
- One current version of each document is marked approved; earlier versions are marked superseded and moved to an archive, not deleted.
- An approval step before any new or revised technical document is published, with the approver recorded.
- A revision history describing what changed and why.
- A link to engineering change control, so that when a product changes, the related datasheets, manuals, images and drawings are reviewed. The issue, change and configuration control article explains configuration management in more detail.
- Withdrawal of documents for discontinued products from active use, while keeping them in the archive for customers still using those products.
Keep superseded technical documents for as long as the business may need to show what information was supplied at a particular time, for example in a warranty claim, a product liability matter or a regulatory inquiry. Decide retention periods with appropriate advice.
Rights and permissions
Using an image or document requires the right to use it. Many businesses discover rights problems only when a photographer, stock agency or former contractor objects.
Who owns what
In Australia, copyright in a photograph or document created by an employee as part of their job generally belongs to the employer. Work created by a contractor, agency or commissioned photographer is generally owned by its creator unless a written agreement assigns copyright or grants a licence. Commissioning and paying for work does not by itself transfer ownership. Agreements with photographers, designers and agencies should state who owns the work and how it may be used. Seek legal advice for specific arrangements.
Licences
Stock images and many commissioned works come with licences that limit use, for example to web use only, a particular region, a period of time or a limited print run. Record licence terms in the metadata and set expiry dates where licences end, so assets can be withdrawn or renewed before they are used outside their terms.
People and property
Photographs that show identifiable people, such as employees, customers or models, should be supported by a written release consenting to the intended uses. Some locations and customer sites also require permission before photographs are published. Images taken at customer sites may reveal confidential equipment, processes or security details, so check before publishing.
Brand and third-party marks
Images of products installed with other manufacturers’ equipment may show their trade marks. Make sure use of such images does not suggest endorsement or a relationship that does not exist.
Sharing assets with distributors and customers
Distributors, resellers, retailers and customers need product assets to sell and use products. Sending files by email on request is slow and leads to outdated versions circulating indefinitely.
Better approaches include:
- A distributor portal or shared collection with approved, current assets organised by product.
- Download packs for each product, containing images in common sizes, the current datasheet and key documents.
- Links rather than attachments, so recipients always reach the current version.
- Usage guidance explaining how images and logos may be used, with any licence restrictions passed on clearly.
- Notifications to distributors when important documents change, especially safety and installation information.
Choosing tools
The right tool depends on the size of the library and the number of people using it:
| Approach | Suits | Strengths | Limitations |
|---|---|---|---|
| Structured shared drive or cloud storage | Small libraries and teams | Low cost, familiar | Limited metadata and search, manual version control |
| Digital asset management (DAM) system | Larger image and marketing libraries, external sharing | Metadata, search, previews, rights fields, portals | Subscription cost, setup and discipline needed |
| Product information management (PIM) system | Many products, many sales channels | Links assets to product data and distributes to channels | Larger implementation |
| Document management system | Controlled technical and quality documents | Approvals, revisions, audit trails | Less suited to marketing images |
Many small businesses start with a well-structured cloud folder, a naming convention and a simple register in a spreadsheet, then move to a DAM or PIM system as the library and the number of users grow. Whatever the tool, make sure the business owns and controls the account, can export its files and metadata, and has backups. The owning your website and digital presence article covers similar questions of control for websites and domains.
Keeping the library useful
Libraries decay without care. Practical habits include:
- Assign an owner for the library as a whole and owners for each product range.
- Make adding assets part of normal work, such as product launches, photo shoots and engineering changes.
- Review regularly, for example every six or twelve months, to withdraw outdated items, renew licences and fill gaps.
- Measure use: which assets are downloaded, which requests the library could not meet and how long searches take.
- Train new staff in the structure, naming and approval steps.
- Remove duplicates and personal copies kept outside the library.
A worked example
This is an illustrative example. A manufacturer of industrial pumps and valves sells about 1,200 products through 35 distributors. Product images and documents are spread across shared drives, a former designer’s archive and the website. Distributors email about 40 requests a week for images and datasheets, each taking staff about 15 minutes to find and send, or about 10 hours a week. Twice in the past year, a distributor used an outdated datasheet in a tender.
Set up. The marketing coordinator and an engineer define a product-based structure, a naming convention using product codes and a short set of mandatory metadata: product code, asset type, status, owner and rights. Over three months, they gather files, remove about 4,000 duplicates and mark one approved version of each datasheet.
Rights check. Reviewing licence records, they find about 60 stock images licensed for web use only that had appeared in printed catalogues. Those images are replaced in the next catalogue print and marked web-only in the library. Contracts with photographers are updated to grant the business a licence for all marketing uses.
Sharing. The business subscribes to a cloud digital asset management service, at about $4,000 a year in this illustration, and gives distributors portal access to current, approved assets. When a datasheet is revised, distributors are notified automatically.
Result. Email requests fall to about five a week, saving roughly 8.75 hours a week, about $20,000 a year at an assumed $50 an hour, well above the subscription cost. More importantly, distributors use current documents, and the business can show which version of each document was available at any time.
Applying this in an Australian business
- Treat product files as assets with owners and value.
- Organise around products, with shallow folders and useful metadata.
- Name files consistently, starting with the product code.
- Approve and version technical documents, and link them to engineering change.
- Record rights, licences and releases for every image.
- Share through links and portals, not email attachments.
- Choose tools that grow with the library and that the business controls.
- Review the library regularly and measure whether it meets people’s needs.
Questions worth considering
- How long does it take us to find the current datasheet and best image for a product?
- Do we know who owns the copyright in our product photographs?
- Which of our images carry licence restrictions we may not be respecting?
- How do distributors learn that a technical document has changed?
- Who is responsible for keeping each product’s assets current?
Bringing it together
A product image and document library turns scattered files into business assets that support sales, distributors and customers. Organise it around products, name files consistently, record a small set of useful metadata, approve and version technical documents, track rights and releases, share through links and portals and choose tools the business controls. Keep it alive with owners, regular reviews and habits that add new assets as part of normal work.
Source: KEVOS editorial notes on managing product images and technical documents in small and medium businesses, drawing on general digital asset and document management practice. Information about copyright and permissions is general and not legal advice. The worked example is illustrative. This article is general information.
