Sports photography workflow FAQ

Batch Relay supports White House Custom Colour (WHCC) and Richmond Pro Lab (RPL). We map your catalog, package rules, prepared images, shipping choices, and order data to the supported lab workflow during onboarding.

Not yet. We start with a real event and work through your roster, packages, fulfillment path, and exceptions with you. That white-glove onboarding lets us verify the workflow before your studio depends on it. Tell us about the next event on your calendar and we will personally review the fit.

Batch Relay can validate, prepare, and move eligible orders through the connected workflow continuously, including outside normal office hours. Same-day processing refers to Batch Relay's order work and submission path; lab production and carrier delivery times still depend on the selected provider, products, shipping service, and any exception that needs review.

Batch Relay does not impose an artificial per-batch limit. During onboarding we still review event size, product mix, image readiness, and lab requirements so a high-volume event moves through a controlled production plan instead of becoming one opaque upload.

Yes. Currently you upload pre-cropped images with your CSV data file. Batch Relay handles automated routing and processing after files are ready.

We support standard CSV files for order data plus prepared JPEG, PNG, TIFF, and WebP images accepted by the configured workflow. During onboarding, we provide the required fields and product asset rules so athlete, package, image, and delivery records stay connected.

Yes. Orders are processed and shipped directly to parents' addresses, so you do not need to manage physical print distribution.

You get live order tracking and issue visibility. If quality or fulfillment problems appear, we help coordinate reprints and corrections through your lab workflow.

The studio keeps control of its product definitions, package strategy, customer relationships, and operational data. Batch Relay uses explicit roles and event context to keep studio, staff, guardian, athlete, order, and fulfillment information separated while the workflow is active.

The studio defines the products and packages it wants to sell, and Batch Relay keeps those selections connected to the athlete, purchaser, prepared image assets, delivery choice, and supported lab product. That shared context reduces the need to rebuild an order from a storefront export before production. Product mapping is reviewed during onboarding because sizes, crops, finishes, and shipping rules still need to match the selected WHCC or RPL path.

A recent or upcoming event is the best starting point. Bring an example roster or CSV, the packages you sell, representative prepared images, estimated athlete and order volume, your current lab, delivery options, and a description of every manual handoff. You do not need perfect documentation. We use the review to identify missing fields, exception rules, product mappings, and the smallest realistic event that can prove the workflow.

Batch Relay is being built with automation and API-driven workflows as first-class parts of the platform. Zapier and n8n connections are in the near-term launch path rather than generic self-service integrations today. If either is important to your studio, include the trigger, destination, and data you need in the event-intake form so we can confirm current availability and scope during onboarding instead of promising an unsupported recipe.

Bring us one event already on your calendar. Tell us about the studio, estimated volume, current lab, package workflow, and biggest manual handoff. We review each request personally and respond within one business day with the next onboarding step.