Overview
In Pricefy, CSV Catalog Import works like a full catalog rebase. That means every import is treated as a refreshed version of your catalog, not a “patch” that updates only a few rows.
So, the best way to update your catalog with new or updated information is to upload a complete, up-to-date CSV of your entire catalog each time.
Key concept: CSV Import = Catalog rebase
When you import a CSV, Pricefy expects that file to represent the current truth of your catalog at that moment.
Practically, this means:
- If a product is in the CSV, Pricefy treats it as part of your active catalog (with the latest data from the file).
- If a product is missing from the CSV, Pricefy will treat it as no longer included in the rebased catalog (depending on your import settings and how your workspace handles missing items).
This is why we recommend thinking of imports as replacing the catalog snapshot, not applying incremental updates.
Best practice: always import the full catalog
To update catalog fields (e.g., price, cost, tags, availability, attributes, product URLs, etc.) you should:
- Export or generate your latest full catalog CSV from your source system (Shopify, WooCommerce, ERP/PIM, database, etc.).
- Make your changes in that full file (or in the system that generates it).
- Re-import the complete CSV into Pricefy.
This ensures:
- no missing products
- no stale data
- consistent product matching and reporting
What counts as “new or updated information”?
CSV import is typically used to update things like:
- new SKUs/products added to your store
- updated product titles
- updated brand/category
- cost updates
- tags updates
- GTIN/EAN updates
- internal product URLs
- any catalog fields Pricefy uses for filtering, organization, or reporting
Recommended workflow for continuous updates
Option A: Scheduled “full refresh” imports (recommended)
If you update your catalog frequently, treat your CSV as a recurring sync:
- Daily import (for fast-changing catalogs)
- Weekly import (for stable catalogs)
- After major catalog changes (new collection, seasonal launch, repricing)
Option B: One-off refreshes when needed
If your catalog changes occasionally, simply re-import the full CSV anytime you need to reflect updates in Pricefy.
Common mistakes to avoid
Mistake 1: Uploading only the rows that changed
Uploading a “delta” file (only updated SKUs) can cause confusion, because import is not designed to behave like an incremental patch.
Fix: Always upload the full catalog snapshot.
Mistake 2: Removing products unintentionally
If a SKU disappears from your CSV because your export was filtered or incomplete, it may be treated as removed from the rebased catalog.
Fix: Make sure your export includes all relevant products you want managed in Pricefy.
Mistake 3: Changing unique identifiers
If you change your SKU or primary identifier formatting, Pricefy may interpret items as new products rather than updates.
Fix: Keep your unique identifiers consistent across imports.
Quick checklist before importing
Before you upload your updated CSV, confirm:
- ✅ The CSV contains your entire current catalog
- ✅ SKUs/IDs are consistent with past imports
- ✅ Columns match what Pricefy expects (same headers/format)
- ✅ No accidental filtering (e.g., excluding out-of-stock items if you still want them tracked)
- ✅ Your updates are reflected in the correct rows
FAQ
Does Pricefy support incremental CSV updates?
Not as a primary workflow. Catalog import is essentially a full rebase—Pricefy expects a full snapshot of the catalog each time.
How often should I import?
It depends on how often your source catalog changes. Many stores import:
- weekly for stable catalogs
- daily for fast-moving catalogs or frequent merchandising changes
What if I only need to update one field (like tags or cost)?
You should still update that field in your full catalog CSV and re-import the complete file.
