A credential must not cross stores
Autopricy associates marketplace access with the actual shop and uses that context for eligible operations.
Feature / multi-store operations
Manage many marketplace stores without mixing their authority
Autopricy brings supported stores into one operational workspace while keeping credentials, identifiers, rules, tasks and results scoped to the correct shop. Teams can filter and act in bulk without turning a shared view into shared authority.
Multi-store repricing
Scale creates identity risk before it creates convenience
When stores share a dashboard, every read and write still needs the correct platform, account, shop, SKU and rule context.
Bulk actions need an explicit scope
Filters, selected rows and task records make it clear which stores and Offers are included.
Results need store-level evidence
A global success count is not enough; operators need the relevant shop, item and platform status.
Marketplace mechanics
What stays scoped in a multi-store workflow
| Connection | Marketplace authorization and seller identity remain attached to one shop record. |
|---|---|
| Data | Products, Offers, Listings and Articles retain their platform and shop context. |
| Rules | Minimum, maximum and repricing settings apply to the selected eligible records. |
| Tasks | Bulk execution and status history identify the originating store and operation. |
Multi-store pricing is not ERP expansion
Autopricy centralises repricing and adjacent Offer operations where verified. It does not claim to replace order management, warehouse, procurement, finance or logistics systems.
Workflow
Add stores with an auditable boundary
Create the shop record
Choose the correct platform and store identity before adding authorization.
Synchronise a bounded scope
Confirm exact products and Offer identities without relying on approximate matches.
Filter before bulk action
Use shop, platform, SKU, status and rule conditions to define the target set.
Review task-level results
Check per-store progress and failures instead of relying only on a global completion message.
Operational example
One filter should define one clear target set
Example: an operator filters OnBuy Store A for active Listings without minimum prices. A bulk rule action should target only those visible records, create a traceable task and leave Store B and every other platform untouched.
Related resources
Continue with the relevant workflow
FAQ
Manage many marketplace stores without mixing their authority: common questions
Can one account manage stores on different marketplaces?
The workspace can present supported stores together, while each shop keeps its own authorization, data and platform adapter.
Can I apply rules in bulk?
Supported workflows can use filters and selected records for batch operations. The target scope should be explicit before execution.
Does multi-store management include orders and warehouses?
No. Autopricy is focused on repricing and adjacent Offer operations, not full ERP functions.
How are failures investigated?
Task and item context should preserve the shop, operation and platform result so failures can be reviewed without guessing.
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