Help Center
Answers for every catalog workflow.
Getting started
What Storeshift does and how it works
Storeshift turns marketplace or Shopify catalog data into cleaner Shopify-ready product outputs.
Free preview vs paid full run
The free preview proves the output shape on a small sample before Checkout starts a full paid run.
How long does my run take?
Run duration depends on listing count, image count, marketplace response time, and AI-copy scope.
Reading your Shopify import CSV
The CSV follows Shopify product import rules, including handles, variant rows, image rows, and SEO fields.
Importing your CSV into Shopify Admin
Import a small sample first, then import the full file after products, images, variants, and SEO fields look correct.
What happens if my run fails?
Failed runs preserve the error reason and, where possible, allow retry after the underlying issue is fixed.
Convert mode
What eBay store URLs are supported
Convert mode supports public storefront URLs that expose listings without seller credentials.
Choosing a tone for AI rewrites
Tone steers product copy style while source facts remain the grounding constraint.
Audience targeting and channel selection
Audience settings help the copy emphasize the buyer context without inventing product facts.
Listing cap and what it controls
Listing cap limits how many products the worker processes and protects cost exposure.
Markup pricing and rounding strategies
Markup and rounding convert source marketplace prices into Shopify-ready prices.
Excluding keywords from your scrape
Exclusion keywords remove unwanted source listings before expensive AI and image work begins.
Variants: how Storeshift maps eBay options to Shopify
Variant mapping turns eBay option axes into Shopify option names, values, and variant rows.
Image quality tiers: cutout, lightbox, original-square
The image pipeline chooses treatments based on product fit, background quality, and confidence.
What gets stripped from source images and copy
Repeated seller logos, watermarks, and marketplace clutter are removed when the pipeline can identify them safely.
Reviewing your preview before paying
The preview is the checkpoint for title, image, body, SEO, and CSV-shape confidence.
Rewrite mode
Uploading your existing Shopify catalog
Rewrite mode starts from an uploaded Shopify CSV and treats it as the source of truth.
Choosing rewrite scope
Select titles, bodies, SEO fields, images, or a narrow combination to control risk and cost.
Voice transfer: matching your existing copy style
Voice samples help the prompts preserve brand phrasing and cadence across rewritten products.
What rewrite mode preserves
Handles, SKUs, lifecycle fields, and untouched columns are preserved unless the selected scope requires a change.
Brand kit: logo, colors, fonts
Brand kit settings provide reusable context for rewrite prompts and image-presentation choices.
Reviewing rewritten copy before import
Review rewritten fields side by side and keep originals where the AI version is not better.
Per-field overrides: keep original on specific fields
Overrides let one product keep its source title, body, or SEO value while the rest of the CSV updates.
Image cleanup: when to enable it
Enable image cleanup only when the source images need rehosting, background work, or candidate treatment review.
Rewrite pricing: scope-based math
Rewrite cost depends on listing count, selected fields, and whether image cleanup is enabled.
Importing the rewritten CSV
A rewritten CSV updates existing Shopify products when handles and SKUs are preserved.
Sync mode
How sync mode works
Sync mode compares a fresh marketplace scrape against a baseline Shopify CSV and emits a delta.
Setting up monthly or weekly sync
Recurring syncs are subscription-backed and create scheduled sync runs at the selected cadence.
What is in the delta CSV
Delta CSVs contain new, changed, and archived product rows depending on the detected source changes.
Identity metafields: the foundation
Stable source identity fields make future sync matching more exact and less dependent on fuzzy title comparison.
Pre-flight scan for pre-existing catalogs
A pre-flight scan reviews likely matches before the first sync so future cycles can run cleaner.
Borderline matches: when to review
Borderline matches need human confirmation because the signal score is plausible but not decisive.
Pausing or cancelling a sync subscription
Pause or cancel sync subscriptions when the source catalog should stop producing scheduled deltas.
Sync with multi-marketplace inputs
The sync architecture supports marketplace-specific source scrapers feeding a common matching pipeline.
API and integrations
Generating your API key
API keys are created in account settings, shown once, and stored server-side as hashes.
Authentication and rate limits
Send API keys as bearer tokens and expect per-key rate limits on public endpoints.
Submitting a run via the API
The API can create preview runs and queue them for processing. Paid full runs still require Checkout.
Subscribing to webhooks
Webhook subscriptions receive signed run and sync events at an HTTPS endpoint.
Webhook signing and verification
Verify the timestamped HMAC signature before trusting a webhook payload.
CLI: installation and getting started
The CLI wraps the public API for preview creation, run listing, cancellation, and item export.
CLI: scheduling runs
Scheduling is subscription-backed; use the CLI to inspect active subscriptions and export run data.
Sandbox environment for development
Sandbox uses separate Vercel, Modal, Supabase, and Stripe test-mode resources.
Troubleshooting
Run failed: common reasons and fixes
Common failures include private source data, image fetch issues, cost caps, marketplace blocks, and CSV validation problems.
CSV import error in Shopify Admin
Import errors usually trace back to handles, required fields, image URLs, price format, or variant row shape.
Image cleanup didn't fire on my product
Image cleanup may be disabled by scope, skipped by confidence gates, or bypassed when the original image is already acceptable.
Identity metafield missing on my products
Missing identity fields make future syncs rely on weaker matching signals until a pre-flight decision fills the gap.
Sync delta has products I already have
Existing products in a delta usually mean the matching signals were weak or a baseline CSV was missing.
Output review flagged my product
Review flags identify copy, image, or policy risks that deserve human approval before import.
Captcha solver exhausted
Captcha exhaustion means the marketplace source resisted automated collection past the configured spend cap.
Worker timeout: what happened?
Worker timeouts are captured with run status, checkpoints when available, and retry guidance.