Look up a catalogue item
Module · Stable
Find a product in the workspace’s own catalogue by name or code, without calling the shop.
Searches the catalogue held in this workspace — the list a person curates under Data → Catalogue — rather than the connected shop. Use it to turn what a customer called something into the name the business actually uses, before asking the shop about stock or price: the shop’s own search matches product names only, so a lookup fails whenever the customer’s word is not the catalogue’s word. This one matches names AND codes, so a part number pasted off an invoice resolves here too. Local read — no network call, no rate limit, and it works when the shop integration is not connected at all. It reports what the business sells, NOT whether a thing is in stock or what it costs today; ask the shop for those. Every match carries what it FITS and whether the business still SELLS it (availability: available, temporarily_unavailable, discontinued, unknown — never offer a discontinued item, and never read unknown as available), and the fits input asks fitment as its own question — ‘what do you have for a KTM 690 MY19?’ — which a name search cannot answer at all, because what a product fits is a recorded fact rather than a substring of its title. Read-only.
When to use
Section titled “When to use”Before asking the shop anything, to turn the customer’s word into the catalogue’s. And whenever the question involves a machine: a part that fits several bikes, or is brand-wide, cannot be found by searching for a model name — ‘TRACTIVE SUSPENSION for CFMOTO’ contains no model, so a search for ‘CFMOTO 450MT’ misses it and the empty result reads as ‘we don’t sell it’. That answer went to a real customer. Ask with fits instead.
When not to use
Section titled “When not to use”Not for stock or price — the catalogue records what the business sells, the shop records what can be bought today. And never decide what a product fits from an empty fits list: read fitment_reviewed with it. Three cases, and the third is the one that goes wrong. (1) fits is non-empty — say what it fits, and cite it. (2) fits is empty AND fitment_reviewed is true — someone looked and recorded no constraint; it is safe to say nothing is recorded. (3) fits is empty AND fitment_reviewed is false — NOBODY HAS LOOKED. Say you cannot confirm the fit and offer to check. Do not claim it fits, and do not claim it does not. This is measured, not hypothetical: on a live desk, products in exactly this state drew answers like ‘the USB Power Outlet is suitable for the GASGAS 700’ invented from nothing, and saying all this in prose alone did not prevent it — branch on the field.
Inputs
Section titled “Inputs”Configured per use: search, sku, fits, facet, limit.
Outputs
Section titled “Outputs”Auto-generated from the skill registry (load_skills()). Do not edit by hand.