Searchspring

Merchants like the fine-grained control for handling real inventory and catalog quirks, though some argue no tool truly automates this away.

“Merchants don’t think in formulas. They think about real problems. Like: “My ERP exports color names in ALL CAPS. Can I make them shopper-friendly?” Or: “We’re sold out of small, medium, and XL. Shouldn’t those products move down in search?” These aren’t edge cases. They’re everyday problems. In the early days, we patched them with one-off overrides. It worked, but it didn’t scale. Every brand had its own quirks. That’s why we built calculated attributes. They’re like automated metafields that live in @uselayers_. You define the rule once, and it creates a new attribute instantly. The rules underneath use JSONLogic, a powerful way to describe if/then rules. You don’t need to know the syntax. We set it up. You just use the result. First, it handled simple transformations: cleaning text, normalizing values, and building better filters. Now it powers complex merchandising strategies. Take the “size broken” products. One brand might call a single in-stock XL “broken.” Another might say it’s only broken when core sizes are missing. Both are valid. With calculated attributes, those definitions become formulas. If small, medium, and XL are missing, flag it with a 0. If not, mark it 1. Then you can sort, filter, or demote based on that value, with no manual work. Before Layers, brands hacked this with custom scripts, writing stock availability into metafields in Shopify or Searchspring every night. With calculated attributes, it’s instant. No developer time. No fragile scripts. Flexible logic that adapts to each brand’s needs.”— @0x15f on X

Integration works for real brand rollouts, but catalog sync speed is a known pain point post-launch.

“Your merch team just dropped a new collection. You just hit “send” on your email and SMS campaign. But your store’s search doesn’t show any of it. That’s what happens when your catalog sync takes 12+ hours. What does that delay mean? → Shoppers search for products that have just dropped → Nothing shows up → Support gets the call → A rep has to manually hunt down product IDs and place the order It gets worse when that same delay bleeds into merchandising. New collections launch, but the merch team can’t re-rank pages until the data shows up in the tool. Which means: → No control over what’s featured → Collections that look stale → Pages that don’t reflect live pricing or inventory This happens more often than most brands admit. Especially with large catalogs, where syncing 10,000+ SKUs lags across pricing, inventory, and visibility. We saw this with a 9-fig apparel and accessories brand. When they used SearchSpring, the system took 24 hours to reflect catalog changes. That meant their merch team was always a day behind. Their team would send out promos with new arrivals that didn’t even appear in search or category pages until the next day. That’s why we built Layers to reflect your catalog exactly as it looks now. Not how it looked 15 hours ago. Because your site should reflect what’s actually in stock and ready to sell right now.”— @0x15f on X

Core search basics are solid, but slow catalog refresh undercuts performance during high-velocity moments like launches.

“Everyone says ecommerce search is solved. It’s not. It just looks solved because there are too many tools doing the same thing. Algolia. Searchspring. Constructor. These tools solved the basics: → Show some products → Add synonyms → Let people search But the work never ends. You're still the one reading no-results reports. Still the one guessing at slang across cities. Still the one trying to band-aid poor navigation with keyword hacks. Most of these tools were built for generic use cases. When we started building @uselayers_, we tried using those tools too. Our early builds were layered on top of them. The more we used them, the more we realized: • The data model was off • The UI was cluttered • The logic didn’t match how people actually shop. Most brands don’t see this until they are 6 months into implementation, chasing dead ends and writing regex rules just to make search functional. So we started from scratch. → Built for Plus from day one → Product-first, not keyword-first → No workarounds, no platform hacks This week, we launched geo-aware autocomplete. It learns how people speak, so you don’t need a language model for every city. Even if you sell within one country, the terms for slang on the East Coast are not the same as those on the West Coast. You shouldn’t be the one updating queries for “coke” vs. “pop” versus whatever else you call it in other places. Most tools push this work to your team. We built Layers to take it off your plate.”— @0x15f on X

Agencies and clients report satisfaction with results, positioning Searchspring as a trusted, approachable option versus premium competitors.

“Algolia is the GOAT, but Klevu is seriously slept on, and are now also partnered with Searchspring under the banner of Athos Commerce. Check them out (not sponsored 🤪) I'm also intrigued by newcomer https://t.co/9YXiGEKGxp which looks like it does a good deal of personalization and visual data enrichment with AI, genai lite features; but I have no direct experience with it.”— @philwinkle on X