The correct Darty shop must own the action
Autopricy keeps shop credentials and Offer identity scoped to the Darty account.
Darty repricer / marketplace sellers
Autopricy supports bounded Darty Offer repricing through the FNAC/Darty XML 2.6 integration boundary, while preserving Darty’s own shop identity and competitor logic. Price requests, batch processing and confirmed outcomes remain distinct.
Darty repricing details
The transport format can be shared while seller identity, shop type and competitor choice still require marketplace-specific logic.
Autopricy keeps shop credentials and Offer identity scoped to the Darty account.
The repricer uses Darty-specific handling instead of inheriting another marketplace’s seller comparison blindly.
Submission, waiting, marketplace confirmation and failure are shown as different stages.
Marketplace mechanics
| Synchronise | Read the Darty Offer and retain its exact shop, SKU and marketplace identity. |
|---|---|
| Compare | Evaluate only the competing Offers that meet the Darty workflow’s current criteria. |
| Constrain | Keep the target between the seller-defined minimum and maximum. |
| Confirm | Submit through XML and track the later batch status before reporting a final result. |
Autopricy controls eligible price actions; it does not control every Darty ranking signal. Availability, delivery, seller quality and marketplace policy can affect placement alongside price.
Workflow
Check the Darty shop identity and authorization path.
Review exact SKU, current price, available competition and status.
Add minimum, maximum and difference rules to a controlled product set.
Expand only after processing and confirmation behave as expected.
Example: Autopricy calculates €54.90 inside a €50.00–€62.00 range and submits the Offer in an XML batch. The operation remains “submitted” or “processing” until the Darty batch status provides a final result.
Related resources
FAQ
No. The XML boundary is shared, but the marketplace type, store identity and competitor handling remain explicit.
No. The configured rule and boundaries determine eligible targets; continuous price cutting is not the objective.
Yes. A marketplace batch can remain pending or return an error after submission, so confirmation is tracked separately.
The account and current API capability are reviewed before activation.
Start with one supported store, a controlled product scope, explicit boundaries and visible platform results.
yuanyongvia@gmail.com