Click on the features below for a detailed description
Custom API calls are used most often for complex/messy data feeds or unique merchandising requirements.
All plans include the first 20,000 searches per month. Use the slider below to calculate the cost of additional searches. As the volume grows, so do the discounts.
We charge based on a combination of feature usage and search volume. All our plans include the first 20,000 searches per month. We only charge for completed searches and apply discounts as your search volume grows. We do not charge for bots, software updates or standard tech support.
Note: When your dev engine goes up, we begin charging 50% of your subscription fee. Once you are live in production, we will charge the full amount (100%). You do not pay for searches (i.e. those above 20,000/mo) until you are live in production.
No. Loop54 is SaaS (software-as-a-service), this means our engines our hosted in the cloud and new versions can be rolled out without any extra work or cost to our clients. To access some new features, some clients may need to implement new APIs.
Yes. Our standard SLA includes a Monthly Uptime Percentage (MUP) of 99.98%. All critical issues are addressed by the next work day. Non-critical issues are addressed within two work days (work day: Monday-Friday, 9-18).
A premium SLA is available should you require faster response times and/or percentage discounts if MUP goes below 99.8%.
Once we receive your product feed we build a model of your catalogue - identifying and mapping the complex relationships between products. Because of this mapping, we're able to generate a list of related results.
These related products are similar to the 'direct results' but they do not contain the actual search term in their metadata (i.e. they would have never been found through simple text-matching search). Basically, they have nothing to do with the actual search query, but everything to do with the what products are listed as 'direct results'. Learn more.
Response times will be much faster than to filter on your end once the products are returned by the engine.
If you choose to filter on your end instead, then we would first have to return all the products in the search results and as a second step you would have to apply filters to that list of products prior to showing any results to the user. Doing this will add unnecessary latency.
Boost or bury search results or category listings based on any product attribute. For example, promotional campaign, new products, high-margin products, etc. Boost and bury rules are applied to an established list of relevant results/products - this ensures that what is boosted still matches the user's intent.
For example: <OnSale>true</OnSale> would get 25% higher value so it has a higher possibility to appear at the top of the results/listings. The opposite goes for products that you want to “bury”, which is typically used for products that are out-of-stock.