Japan Denim Restock & Price Monitor avatar

Japan Denim Restock & Price Monitor

Pricing

from $2.00 / 1,000 product variant rows

Go to Apify Store
Japan Denim Restock & Price Monitor

Japan Denim Restock & Price Monitor

Monitor official Japanese denim brand stores (WAREHOUSE & Co., TCB jeans): back in stock, sold out, price changes, new models and sizes per waist, with lot number, fabric weight (oz), wash and fit fields.

Pricing

from $2.00 / 1,000 product variant rows

Rating

0.0

(0)

Developer

Task Data

Task Data

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

Track stock, prices and new arrivals of Japanese denim at the official online stores of WAREHOUSE & Co. (Osaka) and TCB jeans (Kojima, Okayama) in one run. You get one row per colour × size (variant) with price, in-stock flag, lot / model, fabric weight (oz), wash, waist size and URL, and in monitoring mode only what changed since the last run: back in stock, sold out, price up, price down, new model, new size, purchase limit added. No coding needed.

Built for people who follow Japanese jeans and denim jackets — denim shops, buyers doing price research, and enthusiasts waiting for one waist size — without checking each brand's website by hand. On 2026-10-10, 486 of the 1,004 jean / jacket / overall variants in these two stores were sold out.

What data can you extract?

