Catalogue Import Rescue avatar

Catalogue Import Rescue

Pricing

$500.00 / 1,000 completed ready batches

Go to Apify Store
Catalogue Import Rescue

Catalogue Import Rescue

Merge and validate supplied product CSV files against explicit mappings. Preserve text IDs, normalize declared types and dates, remove authorized exact duplicates, and hold conflicting data. Download a CSV, audit and source lineage.

Pricing

$500.00 / 1,000 completed ready batches

Rating

0.0

(0)

Developer

Rajhan

Rajhan

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

21 hours ago

Last modified

Categories

Share

Merge supplied product CSV files and apply explicit field rules before a business import. Preserve text IDs, normalize declared types and dates, and trace released records back to their source.

Price: $0.50 USD per completed READY batch. One batch can contain up to 10,000 combined records within the limits below. No startup, per-row or dataset-item fee. HOLD and invalid requests have no completed-delivery event. Standard platform usage is included in this price. Check Apify's displayed price and set a maximum event budget of at least $0.50 before running. Own runs and free-credit tests are not paid demand or revenue.

Use the tool

  1. Open Input and restore the synthetic example to see the exact structure.
  2. Supply sources: one to five objects with a simple .csv filename in name and its full UTF-8 text in csv. No URL is fetched and no external account is connected.
  3. Supply an explicit contract: filenames in the same order, delimiter, all source-to-target column mappings, business key and exact-duplicate policy. Confirm that you are authorized to process the supplied data.
  4. Start the run. Read OUTPUT in Delivery files before using other records. complete: true means all listed delivery artifacts were saved.
  5. Download DELIVERY.zip. The default dataset contains a processing and billing summary; the CSV and diagnostics are in Delivery files. For READY, it contains ready.csv, audit.json, issues.json, REPORT.md and lineage.json. For HOLD, it contains diagnostics and no ready CSV. Correct the source or explicitly revise the contract and start a new run.

Supported rules

  • Text: preserves leading zeros. Trimming happens only where declared. Formula-like text beginning with =, +, - or @ after whitespace is held, even if otherwise legitimate.
  • Decimal: non-negative dot-decimal price, at most two decimal places, formatted to two places. No rounding or currency conversion.
  • Integer: non-negative whole number; identifiers requiring leading zeros should use text.
  • Date: explicitly declare %Y-%m-%d, %d/%m/%Y or %m/%d/%Y; output is ISO date text.
  • Allowed values and required fields: explicit per-column rules.
  • Duplicates: removal only when authorized and records are identical after declared normalization. Conflicting records with the same business key hold the whole delivery. Lineage retains every contributing source coordinate.

All source headers must be mapped exactly once. Reordered headers are accepted; extra, missing or duplicate headers are held. Empty parsed records are omitted and counted. Invalid values are reported by record/column and issue code; the issue list does not repeat raw cell values. Supplied source text is never overwritten.

Limits and scope

Five files; two million UTF-8 bytes each; 10,000 combined parsed records after headers; 30 columns; 2,000 characters per cell. Comma, semicolon or tab is explicit. UTF-8 BOM and properly quoted multiline cells are supported. Source filenames must be simple CSV basenames. No Excel files, OCR, scraping, factual enrichment, inferred missing values, third-party account changes or direct shop imports.

READY means structural compliance with your declared contract. It does not guarantee that Shopify, WooCommerce or any other destination will accept the file. Verify the destination's current import specification and inspect output before importing. This tool does not make financial, medical or other consequential decisions.

Data handling

Use non-personal product catalogue data that you may lawfully process. Do not submit passwords, API keys, customer/contact lists, employee records, special-category data or employer/client confidential information. The Actor uses limited permissions and only its own run storage. It sends no input to an LLM or external data service. Apify hosts the run and its records under its applicable storage, retention and access controls. Download anything you need to retain. The operator does not promise a separate archival service or a particular UK-only processing region.

Automation and support

An existing workflow may send the same declared contract with new authorized CSV text through the Apify API and read OUTPUT after completion. Each new batch needs a new run. No external API key is required by this Actor itself.

Report reproducible defects through this Actor's Issues tab, using a synthetic example and issue codes rather than private data. The scope is software functionality and documented input rules; custom data repair and destination import work are not included. No accuracy testimonials, customer results or earnings are claimed.