# Find added and removed supplier SKUs

**Use case:** 

Compare complete supplier snapshots to find added and removed SKUs. This synthetic example checks identifier presence only. Both snapshots must cover the same catalog population; a missing SKU does not prove discontinuation.

## Input

```json
{
  "baselineCsv": "sku,price,stock\nA-001,29.00,12",
  "currentCsv": "sku,price,stock\nA-001,31.00,8",
  "rightsConfirmed": true,
  "comparison": {
    "baseline": [
      {
        "sku": "A-001",
        "price": "19.99"
      },
      {
        "sku": "A-002",
        "price": "8.00"
      }
    ],
    "current": [
      {
        "sku": "A-001",
        "price": "21.99"
      },
      {
        "sku": "A-003",
        "price": "5.00"
      }
    ],
    "keyField": "sku",
    "fields": []
  }
}
```

## Output

```json
{
  "before": {
    "label": "Baseline products",
    "format": "number"
  },
  "after": {
    "label": "Current products",
    "format": "number"
  },
  "added": {
    "label": "Added products",
    "format": "number"
  },
  "removed": {
    "label": "Removed products",
    "format": "number"
  },
  "changed": {
    "label": "Changed products",
    "format": "number"
  },
  "unchanged": {
    "label": "Unchanged products",
    "format": "number"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The Supplier Feed Change Checker — CSV/JSON SKU Diff Actor is ready to run with the inputs already set for "Find added and removed supplier SKUs". [Sign up or log in](https://console.apify.com/create-task-from-example/8nrVeaFoYvKcGoPau) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Find added and removed supplier SKUs" task

The Supplier Feed Change Checker — CSV/JSON SKU Diff Actor will start running based on the input automatically. You can also change all the input fields, like previous catalog csv, current catalog csv, and more, to match your specific use case.

### 3. Receive the "Find added and removed supplier SKUs" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as baseline products, current products, added products, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Find added and removed supplier SKUs" task via API](https://apify.com/autonome_bots/supplier-feed-change-checker.md).

## About this Actor

This example demonstrates how to use [Supplier Feed Change Checker — CSV/JSON SKU Diff](https://apify.com/autonome_bots/supplier-feed-change-checker.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/autonome_bots/supplier-feed-change-checker.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/autonome_bots/supplier-feed-change-checker.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).