API improvements for catalog integrations
This release introduces improvements focused on catalog management and integrations, including product update tracking and new API capabilities designed to support real-world synchronization scenarios.
Product and variant last modification date
Products and variants now include a last modification date (updated_at), allowing you to know when each catalog element was last updated.
This timestamp is automatically updated when relevant changes occur, including:
- Product information, texts, images, or categories
- Variant-specific data such as price, stock, or attributes
- Creation or deletion of variants
- Changes in product or variant visibility
Both creation date and last modification date are now visible in the backoffice, at the bottom of product and variant edit pages.
Why this matters
This change enables several improvements across the platform:
- Better visibility of recent catalog changes
- A practical signal to detect potential updates in the catalog
The updated_at field is designed to help identify resources that may have changed and need to be revisited or re-synchronized.
However, it reflects an aggregated view of changes and should not be treated as a complete or fully reliable change history. Depending on the integration requirements, additional strategies may be needed to ensure consistency.
Improvements for catalog integrations
The API has been extended to better support integrations with external systems such as ERPs, PIMs, and inventory tools.
These improvements are based on real integration use cases and aim to simplify synchronization and data access.
More filtering options in list endpoints
List endpoints now support more flexible filtering capabilities:
- Search by lists of IDs:
product_ids,brand_ids,category_ids,order_ids
- Search by
internal_idsusing CSV format - Clearer documentation of
internal_idas an alternative identifier for integrations
These additions make it easier to retrieve specific resources without iterating through the entire catalog.
Incremental synchronization with date filters
The List products endpoint now supports filtering by:
created_atupdated_at
With comparators:
_from_to
This allows external systems to:
- Detect newly created products
- Identify products that have changed since a given timestamp
- Build incremental synchronization strategies without traversing the entire catalog
These filters are intended to reduce the amount of data to process, but should not be considered a complete or fully reliable change tracking mechanism.
Stock management and online availability
New fields have been added to better represent how products behave in terms of purchase availability:
stock_managementeffective_stock_managementonline_availability
These fields allow external systems to determine whether a product is actually purchasable, taking into account:
- Stock rules
- Backorder configuration
- Online availability (shipping, pickup, or both)
They are available in:
- Product detail
- Product lists
- Bulk operations (where applicable)
Additional API enhancements
Other improvements included in this release:
- Customer
emailis now explicitly documented as a unique identifier internal_idis now consistently defined across resources for integration use casestax_id(NIF/VAT) added to order addresses for ERP integrations- Improvements in order customer data clarity (snapshot vs current customer)
- Extended default variant fields with pricing data (
list_price,offer_price,flash_offer) - New examples in documentation for
fieldsandincludesusage
What's next
Upcoming improvements will focus on:
- Expanding API coverage to support broader ERP and integration use cases
- Continuing to evolve the API as a robust integration platform
- Customer endpoint.

