# Shopify Scraper - Products & Brand Profiles (`datalayer/shopify-brand-intelligence`) Actor

Everyone dumps /products.json. This assembles a brand profile: catalogue size, median-based price positioning, discount depth and genuine launch cadence measured from created\_at — not published\_at, which stores bulk-refresh and which fakes growth.

- **URL**: https://apify.com/datalayer/shopify-brand-intelligence.md
- **Developed by:** [Datalayer](https://apify.com/datalayer) (community)
- **Categories:** E-commerce, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.35 / 1,000 products

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Shopify Store Scraper — brand profiles, not just products

Get a **complete profile of any Shopify store**: how big the catalogue is, where it prices, how heavily it discounts, and how fast it publishes new products. Plus the full product catalogue if you want it.

Point it at a list of domains and get one comparable row per brand.

### Why this is different

Every other Shopify scraper fetches the product feed and hands you a dump. That is fine if you want products. It is useless if you want to *evaluate a brand*.

Nobody buying this data actually wants products. App vendors want to know which stores are big enough to sell to. Wholesalers want to know where a brand prices. Agencies want to know who is growing. Investors want catalogue velocity.

This actor answers those questions directly:

| Signal | What it tells you |
|---|---|
| **Product and variant count** | Catalogue depth, and whether they are a real operation |
| **Price min / median / max** | Where they actually sit in the market |
| **Price positioning** | Budget, mid-market, premium or luxury |
| **Discount share** | Percentage of catalogue on sale — a permanently high number means a discount-led brand |
| **New products last 30 / 90 days** | Whether they are actively trading or dormant |
| **Monthly publish rate** | The growth signal, in one number |
| **Top product types, vendors, tags** | What they actually sell |

#### Median, not mean

Price positioning uses the **median**, not the average. One £5,000 outlier in a £35 catalogue would drag a mean into "luxury" and mislabel the brand entirely. The median resists that. Small detail, and it is the difference between a usable dataset and a misleading one.

#### Honest discount detection

A product counts as on sale only when its compare-at price genuinely **exceeds** its price. Many stores leave compare-at set equal to price, which naive scrapers count as a discount and inflate the number.

### Input

```json
{
  "domains": ["allbirds.com", "gymshark.com"],
  "includeProfile": true,
  "includeProducts": false
}
```

Paste bare domains or full URLs — `https://www.allbirds.com/collections/mens` normalises to `allbirds.com` automatically.

Set `includeProducts: false` for a fast, tiny dataset when you only want to compare brands. Set `maxProductsPerStore` to cap large catalogues.

### Use cases

- **Shopify app and SaaS sales** — qualify stores by catalogue size and price band before you pitch
- **Wholesale and dropshipping** — find brands at the right price point
- **Competitive analysis** — track a rival's pricing, discounting and launch cadence
- **Agency prospecting** — a store publishing 40 products a month has budget; one publishing zero does not
- **Market research** — profile an entire category in one run

### Reliability

One store failing never fails the run. Point it at 200 domains and the handful that are password-protected or not on Shopify come back as a clear record of what failed and why — you keep the rest. You are only charged for rows actually returned.

Stores that are not Shopify get an explicit message saying so, rather than an empty result you have to diagnose yourself.

Data comes from the public JSON endpoints Shopify exposes by default on every store. No login, no browser automation, no session.

### Notes

Price bands are currency-naive — compare stores in the same currency. The currency is included on every profile row so you can group correctly.

Unofficial and not affiliated with Shopify. Product data belongs to the respective stores; use it in line with applicable laws and terms.

# Actor input Schema

## `domains` (type: `array`):

One per store. Paste a domain or a full URL - allbirds.com, https://www.gymshark.com, either works.

## `includeProfile` (type: `boolean`):

One summary row per store: catalogue size, price band, discount share and publishing rate. This is the part other scrapers do not produce.

## `includeProducts` (type: `boolean`):

Every product with prices, variants and images. Turn off for a much smaller dataset when you only want the profile.

## `maxProductsPerStore` (type: `integer`):

Cap the catalogue pulled per store. Large brands can carry thousands of products.

## `proxyConfiguration` (type: `object`):

Optional. These are public JSON endpoints and usually work without one.

## Actor input object example

```json
{
  "domains": [
    "allbirds.com",
    "gymshark.com"
  ],
  "includeProfile": true,
  "includeProducts": true,
  "maxProductsPerStore": 1000,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `all` (type: `string`):

Brand profiles and products.

## `profiles` (type: `string`):

One summary row per store - the fastest way to compare brands.

## `products` (type: `string`):

Full product catalogue with prices and variants.

## `csv` (type: `string`):

Everything as a CSV download.

## `runSummary` (type: `string`):

Counts and any store that could not be reached.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "domains": [
        "allbirds.com",
        "gymshark.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("datalayer/shopify-brand-intelligence").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "domains": [
        "allbirds.com",
        "gymshark.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("datalayer/shopify-brand-intelligence").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "domains": [
    "allbirds.com",
    "gymshark.com"
  ]
}' |
apify call datalayer/shopify-brand-intelligence --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,datalayer/shopify-brand-intelligence"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/zB9IqByts9Akd0fKJ/builds/KEGfeh2WlqusF1yUg/openapi.json