L'Etoile Price & Stock Monitor — letu.ru Catalogue

L'Etoile (ЛЭТУАЛЬ, letu.ru) is one of Russia's largest beauty chains. This Actor reads its catalogue — brand, name, price, the base price and discount, stock, rating and review count for every product — and tells you when a price moves, an item comes back into stock, or a product drops out of the range.

No key, no login. The cheap datacenter proxy is enough.

One clean JSON call per page

The catalogue runs on Oracle Commerce, and its product grid comes from a single search endpoint that returns everything in one response: id, brand, price, base price, discount percent, rating, review count, stock, instalment and link — 24 products a page. There is no second request per product and no HTML to scrape. The discount is right there in the grid, not hidden on a two-megabyte product page.

Measured: 2,000 products in 31 seconds across 28 categories and 339 brands, zero duplicates.

What you get per product

Identity	Product id, SKU id, name, brand, category, link
Price	Current price, base price, discount percent and the shop's own discount note
Stock	In stock, out of stock, or genuinely unknown
Reputation	Rating and how many reviews back it
More	Variant count and lead variant, instalment payment, promo markers, first image

Prices are per city

L'Etoile prices by region, and its search API will not run without a city. Leave City ID empty and the shop's own IP lookup picks one — Moscow (id 8113) from most exits — and the run logs which city it priced for, so you are never shown one region's prices while thinking you asked for another. Set a specific id to price elsewhere.

Monitor mode

changeType	Means
price_drop / price_rise	The price moved, with the old figure, the difference and the percentage
back_in_stock	It was out of stock last run and is available now
out_of_stock	The reverse
new_reviews	Customers reviewed it since the last run, with how many
no_longer_listed	The product was in the catalogue last run and is not in this one
new, unchanged	First sighting / nothing moved

no_longer_listed is raised only after a run that could have found the product — whole-catalogue mode on, all categories covered, and nothing cut short. When any of that fails, the run says so and raises nothing, because a delisting claim from a partial read is a guess.

Notes & limits

Properties of the source, measured rather than assumed:

• A single category caps at 10,000 products (about 417 pages). The catalogue is fully reachable through the deep leaf categories, which is why the whole-catalogue sweep reads the deepest categories first — the sitemap lists 1,310 of them.
• The end of a category is the API answering 400 with "page beyond result window." That exact message is the end; any other 400 is a real problem and is reported rather than mistaken for it. A page that repeats the previous one is also treated as the end.
• page is an object, not a number — {number, size}, and number starts at 1. This is the kind of detail that returns an empty catalogue if guessed wrong.
• The base price is only a discount when it is actually higher than the price paid. When the two are equal there is no saving, and oldPrice/discountPercent are left empty rather than reported as a 0% discount.
• Availability is the shop's own flag. Anything that is neither in- nor out-of-stock is reported as unknown, not guessed as out of stock.
• The Actor honours your Maximum cost per run and stops when the cap is reached.

Input

Field	What it does
Categories	/browse/… URLs or bare slugs. Leave empty to take them from the shop's sitemap.
Scan the whole catalogue / Maximum categories	Read every category — required for the delisting alert.
Pages per category	24 products per page.
City ID	Which region to price for.
Brands / Minimum price / Maximum price / In stock only / Only discounted	Filters, applied before anything is written.
Monitor mode / Output only changes	The alert behaviour above.