Live

ArtDrop glossary

The words ArtDrop uses for destinations, publishing, and everything a single drop touches, defined once so nothing gets confused.

Availability
Live
Last verified

What this does

The words ArtDrop uses for destinations, publishing, and everything a single drop touches, defined once so nothing gets confused.

Before you begin

  • Product labels stay in English where the app itself is in English, so these terms match what you see on screen.

What changes outside ArtDrop

This page is read-only. Reading it changes nothing inside or outside ArtDrop.

Steps

  1. Drop

    When each admitted artwork is released, ArtDrop applies the row, sidecar, or line and starts the configured route. The result may be a storefront listing, a draft, or a provider-only product, depending on the destination. Accepted, processing, scheduled, published, and failed are distinct states.

  2. Store / destination

    A store is one connected storefront in your account, Shopify or Etsy, and you can have several. The destination is the exact store plus its provider mapping that a drop routes toward.

  3. Product line

    A named set of voice, title, SEO, tag, intro, and template-filter rules inside one store. Each store supports up to 50 product lines.

  4. Product template

    A saved provider product setup, such as a Gelato product and variants, a Printify blueprint, or a Printful product. When enabled and selected by the effective filters, a future drop can create it. It is not a product line.

  5. Publication

    A provider-only product is an external result, not a publication. Publication here means a storefront publication.

  6. External write

    Any action that creates or updates something in a connected service outside ArtDrop, such as creating a product at a provider or publishing a listing to your store.

  7. Demo drop

    The Web demo uses a 3-drop counter. After a request saves at least one artwork file, the route rechecks demo mode and, if it is still active, attempts one increment. A failed counter update does not fail the accepted upload response, so the counter is not a hard maximum. Web demo requests use the real route with a watermark. The demo is not available in the Mac app. Routed derivatives can create external records, so inspect every named result.

  8. Live Log

    The per-user dashboard log stream that the browser starts after an accepted upload or worker start. It shows up to the newest 500 lines across recent sessions and concurrent drops, so its route stages, external-result messages, and failures are not a complete durable history for one drop.

  9. Fan-out

    One worker-visible artwork with a plural target stamp can resolve into separate runs for several stores. Stamp failure can leave default routing, and an explicit unknown target can fail the whole fan-out before those runs begin. After resolution, target processing failures are isolated from eligible siblings.

  10. Publish drops to set

    The saved Storefronts checkbox set that chooses which stores receive an ordinary drop unless a more specific route overrides it.

  11. Per-store release cadence

    A separate timed target captured at upload with a choice from Now through 30 days. It is handled by the timed sweeper, not by the paced multi-image batch lane.

  12. Held batch

    A multi-image group held until Publish all now, a paced choice, or Clear Queue. Hosted Web advances due paced releases through its server sweeper without an active login or open dashboard. On Mac, keep the app running.

  13. Provider Cost Comparison

    A representative and potentially incomplete table whose account and route isolation is not proven. Rows can mix provider requests, saved Printify template costs, and no static-estimate gap fill. Missing provider-category results stay absent. It is not a quote.

  14. Pending sync

    A persisted checkpoint for an expected Shopify reconciliation result. It starts in waiting state before any timeout and can later complete or be classified as a sync, soft, or hard timeout.

  15. Retry Sync

    The action that queues a reset for every timed-out pending storefront-sync item whose title matches the selected row. The worker applies it on its next poll. It is not a general retry for every pipeline failure.

  16. Connection readiness

    Evidence that every exact provider variant is connected to the intended storefront route. A create response alone does not prove it.

  17. Accepted

    Accepted is the browser label for a nonempty saved list. A final rename failure can leave that label without a worker-visible file, so confirm the queue or Live Log. It does not prove processing or an external result.

  18. Processing

    The route-specific pipeline is running for one named target. Processing is not a confirmed provider or storefront result.

  19. Scheduled

    Scheduled is a route label for work intended to remain in a paced or timed lane until release. Confirm the held list because an earlier admission or filesystem failure can leave the interface label without the intended file.

  20. Published

    Published is route-specific, not universal proof of a live listing. Printify uses an accepted publish request without storefront readback, and legacy routes can prove less. Verify the storefront unless the route guide names stronger readback. Printful remains provider-only.

  21. Failed

    Failed means this browser received a failure for one named target. ArtDrop does not currently provide customers a complete durable history of every terminal drop error. Preserve the lines received by this browser and inspect the named external services before retrying.

Expected result

This reference distinguishes stores, lines, templates, route states, and publications without treating an interface label as execution proof.

Good to know

  • Provider and marketplace words can mean something slightly different inside their own tools; these definitions describe how ArtDrop uses them.
  • The Web demo uses a 3-drop counter. After a request saves at least one artwork file, the route rechecks demo mode and, if it is still active, attempts one increment. A failed counter update does not fail the accepted upload response, so the counter is not a hard maximum. Web demo requests use the real route with a watermark. The demo is not available in the Mac app.
  • The Web demo uses a 3-drop counter. After a request saves at least one artwork file, the route rechecks demo mode and, if it is still active, attempts one increment. A failed counter update does not fail the accepted upload response, so the counter is not a hard maximum. Web demo requests use the real route with a watermark. The demo is not available in the Mac app.

Troubleshooting

  • If an app label differs from this page, record the exact label and ArtDrop version and ask support to reconcile them. Do not infer a capability or external result from either label.

How to undo or clean up

Nothing to undo. This is a reference page.