Release one drop to several stores on separate schedules

What this does

A drop can target several eligible stores. Each resolved store runs independently and can receive one bounded automatic retry for a retry-safe failure. Hosted Web advances due releases without an open dashboard.

Before you begin

• Save every destination store. Use any visible connection test, then verify the external storefront and provider binding in the services that own them.
• For physical products, save the intended Gelato Store ID or Printify Shop ID on each store. Provider API credentials are account scoped; execution uses the ID saved on that store and does not fall back to another store's ID. ArtDrop does not prove storefront identity from a typed ID.
• Review the saved voice and default line for every target. Upload Writing, Website, and Store Identity are root or default scoped; only Image Trainer sends a selected store ID.
• Decide whether any destination should wait. Available delays run from one hour through 30 days.

Steps

1. 01

   Select each intended store

   In Storefronts, choose the exact eligible stores that should receive the drop. Check each store's provider and product settings.

2. 02

   Choose a release time

   Use the release choices shown for each store. Hosted Web's server sweeper moves due releases into processing without an active login or open dashboard. On Mac, keep the app running. Treat external publication time as approximate.

3. 03

   Let each store use its bounded retry

   A retry-safe target failure can receive one automatic retry. ArtDrop uses safe retry or readback handling and does not blindly repeat an external create whose outcome is unknown.

4. 04

   Verify every result

   Open each named provider and storefront. If a target still fails after its bounded retry, reconcile that target and confirm no duplicate exists before a manual resubmission.

Expected result

Every selected store has an independently verified result. Retry-safe failures received at most one automatic retry, and ambiguous creates were not blindly replayed.

Good to know

• ArtDrop creates product and listing data only. It does not access orders, customers, payments, shipping, or fulfillment.
• A scheduled release starts processing around the selected time. It does not guarantee an exact external publication time.
• A successful result for one store does not prove a result for any other store.
• The per-store retry budget is one automatic retry and applies only when the target is safe to retry. An outcome-unknown external create is not blindly repeated.
• Retry Sync is limited to polling the named pending storefront synchronization. It is not the fan-out target retry and is not a general retry for provider or publication failures.

Troubleshooting

• One store is still missing a result after its bounded retry? Check only that store's connection, provider settings, and external records. If creation is ambiguous, do not resubmit until you reconcile it.
• A Needs Attention storefront poll timed out? Inspect the external services, then use Retry Sync only for that named synchronization.

How to undo or clean up

Removing a store from future drops does not remove products or listings already created in external services.