// Operations guide · ~10 min read

One drop, several store releases

Send one artwork to several stores while each keeps its own voice, products, provider, and release time. Publish now or schedule each store up to 30 days later.

// The model

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 have a problem while the others finish normally. Live Log keeps each store's progress together.

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.

// Before the upload

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.

// Store checklist
  • Storefront: the correct Shopify or Etsy destination is connected and currently authorized.
  • Provider: the store names its exact Gelato store or Printify shop when one is used.
  • Templates: the store-level filter contains only the products intended for that audience.
  • Voice and line: the correct store voice and optional product line are saved.
  • Proof: one small representative test has succeeded before a wide release.

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.

// Your Stores

Choose your stores

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.

// Release timing

Choose a release time 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.

Example Release choice Result
Etsy launch Now The Etsy copy starts processing when the upload is accepted.
Shopify follow-up 7 days The Shopify copy waits until its saved release time.
Seasonal store 30 days The artwork waits 30 days, then starts for that store.

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

// One source, separate releases
The artwork is shared. The destination decisions are not.
Every store keeps its own writing style, products, connection, release time, and result.
// Saved at upload

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 releases each store at its chosen time even when the browser is closed. On Mac, keep ArtDrop running until scheduled work starts. The Batch page shows schedules for groups of artworks; each store's release time stays with the upload that created it.

// Evidence

Review each store separately

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

// Inspect after release
  • Copy: title, description, tags, SEO fields, and store voice.
  • Products: intended template set, variants, placement, media, and retail price.
  • Destination: exact store, product line, Gelato store or Printify shop, and storefront record.
  • Status: provider creation, storefront publication, any draft or approval requirement, and any pending synchronization.
// Fix one store

Fix one store without duplicating the others

A problem in one store does not stop the others. Leave successful stores alone, check whether the product already exists in the affected provider or storefront, and retry only that store when needed.

  1. 1
    Preserve evidence

    Copy the relevant Live Log lines

    Copy the lines for the affected store, including its provider, product, last completed step, message, and time.

  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

    Choose the corrected store as the only destination for the recovery drop. Sending the full set again can duplicate products or listings in stores that already succeeded.

// Recovery controls

Live Log versus Retry Sync

Use Live Log to follow each store. If the page was closed or disconnected, reload it and check the named provider or storefront before retrying. Retry Sync is not a general retry. It is only for a storefront connection that is still waiting to finish.

Control Use it for Boundary
Live Log Read the lines this browser received. Copy the displayed lines with their time when you need partial evidence. Read-only. External records stay unchanged.
Needs Attention Review a product that is still waiting for a storefront sync result. A focused pending-sync view, not the complete error history. An empty view is not proof of success.
Retry Sync Reset and resume polling for a timed-out pending storefront synchronization. Only storefront sync polling. Provider creation and other errors need a separate fix.
Dismiss Remove a pending wait from the Needs Attention view after you have inspected it. Removes the item from this view only. The external product stays unchanged.
// Two schedulers

Store offsets are different from batch pace

A store release time controls when one store starts. Batch pace controls how several artwork files are spaced. You can use either schedule on its own.

  • 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.
  • Publication time: a schedule chooses when ArtDrop starts the work. The provider and storefront may finish later.
// FAQ

Frequently asked questions

Can one upload go to several stores?

Yes. Select several destinations in Publish drops to. Each store keeps its own release time, writing style, product choices, provider connection, and result.

What is the maximum store delay?

Thirty days. Each store can start now or after its own delay.

Will changing the release times move an upload that is already waiting?

No. ArtDrop saves the selected stores and release times with each upload. Later changes apply to future uploads.

Does one failed store stop all the others?

No. The other stores continue independently. Check whether the product already exists in the affected provider or storefront, correct that store, and retry only that destination.

Can I use Retry Sync for any failed drop?

No. Retry Sync only resumes a timed-out pending storefront synchronization. It does not rerun provider creation or repair a general pipeline error.

Stage a multi-store release you can inspect and recover.

Check each store's connection, choose its release time, and test one artwork before sending a larger group.

Open ArtDrop

Separate release times for every store · delays up to 30 days

// More help
Fan-out task reference Store routing Live Log recovery Help center