Published

A retailer is preparing a Canadian product launch. Dimensions and product descriptions are complete in its product information management system, or PIM. The proposed video still has unreviewed French captions, and its recorded permission covers partner training. A complete product record does not establish that this media is ready for a public storefront.
Digital asset management (DAM) does not generally replace PIM. Assign product information, media approval and channel publication to the applications that provide those functions. Connect their authoritative records so a ready product can be paired with the exact approved media for its market, language and destination.
The categories overlap. For example, Akeneo documents both product attributes with locale and channel scope and an Asset Manager with product links and transformations. Compare the functions and editions in your selected products; one suite may meet both needs.
| Record or decision | Primary responsibility | Connected evidence |
|---|---|---|
| Product facts and classifications | PIM, with fields supplied by the agreed ERP or other source where applicable. | Stable product and variant identity, current descriptions, dimensions and market/channel values. |
| Media originals and working versions | The designated asset repository and media owner. | Source file identity, version, owner and relationships to renditions. |
| Approved media release | The configured media review and release process. | Exact files, captions, permitted uses, audience, market, language and decision. |
| Product-to-asset relationship | The owner named in the integration contract. | Product/variant ID, asset release, media role and intended destination; unresolved mappings stay visible. |
| Channel publication and removal | The selected PIM, commerce platform, CMS or delivery service for that operation. | Destination item, applied release, publication result and confirmed replacement or removal. |
A media filename or editable SKU label is a weak join on its own. Agree a stable product identity, variant handling and changes to display identifiers. Keep those mappings subject to the schema and consumer checks used for other business-system integrations.
Identify the product, variant, market, language and media role. Confirm the relevant product data is ready.
Review the selected files and permitted use together. Retain the decision for that release and destination.
Publish through the agreed connection. Confirm which release the destination applied and keep failures pending.
Define the relationship before enabling publication: product and variant IDs, asset and release identity, exact document versions, language, market, media role, intended use, destination and effective usage dates. These are business requirements for the configured integration, not a prescribed FormKiQ request schema.
The destination may use an approved reference or require a delivered copy. Record which method applies. A product's current media link should resolve to its accepted release, while historical publication evidence still identifies the version actually sent. The master and derivative guide explains the separate source and rendition history.
In this fictional example, product P-042 is ready for the Canadian storefront in en-CA and fr-CA. The team proposes a new setup video. Its existing use permission covers partner training, and the new French captions still need review.
The integration matches the asset to the canonical product record behind P-042 and identifies the Canadian public storefront as the destination. Record the two language requirements and the video's media role. A link to a similarly named product or a training-only channel does not satisfy this match.
The PIM's ready product data remains available. The proposed video release stays in review because the recorded use permission and unreviewed French captions do not meet the storefront requirements. The channel owner follows the agreed launch or fallback policy; it does not silently publish the candidate.
The authorised owner records permission for the intended Canadian storefront use and retains the supporting evidence. Reviewers accept video v2 with English captions v3 and French captions v2. Release R-07 identifies those exact versions, market, languages, use conditions and approval. Earlier training approval remains part of the history.
The publisher sends the approved release through the configured connection. The English placement succeeds, but the French placement rejects its caption format. Record each result against R-07 and its destination item. Keep the French placement pending; any converted caption file returns through the required review before replacing the accepted package.
The correction produces release R-08 with its own approval and exact caption version. After the destination accepts it, record the applied release and channel response. Check that a delayed R-07 update cannot replace the newer accepted placement. Product-data readiness, media-release approval and successful publication remain separately explainable.
A revised product, corrected image or usage-rights deadline can require action in several destinations. Identify affected placements, approve the replacement or withdrawal, and record the destination's result. Changing DAM metadata or a PIM relationship alone does not prove that a storefront, CDN or downloaded copy has changed.
Usage metadata informs release decisions. FormKiQ document permissions govern repository access, and the publishing system enforces its own access and delivery controls. Agree how the selected channel handles stored copies and caches. The document-link revocation guide explains why a distributed copy requires separate treatment. Preserve outstanding exceptions alongside confirmed removals.
Select DAM and PIM capabilities around the decisions your teams need to control. Keep product information, approved media and destination outcomes connected through stable identities and specific releases. That relationship lets staff explain what may be published, what was published and what still needs attention.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.