Search the broader major Israeli retailers — Ace, Home Center, Office Depot, Audioline — for products that the tech-focused chains may not carry (home appliances, office gear, audio equipment, hardware-store overlap). Use when the request leans appliance/home/office rather than pure consumer electronics. Prefer `search-zap` first if the SKU is mainstream — Zap covers these retailers too.
Tier-2 major chains that sit alongside the pure tech stores. Use when the product is more "household/office" than "consumer tech."
| Retailer | Best for |
|---|---|
| Ace | Hardware, tools, garden, some electronics |
| Home Center | Home improvement, appliances, fixtures |
| Office Depot | Office supplies + tech accessories |
| Audioline | Audio equipment specialist |
Read first:
data/discovery-techniques.md. The discovery playbook applies to all search skills — Hebrew term resolution, fallback chain, etc.
search-zap — covers all four of these too. Try first unless the user explicitly named one of these retailers.search-google-il — for niche category items.Same as search-main-tech-stores:
data/hebrew-category-map.json.discover-hebrew-term if missing.<hebrew category> <brand Latin> <model Latin>.he_terms ready to retry.Same as the other search skills: Playwright (default, local IP) or Tavily (fast fallback). Ask the user once per session.
Same caveat as search-main-tech-stores — data/retailers.md URL patterns are last-known-good hints, not contracts. If a pattern fails, navigate to the retailer's homepage, locate the search input, submit the Hebrew query, and read the results. Update data/retailers.md with whatever you discover.
he_terms if the primary returns nothing.data/shopping-rules.md.If a retailer comes back empty after all he_terms:
search-google-il with <brand model> site:<retailer-domain>.Same table format as search-main-tech-stores. Note when a retailer is clearly out-of-category for the query (e.g. searching Audioline for a vacuum cleaner — say so).
search-by-category instead.