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.

🚀 The Query API .NET SDK has been updated with a completely new syntax.

We've rebuilt the SDK around a fluent QueryBuilder API. Queries are now constructed in a way that feels natural in .NET – type-safe, chainable, and with full IntelliSense support. If you're on the previous version, it's worth upgrading.

What's new

• Fluent QueryBuilder API – chain filters, sorting, pagination, and facets in a single expressionTyped query builders – use your own C# models to drive queries; property names are automatically camelCased, or mapped via [JsonPropertyName]
• Lambda-based filtering – reference model properties directly instead of magic strings
• Nested logical grouping – compose complex AND/OR filter trees with ease
• ISuccess / IFailure result handling – no more silent failures or unchecked nulls
• Non-typed builder still available – if you prefer to work without generics

Getting started

1. Install or update the NuGet package
2. Register the service:
   services.AddEnterspeedQueryService()
3. Start building queries – check the GitHub repo for full docs and examples

We have added a bunch of new features for the source entities, making it easier for you to navigate, find the right source entity, and even edit existing source entities.

The list of new features includes:

• Show source entities as a tree view – lets you navigate to a specific source entity using the same structure you have in your CMS instead of searching by id or URL, or navigate product data by category, product, and variants.
• Open source entities in a side panel – makes it easier to quickly view different source entities without leaving the list of source entities. You can still navigate to a full page view of a source entity if you need more space.
• Edit source entities – Until now you have been able to add and delete new source entities directly from the Management App. Now you can also edit existing source entities which is especially useful when testing in early stages – and of course this will be logged in the Activity log, so you can see who changed a source entity.
• Add new source entity as child entity – this is just a nice little addition to the context menu of a source entity so you don't have to figure out the parent id yourself.

The above list is just some of the hightlights, even more small improvements have been added, so make sure to check it out next time you sign in to your tenant in the Enterspeed Management App 🚀

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

You can now read Delivery views as your own C# types. Keep the flexible fetch you know, but de-serialise per-view into real models with IntelliSense and compile-time safety. No more rummaging through dictionaries.

What’s new

• Typed variant of Fetch: fetch as usual, then read each view with GetContent().
• Per-view typing: mix multiple handles (e.g. article, navigation, footer) in one request and deserialise each into its own model.

Why it matters

• Fewer runtime surprises: let the compiler and your IDE do the heavy lifting.
• Cleaner contracts: define a C# model instead of magic dictionary keys all over your code base.
• Less boilerplate: no need for custom serialization.

Example: multiple views, multiple types

Fetch several views in one go, then read each as its own model:

Useful links

• Delivery SDK (.NET) repo & README – install, register, usage, and strongly-typed examples. GitHub
• Docs: Delivering data – overview of Delivery API. Enterspeed Documentation | Enterspeed Docs

Thanks to the community

This shipped because a user opened a clear feature request with suggested behaviour. So, keep the issues and PRs coming – we’re listening.

Fetching data from Enterspeed has just become 100 times easier. With the new Query API, you can create dynamic queries on the data you have in Enterspeed. This means you can now effortlessly create product list pages, article lists, or any other type of list you need. Additionally, you can look up specific customers' orders or events within specific date ranges and locations.

The Query API introduces several new concepts, including the Index Schema, which allows you to define and manage searchable properties, and the Query API Endpoint, a new endpoint in the Enterspeed ecosystem: query.enterspeed.com.

In the Index Schema, you create and manage dynamic queries on your data.

The Query API supports filtering and sorting, and pagination. For instance, you can filter on fields defined in the Index Schema with various operators like equals and greaterThan.

For more detail, please jump to the product article 👉 The Enterspeed Query API is in preview 

What’s next?

• Properties method: Currently, the PropertiesContext object is not available, but we are working on reintroducing this functionality.
• Facets support: We are also working on bringing support for facets to the Query API, expected before summer.

How to get started

To learn more about the Query API, visit our documentation. 

If you want to try out this feature, please reach out to us, and we’ll activate the feature and give you a 1:1 introduction.

We are thrilled to see how you will use the Query API to enhance your projects!

Have you ever wanted to know what a view response looks like from the Delivery API – or maybe wanted to see resolved references for a view? Good news! You can now do that directly from the Generated views panel in the Management App.

In addition to copying a CURL request from the routes list, you can now execute the request directly and view the response from the Delivery API within the app. This feature is particularly useful for seeing the full view, including resolved references, as shown in the examples below.

The statically generated view holds a single unresolved reference for a productListingView. This is how the view is stored as references are resolving during the Delivery API request.

When you execute the CURL request against the Delivery API, you can now see the full response, including the resolve productListingView reference.

We've also introduced the ability to make CURL requests by id. In the Enterspeed Delivery API, you can fetch a view in three ways: by URL, by handle, or by id. URLs and handles are routes you create using the routes function in a schema. Previously, we only provided CURL options for these explicit routes. Now, we've added the id CURL request, allowing you to fetch views without relying on explicit routes. This makes it easier to test references for these views. 

If you’re (also) one of those people who enjoy insights and transparency in your services, you’re gonna like the Ingest requests tile on the dashboard that we’ve just introduced.

The new tile displays the current month’s number of ingest request. You’ll see both the total number of ingest requests and the number of changed ingest requests. These two numbers provide a change ratio, which indicates the percentage of total ingest requests that have changed.

We hope the new tile can help you understand and optimise your integrations to Enterspeed.

Besides the ingest numbers, the new Ingest requests tile is the first tile on the dashboard where you can configure different view options for the tile. We hope to bring this concept to some of the existing tiles as well in the future.

The Versions page in the Enterspeed Management app have gotten an update. And we think you will like it 😀

Check out the features below.

Performance improvements
The page now loads faster, especially if you have many environments.

New version indication
A red dot on the version number is indicating if a newer version exists.

Deployment status
When a schema is actively being deployed, an animation will show the transition from the current version number to the new version number. As soon as the deployment is completed the version number is updated.

The new deployment indicator on the Versions page is just the first step on the way to give your more insights to the status of schema deployments.