Store Currency Locale Detector
Pricing
$3.00 / 1,000 results
Store Currency Locale Detector
Pricing
$3.00 / 1,000 results
Rating
0.0
(0)
Developer
Eichan Jolly
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Features
Share
Store Currency & Locale Detector
Inspect one public store homepage and return a single summary row of its HTML lang attribute and currency hints from JSON-LD, price-related meta tags, and visible price text/symbols. A hint is not proof of the checkout currency; currencies can vary by country, account, or session.
Who is this for?
Storefront QA teams, market researchers, and developers assessing currency presentation from public metadata. This Actor is not a payment or checkout inspector and does not browse product pages.
Quick start / real prefilled demonstration
This public Plus-Plus UK homepage was independently observed on 2026-11-01 displaying prices with GBP on the page. It provides a realistic, non-placeholder first run. Site content may change.
{"storeUrl": "https://www.plus-plus.co.uk/"}
Example output from the local fixture modeled on the public signals (the live page may have more JSON-LD/meta signals):
{"url": "https://www.plus-plus.co.uk/","htmlLang": "en-GB","detectedCurrencies": [{"currency": "GBP","source": "text-symbol","evidence": "Visible price statement: All prices are in GBP."}],"likelyCurrency": "GBP","signals": ["HTML lang is en-GB; language is not used to infer currency.","Visible price statement: All prices are in GBP.","GBP is the only supported currency hint; checkout may differ by region."],"status": "ok","error": null}
htmlLang from this example is a local fixture value, not a claim that the site's live <html> element has precisely that value.
Fields and confidence policy
url: the supplied, validated homepage URL.htmlLang: literal HTMLlang, ornull. Never used for currency inference.detectedCurrencies: list of{currency, source, evidence}.sourceis one ofjsonld,meta, ortext-symbol. An ambiguous$or¥symbol is represented withcurrency: nullrather than guessing USD/CAD/AUD or JPY/CNY.likelyCurrency: one unambiguous, nonconflicting public currency hint, ornullif none / conflict.signals: list of plain-language evidence strings and any conflict/uncertainty explanation.status:okorerror.error: plain-language error description ornull.
The Actor recognizes a bounded set of common ISO currency codes: USD, GBP, EUR, CAD, AUD, JPY, NZD, CHF, SEK, NOK, DKK, INR, KRW, SGD, HKD. From JSON-LD it reads only priceCurrency; from meta it reads price/currency-related tags; from visible text it reads explicit price-code phrases, prices with ISO codes, and recognizable currency symbols. Repeated signals of the same type/code are deduplicated. If conflicting codes are detected, likelyCurrency is null, even if one looks stronger. Mere dollar/yen symbols cannot establish currency.
On download failure the Actor emits exactly one row with status: "error", empty detectedCurrencies and signals, null locale/currency, and a readable error.
Limits and responsible use
- Only the one homepage URL you provide is fetched. No crawling, logins, browser automation, external APIs, or checkout interaction.
- HTML-only extraction: client-side content absent from the initial HTML is not seen. Price displays localized per IP, cookie, device, or account may differ.
- A
£symbol is a GBP hint, not a checkout guarantee. No country inference from.co.uk, language or store name. - 15-second timeout, 2 MB HTML response limit, same-host redirects only, public network addresses only. 403/404/timeouts produce plain-language errors.
- Only use public sites that permit automated access. No Amazon/eBay scraping.
Run locally (Python 3.12+; no dependencies)
$ACTOR_INPUT_JSON='{"storeUrl":"https://www.plus-plus.co.uk/"}' python src/main.py
Local output is saved to storage/datasets/default/000000001.json and subsequent numbered files. Alternatively place an input JSON object in storage/key_value_stores/default/INPUT.json.
On Apify, INPUT is fetched from the default key-value store via the official REST API, authenticated with platform-provided APIFY_TOKEN. Output is POSTed to the default dataset via REST, with no Apify SDK or dependencies.
Reproduce verification
python -m unittest discover -s tests -p 'test_*.py' -vpython tests/run_smoke.py
The smoke runner creates an isolated Python virtual environment (stdlib only) and executes the production file in a real subprocess via python src/main.py, with test-only HTTP fixture substitution at interpreter startup. It records real stdout, stderr, exit code, and dataset output in tests/smoke_evidence.txt and tests/smoke_dataset.json. This tests script-mode correctness; it is not a live HTTP or Apify deployment test.
Suggested Apify Store details (not activated)
- Category: ECOMMERCE (E-commerce).
- Suggested price: USD $2 per 1,000 successful summaries ($0.002 per summary). Do not charge for error items if billing is later implemented.
- Proposal only; see
store_metadata.json. Publishing and billing are not configured.