If you've been building with Enterspeed  –  it means you know better than anyone what works, what doesn't, and what's missing.

We're working on the next major version of the platform, and before we lock in direction, we want to hear from the people actually using it. 

The survey takes about 5 minutes, and your answers will directly influence what we build next.

[Take the survey →]

Oh, and everyone who completes the survey is entered into a draw for an Enterspeed hoodie. 💙 (Just leave your name at the end – we'll only use it for the draw.) 

Brutal honesty welcome 😬

We wanted to give you a heads-up that the global search feature in the Enterspeed Management App — powered by CommandAI's Spotlight — will be discontinued later this month (June 2026).

The reason is twofold: CommandAI is ending support for the Spotlight feature, and looking at our usage data, only a small number of users have been using it regularly.

We know it's a handy feature for navigating the Management App, but based on the low usage and the loss of support, we've decided not to build an alternative — at least for now.

We're sorry for any inconvenience this may cause, and as always, feel free to reach out if you have any questions.

Are you working with large number of entities, being customer specific prices or entities that changes often like e.g. inventory numbers?

Up until now Enterspeed has had its strength on static data from a CMS, a PIM system or something similar. This is because the way Enterspeed preprocesses the data making it stable and fast to fetch on the client.

But no approach is the perfect solution for all use cases, and we know that not all data is static and requires transformations. So, why put data through a transformation process that takes a lot of resources if the data doesn’t need transformation or if it’s never even being fetch by the client?

That’s why we added a new type of data flow in Enterspeed called Auto Indexing.

It’s a feature you enable on the Source group. Once it’s enabled all the data you ingest into this Source group will automatically be added directly to an Index you can query from the Query API.

The new Auto Indexing mode lives comfortably together with the existing schema transformation mode, given you the options to use whatever mode is the best for your specific data set and often it will be a combination of both for your project.

When using Auto Indexing you don’t have the option to create schemas for the source entities, so you can’t do transformation on the data. But instead, you can ingest a large volume of data and have frequently changes to the data making it perfect for dynamic data like customer specific prices or inventory numbers. And especially in combination with the bulk Ingest API you can really send some data through to Enterspeed and have a fast and flexible Query API to fetch the data and offload your ERP system or wherever your data is coming from 🚀

Head over to your Enterspeed tenant today and start using the now Auto Indexing mode and if you need more information, check out the documentation about Auto Indexing.

We've added a safeguard to prevent accidental type changes that could break your content delivery.

What changed

The Ingest API will now reject requests that attempt to change the type of an existing source entity. If you re-ingest a source entity with a different type than what was originally stored, you'll receive a 422 validation error.

Why we made this change

When a source entity's type changes, any routes or views bound to that type become stale — potentially breaking content delivery without warning. This guard makes type mismatches fail loudly rather than silently, giving you immediate visibility into the issue.

What you need to do

In most cases, nothing. This guard only triggers if your ingest pipeline is attempting to change the type of an entity that already exists.

If you see the error and the type change is intentional, you have two options:

1. Delete the entity first — Remove the source entity via the delete endpoint, then re-ingest with the new type. This is the recommended approach as it properly invalidates dependent routes and views.
2. Use the bypass header — Include the X-Enterspeed-Force-Type header in your ingest request to override the protection. Only use this if you're certain the type change won't cause downstream issues.

Example error response

If you encounter this unexpectedly, it likely indicates a data inconsistency in your ingest pipeline that's worth investigating.

Questions or concerns? Reach out to us on our support Slack channel or at support@enterspeed.com — we're happy to help.

Shopify is undoubtedly the leading commerce platform out there, and now you can push products directly from Enterspeed to Shopify. 

With our new Shopify Destination, you can map your product, variant, and pricing data – and more – from any source system in Enterspeed, then push it directly to one or multiple shops in Shopify.

The Shopify Destination is now in preview. It supports things like price lists, metafields, and translations all in a single unified model. You don't need to deal with Shopify's GraphQL API, async bulk ingests with callbacks, rate limits, internal Shopify ids, or multiple request to fully update a product. We handle it all for you .

If you want to get started or have any question, just reach out. 

Check out the blog post for more info https://www.enterspeed.com/blog/announcing-the-enterspeed-shopify-destination or head over to the documentation: https://docs.enterspeed.com/integrations/shopify

 🚀 Today we launched the .NET SDK for the Enterspeed Query API. 

The Query SDK works seamlessly with the existing Delivery SDK and brings all the powerful features of the Query API directly into your .NET projetcs:

✅ Filtering, sorting, pagination, and facets
✅ Dynamic view references
✅ Strongly typed results – no more generic data structures or magic strings 

Getting started is simple:

1. Install the Nuget Package
2. Add the service registrations
   
   
   
3. Start querying your index in a strongly typed way – no need to worry about HTTP clients or plumbing. We’ve done the heavy lifting for you.

Check out the open source Github repo for documentation and more examples 🚀

We are proud to announce the public release of our new Query API, adding even more power to the Enterspeed platform.

The last couple of months during the public preview phase we've gained a lot of valuable feedback and brought a lot of this feedback into the public release. Thank you so much to all of you helping to shape and make Enterspeed an even better product.

The Enterspeed Query API

The Enterspeed Query API lets you easily build search indexes from a new Index schema type and return lists of items – directly within the Enterspeed platform. It also, as the name implies, brings a new Query API that lives side by side with the existing Delivery API, which gives you even more power and flexibility in the way you can fetch data from Enterspeed.

Some of the highlights in the Query API are:

• Easy creation of new search indexes without new infrastructure or external search providers
• Filtering, sorting, pagination, and even facets on request time
• Deep integration with existing full-schema views, letting the query result return views
• Do multiple queries in a single request

Quick start

1. Create an Index Schema for the data you need list/filter on (e.g., productIndex). Index schemas define the fields and their types you want in the index and maps the data to go into the index.
2. Get an Environment API key (Management App → Environment client) to call Delivery & Query API. Just like you know it from the Delivery API.
3. Query the index via POST https://query.enterspeed.com/v1/{indexAlias} with filters/sort/pagination — optionally add aliases to get Delivery API views per item. 

Check out the full launch blog (background, facets & Delivery API integration examples - plus pricing) 👉 Launching the Enterspeed Query API 

Links

• Query API docs (endpoint, filters, facets, aliases, responses) Enterspeed Docs
• Index Schemas (when & why to use indexes vs. full schemas) Enterspeed Docs

Umbraco 15 is out – and as always, we have upgraded our integration to support the new Umbraco version 👌

Besides the support of Umbraco 15, the new package also contains some new features and fixes, like support for the new RTE editor and the option to remove trailing slashes in the URLs. 

So, make sure to check out the Enterspeed package on Umbraco marketplace.

OBS, if you are using Umbraco 9 to 15, make sure to get the right package version 😉

Version 5.x is for Umbraco version is 14 or higher.
Version 4.x is for Umbraco version 9 to 13.

Umbraco has launched Umbraco 14 – and we have launched our integration for it 👌

The Umbraco 14 upgrade is a pretty significant step forward in their back office, which is now based on modern frontend technologies – but in the tried and tested Umbraco back office we all know (and love).

The Enterspeed Umbraco package is now updated and supports all versions from Umbraco 7 to Umbraco 14.

So, no matter if you’re looking to migrate a legacy Umbraco site or wish to utilise Enterspeed in a new and modern Umbraco 14 stack, we can support it 😊

In the Enterspeed Management App, we've introduced an Activity log. You find it under Settings > Activity logs. The Activity log allows you to go back in time and see all activities, such as the creation, updating, and deletion of schemas, environments, source groups, and more. You can see who made the changes and when they were made. For many logs, you can even compare the new and previous values before the change.

The new Activity log is based on the new Logs UI we introduced a couple of months ago, but the default columns and filters are adjusted to fit the purpose of an activity log. Just like you know it from the logs, you can filter on different properties, set a time interval, and add or remove columns in the list. For example, you can filter by user (actor) to see all changes by a specific user within a time interval. Selecting a log message brings up the side panel, where you can see more details about the log and use shortcuts to add columns to the list or filter by specific values.

Our hope is that the Activity log can be yet another tool to help you get a better overview of what's happening on your Enterspeed tenant.