FOR ECOMMERCE AGENCIES & CATALOG TEAMS

A clearer handover.
One supplier at a time.

Match supplier photos to product SKUs, resolve the uncertain ones and export an organised package for your existing hosting and store import workflow.

Browser-local file processing · No account needed · Original photos stay unchanged

You handle photo hosting and the final store import. Tidrivo handles the preparation and review between those steps.

BUILT AROUND THE HANDOVER

For the next supplier drop. And the one after it.

01

Agency production teams

Turn a supplier CSV and a folder of JPEG or PNG files into explicit photo-to-SKU assignments. Keep ambiguous matches visible until someone reviews them.

02

Variant-heavy collections

Assign one photo to several variant SKUs, set the order and exclude unwanted files. Export one photo copy with separate mapping rows for its variants.

03

Recurring supplier work

Reuse column and filename rules through supplier profiles. Name each project and save a portable draft to continue with the same source files later.

A FILE PACKAGE YOUR TEAM CAN INSPECT

Know what goes to the next person.

Your review ZIP includes unchanged image copies with safe output names, the original CSV, a mapping CSV, exceptions, a saved project and a README.

When your own upload process returns image URLs, add the filename-to-URL CSV and export an updated mapping. Your assignments and exclusions remain in place.

See the upload-and-return step →

Keep client files under your control.

Work locally

Selected catalog and photo files are processed in your browser. The app does not upload them or send them to an AI model. The marketing pages contain no analytics, tracking pixels or third-party scripts.

Save deliberately

There is no autosave. Save a draft before leaving and retain the original CSV, every photo, any supplier profile and the URL CSV. Restore checks photo contents to reject changed files.

A downloaded ZIP can contain client information and supplied URLs. Share it through your agency’s normal approved process.

TRY ONE REAL BATCH BEFORE CHANGING YOUR PROCESS

Judge the whole job, including the upload.

Start with the fictional walkthrough, then compare one permitted client batch against your usual method. Record preparation time, upload time, corrections, final import checks and whether someone else can use the handover.

Agency time savings and willingness to pay have not yet been established. The demo shows functionality, not a customer result or a promise of revenue.

Try the guided example →

Check the fit before you begin.

Up to 500 products and 500 PNG/JPEG photos per collection, with 100 MiB of photos in total, 10 MiB per photo and 1 MiB per CSV. Each photo must be within 8192 pixels per side and 16 million pixels total. Use smaller batches on constrained devices.

The desktop workflows have local Chromium and Firefox test evidence. Physical Safari, iOS and Android qualification remains outstanding. Store imports, photo hosting and paid access are not part of this local release.

Read the format and limits guide (new tab)