Skip to content
DP-RETURNSReviewed · 2026-11-19Desktop 1.8 · Companion 1.1.1Lire en français

Sales, returns and unsold items ​

An item returning through mail is a signal to inspect. It does not alone prove the price should fall or distinguish expiration from cancellation. D&P uses saved TSM history and keeps those outcomes separate.

Changing the routine ​

“Select All in TSM, then post everything green” applies a pricing operation across the bags. D&P starts with a selection: ready items, items to check and paused items. TSM remains the scanning and posting tool; D&P adds a decision filter before the scan.

Desktop stateMeaningHuman action
ReadyKnown stock, recent enough quote, no higher-priority blockPrepare a small batch and verify in TSM
CheckMissing/stale price or uncertain stock identityRefresh or inspect the variant
PausedManual hold or repeated expirationsKeep outside the active selling group
PreparedA relisting decision has been recordedImport/apply the group and scan
HistoryNo available stock or manually handledInspect history; no implicit new listing

Three expired lots since the last sale trigger an automatic pause. A cancellation is a different signal. Event quantity and lot count are not interchangeable: a stack of 20 is 20 units but one listing.

What “ready” means ​

The desktop suggests at most one unit for equipment, exact variants or items with replacement cost of at least 10s; otherwise at most five units, limited to stock outside the AH. The price must be a positive integer and recent enough. A regional reference far below the quote reduces the trial to one unit.

Relisting and production are different decisions

Potential post-fee unit proceeds below replacement cost add a belowReplacement warning to desktop preparation. This flag does not always block relisting an already-owned item. For example, a 100s ask, 5% fee and 97s cost yield 95s net: the flag applies even though the asking price exceeds cost. Restocking requires a positive reference margin before creating more inventory.

The Companion adds Keep and Vendor states. It compares potential net proceeds with vendor value and a configurable minimum benefit; this is not manufacturing profit. Bound and quest items remain in Keep. See settings.

Avoid counting the same mail again ​

The journal groups events by identity and keeps the largest cumulative quantity already observed. Reloading the same file does not create a new sale. Existing history becomes the initial baseline; later additions can be marked as new returns.

Manual decisions carry a revision. Relevant data changes invalidate them instead of silently applying an old decision to a new state. Undoing a batch preparation is available only while the corresponding state remains unchanged.

Read the two handoffs to act in the game, and profitability and capital to interpret monetary values.

A local-first advisor. Estimates stay visible.