Invalid ranges must not run
A missing value, non-numeric input or minimum above maximum should block activation.
Feature / price safety
Minimum and maximum prices are hard operating boundaries
Autopricy evaluates eligible repricing actions inside seller-defined minimum and maximum values. The boundaries are attached to the real Offer and visible in operations, so a competitive target cannot silently become an unprofitable price.
Repricing safety
A floor is useful only when validation and execution agree
Price safety depends on correct Offer identity, valid numeric boundaries, the calculation path, and the submitted value—not only a form field in the interface.
Boundaries belong to a specific Offer
Autopricy keeps the rule tied to the correct store and SKU rather than guessing from EAN or list position.
Protection should be an observable result
When a computed target crosses a boundary, operations should show that the guardrail stopped or changed the action.
Marketplace mechanics
How price boundaries affect a decision
| Validate | Require numeric values and a minimum that does not exceed the maximum. |
|---|---|
| Calculate | Run the marketplace-specific rule using the available market input. |
| Constrain | Block or clamp a target that would leave the approved range, according to the configured workflow. |
| Record | Persist the reason, target and resulting action so the operator can audit the decision. |
Your floor must reflect your business costs
Autopricy enforces the values you configure; it does not calculate your true margin automatically. Sellers remain responsible for fees, tax, shipping, promotions, currency and other costs when setting a safe minimum.
Workflow
Set boundaries before enabling automation
Calculate the commercial floor
Include the costs and margin requirements relevant to the store and product.
Set a realistic ceiling
Define how far a winning Offer may recover without leaving the intended range.
Validate on real Offers
Check store, SKU, currency and current price before activation.
Review protection events
Use history to find products repeatedly hitting the floor or ceiling.
Illustrative calculation
A target below the floor should not be sent
Example: an Offer has a €20.00 minimum and €28.00 maximum. A competition rule calculates €19.75. The safe outcome is a protected decision—not a €19.75 submission. Whether the workflow holds at €20.00 or skips the action is made explicit in the applicable rule.
Related resources
Continue with the relevant workflow
FAQ
Minimum and maximum prices are hard operating boundaries: common questions
Does Autopricy calculate my minimum price?
No. The seller sets the business boundary. Autopricy validates and enforces it in eligible repricing workflows.
What happens if minimum price is above maximum price?
The rule is invalid and should not be activated until the range is corrected.
Can different Offers have different boundaries?
Yes. Boundaries are associated with the real store Offer so products can use different commercial limits.
Will a winning Offer always rise to the maximum?
No. A raise depends on the platform capability and configured strategy; the maximum is a ceiling, not an automatic target.
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