CH2 → Shopify Scraper

Status
—
Processed
0
Updated
0
Created
0
Errors
0
Current SKU
—
Elapsed
—
Next run
—
What do these mean?

Not in last CH2 run — the product is linked to a CH2 SKU, but that SKU was not seen in the most recent completed scrape. CH2 no longer lists it, so it is most likely discontinued.

Products with no CH2 SKU at all (never linked to CH2) are also detected by the scan but are hidden from this list, as they are not normally archived.

A scan compares every live (ACTIVE) Shopify product against the SKUs seen in the last scrape. Run a scan only after a scrape has finished — while one is running the CH2 list is still being built.

This list is a report only. Nothing here changes Shopify. Review the products (each title opens it in Shopify admin) and archive the ones you choose from Shopify admin.

Fields the scraper may update on existing products

Takes effect from the next product processed. Anything not listed here (description, product type, tags, images, SEO, status / published state, compare-at price, barcode, SKU) is never changed on existing products. New CH2 products are always created as Draft, filled in from CH2, for you to tidy and price before publishing.

CH2 credentials

How credential overrides work

The scraper normally reads CH2_USERNAME / CH2_PASSWORD from the container's environment. Saving values here stores an override on the settings volume; the override wins over the environment for every run from then on, and survives container updates.

Clear override removes the stored values and goes back to the environment variables. Stored values are never shown back here.

Test login tries whatever is typed in the fields without saving; a blank field uses the current saved/env value. With both fields blank it tests the credentials the scraper would use right now. Once a test passes, Save override, then Run test on the Running Status tab for an end-to-end check.