Each store keeps its own authority
Credentials, identifiers, channels and actions stay scoped to the connected shop.
Multi-marketplace repricing / Europe
One repricing workspace, marketplace-specific execution
Autopricy gives cross-border sellers one place to manage pricing rules and execution history across supported European marketplaces. The workspace is shared; authorisation, data, competition, submission and confirmation remain platform-specific.
Cross-border pricing operations
Centralised control should not erase marketplace differences
A seller needs one operational view without pretending that every marketplace exposes the same Buy Box, competitor data, rate limit or update method.
A common UI can hold different logic
Teams can use familiar minimum, maximum and status concepts while the adapter handles marketplace-specific details.
One history, honest states
The shared view keeps calculated, protected, submitted, processing, confirmed and failed states distinct.
Marketplace mechanics
Current repricing scope
- WortenMature Offer repricing and confirmation workflow.View platform details
- FNACXML Offer updates, seller comparison and batch status.View platform details
- DartyDarty-specific competitor handling through the XML workflow.View platform details
- OnBuyProduct/Listing sync, winning checks and bounded raise/decrease.View platform details
- CdiscountOAuth, rules, packages, feedback and read-back.View platform details
- Selected Mirakl operatorsAssessed per operator; no universal compatibility claim.View platform details
Autopricy is not an ERP
The core scope is repricing, competitive Offer monitoring, bounded price automation and multi-store operations, with adjacent collection or listing workflows where verified. It is not positioned as order, warehouse, procurement, finance or logistics management software.
Workflow
Add marketplaces without losing control
Map current stores
List each operator, account, country, SKU volume and current pricing owner.
Validate adapters
Confirm available data, limits, identity and update semantics per marketplace.
Apply store-safe rules
Configure boundaries and strategies without sharing credentials or state across shops.
Review one history
Use the common view to find protected, pending, confirmed and failed actions.
Operational example
A shared dashboard does not mean shared logic
Example: a team may use the same minimum/maximum workflow for Worten, FNAC and OnBuy. Underneath, Worten uses its Offer/channel path, FNAC submits XML batches, and OnBuy checks Product/Listing and winning state. The shared interface reduces switching; it does not flatten those differences.
Related resources
Continue with the relevant workflow
FAQ
One repricing workspace, marketplace-specific execution: common questions
Which marketplaces currently have repricing pages?
This release covers Worten, FNAC, Darty, OnBuy, Cdiscount and selected Mirakl-powered operators. Each page states its own limitations.
Is Fyndiq included as a competitive repricer?
No. Current Fyndiq capability is positioned around Article and listing price or inventory operations, not a competitor-driven repricing engine.
Can one rule be copied to every marketplace?
The UI concepts can be familiar, but eligibility, market inputs and action semantics must be validated per platform.
Does Autopricy manage orders or warehouses?
No. Autopricy is not positioned as an ERP for orders, warehousing, procurement, finance or logistics.
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