Seller guide / FNAC and Darty
FNAC and Darty repricing: what is shared and what must stay separate
FNAC and Darty can share an XML 2.6 integration boundary, but they are not interchangeable marketplaces. Store identity, seller filtering, competitive context and ranking information must remain explicit for each platform.
See FNAC and Darty repricingNeed the product workflow first? Review the FNAC and Darty repricer page for supported capabilities and limits.
The shared technical boundary
Both workflows can use the same XML 2.6 style of Offer exchange and asynchronous batch handling. Shared parsing, validation and batch-status components reduce operational duplication.
That shared transport does not justify copying marketplace type, account identity or competitor-selection logic. The action must still originate from the correct FNAC or Darty shop.
How FNAC presents Offers
FNAC’s public ranking information describes priority and increasing-price ordering in relevant marketplace contexts. It also lists seller-quality factors such as ratings, complaint history or professional status for some partner Offer situations.
A repricer should therefore treat price as an important input without claiming it is the only determinant of placement. Available delivery data should be interpreted consistently when comparing Offers.
How Darty differs
Darty’s marketplace information exposes alternate ordering criteria such as seller rating and delivery time. Its customer guidance also shows that partner delivery modes and estimated delivery dates matter to the buying experience.
The Darty workflow must retain its own seller identity and marketplace-specific competitor handling even when the XML submission mechanism resembles FNAC.
Batch status is part of the workflow
An eligible target is placed in an XML update batch. The batch identifier proves submission, not a live price. Processing can remain pending or return item errors, so the system must poll and store the later result.
Keep calculated, submitted, processing, confirmed and failed states separate. This makes failed items visible instead of hiding them behind a successful batch request.
Practical rollout
Start with one store and a small Offer set on each platform. Confirm seller identity, SKU, current price, available competition, delivery context and boundaries. Then compare submitted batches with later marketplace status.
If both FNAC and Darty are connected, test them independently. A successful FNAC path is useful technical evidence, but it does not prove that Darty business logic is correct.
Primary sources
FNAC and Darty repricing FAQ
Are FNAC and Darty repricing identical?
No. They share parts of the XML boundary, but marketplace identity, seller filtering and competitive logic remain separate.
Does XML batch submission mean the price is live?
No. The batch still needs processing and item-level status must be reviewed.
Is price the only ranking factor?
No. Public FNAC and Darty information also describes seller-quality, rating, delivery or related criteria.
Can one store credential update both platforms?
Store authority stays scoped to the actual marketplace account; it should not be inferred or shared.
Related resources
Continue from guide to implementation
Test the workflow on a real store
Start with one supported store, a controlled product scope and visible platform results.