Control one image with a JSON sidecar

What this does

Matching JSON supplies per-image copy, product_tags, singular routing or stores fan-out, overrides sheet values, and travels with delayed copies.

Before you begin

• Name the sidecar with the same stem as the artwork, such as art.png and art.json.
• Keep credentials out of the file. Use product_tags for per-image tags.

Steps

1. 01

   Match the artwork stem

   Place the artwork and same-stem JSON together. The worker checks the JSON next to both the image and its metadata path.

2. 02

   Choose singular or plural routing

   Use store with an optional line for one target. Use stores as a list for explicit per-image fan-out. The key diagnostic logs stores as unrecognized, but target resolution still executes it.

3. 03

   Know the failure boundary

   An unknown store in an explicit JSON stores list fails the whole drop. By contrast, stale stores in the saved Publish drops to set are skipped while healthy siblings continue, unless none remain.

4. 04

   Use JSON for delayed copies

   Paced and per-store timed paths carry the artwork and matching JSON. They do not carry a batch sheet.

Expected result

The image uses its JSON copy and routing at execution time. Explicit fan-out either resolves every named target or fails before partial output.

Good to know

• Each JSON sidecar is limited to 2 MiB at upload.
• Unknown singular store or line names fail only in a real multi-store or product-line setup. An effectively single-store setup warns and uses default routing.
• A JSON stores list overrides lower routing tiers. An explicit unknown target fails the whole fan-out.

Troubleshooting

• Sidecar ignored? Match the filename stem exactly and validate that the JSON object parsed.
• One explicit fan-out target is stale? Correct or remove it before retrying; explicit JSON does not skip a bad sibling.

How to undo or clean up

Correct or remove the sidecar before a future drop. It cannot undo external records created by an earlier run.