{
  "title": "Check first. Import second.",
  "subtitle": "A product-led content campaign for CatalogOps",
  "author": "Oleg Gainutdinov / Ki33",
  "date": "2026-10-16",
  "demo": "https://spectacular-jalebi-c45e30.netlify.app/catalogops/",
  "disclosure": "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.",
  "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."
  },
  "slides": [
    {"id":"01","tag":"BEFORE YOU IMPORT","headline":["A CSV is a file.","An import is","a decision."],"body":["See what will change before","you update your catalogue."],"visual":"cover","alt":"CatalogOps campaign cover: A CSV is a file. An import is a decision. A supplier CSV moves into a review step before the catalogue."},
    {"id":"02","tag":"01 / PRODUCT IDENTITY","headline":["One SKU.","One product."],"body":["Match incoming rows to existing products.","Add a new SKU. Update an existing one."],"visual":"sku","alt":"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."},
    {"id":"03","tag":"02 / ROW VALIDATION","headline":["Bad rows", "shouldn't travel."],"body":["Check names, prices, stock and duplicate SKUs.","A file with errors is blocked."],"visual":"errors","alt":"An illustrated CSV validation list flags a duplicate SKU, a missing product name and a negative stock value. Fix the file before applying it."},
    {"id":"04","tag":"03 / BATCH PREVIEW","headline":["Preview the", "whole batch."],"body":["See new, updated, unchanged and invalid rows.","The preview does not change the catalogue."],"visual":"summary","alt":"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."},
    {"id":"05","tag":"04 / THE ACTUAL CHANGE","headline":["See what's", "actually changing."],"body":["For AU-101, review the incoming price and stock.","Then decide whether the update is right."],"visual":"change","alt":"Fictional product AU-101, Studio headphones, changes from 129 euros and 24 units to 119 euros and 30 units in the valid demo sample."},
    {"id":"06","tag":"05 / EXPLICIT APPROVAL","headline":["Fix errors.", "Then apply."],"body":["Correct the file and preview it again.","Apply the batch only when it is valid."],"visual":"approval","alt":"A three-step diagram shows a blocked file, a corrected preview and an explicit apply action. No changes are made during preview."},
    {"id":"07","tag":"06 / REPEATABLE IMPORTS","headline":["Same file.", "No extra products."],"body":["Import the same file again:","existing SKUs are matched, not duplicated."],"visual":"repeat","alt":"After the four-row sample has been applied, reimporting it shows zero new rows, zero updates and four unchanged rows."},
    {"id":"08","tag":"EXPLORE THE WORKFLOW","headline":["Check first.", "Import second."],"body":["Open CatalogOps. Try a sample import.","Review the rows before you apply."],"visual":"cta","alt":"Closing slide invites viewers to try the CatalogOps sample import. Independent browser demo with fictional data; no sign-up required."}
  ],
  "posts": [
    {
      "id":"01", "type":"LinkedIn / product introduction", "title":"The useful step before Import", "banner":["Your next import", "deserves a second look."],
      "copy":"A supplier sends a CSV. You need to update your product catalogue.\n\nBefore clicking Import, there is a useful question to ask: what will this file actually change?\n\nCatalogOps is my independent catalogue-operations project. It matches products by SKU, validates incoming rows and separates the preview from the apply step.\n\nIn the initial valid sample, four rows produce:\n- 1 new product\n- 2 updates\n- 1 unchanged product\n- 0 invalid rows\n\nYou can inspect those rows before saving the batch. There is also a deliberately invalid sample to explore what gets blocked.\n\nTry the sample import: {LINK}\n\nThe public demo runs in your browser with fictional data. It does not connect to a live store.\n\n#Ecommerce #ProductDesign #WebDevelopment",
      "instagram":"A file can be ready to open without being ready to import.\n\nSwipe through the checks behind a deliberate catalogue update: product identity, row validation, preview and approval.\n\nExplore the CatalogOps demo via the portfolio link in my bio, then choose “Try a sample import”.\n\nIndependent project. Fictional product data.\n\n#Ecommerce #UXDesign #ProductDesign #CatalogManagement",
      "proof":"Live demo: Try a sample import → Preview changes, starting from the initial catalogue.",
      "asset":"social/post-01.png"
    },
    {
      "id":"02", "type":"LinkedIn / educational", "title":"Three CSV checks worth making", "banner":["Before you import,", "check the rows."],
      "copy":"Three checks I would put before a catalogue import:\n\n1. Identity\nDoes each row have the right SKU? Are any SKUs repeated within the file? A product name alone is not a dependable identifier.\n\n2. Valid values\nIs the product name present? Is the price in the expected format? Is stock a non-negative whole number?\n\n3. A visible result\nWhich rows will add products, update them or leave them unchanged? Can the operator inspect that before applying anything?\n\nI 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.\n\nExplore the error sample: {LINK}\n\nIndependent browser demo using fictional product data.\n\n#EcommerceOperations #UXDesign #WebDevelopment",
      "proof":"Live demo: Import CSV → Load sample with errors → Preview changes.",
      "asset":"social/post-02.png"
    },
    {
      "id":"03", "type":"LinkedIn / technical trust", "title":"What happens when the same file returns?", "banner":["Same file.", "No extra products."],
      "copy":"What happens when someone imports the same supplier file twice?\n\nIn CatalogOps, SKU matching makes that question visible.\n\nApply the initial four-row sample once. Then preview exactly the same file again. The result is:\n- 0 new rows\n- 0 updated rows\n- 4 unchanged rows\n\nThat is a small interaction with a clear purpose: an unchanged file should not become extra products.\n\nThe project includes a browser demo and a separately downloadable PHP/SQLite implementation. Netlify hosts the browser demo; it does not run the PHP backend.\n\nTry the workflow: {LINK}\n\nIndependent project. Fictional data. The figures above describe the sample import, not customer or campaign results.\n\n#PHP #Ecommerce #SoftwareDevelopment",
      "proof":"Live demo: apply the initial valid sample, load the same sample again and preview. The second preview shows four unchanged rows.",
      "asset":"social/post-03.png"
    }
  ],
  "article": {
    "title":"Before you import a product CSV, check what will change",
    "metaTitle":"Product CSV imports: checks to make before applying an update",
    "metaDescription":"A practical guide to SKU matching, row validation and import previews, illustrated with the CatalogOps browser demo and fictional product data.",
    "slug":"product-csv-import-checklist",
    "intro":"A supplier file arrives. It contains new stock levels, revised prices and a few new products. The next action looks obvious: import it. But opening a CSV successfully does not tell you whether its rows are valid, whether they match the right products or what an update will do to your catalogue. Those are separate questions. A deliberate import workflow answers them before anything is applied.",
    "sections":[
      {"title":"Start with product identity", "paragraphs":["Before reviewing a price change, establish which product the row describes. Names can change, and different products can have similar names. In CatalogOps, the SKU is the matching key: an existing SKU updates its product, while a new SKU adds a product.","That also makes duplicate SKUs inside the incoming file worth checking. Two rows that point to the same product can carry conflicting instructions. Treat that as a problem to resolve in the source file, rather than a detail to discover after importing."]},
      {"title":"Validate the values, not just the column headings", "paragraphs":["The sample CSV uses five columns: sku, name, category, price and stock. Having those headings is a useful start, but each row still needs attention. A name can be missing. A price can use an invalid format. Stock can be negative or contain text where a whole number is expected.","CatalogOps includes a deliberately invalid sample so this behaviour can be explored directly. It contains a repeated SKU, an empty product name, a price with excessive decimal precision, negative stock and a stock value written as “ten”. The point is to make errors visible while there is still an opportunity to correct the file."]},
      {"title":"Separate the preview from the decision to apply", "paragraphs":["A preview should answer a simple question: what would happen if this file were applied? It should not quietly perform the update. In CatalogOps, the initial valid sample is classified as one new product, two updates, one unchanged product and zero invalid rows. The catalogue remains unchanged while that preview is being reviewed.","For a concrete example, the sample updates SKU AU-101, Studio headphones. Its price changes from €129.00 to €119.00, and stock changes from 24 to 30 units. These are fictional values, but the decision is realistic: the operator needs to check the intended product and the incoming values before approving the batch."]},
      {"title":"Resolve errors before applying the batch", "paragraphs":["A file that contains invalid rows should not look ready for approval. CatalogOps blocks applying a file with validation errors. Correct the source data, preview it again and review the revised result before applying it.","When a valid batch is applied, the demo records an import summary in the Activity view. This provides a place to inspect what happened after approval. It is a record of the update, not a substitute for checking the preview beforehand."]},
      {"title":"Try the same file twice", "paragraphs":["Repeated imports are a useful way to inspect matching behaviour. Start with the initial catalogue, apply the valid sample, then load that same sample and preview it again. In this example, the second preview shows zero new products, zero updates and four unchanged rows.","This is why the SKU rule matters beyond the first import. An unchanged source file is matched against existing products instead of being treated as a new set of products each time. If you deliberately change a price or stock value in the file, that is a different update and should be reviewed as such."]},
      {"title":"Explore the workflow yourself", "paragraphs":["Open CatalogOps and choose “Try a sample import”. Preview the valid file before applying it. Then explore the error sample and compare what the interface allows. You do not need a live store or a sign-up to try the public demo.","CatalogOps is an independent portfolio project. The Netlify version runs locally in the browser with fictional data, and imports stay on that device. A PHP/PDO and SQLite implementation is available separately from the project page. The public demo is not a hosted PHP application, a payment service or an ERP integration."]}
    ],
    "checklist":["Confirm the matching key and check for duplicate SKUs.","Check required values, price format and stock values.","Review new, updated, unchanged and invalid rows.","Correct errors and generate a fresh preview.","Apply the valid batch deliberately, then inspect its activity record."],
    "cta":"Try the CatalogOps sample import"
  },
  "landing": {
    "eyebrow":"CATALOGOPS / CATALOGUE OPERATIONS",
    "headline":"Your next import deserves a second look.",
    "subhead":"Match products by SKU, check incoming rows and review the result before applying a CSV update. Explore the workflow in the CatalogOps browser demo.",
    "primary":"Try the sample import",
    "secondary":"Read the import checklist",
    "microcopy":"No sign-up. Fictional product data. Changes stay in your browser.",
    "problemTitle":"A spreadsheet is only the starting point.",
    "problem":"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.",
    "steps":[
      {"title":"Add the file", "text":"Load a built-in sample, paste CSV content or choose a file with the expected columns."},
      {"title":"Review the rows", "text":"Inspect which rows are new, updated, unchanged or invalid. Correct errors before applying anything."},
      {"title":"Apply deliberately", "text":"Approve a valid batch, then inspect the import summary in Activity."}
    ],
    "proofTitle":"A small sample. A visible decision.",
    "proof":"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.",
    "closingTitle":"See the change before you make it.",
    "closing":"Try both sample files. Compare the previews. Decide when to apply.",
    "faq":[
      {"q":"Does the public demo connect to my store?", "a":"No. The browser demo uses fictional data and saves changes on your device. It has no live store, payment or external ERP connection."},
      {"q":"Can I inspect the backend implementation?", "a":"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."},
      {"q":"What CSV structure does this demo expect?", "a":"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."}
    ],
    "note":"Independent project by Oleg Gainutdinov / Ki33. This page is campaign copy for a portfolio demonstration, not a subscription offer."
  },
  "video": {
    "title":"Check first. Import second.",
    "duration":"30 seconds",
    "format":"1080 × 1920 / 9:16 / 30 fps",
    "status":"Production-ready script and storyboard; no finished video is included.",
    "direction":"Use actual screen recordings of the browser demo, with tight crops and the original UI proportions. The vertical storyboard cards are art direction, not product screenshots. Use restrained cuts and brief field highlights. Keep meaningful text within x=90–990 and y=250–1500. No simulated cursor clicks, fabricated screens or unlicensed audio. Voiceover is optional; captions must carry the full explanation.",
    "scenes":[
      {"time":"00:00–00:04","duration":4,"screen":["A CSV is a file.","An import is a decision."],"voice":"A CSV is a file. An import is a decision.","capture":"Show the initial catalogue, then the CSV header sku,name,category,price,stock. Reset the demo only before recording this initial state."},
      {"time":"00:04–00:09","duration":5,"screen":["Check the rows.","Keep errors out."],"voice":"Check the rows. Keep errors out.","capture":"Import CSV → Load sample with errors → Preview changes. Crop to the validation result and disabled Apply control. Wait for the actual result to appear before capturing."},
      {"time":"00:09–00:14","duration":5,"screen":["Preview first.","Nothing has changed yet."],"voice":"Preview the update before anything changes.","capture":"Load valid sample → Preview changes. Show the initial summary: 1 new, 2 updated, 1 unchanged, 0 invalid."},
      {"time":"00:14–00:20","duration":6,"screen":["Review AU-101.","€119.00 / 30 units"],"voice":"Review the incoming price and stock. Then apply the valid batch.","capture":"Highlight the actual AU-101 row in the preview. Click Apply 4 rows once, then capture Activity showing 1 new, 2 updated and 1 unchanged."},
      {"time":"00:20–00:25","duration":5,"screen":["Same file again?", "4 unchanged rows."],"voice":"Preview the same file again: four unchanged rows.","capture":"Try a sample import → Preview changes after the first apply. Record 0 new, 0 updated, 4 unchanged, 0 invalid. Do not reset between these two imports."},
      {"time":"00:25–00:30","duration":5,"screen":["Check first.", "Import second."],"voice":"Explore CatalogOps. Try the sample import.","capture":"End card: CatalogOps / Try the sample import / Independent browser demo. Fictional data. Put the working demo link in the post caption."}
    ],
    "caption":"A closer look at a catalogue update: validate the rows, preview the changes and apply deliberately. Explore my independent CatalogOps demo: {LINK}\n\nFictional product data. Browser demo; no live store connection."
  },
  "email": {
    "subject":"Before your next CSV import, take a second look",
    "preheader":"A small demo of SKU matching, validation and deliberate updates.",
    "body":"A product CSV can open correctly and still contain rows you would not want to apply.\n\nCatalogOps makes the review step visible. Load the sample, check which rows are new or updated, and inspect any validation errors before applying the batch.\n\nYou can also try the same valid file twice. After the first import, its four rows are unchanged on the second preview.\n\nExplore the demo: {LINK}\n\nNo sign-up is required. The public demo uses fictional data and saves changes only in your browser.\n\nOleg / Ki33",
    "usage":"Example newsletter copy. No mailing list, delivery automation or email sending has been set up."
  },
  "calendar":[
    {"day":"Day 1","channel":"LinkedIn","asset":"Post 01 + banner 01","purpose":"Introduce the review-before-apply workflow","cta":"Open the demo and try the sample import","content":"introduction"},
    {"day":"Day 2","channel":"Portfolio / blog","asset":"Educational article","purpose":"Explain the checks with a concrete sample","cta":"Try the valid and invalid samples","content":"article"},
    {"day":"Day 3","channel":"Instagram / LinkedIn document","asset":"Eight-slide carousel + caption","purpose":"Make the workflow easy to follow visually","cta":"Explore the demo via the caption or profile link","content":"carousel"},
    {"day":"Day 4","channel":"LinkedIn","asset":"Post 02 + banner 02","purpose":"Teach three practical CSV checks","cta":"Inspect the error sample","content":"validation"},
    {"day":"Day 5","channel":"Reels / Shorts","asset":"30-second video script and storyboard","purpose":"Guide production of a real workflow recording","cta":"Try the demo","content":"video"},
    {"day":"Day 6","channel":"LinkedIn","asset":"Post 03 + banner 03","purpose":"Show repeat-import behaviour","cta":"Apply once, preview the same file again","content":"repeat-import"},
    {"day":"Day 7","channel":"Existing opted-in newsletter","asset":"Email copy","purpose":"Invite existing readers to explore the demo","cta":"Try the sample import","content":"newsletter"}
  ],
  "measurement": {
    "status":"Proposed measurement plan. No results are available and no tracking has been installed.",
    "metrics":["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."],
    "events":["campaign_demo_visit", "sample_import_loaded", "import_preview_viewed", "import_applied"],
    "rules":["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."]
  }
}
