# Check first. Import second.

A product-led content campaign for CatalogOps

Independent portfolio campaign. CatalogOps is a self-initiated project. Product examples use fictional data. These assets have not been published as a live campaign; no audience, revenue or conversion results are claimed.

## Campaign brief

**audience:** Small e-commerce teams and store owners who receive product, price and stock updates in CSV files.

**problem:** A file can look ready while still containing duplicate SKUs, missing names or invalid stock values. The operator needs to know what will change before applying an update.

**objective:** Help a prospective client understand a real product workflow and encourage an intentional visit to the working demo.

**positioning:** A focused catalogue workspace that makes CSV updates visible before they are applied.

**promise:** Review new, updated, unchanged and invalid rows before applying a batch.

**cta:** Try the sample import

**voice:** Clear, calm and specific. Explain the workflow with visible examples. Avoid hype, invented business results and claims of production integrations.

**creative:** Editorial typography, forest green, warm paper and spreadsheet-inspired diagrams. The visual sequence moves from a familiar CSV file to a considered import decision.

**scope:** Campaign strategy, English copy, an eight-slide carousel, three social posts and banners, an educational article, landing-page copy, a 30-second video script/storyboard, an email and a proposed publishing sequence.

**measurement:** If published: measure tagged-link clicks, demo visits and the sample-import funnel. No analytics instrumentation or campaign results are included in this package.

## LinkedIn / product introduction: The useful step before Import

A supplier sends a CSV. You need to update your product catalogue.

Before clicking Import, there is a useful question to ask: what will this file actually change?

CatalogOps is my independent catalogue-operations project. It matches products by SKU, validates incoming rows and separates the preview from the apply step.

In the initial valid sample, four rows produce:
- 1 new product
- 2 updates
- 1 unchanged product
- 0 invalid rows

You can inspect those rows before saving the batch. There is also a deliberately invalid sample to explore what gets blocked.

Try the sample import: https://spectacular-jalebi-c45e30.netlify.app/catalogops/?utm_source=linkedin&utm_medium=organic_social&utm_campaign=catalogops_check_first&utm_content=01

The public demo runs in your browser with fictional data. It does not connect to a live store.

#Ecommerce #ProductDesign #WebDevelopment

Asset: social/post-01.png

## LinkedIn / educational: Three CSV checks worth making

Three checks I would put before a catalogue import:

1. Identity
Does each row have the right SKU? Are any SKUs repeated within the file? A product name alone is not a dependable identifier.

2. Valid values
Is the product name present? Is the price in the expected format? Is stock a non-negative whole number?

3. A visible result
Which rows will add products, update them or leave them unchanged? Can the operator inspect that before applying anything?

I built these checks into CatalogOps as a small, focused product workflow. The error sample deliberately includes a repeated SKU, a missing name and invalid numeric values.

Explore the error sample: https://spectacular-jalebi-c45e30.netlify.app/catalogops/?utm_source=linkedin&utm_medium=organic_social&utm_campaign=catalogops_check_first&utm_content=02

Independent browser demo using fictional product data.

#EcommerceOperations #UXDesign #WebDevelopment

Asset: social/post-02.png

## LinkedIn / technical trust: What happens when the same file returns?

What happens when someone imports the same supplier file twice?

In CatalogOps, SKU matching makes that question visible.

Apply the initial four-row sample once. Then preview exactly the same file again. The result is:
- 0 new rows
- 0 updated rows
- 4 unchanged rows

That is a small interaction with a clear purpose: an unchanged file should not become extra products.

The project includes a browser demo and a separately downloadable PHP/SQLite implementation. Netlify hosts the browser demo; it does not run the PHP backend.

Try the workflow: https://spectacular-jalebi-c45e30.netlify.app/catalogops/?utm_source=linkedin&utm_medium=organic_social&utm_campaign=catalogops_check_first&utm_content=03

Independent project. Fictional data. The figures above describe the sample import, not customer or campaign results.

#PHP #Ecommerce #SoftwareDevelopment

Asset: social/post-03.png

## Instagram carousel caption

A file can be ready to open without being ready to import.

Swipe through the checks behind a deliberate catalogue update: product identity, row validation, preview and approval.

Explore the CatalogOps demo via the portfolio link in my bio, then choose “Try a sample import”.

Independent project. Fictional product data.

#Ecommerce #UXDesign #ProductDesign #CatalogManagement

## Carousel transcript and alt text

### Slide 01

A CSV is a file. An import is a decision.

See what will change before you update your catalogue.

Alt text: CatalogOps campaign cover: A CSV is a file. An import is a decision. A supplier CSV moves into a review step before the catalogue.

### Slide 02

One SKU. One product.

Match incoming rows to existing products. Add a new SKU. Update an existing one.

