FAQ & Tips

Practical answers to common questions, plus tips from experienced HippoLink users to help you get the most out of repricing.

Frequently Asked Questions

My rule isn't matching any cards. What's wrong?

Check these things in order:

1. Is the rule active? Inactive rules are skipped during evaluation. Toggle it on in the rule list.
2. Is a rule above it catching those cards first? Remember, repricing uses first-match-wins. If a broader rule sits above yours, it grabs the cards before your specific rule gets a chance. Move your specific rule higher.
3. Is a price variable null? If your condition checks TCGPLAYER_LOW_NM >= 1.00 and TCGPlayer doesn't have data for that card, the comparison fails. Add an IS_NOT_NULL check.
4. Are string values exact? Attribute values are case-sensitive and must be in single quotes in DSL mode. 'NM' works, 'nm' does not, NM (no quotes) does not.

A card's price didn't change after running repricing. Why?

• No rule matched. If none of your rules' conditions match a given card, its price stays the same. Check that your rule set has a catch-all at the bottom.
• The guard blocked the change. If the calculated price was too far from the current price, the Guard capped the move. The new price might be very close to the old price, or identical if the guard is tight. See Adjust, Limit & Guard.
• The price source is the same. If your rule says SET PRICE TCGPLAYER_LOW_NM and TCGPlayer Low NM happens to equal your current price, there's no change — which is correct.

Can I undo a repricing run?

There is no automatic "undo" button. However:

• Your previous prices are visible in inventory history.
• You can adjust your rules and run again to correct any issues.
• Guards are the best prevention tool — they cap how far a single run can move a price.

Use Guards while you're learning. They're training wheels that prevent any single mistake from causing large-scale damage.

How do I handle cards that TCGPlayer doesn't have data for?

Use a FIRST_DEFINED fallback chain in your price action:

SET PRICE FIRST_DEFINED(TCGPLAYER_LOW_NM, CARDKINGDOM_RETAIL_NM, MANAPOOL_LOW_NM, 0.99)

The system tries each source in order and uses the first non-null value. The hardcoded number at the end guarantees a price is always set.

You can also add a dedicated catch-all rule at the bottom of your rule list that uses a fallback chain.

What happens if I have no rules at all?

Nothing. Repricing won't change any prices if the rule list is empty. Your inventory stays as-is.

Can two rules apply to the same card?

No. Only the first matching rule applies. If Rule 2 and Rule 5 would both match a card, only Rule 2's price action takes effect. This is by design — it keeps pricing deterministic and predictable.

Is there a limit on how many rules I can create?

There's no hard limit, but we recommend keeping your rule set under 20–30 rules for manageability. If you find yourself creating dozens of nearly identical rules, look for ways to consolidate using broader conditions or fallback chains.

Operational Tips

Start Small, Verify, Then Expand

Don't build 15 rules on day one. Start with 2–3 simple rules, run repricing, and check the results in your inventory. Once you're confident they work as expected, add more complexity.

Always Use a Catch-All Rule

Your last rule should be broad enough to match everything that the rules above it missed. A catch-all prevents "orphan" cards from going unpriced. Example:

IF CONDITION IS 'NM'
THEN SET PRICE FIRST_DEFINED(TCGPLAYER_LOW_NM, CARDKINGDOM_RETAIL_NM, 0.99)

Use Guards While You're Learning

Guards limit how much a price can change in a single run. Set MAX_DECREASE 15% MAX_INCREASE 25% on your rules until you're confident in them. You can always relax or remove guards later.

Be Specific First, Broad Last

Order your rules from most specific to most general:

1. New releases (specific time window)
2. Foils (specific finish)
3. High-value cards (specific price threshold)
4. Stale inventory (specific date condition)
5. Standard cards (general condition check)
6. Catch-all (matches everything)

Check Null States

The most common "gotcha" in repricing is null price data. Get in the habit of:

• Adding IS_NOT_NULL checks on any price variable you use in conditions.
• Using FIRST_DEFINED in price actions when you're not 100% sure data exists.

Save Often, Run Deliberately

• Save after each rule edit — don't batch 10 changes and save once.
• Run repricing only when you're ready to apply changes. Saving doesn't change prices; running does.

Review Your Results

After a repricing run, spot-check 10–20 cards in your inventory:

• Do the prices look reasonable?
• Are any cards priced suspiciously low or high?
• Did the catch-all rule work for obscure cards?

If something looks off, check which rule matched (or didn't match) and adjust accordingly.

Keep Rules Named Clearly

Give each rule a descriptive name that tells you what it does at a glance:

Clear names save time when you're reordering or debugging rules three months from now.

Common Pitfalls

Getting Help

If you run into an issue that this documentation doesn't cover:

• Review the Repricing Overview for a refresher on concepts.
• Check the Real-World Examples for end-to-end walkthroughs.
• Contact HippoLink support — we're happy to review your rule set and suggest improvements.