Pricing rules

A rule covers one card class on one marketplace. You set the bounds; the engine computes a price inside them from live market data.

Suggests, then applies

On most plans the engine suggests and you set the price with a click — nothing reaches a marketplace without you. Fully automatic application is a Professional · Automate capability.

This is deliberate: a rule that moves prices on its own should be a decision you made once, explicitly, not the default.

The bounds you set

A floor. Below it you do not sell, whatever the market does.

A ceiling. Its real job is catching a typo — 1.80 typed where 0.18 was meant — before it reaches a marketplace.

A reliability gate. Below this score the rule stays silent for that machine. Vast drops machines from search below its own threshold, so 90% is the safe side of it; on Clore the machine stays listed either way and the gate mostly keeps the rule quiet while a new machine’s score climbs from near zero.

Never raise during a rental, optionally. A rental extends only while the offer is not dearer than the contract, so a raise ends it quietly — the renter finishes the term and leaves. If you would rather keep a paying tenant than catch a price rise, turn this on.

When a rule stays silent

Silence is a result, and the panel always says which of these it is:

• The market is too thin. Fewer offers than the engine needs. A median over a handful of offers moves tens of percent when one seller leaves, so no price is suggested at all.
• The card has not been sampled on that marketplace yet.
• No machine of that class is here, or none is listed — the rule waits.
• Reliability is below the gate, or the marketplace reports none, so the gate cannot be checked.
• The goal is not computable from market data alone.

Two things a rule does not touch

Machines under maintenance. Announcing a maintenance window takes the machine out of the rule entirely.

Currencies you pinned to their own amount. On Clore you can pin a currency to a fixed price; the rule moves the dollar price and leaves pinned currencies alone. A renter paying in one keeps the old price until you unpin it.

Setting up a first rule

Start with one card class, a floor you would genuinely accept, and a ceiling about twice your normal price. Watch the decision log for a few days before adding more — the log tells you whether the rule would have done something sensible, without it having done anything yet.

The decision logWhat the engine decided, and what the market looked like when it decided.