FieldDescription
storeName, storeId, storeDomain, marketWhich store the row comes from (japan = Japanese store, global = English store)
title, variantTitleProduct title and variant as the store writes them (e.g. Lot 800XX (STANDARD) NON WASH / INDIGODENIM NONWASH / 32)
brand, subBrandThe store's vendor field, and a line named in WAREHOUSE's own tags (DENIME, DEADSTOCK BLUE, Duck Digger, John Gluckow, Greenebaum Brothers, 2nd-Hand series)
lotNumber, modelNameLot number from the title (Lot 1001XX → 1001XX; TCB has none) and the title without weight/wash words (50's Jeans 13.5oz / One-Wash → 50's Jeans)
garmentTypebottoms, jacket, overall, shirt, tshirt, sweat, headwear, footwear, accessory, care, other
denimStatedtrue when the title, colour option, tags or fabric line say denim
fabricOz, fabricOzSourceFabric weight in ounces and where it was read (title, tags or the description's fabric line)
wash, washTextone_wash, non_wash (raw / rigid) or used_wash, and the words it was read from
fitslim_tapered, tapered, slim, straight, baggy, wide, relaxed — only when a trouser's title or tag names it
editioncollaboration or special_order when the title says so
color, size, waistInch, inseamInchColour option, size label, waist in inches (trousers/overalls) and inseam when the store has a length option
preorder, purchaseLimitQty, purchaseLimitTextPre-order flag (title/tag), purchase limit per customer (お一人様3点まで → 3) and a short excerpt (≤120 characters) of that sentence
price, compareAtPrice, currencyCurrent price and the currency the store answered in (JPY is requested)
availableThe store's in-stock flag for that exact colour × size
changeType, changesrestocked, sold_out, price_up, price_down, new_product, new_variant, preorder_started, purchase_limit_changed, removed, first_run, unchanged
previousPrice, previousAvailable, previousPurchaseLimitQty, priceChange, priceChangePct, previousRunAt, firstSeenAtValues at the previous run and the difference
productUrl, variantUrl, imageUrlProduct page, page with the variant preselected, image URL on the store's CDN (reference only)
sku, productId, variantId, handle, productType, tags, timestampsIdentifiers and the store's own labels

Only what the store states is filled in. Fabric weight, wash and fit are null when the store does not write them — for example, WAREHOUSE states a weight for 59 of its 431 trouser/jacket variants ("light-ounce denim" without a number stays null). Product descriptions are not copied (only the ≤120-character purchase-limit sentence), and images are referenced by URL, not downloaded.

Why monitor Japanese denim stores?

  1. Restock alerts for your size — sizes that are sold out show up again as in stock when the store restocks. Schedule the Actor with sizes: ["32"] and changeTypes: ["restocked", "new_variant"] and get only the jeans that just became available in your size.
  2. Price tracking — price_up / price_down rows give the date, old price, new price and percentage per size.
  3. New releases — new_product rows show new models and colours the day they are published.
  4. Price and assortment research — a full snapshot of lots, weights, washes, sizes and prices across both brands, ready for a spreadsheet or BI tool.
  5. AI agents / RAG — the Actor is callable through the Apify MCP server, so an AI assistant can answer "which 14 oz one-wash jeans are in stock in W32 right now?" with live data.

How to use it (no coding)

  1. Click Try for free.
  2. Pick the stores, and optionally garment types (default: jeans/trousers, jackets, overalls), washes, sizes (e.g. 32) and a fabric weight range.
  3. Choose Mode: changes (monitoring) or snapshot (everything now).
  4. Click Start. The first changes run saves a baseline of every variant and returns rows as first_run (up to maxItems).
  5. Open Schedules and run it every few hours or daily. From the second run on you get only the changes — connect a webhook, Slack, email or Google Sheets integration to be notified.

Input example

{
"mode": "changes",
"stores": ["warehouse", "tcb-jeans"],
"garmentTypes": ["bottoms", "jacket", "overall"],
"denimStatedOnly": false,
"washes": [],
"sizes": ["32"],
"keywords": [],
"changeTypes": ["restocked", "new_product", "new_variant", "price_up", "price_down"],
"maxItems": 100,
"stateStoreName": "japan-denim-restock-monitor",
"proxyConfiguration": { "useApifyProxy": true }
}
  • mode — changes returns only differences from the previous run; snapshot returns every matching variant. When omitted (API calls), the default is snapshot.
  • garmentTypes — defaults to ["bottoms", "jacket", "overall"]; pass [] for everything (T-shirts, sweats, hats, bandanas, denim detergent…).
  • denimStatedOnly — keeps only items the store calls denim. Off by default because TCB does not write "denim" in the titles of several denim jackets.
  • washes, minFabricOz / maxFabricOz — drop items whose wash or weight the store does not state.
  • sizes — exact size labels or waists ("32", "M", "38").
  • keywords — optional lot numbers or model names (1001XX, S40). デニム → denim and Chinese words such as 牛仔 → denim / デニム are retried automatically when they match nothing in a store.
  • maxItems — total rows for the run (default 100), shared fairly between the selected stores.
  • stateStoreName — a named key-value store in your own Apify account that remembers the previous prices and stock. Use a different name for each schedule with different filters.

Output example

{
"storeId": "warehouse",
"storeName": "WAREHOUSE & Co.(ウエアハウス)",
"storeDomain": "warehouse-shop.jp",
"market": "japan",
"productId": "12227666772286",
"variantId": "52923721646398",
"handle": "lot-800xxstandard-non-wash",
"title": "Lot 800XX (STANDARD) NON WASH",
"variantTitle": "INDIGODENIM NONWASH / 32",
"brand": "WAREHOUSE&Co",
"subBrand": null,
"modelName": "Lot 800XX (STANDARD)",
"lotNumber": "800XX",
"garmentType": "bottoms",
"denimStated": true,
"fabricOz": 14.5,
"fabricOzSource": "tags",
"wash": "non_wash",
"washText": "NON WASH",
"fit": null,
"edition": null,
"color": "INDIGODENIM NONWASH",
"size": "32",
"waistInch": 32,
"inseamInch": null,
"preorder": false,
"purchaseLimitQty": null,
"purchaseLimitText": null,
"sku": null,
"productType": "PANTS",
"tags": ["14.5OZ", "WAREHOUSE", "メンフィスコットン", "単一綿", "定番モデル"],
"price": 29700,
"compareAtPrice": null,
"currency": "JPY",
"available": true,
"imageUrl": "https://cdn.shopify.com/s/files/1/0970/9620/4606/files/132358497_31e30feb-51f2-40ea-956e-89884b588d52.webp?v=1767844248",
"productUrl": "https://warehouse-shop.jp/products/lot-800xxstandard-non-wash",
"variantUrl": "https://warehouse-shop.jp/products/lot-800xxstandard-non-wash?variant=52923721646398",
"publishedAt": "2026-01-08T12:52:33+09:00",
"productCreatedAt": "2026-01-08T12:52:31+09:00",
"variantUpdatedAt": "2026-10-10T23:02:36+09:00",
"scrapedAt": "2026-10-10T14:30:00.000Z",
"changeType": "restocked",
"changes": ["restocked"],
"previousPrice": 29700,
"previousAvailable": false,
"previousPurchaseLimitQty": null,
"priceChange": 0,
"priceChangePct": 0,
"previousRunAt": "2026-10-10T08:30:00.000Z",
"firstSeenAt": "2026-10-10T08:30:00.000Z"
}

(The product data above is real; the availability and change values illustrate how a restocked row looks.)

Field notes

  • changeType is the most important change; changes lists all of them (a size can be restocked and price_up in the same run).
  • Currency: TCB's store can show prices in other currencies, so the Actor asks both stores for JPY and reads the currency the store actually answered in (cart_currency). Prices are compared between runs only in the same currency, so a currency switch never produces a fake price change.
  • preorder_started is reported when a title or tag starts saying pre-order / 予約 / 受注生産. On 2026-10-10 neither store marked items this way (TCB mentions pre-orders only in running text, which the Actor does not interpret), so this event may stay rare.
  • purchase_limit_changed is reported when a limit appears, disappears or changes its quantity (on 2026-10-10 two WAREHOUSE jeans stated お一人様3点まで).
  • removed rows describe a variant that disappeared since the last run (sold through and unlisted, or hidden); they carry the last known title, size and price (previousPrice) with price and available set to null. They are only reported when the whole catalogue was read successfully.
  • Restock dates announced only on Instagram or newsletters are not visible; the Actor sees what the store's product feed shows.
  • The RUN_REPORT record (default key-value store) has a per-store summary: HTTP status, currency, variants read, rows returned, change counts, whether the baseline was updated, and a plain-language hint when a store returned nothing.

How much does it cost?

Pay-per-event: a tiny start charge of $0.00005 (Apify's default Actor Start event, charged once per GB of memory; this Actor runs on 1 GB) plus a per-row price:

EventWhat it isPrice
Actor Start (apify-actor-start)Once per run (per GB of memory)$0.00005
Result row (apify-default-dataset-item)Each row returned$0.003 (FREE and BRONZE plans) · $0.002 (SILVER and above)

In changes mode you pay only for rows that changed, so a monitor that finds 5 restocks costs about $0.015 on the FREE plan. The default run (100 rows) costs about $0.30 on FREE; every jean, jacket and overall in both stores is about 1,000 rows (≈ $3.02), and every item including T-shirts and accessories about 3,170 rows. Use maxItems to cap spend. Platform usage (compute) is included in these prices; a full run takes about 10 seconds.

Integrations: API, MCP, and AI agents

This Actor is read-only: it only reads public product feeds. It never logs in, adds to cart, orders or reserves anything, and it does not help get around purchase limits.

API (curl)

curl -X POST "https://api.apify.com/v2/acts/datalab-jp~japan-denim-restock-monitor/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" -d '{"mode": "snapshot", "garmentTypes": ["bottoms", "jacket", "overall"], "maxItems": 100}'

Python

from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("datalab-jp/japan-denim-restock-monitor").call(run_input={"mode": "snapshot", "garmentTypes": ["bottoms", "jacket", "overall"], "maxItems": 100})
items = client.dataset(run["defaultDatasetId"]).list_items().items

JavaScript

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });
const run = await client.actor('datalab-jp/japan-denim-restock-monitor').call({ mode: 'snapshot', garmentTypes: ['bottoms', 'jacket', 'overall'], maxItems: 100 });
const { items } = await client.dataset(run.defaultDatasetId).listItems();

