Product search is not implemented in XOM today. There is no product index, no search component, and no catalog integration in the application. What exists is a set of adjacent pieces that a product-discovery feature would eventually be built from. This page describes those pieces honestly rather than describing a capability that does not yet exist.
01What exists today
Industry categorization. Every post is tagged with an industry at upload time, drawn from a fixed list covering verticals such as fashion, automotive, beauty, fitness, gaming, luxury, electronics, streetwear, and cuisine. The feed uses these tags for filtering and the ad system uses a parallel category list for creative targeting. This is the closest thing XOM has to a commerce taxonomy, and any product search would likely key off it.
Commercial ad units. The advertising system supports affiliate and native ad types. An affiliate creative carries a call-to-action destination and earns on conversion rather than on impression or click, which is the mechanism by which a product currently reaches a user inside the feed. This is placement, not search — the creative is selected by targeting and feed position, not by a query the user typed.
A marketplace module. A marketplace class exists in the revenue layer with the basic listing operations: retrieve all listings, create a listing with a name, description, price and payment type, purchase a listing, and retrieve a user's own listings. Purchase branches on payment type — an in-app XP balance is checked and debited directly, while a real-currency purchase is routed to a payment gateway. The module is written against a data layer and a gateway that are referenced but not connected. The platform architecture document lists marketplace as planned, with the inventory and reward systems as its foundation.
02What building this would require
Three decisions come before any implementation work. First, the catalog source: whether products are listings created inside XOM, feeds ingested from merchants, or items pulled from an affiliate network. Each implies a different data model and a different commercial relationship. Second, the index: XOM stores content in Firebase and does not currently run a search service, so a text-and-facet product search over a live catalog would need one. Third, the transaction boundary — who takes payment, who handles fulfilment, and who carries the liability.
Until those are settled, the accurate description is that XOM has the tagging vocabulary and the ad placement mechanics for commerce, and does not have product search.