How to

How to archive your merch digital assets

A lightweight DAM (Digital Asset Management) system for merch teams in CDMX, Monterrey and Guadalajara: structure, metadata, versioning, and search in under 30 seconds.

Download metadata template DAM tools

Why a merch asset archive is not "the designer's folder"

When assets live on the designer's desktop or an unstructured Drive, three things happen: nobody finds the right version, the editable master gets lost, and nobody knows which supplier approved which art. For a corporate merch program in Mexico that goes through multiple campaigns, events, regions and revisions, that means rework and expensive mistakes.

A lightweight DAM — based on Airtable, Asset Bank, Bynder, or a well-built SharePoint — solves this with three rules: versioned master files, consistent metadata, and fast search by business criteria (brand, event, supplier, year, product type).

Plus, in scenarios with IMMEX or export under USMCA, having an auditable master file (with its last modified date and owner) makes it easier to prove the art that traveled on a shirt to Dallas matches what was filed before SAT.

A merch DAM also reduces the risk of misuse: with a status field (draft / approved / in production / retired), you know exactly which pieces may be used and which are out of circulation due to a brand change or a finished event.

Implementing the DAM in 7 steps

  1. Define asset types — logos (master, mono, inverted, knockout), print art (screen print, embroidery, sublimation, laser engraving), digital art (social, web, email), product photos and renders.
  2. Set the naming convention — one name per file: brand-product-asset-type-version.ext (e.g. ACME-TEE-LOGO-MASTER-V03.ai). The same name goes into the metadata field.
  3. Version explicitly — V01, V02, V03. Never "logo final", "logo final 2", "logo final FINAL". And never delete old versions: archive them as "superseded".
  4. Load consistent metadata — brand, product, event, date, supplier, PO, CFDI, color, tolerance, brand owner, status (draft / approved / retired), search keywords.
  5. Separate masters from derivatives — the AI / EPS / PSD / AFFINITY master goes in a protected folder; PDF, PNG and JPG exports go in a public folder for daily use.
  6. Define access rules — brand, marketing and procurement see derivatives; only the creative team and the brand owner can modify or replace masters.
  7. Audit monthly — a monthly review to retire obsolete versions, fill missing metadata, and confirm the file is backed up (ideally in off-site storage, ideally encrypted).

Common mistakes when building a DAM

The first mistake is confusing the DAM with a file dump: upload everything and hope the search works. Without consistent metadata and strict naming, the DAM becomes a digital graveyard. Discipline at intake is the only thing that keeps the system useful.

The second mistake is failing to separate master from derivative. When the editable AI lives in the same folder as the compressed PNG, someone will edit the PNG by mistake and the master is lost. Separate folder, restricted access, derivative stays derivative.

The third mistake is using "pretty" names instead of codes. "End of year party logo 2024" does not scale. "ACME-EOY-LOGO-V02" does. Aesthetics yield to search.

The fourth is forgetting where the file is backed up. A Drive synced locally is not a backup: if the laptop is lost, the file is lost. Move the master copy to a service with versioning and encryption (Backblaze B2, AWS S3 with Glacier, Google Workspace with Vault) — a decision you will thank yourself for when you need it.

Templates, tools and references

Metadata template: sheet with columns for code, brand, event, date, supplier, PO, CFDI, color, tolerance, owner, status and keywords. Useful for populating Airtable, Notion or a dedicated DAM.

DAM tools: Airtable (basic, free up to a volume), Asset Bank (pro, mid-price), Bynder (enterprise), SharePoint (if you already have Microsoft 365), Google Workspace + Vault (for Google Drive).

Recommended storage: masters in S3 / Glacier or equivalent; derivatives in Drive / SharePoint / Dropbox; automated backups with versioning; encryption at rest and in transit.

Technical references: PDF/X-4 for offset print, PDF/X-1a for screen print and embroidery, ISO 12647-2 for press color control, and your local printer or embroiderer's guides.