Feature-by-feature, from the team building Trooply.
These aren't release notes. They're the short guides we wish every new merchant and developer had before their first integration call — one concept per post, one working example each.
Latest posts
Visual search 101: what happens when a shopper uploads a photo.
CLIP ViT-L/14, the shared embedding space for images and text, and what /v1/search/url is actually doing under the hood.
Merchandising without the ticket queue.
Pin, boost, and bury rules that scope themselves to the right query, category, or time window — so the merchandising team stops paging engineering.
ReadCustom fields: teach Trooply your catalog's vocabulary.
Declare fields once, get a filter UI for free, and scope every search to exact values, lists, or numeric ranges.
ReadPromo banners that know when to fire.
Scope-aware callouts inside search results — sitewide, query-triggered, or category-triggered — with start / end windows baked in.
ReadDrop-in widget without leaking secrets.
Why embedding a client_secret in page source is a footgun, and how Origin-bound pk_live_ keys replace it in four lines.
The SKU-level report that tells you what to re-shoot.
Resolution, blur, exposure, contrast — four signals combine into a quality score with a concrete fix hint per product.
ReadAPI key or OAuth: which one do you actually need?
Two server-side auth methods, one decision. Plus the most common mistake — using an API key where a client_secret was expected.