The synchronous run-sync-get-dataset-items endpoint waits up to 300 seconds; a full run normally finishes in well under a minute.

Use with AI agents (MCP)

Add the Apify MCP server (https://mcp.apify.com) to Claude, ChatGPT, Cursor or any MCP client and ask, for example, "Which one-wash jeans of 13.5 oz or more are in stock in waist 32 at TCB right now?" The agent calls this Actor with mode: "snapshot", stores: ["tcb-jeans"], garmentTypes: ["bottoms"], washes: ["one_wash"], minFabricOz: 13.5, sizes: ["32"] and onlyAvailable: true.

Other Japan data Actors by the same developer:

FAQ

Is this legal? The Actor reads only the public product feed (/products.json) that each store serves to every visitor, without logging in or bypassing any access control, one request at a time with pauses. It returns factual data (names, sizes, prices, stock) and does not copy product descriptions or images. Each store's robots.txt and terms pages were checked before the store was added (2026-10-10). Neither supported store publishes a usable terms-of-use text — WAREHOUSE's terms page contains hemming instructions and TCB's terms pages are empty — so nothing in them prohibits this use, but that is not the same as permission. Stores whose terms prohibit scraping, commercial use of their information or copying it are not supported. You are responsible for using the data in line with applicable laws and each store's terms.

Can I use it through the API? Yes — see the curl, Python and JavaScript examples above. Schedule it in Apify and read the dataset, or connect a webhook.

Can AI agents use it? Yes. It is read-only, needs no credentials for the stores, and every input has a default, so an agent can call it safely.

How is this different from a generic Shopify scraper? A generic Shopify scraper gives you the raw feed of any store you point it at. This Actor comes with a checked list of Japanese denim brand stores, adds denim fields that a generic scraper leaves inside the title, tags or description (lot number, fabric weight, wash, fit, waist, purchase limit), and returns only the changes since the last run.

How does change detection work? After each run the Actor saves the price, stock, pre-order flag and purchase limit of every variant in the named key-value store stateStoreName in your account. The next run compares against it. The first run per store (or a new store name) saves the full baseline and returns rows as first_run.

Why is my favourite denim brand not supported? A store is added only if it serves a public product feed and its terms of use, read in full, do not restrict this kind of use. Several well-known Japanese denim brands were checked and left out for that reason (or because the site blocks automated requests); asking for one by its ID returns the reason.

Does it buy or reserve jeans? No. It does not add to cart, check out or reserve, and it does not help get around purchase limits. It only reports what the stores publish.

Do I need a proxy? The default uses Apify's datacenter proxy because Shopify-based stores rate-limit busy cloud IP addresses. Residential proxy is not needed. If a store answers HTTP 429 repeatedly, the run report says so; run again later.

Disclaimer

This Actor is not affiliated with, endorsed by or connected to WAREHOUSE & Co., TCB jeans or any other brand mentioned. Brand and store names are used only to identify the data source. Data is provided as published by the stores at the time of the run and may change at any time.

中文简介

  • 监控日本牛仔品牌官方网店(WAREHOUSE & Co.、TCB jeans)的牛仔裤、牛仔夹克等商品的库存、价格和新品。
  • 每个颜色×尺码一行:价格、是否有货、型号(Lot)、面料克重(oz)、洗水(一水/原色)、腰围、链接;监控模式只返回与上次相比的变化(补货、售罄、涨价、降价、新品、新尺码)。
  • 只读取公开商品数据,不会下单、加入购物车,也不会帮助绕过限购;适用于库存与价格监控、价格调研。