Skip to main content
HippoLink logo
HippoLink Docs

Building Conditions

Conditions define which listings a rule applies to. They form the IF section of every rule. A listing must satisfy all the conditions in a rule before the price action fires.

The Component Palette

The right panel of the repricing interface contains five draggable condition types. To add one, drag it from the palette and drop it onto the IF section on the canvas.

The component palette with all condition types

Condition Types

Price Condition

Compares a price variable against another variable or a fixed dollar amount.

Use it when: you want to filter listings based on market price thresholds — for example, only reprice cards where TCGPlayer Low is at least $1.00.

A price condition card

Fields:

Field Description
Left value The price variable or fixed number on the left side of the comparison.
Operator How to compare: is at least (≥), is at most (≤), is greater than (>), is less than (<), or equals (=).
Right value The price variable or fixed number on the right side.

Both left and right values can be either a market price variable (like TCGPlayer Low NM) or a fixed number. Use the dropdown to select a variable; select "Fixed number" to type a dollar amount.

Common examples:

  • TCGPlayer Low (NM) is at least $1.00 — only apply this rule to cards worth $1 or more.
  • Current Price is greater than TCGPlayer Low (NM) — only apply if the card is currently priced above market.
  • Current Quantity is greater than 10 — target cards you have a lot of in stock.

Attribute Condition

Filters listings by card properties like condition, finish, rarity, or language.

Use it when: you want to target specific types of cards — for example, only Near Mint non-foil rares.

An attribute condition card

Fields:

Field Description
Attribute Which property to check: Condition, Finish, Rarity, or Language.
Operator is, is not, is one of, or is not one of.
Value The value(s) to match against. Options change based on the attribute.

Attribute values:

Attribute Possible Values
Condition Near Mint, Lightly Played, Moderately Played, Heavily Played, Damaged
Finish Foil, Non-Foil, Etched
Rarity Common, Uncommon, Rare, Mythic
Language English, Japanese, German, French, and others

Common examples:

  • Condition is Near Mint — only NM cards.
  • Finish is not Foil — exclude foils.
  • Rarity is one of Rare, Mythic — only rares and mythics.

Date Condition

Compares a listing date against a specific date or a relative time period (e.g., "more than 4 weeks ago").

Use it when: you want to target cards based on how long they've been in inventory, when they last sold, or when the product was released.

Fields:

Field Description
Date variable Which date to check (e.g., Oldest Copy Insertion Date, Latest Copy Sold Date).
Operator is at least, is at most, is greater than, is less than, or equals.
Compare to A relative period (e.g., "4 Weeks Ago", "3 Months Ago") or a specific date.

Date variables:

Variable What It Tracks
Oldest Copy Insertion Date When the oldest copy of this card was first added to your inventory.
Newest Copy Insertion Date When the most recent copy was added.
Latest Copy Sold Date When the last copy of this card was sold from your store.

Relative periods: Today, Yesterday, 3 Days Ago, 1 Week Ago, 2–4 Weeks Ago, 2–6 Months Ago.

Common examples:

  • Oldest Copy Insertion Date is less than 4 Weeks Ago — cards sitting in inventory for over a month.
  • Latest Copy Sold Date is at least 3 Days Ago — cards that sold recently (don't discount them).

Null Check

Verifies whether a price variable has data available. Market data isn't always present for every card — a source might not have a listing.

Use it when: you're about to use a market price in your rule and want to make sure the data exists first. Without a null check, a rule could produce unexpected results if the referenced variable has no data.

Fields:

Field Description
Variable The price variable to check.
Check type is null (no data available) or is not null (data exists).

Common examples:

  • TCGPlayer Low (NM) is not null — only apply this rule when TCGPlayer has pricing data.
  • Card Kingdom Retail (NM) is null — apply only when Card Kingdom has no listing (useful for fallback rules).

Nested Group

Creates an AND/OR sub-group for complex logic. See Combining Conditions for full details.

Editing a Condition

Once a condition card is on the canvas, its fields are immediately editable. Use the inline dropdowns and inputs to configure the condition. Changes are applied in real time — you'll see the rule update as you adjust values.

Removing a Condition

Click the × button on the right side of any condition card to remove it from the rule.

What's Next