Capabilities differ by marketplace
A field or action available on one operator cannot be assumed to exist on another. Autopricy checks the target marketplace before enabling automation.
Mirakl repricer / selected operators
Mirakl repricing that respects each marketplace operator
Autopricy automates eligible Offer price changes on selected Mirakl-powered marketplaces. It keeps operator data, channel rules, minimum and maximum prices, submission, and confirmation separate—because a Mirakl connector is not one universal repricing algorithm.
Why Mirakl repricing varies
The platform is shared; the marketplace rules are not
Mirakl gives operators a marketplace foundation, but each operator decides which Offer fields, competitor signals, channels, limits, and update workflows are available.
Offers need exact identity
Updates stay tied to the actual shop, SKU, product and channel identity. Autopricy does not infer an Offer from position, price, or an approximate product match.
An accepted request may still be pending
Submission, operator processing, confirmation and failure remain separate operational states.
Marketplace mechanics
How an assessed Mirakl repricing workflow works
| Market input | Use only Offer and competitor data that the selected operator actually exposes. |
|---|---|
| Decision | Evaluate the configured rule inside the Offer’s minimum and maximum price boundaries. |
| Submission | Send an eligible update through the operator-specific API and channel context. |
| Verification | Keep the result pending until the platform response or later read-back supports confirmation. |
Reference: Mirakl Offer API documentation
Selected operators, not “every Mirakl marketplace”
Autopricy supports repricing workflows for selected Mirakl-derived operators. Before onboarding, we review the operator, country, authorization model, Offer data, competitor visibility, update method and confirmation behavior. Unsupported fields are not filled with generic assumptions.
Workflow
Validate one operator before scaling
Name the operator
Share the marketplace, country, stores, SKU volume and current price process.
Confirm API scope
Check authorization, Offer fields, competitor visibility, channels and limits.
Audit a controlled sample
Verify exact identifiers, current prices, boundaries and available market signals.
Enable and observe
Start with bounded rules and expand only after platform results are visible.
Illustrative rule, not a performance claim
A boundary-first Mirakl example
Example rule: an Offer has a minimum of €24.00 and a maximum of €32.00. If the assessed operator exposes a comparable competing Offer at €26.50, the rule may target €26.49. If the operator does not expose the required signal—or the update cannot be confirmed—the workflow should not pretend that the price is live.
Related resources
Continue with the relevant workflow
FAQ
Mirakl repricing that respects each marketplace operator: common questions
Does Autopricy support every Mirakl marketplace?
No. Support is assessed per operator because data, channels, rate limits and permitted actions differ.
Is Mirakl repricing the same as price synchronisation?
No. Price synchronisation copies a value. Repricing also needs a market signal, decision rule, boundaries, submission and result verification.
Can Autopricy price below the configured minimum?
Eligible calculations are constrained by the configured minimum and maximum price. Invalid or missing boundaries should stop automation.
Does the lowest price guarantee the winning Offer?
No. Price may matter, but availability, delivery, seller performance and operator rules can also influence placement.
Test the workflow on a real store
Start with one supported store, a controlled product scope, explicit boundaries and visible platform results.
yuanyongvia@gmail.com