Alt text: Two supplier rows are matched by SKU. AU-101 matches an existing product; DS-205 is a new product. The name is not used as the identifier.

### Slide 03

Bad rows shouldn't travel.

Check names, prices, stock and duplicate SKUs. A file with errors is blocked.

Alt text: An illustrated CSV validation list flags a duplicate SKU, a missing product name and a negative stock value. Fix the file before applying it.

### Slide 04

Preview the whole batch.

See new, updated, unchanged and invalid rows. The preview does not change the catalogue.

Alt text: The initial valid sample contains one new row, two updated rows, one unchanged row and zero invalid rows. These are fictional sample counts, not campaign results.

### Slide 05

See what's actually changing.

For AU-101, review the incoming price and stock. Then decide whether the update is right.

Alt text: Fictional product AU-101, Studio headphones, changes from 129 euros and 24 units to 119 euros and 30 units in the valid demo sample.

### Slide 06

Fix errors. Then apply.

Correct the file and preview it again. Apply the batch only when it is valid.

Alt text: A three-step diagram shows a blocked file, a corrected preview and an explicit apply action. No changes are made during preview.

### Slide 07

Same file. No extra products.

Import the same file again: existing SKUs are matched, not duplicated.

Alt text: After the four-row sample has been applied, reimporting it shows zero new rows, zero updates and four unchanged rows.

### Slide 08

Check first. Import second.

Open CatalogOps. Try a sample import. Review the rows before you apply.

Alt text: Closing slide invites viewers to try the CatalogOps sample import. Independent browser demo with fictional data; no sign-up required.

## Landing-page copy

CATALOGOPS / CATALOGUE OPERATIONS

# Your next import deserves a second look.

Match products by SKU, check incoming rows and review the result before applying a CSV update. Explore the workflow in the CatalogOps browser demo.

CTA: Try the sample import

Secondary CTA: Read the import checklist

No sign-up. Fictional product data. Changes stay in your browser.

### A spreadsheet is only the starting point.

A missing name, a repeated SKU or an invalid stock value can turn a routine update into a question mark. Make the matching rules and the intended changes visible before applying the file.

### Add the file

Load a built-in sample, paste CSV content or choose a file with the expected columns.

### Review the rows

Inspect which rows are new, updated, unchanged or invalid. Correct errors before applying anything.

### Apply deliberately

Approve a valid batch, then inspect the import summary in Activity.

### A small sample. A visible decision.

From the initial catalogue, the valid sample produces 1 new product, 2 updates and 1 unchanged row. Preview it without changing the catalogue. After applying it, preview the same file again: all 4 rows are unchanged.

### See the change before you make it.

Try both sample files. Compare the previews. Decide when to apply.

### Does the public demo connect to my store?

No. The browser demo uses fictional data and saves changes on your device. It has no live store, payment or external ERP connection.

### Can I inspect the backend implementation?

Yes. The product page links to a downloadable PHP/PDO and SQLite application and backend test results. The Netlify preview itself does not execute PHP.

### What CSV structure does this demo expect?

The columns are sku, name, category, price and stock. The interface specifies UTF-8, a maximum file size of 256 KB and up to 500 products.

Independent project by Oleg Gainutdinov / Ki33. This page is campaign copy for a portfolio demonstration, not a subscription offer.

## Newsletter

Subject: Before your next CSV import, take a second look

Preheader: A small demo of SKU matching, validation and deliberate updates.

A product CSV can open correctly and still contain rows you would not want to apply.

CatalogOps makes the review step visible. Load the sample, check which rows are new or updated, and inspect any validation errors before applying the batch.

You can also try the same valid file twice. After the first import, its four rows are unchanged on the second preview.

Explore the demo: https://spectacular-jalebi-c45e30.netlify.app/catalogops/?utm_source=newsletter&utm_medium=email&utm_campaign=catalogops_check_first&utm_content=email

No sign-up is required. The public demo uses fictional data and saves changes only in your browser.

Oleg / Ki33

Example newsletter copy. No mailing list, delivery automation or email sending has been set up.

## Measurement plan

Proposed measurement plan. No results are available and no tracking has been installed.

- Tagged-link clicks and demo landing visits by channel and asset.
- Visits that trigger the sample-import action.
- Sample-import visits that reach a preview.
- Valid previews followed by an explicit apply action.

Proposed events (not implemented): campaign_demo_visit, sample_import_loaded, import_preview_viewed, import_applied

- Separate the valid and invalid sample paths. A blocked invalid file is expected behaviour, not an abandoned valid import.
- Deduplicate repeated events within a session when reporting funnel conversion.
- Use the same reporting window across assets. Report sample size alongside rates.
- Do not collect uploaded CSV contents, product values or personal information in analytics.
