CATALOG CHANGE REVIEWEARLY ACCESS

NEW CATALOG REVIEW

Prepare a catalog review.

Catch risky price and catalog edits. Leave with a decision worksheet for the person making the change.

View sample review
  1. 01 Prepare snapshots
  2. 02 Inspect differences
  3. 03 Record decisions
First review? Prepare your two files.

Use catalog data you own or have permission to review. Amazon, Shopify and Mercado Libre snapshots are supported. Start with a few existing SKUs from one seller, channel, market and currency.

  1. Get your current values.

    Use a CSV or tab-separated export with one row per variant, or fill in the blank 12-column template. Native exports need mapping below.

    Download blank catalog template
  2. Make a proposed copy.

    Duplicate the current file, then edit only the planned values. Keep channel, market and SKU unchanged to match rows. Save both files as CSV.

  3. Decide and take the record.

    Compare, inspect the flags, and record hold or keep with a reason. Export a CSV decision worksheet and the full evidence JSON.

    Go to the two-file comparison ↓

Free review. No card required. Up to 200 rows and 256 KB per file; 20 saved reviews per browser. The $49 page repair pack is a separate optional tool. See scope and pricing.

COMPARE YOUR SNAPSHOTS

Bring your current and proposed catalogs.

Use one client or seller business per review and one account per channel and market. Keep market labels and SKUs consistent. Use only catalog data you are authorized to process. Remove customer, order, and payment details before selecting a file.

The mapper reads files in this browser. Preview and apply each mapping before comparing. Keep the same SKU scope in both snapshots. No Excel workbooks or marketplace publishing feeds are created.

Template and mapping guide

This is a Canopy review format. It is not a Shopify import or Amazon feed. Use the guided mapper below to select source columns, or prepare all 12 columns yourself. Mapping runs in this browser; only the applied CSV is submitted when you compare. One row per variant, up to 200 rows and 256 KB per file.

Keep every header, even when a value is unknown:

channel, market, sku, product_id, title, price, currency, status, image_url, unit_cost, fee_percent, fulfillment_cost

  • channel: shopify, amazon, or mercadolibre. market: a consistent market label, such as us or amazon.com. sku: the same variant SKU in both files.
  • product_id: Shopify variant ID, Amazon ASIN, or Mercado Libre item ID, if known. title, price, currency: seller-supplied values. Currency uses three uppercase letters. Prices and costs use at most two decimal places.
  • status: normalize to active, inactive, draft, archived, or blank. image_url: a reference only; images are not fetched.
  • unit_cost, fee_percent, fulfillment_cost: enter your costs for that snapshot and currency. Enter 15 for 15% fees. A known zero must be 0. Leave unknown costs blank.
  • Include the same intended product scope in both files. Missing rows are flagged for review, not treated as deletions. Platform category, variation, and publishing rules require separate checks.

An internal label for this review, not a shared client workspace. Required when adding period evidence.

01 / Current catalog

The values you use today.

Choose a catalog file to map its columns, or paste a Canopy-format CSV below.

02 / Proposed catalog

The update you plan to review. Keep the same SKU scope.

Choose a catalog file to map its columns, or paste a Canopy-format CSV below.

Add SKU contribution history · optional

Bring sales, refunds, fees, product costs, fulfillment, and ad spend for one observed period. Find SKUs with weak economics alongside your proposed changes.

Period evidence mapping guide

Aggregate one row per channel, market, and SKU for the same client / seller and date range. Use the exact catalog identifiers and the current catalog currency. For a new SKU, use its proposed currency. Unmatched or duplicate rows are rejected. This is a Canopy template, not a native Amazon settlement or Mercado Libre export.

channel, market, sku, currency, units_sold, sales, refunds, product_cost, platform_fees, fulfillment_cost, ad_spend

  • units_sold: whole units sold in the period, before returns. Blank means unknown.
  • sales: product revenue after discounts, before refunds, excluding tax. refunds: refunded product revenue. Do not subtract refunds twice.
  • product_cost: total cost of goods sold, adjusted for any recoverable returned inventory. platform_fees, fulfillment_cost, ad_spend: total net expenses attributable to this SKU and period. Include each cost once.
  • Use positive expense amounts. Normalize signed settlement rows before upload. Blank amounts are unknown; enter 0 only when confirmed. Do not upload customer names, order IDs, payment details, or credentials.
  • Only SKUs in these catalogs are covered. Totals stay separate by currency. Tax, overhead, and unlisted costs are excluded. This is contribution history, not net profit or a sales forecast.
Download period example

Choose a Canopy-format CSV. Up to 200 rows and 256 KB.

Deleting a review removes its active report, decisions, and feedback. Backup copies and files already downloaded may remain.

Your recent reviews

Private to this browser

Your first review starts here.

Saved comparisons will appear in this browser. See a complete fictional review before preparing your files.

View sample review

Per-unit checks use your supplied snapshots. Per-unit contribution = price minus unit cost, percentage fees, and fulfillment cost. Advertising, returns, tax, and overhead are excluded. Values are per unit, not a profit forecast. No live store connection, platform validation, or automatic publishing.