Darty repricer / marketplace sellers

Darty repricing with marketplace-specific competitor handling

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

Shared XML does not make FNAC and Darty interchangeable

The transport format can be shared while seller identity, shop type and competitor choice still require marketplace-specific logic.

01 / ACCOUNT

The correct Darty shop must own the action

Autopricy keeps shop credentials and Offer identity scoped to the Darty account.

02 / COMPETITION

Competitor selection is platform-specific

The repricer uses Darty-specific handling instead of inheriting another marketplace’s seller comparison blindly.

03 / PROCESSING

Batch processing takes time

Submission, waiting, marketplace confirmation and failure are shown as different stages.

Marketplace mechanics

How Darty repricing is controlled

SynchroniseRead the Darty Offer and retain its exact shop, SKU and marketplace identity.
CompareEvaluate only the competing Offers that meet the Darty workflow’s current criteria.
ConstrainKeep the target between the seller-defined minimum and maximum.
ConfirmSubmit through XML and track the later batch status before reporting a final result.

No guaranteed winning Offer

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

Validate one Darty store first

Confirm the account

Check the Darty shop identity and authorization path.

Inspect Offer data

Review exact SKU, current price, available competition and status.

Set the safe range

Add minimum, maximum and difference rules to a controlled product set.

Watch batch results

Expand only after processing and confirmation behave as expected.

Illustrative workflow

A Darty update should remain pending

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.

FAQ

Darty repricing with marketplace-specific competitor handling: common questions

Does Autopricy treat Darty exactly like FNAC?

No. The XML boundary is shared, but the marketplace type, store identity and competitor handling remain explicit.

Will Darty repricing always choose the lowest price?

No. The configured rule and boundaries determine eligible targets; continuous price cutting is not the objective.

Can a submitted Darty price still fail?

Yes. A marketplace batch can remain pending or return an error after submission, so confirmation is tracked separately.

Is Darty repricing available for every account configuration?

The account and current API capability are reviewed before activation.

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