One drop, several store releases

What multi-store fan-out does

One upload can become a separate drop for every selected store. ArtDrop shares the artwork analysis, then prepares each store with its saved voice, products, provider, and timing.

• Its own voice. Each store keeps its trained voice, naming, tags, product lines, and copy rules.
• Its own products. Store-level template filters choose the saved products for that destination. A product line can narrow the selection further.
• Its own provider. Each store names the exact Gelato store or Printify shop that belongs to it.
• Its own result. One store can fail while the others reach their external results. The Live Log lines visible in a browser are useful evidence, but not a complete durable error history.

Each store stays separate. Copying store settings carries over voice and product-line rules while storefront credentials and provider destination IDs stay with their original store.

Check every selected store

Give each store a quick check before the upload. Confirm its storefront, provider, active templates, product line, copy voice, and publishing settings.

If destination details are missing, ArtDrop stops that store instead of sending the work somewhere else. Fix the store, then include it in the release.

Choose the target set

Open the Your Stores card and use Publish drops to to select every destination that should receive the next upload.

1. 1
   Open

   Review Your Stores

   Check the store names and platforms. Open any store that needs a connection, provider destination, voice, product-line, or template-filter correction.

2. 2
   Select

   Check each intended destination

   Your selection becomes the default for new drops. Keep only the stores that belong in this release.

3. 3
   Confirm

   Read the Drop Zone destination badge

   Before you upload, confirm that the badge shows the exact stores you intended. You can still correct the selection before ArtDrop creates provider or store records.

Set a release offset for each store

Each selected store can release immediately or after its own delay, up to 30 days. Any combination is allowed, including every store now, every store later, or a different delay for each destination.

A release time tells ArtDrop when to start that store. Provider and storefront processing can add time afterward.

What ArtDrop saves when you upload

When ArtDrop accepts the upload, it saves the selected store names and release times. Later changes to the checkboxes or delays apply to future uploads. When a delayed store's time arrives, ArtDrop uses that store's current provider, voice, product lines, and templates.

• Immediate stores start processing with the selected store identity.
• Delayed stores receive a store-specific copy with an exact release time.
• An all-delayed set waits until each store is due.
• At release the drop uses that store's current publishing settings.

Hosted Web can release a store schedule while the browser is closed when the backend remains running and the timed sweeper is enabled. On Mac, keep the app running unless a separately verified hosted entitlement handles the schedule. A release starts ArtDrop's work; the provider and store may finish later. The Batch page shows the multi-image rate queue, not the per-store schedule.

Monitor each target independently

Watch each store in the Live Log, then open its provider and storefront records. Confirm the voice, products, price, and destination for that store.

Recover one failed target without duplicating healthy ones

A target failure is isolated. ArtDrop makes one bounded automatic retry for that store when the result is safe to retry. It does not blindly replay an ambiguous create that may already exist. Leave successful destinations alone, then reconcile the failed route before any manual recovery.

1. 1
   Preserve evidence

   Copy the relevant Live Log lines

   Record the target store, provider, product, last successful stage, error, and time. This distinguishes a provider failure from a storefront or pending-sync problem.

2. 2
   Inspect

   Open the provider and storefront first

   Search for a partial or completed product before you create anything again. A timeout can happen after an external service accepted the request, so ArtDrop does not blindly replay an ambiguous create.

3. 3
   Correct

   Fix the problem for that store

   Refresh the store connection, correct the provider, adjust the template, or complete a storefront requirement. Leave the healthy stores as they are.

4. 4
   Reroute

   Recover only the failed store

   If ArtDrop's one bounded automatic retry did not finish the target, make the corrected store the only destination for a manual recovery drop. Sending the full set again can create duplicate products or listings in stores that already succeeded.

Live Log versus Retry Sync

Use the Live Log to see worker output received by this browser. A connection loss or failed replay can leave it incomplete while processing continues. Retry Sync only resumes a timed-out pending storefront synchronization. Other provider or publishing errors need their own fix.

Store offsets are different from batch pace

A store offset controls when one store-specific copy enters processing. Batch pace controls how multiple artwork files are spaced. They solve different problems and can be used separately.

• Per-store release cadence: now or a delay up to 30 days for each store in one fan-out set.
• Multi-image batch pace: release accepted artwork files into processing now or hold them for release at 1, 2, 5, or 10 artworks per day, or about 1 artwork per hour. Hosted Web advances due releases on the server without a login or open dashboard. On Mac, the app must remain running.
• No ranking promise: either schedule can make review and promotion more manageable, but neither guarantees reach, ranking, traffic, or sales.

Frequently asked questions