Structured product data means every product fact lives in a typed attribute with a unit, a stable id…
Product Image Deep Links, Not ZIP Files: Assets That Stay Current
If you still send product images to retailers, marketplaces and press as ZIP files, every package starts aging the moment it leaves your outbox. Asset deep links replace the copy with a reference: one stable URL per image that always serves the current file. With Distributr (add-on) in Laioutr, that link travels inside the same channel export as your product data, so a replaced image reaches every recipient without a second process.
Why ZIP files go stale the moment you send them
A ZIP file is a snapshot. The retailer unpacks it, uploads the images into their own system, and from then on your brand lives in their copy. When you reshoot a product, fix a color cast or swap a packaging image after a relaunch, nothing in that chain notices. You would have to know who received which package, send a new one and hope someone replaces the old files.
In practice, three things tend to happen:
- Retailers keep showing outdated packaging or discontinued colorways for months.
- Marketing answers the same "can you resend the images" emails before every season.
- Nobody can say which version of an image is live on which channel.
The listing spreadsheet is rarely the expensive part of onboarding a retailer. The images are. And the problem is structural: a copy has no return channel. We covered the data side of this in one product, forty channels, forty truths. With images, shoppers are the first to see the inconsistency.
What an asset deep link actually is
An asset deep link is a stable URL that points to an image instead of containing it. The URL stays the same, the file behind it can change. Replace the image, and every recipient using that link gets the new version on the next request, with no download and no re-upload.
That turns distribution around:
- Reference instead of copy: the retailer embeds your URL or pulls the image from it, and the file stays under your control.
- One change, every channel: a new product shot is live wherever the link is used.
- Traceable: you know which links went into which channel export, because they are part of the export.
The Data Distribution page describes the feature in one line: stable image URLs that always serve the current file. Asset deep links belong to the B2B scope of Distributr, next to retailer Excel templates, ERP exports and PDF spec sheets.
Step by step: from ZIP folders to deep links
Moving from packages to links is less a migration than a change of habit. A sequence that works in practice:
- Keep images where they are managed. Asset management is part of every Laioutr license, and its feature set is still growing, so your product images can sit next to your pages and product presentation. If a DAM is your leading system for assets, that stays as it is.
- Put the image reference into the export profile. In Distributr, every channel is a typed definition in code, with field mapping, rules and filters. Map the image fields to asset deep links instead of treating images as a separate delivery.
- Validate before you ship. Distributr checks every export against the channel schema, including required fields and allowed values, and a diff guard compares the item count with the previous run. Missing or broken image fields are a classic among the nine product data export errors worth catching early.
- Set the rhythm. Define a schedule or let the export run on every data change. This is where a replaced image actually flows through, instead of waiting for the next manual send. Being up to date is not a premium feature.
- Deliver the way the recipient needs it. Recipients pull a URL, or Distributr pushes actively via HTTPS, SFTP, S3 or webhook, as CSV, XML, JSON, XLSX or PDF.
- Retire the ZIP routine. Tell partners that links replace packages, and archive the "who has which version" spreadsheet.
For developers: channel definitions live in Git. Changes go through a pull request, a rollback is a git revert, and snapshot tests protect a channel against unintended changes. Larry AI drafts a new channel definition in minutes instead of hours; a person on your team reviews and merges it.
Where Distributr ends: not a PIM, not a DAM
Precision matters here, because asset topics tend to grow beyond their scope.
Distributr is the Data Distribution add-on of Laioutr, the Frontend Management Platform (FMP). It is not a PIM and not a system of record, and it does not import or sync data. Its claims are deliberately narrow: 0 imports, because the data is already there, and 1 direction, out, never in. Product data comes from Orchestr, which reads your backend, and content comes from the Laioutr CMS. Distributr shapes both per channel and ships them.
Distributr does not replace a DAM either. If you manage usage rights, license metadata or complex approval steps in a dedicated DAM, keep doing that there. Distributr makes sure the right reference to the current file ends up in the right channel. If your product attributes and media are maintained in a PIM, the page on PIM integration for the frontend shows how that data reaches the storefront in the first place.
Delivery quality: formats, cropping and access
A link is only as good as what it delivers. Retailers need different sizes, crops and formats, and not every image should be open to everyone.
That is what the Image CDN covers as a separate package: automatic WebP and AVIF conversion, smart cropping and resizing via URL parameter, token authentication for signed, time-limited access, and hotlink protection that controls which domains may embed your images. For a press preview under embargo, a signed link that expires is often a better fit than an open URL. For a retailer, a size parameter replaces the folder of pre-exported renditions.
The same delivery layer serves your own storefront, where images usually decide the Largest Contentful Paint. Laioutr storefronts reach an LCP of 1.2 s median, and the page on performance and Core Web Vitals explains how.
FAQ
How is an asset deep link different from a shared cloud folder?
A shared folder still hands out copies: the recipient downloads files, and the connection to your current version ends there. An asset deep link is referenced directly per image, so the recipient always receives the file that is current in Laioutr.
Do retailers have to change their systems?
Usually not. Most marketplaces and retailer templates already accept image URLs in a feed or spreadsheet. Distributr delivers those URLs in the format the channel expects, from CSV to your buyer's Excel template.
Does Distributr replace our DAM or PIM?
No. Distributr is an outbound add-on: it reads data that already lives in Laioutr and ships it. Your PIM stays the source of product information, and a DAM stays the place for rights and asset workflows, if you use one.
What does it cost?
That depends on your setup and scope. Asset deep links are part of the larger Distributr package, and the details are best clarified in a demo.
Next steps
If your team still packs ZIP files before every season, start with a single channel: map the image fields to asset deep links, run a dry run, compare the output. In a personal demo we walk through your current retailer and marketplace setup and show where links can replace packages.