By YX Fulfillment
When a pick is cancelled, an append-only stock ledger can preserve the original pick and add a compensating movement. This helps a reviewer answer both “How many units remain?” and “Why did the recorded balance change twice?” Replacing the original row with a zero leaves the first question answerable at the cost of the second.
The synthetic ledger here supports one full reversal per pick. The reversal has a reference to the original ID and derives its quantity from that movement. It has its own audit ID.
from dataclasses import dataclass
@dataclass(frozen=True)
class Movement:
event_id: str
delta: int
reverses: str = ""
class Ledger:
def __init__(self, opening):
self.opening = opening
self.entries = {}
@property
def balance(self):
return self.opening + sum(event.delta for event in self.entries.values())
def pick(self, event_id, units):
if event_id in self.entries or not 0 < units <= self.balance:
raise ValueError("Invalid pick")
self.entries[event_id] = Movement(event_id, -units)
def reverse_pick(self, event_id, original_id):
original = self.entries.get(original_id)
already_reversed = any(row.reverses == original_id for row in self.entries.values())
if event_id in self.entries or original is None or original.delta >= 0 or already_reversed:
raise ValueError("Invalid reversal")
self.entries[event_id] = Movement(event_id, -original.delta, original_id)
ledger = Ledger(10)
ledger.pick("E-1", 3)
assert ledger.balance == 7
ledger.reverse_pick("E-2", "E-1")
assert ledger.balance == 10
running = ledger.opening
for row in ledger.entries.values():
running += row.delta
print(row.event_id, row.delta, "reverses:", row.reverses or "-", "balance:", running)
try:
ledger.reverse_pick("E-3", "E-1")
except ValueError as error:
print(error)
else:
raise AssertionError("pick was reversed twice")
assert ledger.balance == 10
Output from a local run on Python 3.9.6
E-1 -3 reverses: - balance: 7
E-2 3 reverses: E-1 balance: 10
Invalid reversal
The final balance returns to ten through a traceable debit and credit. The ledger rejects a second reversal even under a different event ID. If an operation restores only part of a pick, model the remaining reversible quantity explicitly and add tests for cumulative over-reversal. An actual warehouse may also place recovered items in inspection or quarantine before moving them into available stock.
This example is an in-memory, single-item replay. For concurrent writes, enforce identity and reversal rules transactionally with constraints appropriate to the database. Log the original event, confirmed movement, reason, and responsible actor under the site's own audit and permissions policy.
Top comments (0)