Bulk Update for fixed prices by reference in custom price lists
This release adds bulk management for variant-level fixed prices in custom price lists.
External systems can now create, update or delete price list variant prices at scale through a single asynchronous API endpoint.
Bulk updates for custom price list prices
OpenTiendas now supports asynchronous bulk updates for fixed prices by variant inside a custom price list. This makes it easier for ERPs, PIMs, CRMs and custom integrations to keep customer-specific prices synchronized with OpenTiendas.
The new endpoint is available under the price list prices sub-resource:
POST /api/v1/price-lists/{id}/prices/bulk-update
It complements the existing price list prices endpoints:
GET /api/v1/price-lists/{id}/prices/
DELETE /api/v1/price-lists/{id}/prices/
POST /api/v1/price-lists/{id}/prices/bulk-update
With this addition, integrations can now inspect, clear and synchronize fixed prices by reference from the API.
What this enables
Until now, integrations could read the fixed prices configured in a custom price list and remove all of them when needed.
With this new bulk update endpoint, they can also manage those prices directly.
This is especially useful for integrations that need to:
- update hundreds or thousands of customer-specific prices from an ERP,
- send only the references that have changed since the last synchronization,
- remove obsolete fixed prices without rebuilding the full price list,
- match variants using the identifiers already available in the external system,
- keep price, minimum quantity and quantity multiple conditions aligned with external commercial rules.
The operation is processed asynchronously, so integrations can send larger pricing updates without depending on a long synchronous request.
Two operation modes
The operation to perform is defined by options.mode.
The endpoint supports two modes:
upsert: creates new variant prices and updates existing ones;delete: removes the provided variant prices from the price list.
This covers the most common synchronization flows:
- incremental updates, where only changed references are sent;
- selective cleanup, where only specific fixed prices are removed.
Existing prices that are not included in an upsert request remain unchanged.
This makes the endpoint safe for partial synchronization processes, where an ERP or integration does not need to resend the full price list every time.
Flexible variant matching
Integrations do not need to depend on a single identifier.
Variants can be matched using the value defined in options.match_by:
variant_id,variant_internal_id,ean,sku_supplier.
This allows each integration to work with the identifier model it already has.
For example, an ERP may use internal variant references, a PIM may work with EAN codes, and a supplier-based integration may need to identify variants by SKU and supplier.
Designed for reliable bulk processing
Bulk update requests create an asynchronous job.
OpenTiendas first validates the request structure. If the payload is valid, the endpoint returns 202 Accepted with a job_id.
The job then processes the records and registers the result in the job log, including validation errors by line when available.
This allows integrations to send a bulk update, continue their process, and later review which records were processed correctly and which ones need attention.
The maximum request payload size is 10 MB.
Price list data stays clearly separated
This endpoint only manages fixed prices by variant within a price list.
It does not modify the general price list configuration, such as:
- global discounts,
- category discounts,
- brand discounts,
- active state,
- minimum order amount.
Those fields continue to be managed through the price list CRUD endpoints.
This keeps the API model clear: price list configuration is handled by the price list resource, while fixed prices by variant are handled by the price list prices sub-resource.
Summary
This release completes an important part of the Price Lists API by adding bulk write operations for variant-level fixed prices.
Integrations can now:
- read fixed prices by variant,
- clear all fixed prices from a price list,
- create or update fixed prices in bulk,
- delete selected fixed prices,
- match variants using different identifiers,
- and process large synchronization jobs asynchronously.
This provides a stronger foundation for ERP, PIM, CRM and custom integrations that need to manage customer-specific pricing in OpenTiendas through the API.
Next steps
We will continue expanding API coverage across more areas of OpenTiendas.
Upcoming work will focus on exposing additional ecommerce capabilities through the API, including areas such as quantity discounts, internationalization, localization and other resources that help external systems integrate more deeply with the platform.

