The right images, to the right channel, in the right order, at the right size.
Getting images to a retailer is the part of syndication everyone underestimates. Amazon wants four, Walmart wants six. Walmart puts a video in the second slot; Amazon wants a white-background main image that fills the frame. Your images live in a DAM, your product data lives somewhere else, and nobody is sure which of the five "hero" shots is the real one. Syndic8 links images to products, tags them once, maps each channel's slots to those tags, and checks every collection against the channel's image rules before anything ships.
Images in one system, products in another, and a spreadsheet trying to hold them together.
Most brands keep images in a DAM and product data in a PIM or an ERP. Linking the two, for every SKU, every angle, every channel's naming convention, is a job that never finishes: new photography arrives, products get reloaded, filenames drift. Syndic8 connects to the DAM, matches images to products by rule, and keeps the link when either side changes. Syndic8 can also serve as your DAM!
Matched by rule, not by hand
Set a filename rule once ({SKU}_{angle}.jpg) and Syndic8 attaches every image in a drop to the right product in one pass, across the whole catalog. One shot can serve every size and color of a style. The exceptions, style-named files or one-offs, are matched by ID.
One hero, not five
We see it in nearly every catalog we audit: a product with three, five, eight images all flagged as the hero, so the channel's main image is whichever one the export happened to pick. Syndic8 keeps exactly one hero per SKU, flags the products that have none or several, and makes the main image a decision instead of an accident.
Tag by what the image is, not where it's going
Front, back, lifestyle, swatch, size guide: tags describe the shot. Each channel's mapping says which tag fills which slot and what to name the file. You tag once and Walmart, Amazon and Home Depot each get their own order.
Asset Readiness: the channel's image rules, checked per SKU, before you ship.
Image preflight runs a collection against a channel's image requirements and names the products that would fail: an empty slot, a missing hero, two heroes, a format the channel won't take, a URL that doesn't resolve. It's the third score next to Listing Readiness and Channel Optimization, and it gives you a preview of how the images will render at the channel. How the three scores fit together.
Every required slot filled
Does the product have a main image, and an image in every slot the channel's mapping requires? Footwear on Walmart needs a back view. A rug on Amazon may use a lifestyle main; a faucet may not.
Enough of them, in a type the channel takes
Most retailers want five to eight images and few accept fewer than three. JPG and PNG everywhere; TIF sometimes; EPS never. Preflight catches the EPS main image before the channel does.
What "main image" means on that channel
Pure white background, product filling at least 85% of the frame, no text or logos on Amazon. A numbered eight-shot list for Walmart tires. A dimension silo for refrigerators. The channel's image guideline is scored alongside its content guideline, so preflight tells you whether the slot is filled with an image tagged as the kind of shot the channel asked for.
Preflight reads the tags, formats and mapping, not the pixels, so a correctly tagged image of the wrong product still passes.
Hand the image housekeeping to Copilot or your own assistant.
Ask for the products with a media problem
"Every SKU in the Fall collection with no lifestyle image." "Products with more than one hero." "Anything whose main image is a TIF." The answer is a list you can act on, not a report you have to read.
Set heroes, apply tags, match the unmatched
Promote the front view to hero where there is none. Resolve duplicate heroes to the image tagged Main. Attach the images that automatch skipped, or unlink a wrong one without deleting it. Each change is previewed and approved by a person before it lands.
Bring images in by URL, tagged on arrival
Point the assistant at the photographer's delivery folder or the DAM and name the SKU and the angle; it uploads and tags. Every bulk upload is a named run you can find later, and an unmatched image says why it didn't match.
Writes follow the same rule as everywhere in Syndic8: the assistant proposes, a person approves. How the copilot and the MCP server share one set of tools.
The details that decide whether a launch goes out on time.
Your DAM stays the source.
Syndic8 links to it rather than copying it. Acquia DAM connects with minimal setup; images can also be loaded by URL, by file, or through the API.
Export naming is the channel's, not yours.
Walmart wants the UPC in the filename, Amazon wants the SKU and a slot code. The mapping builds the name from product fields at export time, so your DAM filenames never have to change.
Renamed, resized and reordered at syndication.
You keep one image library. When a channel is syndicated, Syndic8 renames every image to that channel's convention, resizes it to the channel's dimensions, puts it in the channel's slot order, and packages the result as a downloadable file bundle ready to send, or as hosted URLs in the feed, whichever the retailer takes. Nobody exports, renames and re-uploads by hand, for any channel, ever again.
Reload products, re-run the match.
Matches are keyed to the product record. After a product reload, one automatch run brings the images back along. Images, videos, spec sheets, 3d files, and PDFs as product media.
Send a collection and name a channel. We'll return the Asset Readiness list.
You'll see which products would fail that retailer's image spec and why: missing heroes, duplicate heroes, empty slots, bad formats. Before any of it is uploaded anywhere.