POE2 Rare Item Repricing Workflow: Keep, Relist, Reduce, or Stop

A quiet listing does not reveal the correct price by itself. Turn uncertainty into a documented, reversible test.

Define the plausible buyer before choosing a price

Separate item quality from a vague belief that the item should be valuable.

• Describe the build problem the item could plausibly solve without claiming that a particular build currently dominates demand.
• List the properties that support the same use case and flag properties that pull the item toward conflicting uses.
• Record whether keeping the item for personal use is a credible alternative to listing it.

Turn comparisons into documented assumptions

Prevent visible asking prices from being treated as proof of what buyers will accept.

• Record why each comparison appears relevant, including item type, use case, and meaningful property differences.
• Exclude comparisons that depend on an unclear buyer case or materially different item characteristics.
• Write the starting price as a testable assumption rather than a confirmed valuation.

Run one controlled listing test

Make the result interpretable and easy to reverse.

• Save the initial listing details and the reason for the chosen test.
• Change only one variable, such as the asking price or comparison set, before observing the next result.
• Use comparable exposure periods when possible so a short test is not judged against a much longer one.
• Log whether meaningful buyer interest appears without interpreting silence as proof of a precise market value.

Choose keep, relist, reduce, or stop

Convert an uncertain result into a bounded next decision.

• Keep the item when its personal-use value outweighs the uncertain listing case.
• Relist when the buyer case remains plausible but the original comparison or presentation was poorly matched.
• Reduce the asking price when the use case remains coherent but the current test produces no meaningful interest.
• Stop actively listing when repeated review cannot establish a convincing buyer use case or when further attention is not worthwhile.

Apply a patch-aware review gate

Avoid turning recent patch activity into unsupported economy conclusions.

• Note the update context when recording a pricing test.
• Recheck the item's buyer-use assumptions after relevant item, build, or economy information changes.
• Do not infer a market increase or decline from the patch index alone; the supplied official evidence provides no economy-impact details.

Preserve the decision record

Make later repricing decisions consistent rather than reactive.

• Keep the item description, comparison rationale, test dates, changed variable, and observed result together.
• Review the record before repeating a previous test.
• Close the active listing decision when a predefined stop condition is met.

Decision checklist

• Write one plausible buyer use case for the item.
• Identify which item properties support that same use case.
• Record why each comparison is relevant before using it.
• Label the starting price as an assumption rather than a confirmed value.
• Change only one listing variable during each test.
• Use comparable observation periods when practical.
• Define keep, relist, reduce, and stop conditions before testing.
• Recheck assumptions after relevant new patch or economy information appears.

Worked example

A player believes a rare amulet should command a high price, but the listing receives no meaningful interest. They first describe a plausible buyer and group the amulet's properties by whether they support that use case. They then remove comparisons that only share one eye-catching property and document the remaining differences. Instead of applying an unsupported markdown percentage, they preserve the original record and test one lower asking price over a comparable period. If interest remains absent, they revisit the buyer case before reducing again. They keep the item if it has personal use, relist it if the comparison set was weak, reduce it if the use case remains credible, or stop actively listing it if no convincing buyer case remains.

Common mistakes

• Treating visible asking prices as evidence of completed demand.
• Choosing a precise valuation without current market or completed-transaction evidence.
• Changing the price, description, and comparison set in the same test.
• Assuming no immediate interest proves that the item has no value.
• Repeatedly reducing the asking price without a predefined stop condition.
• Attributing a market movement to a patch index that contains no economy-impact details.

Related guides