Running Repricing

Once you've built your rules, the next step is saving them and running repricing against your inventory. This article explains the save/run workflow and what happens behind the scenes.

Saving Your Rules

After editing a rule on the canvas, click the Save button in the canvas footer. This sends your complete rule set to the HippoLink server.

Important: HippoLink saves all rules at once, not just the one you're currently editing. This ensures your rule set stays consistent.

Unsaved Changes

If you've made changes but haven't saved, the footer shows an unsaved changes indicator. Navigating away from the repricing page triggers a warning so you don't lose work.

If you want to discard changes, click Discard. This reloads the last saved version from the server.

Running Repricing

Click the Run Repricing button to start a repricing job. This button is in the canvas footer, next to the Save button.

When you click Run:

1. HippoLink saves your rules first if there are unsaved changes.
2. A repricing job is queued on the server.
3. The system evaluates every item in your inventory against your rules, in order, to calculate a new price.
4. Updated prices are applied or staged, depending on your store settings.

What the System Evaluates

For each item in your inventory:

• The system reads the item's attributes (condition, printing, language, game, set, etc.).
• It walks your rules from top to bottom.
• The first rule whose conditions match wins and its price action is applied.
• If no rule matches, the item's price is left unchanged.

This is the same "first match wins" logic described in Rule Order & Evaluation.

Job Status

After you start a run, the interface shows a status indicator. You might see:

You can navigate away from the repricing page while a job runs — it won't be interrupted. Come back later to see the results.

How Often Should You Run Repricing?

That depends on your store and how competitive your market is. Some guidance:

• Daily is a solid default for most stores. Market prices shift overnight, and a daily run keeps you current.
• After major price movements — if a new set releases or a card spikes, run repricing promptly.
• After editing rules — always run after changing your rules so the new logic takes effect.

Repricing does not run automatically on a schedule (yet). You control when it runs.

Guard Protections During a Run

If you've set Guard blocks on your rules, they act as safety rails during execution. If a calculated price would change an item's price by more than the guard thresholds, the guard prevents that change. This means:

• A card won't suddenly drop from $50 to $5 because of a data error.
• A card won't spike from $2 to $200 because of a temporary market anomaly.

See Adjust, Limit & Guard for details on configuring guards.

After a Run Completes

Once repricing finishes:

• New prices are reflected in your inventory.
• You can review the results in the Inventory section to verify that prices look correct.
• If something doesn't look right, adjust your rules and run again. Repricing is non-destructive in the sense that you can always re-run with updated rules.

Tips

• Save early and often. Don't build 15 rules and then save for the first time.
• Run repricing after every rule change. Saved rules don't affect prices until you run.
• Start with a small rule set and verify the results before adding complexity.
• Use Guards while you're getting started — they prevent any single run from making drastic changes.

What's Next

• Price Variables Reference — every price variable you can use in conditions and actions.
• Real-World Examples — complete rule walkthroughs for common store scenarios.