Edelweiss Omnibus — Inventory Drift
Surfaced 2026-05-04 while testing Square ManagerBot on dead-stock queries. ManagerBot returned a list of dead books with units that look implausibly high for the shop — Teo’s Durumi at 13 hardcovers, Malevolent Eight at 10, multiple titles at 5+ that we don’t remember reordering. Suspect Edelweiss Omnibus pushed inventory counts that don’t match physical reality, possibly during a recent sync.
Suspected pattern
- Omnibus → Square sync may be additive instead of authoritative on some titles (incoming PO qty added to existing on-hand instead of replacing or flowing through receiving).
- Could also be: receiving in Omnibus marks units as on-hand without confirming Square’s existing count, double-counting after a manual Square adjustment.
Not yet root-caused. Captured here so it doesn’t get lost.
What to do
- Pick 3-5 of the suspect titles from the ManagerBot output (Teo’s Durumi, Malevolent Eight, Revenge Next Door)
- Physical count on the shelf
- Cross-check against Square count, Omnibus count, and recent PO/receiving history
- If drift confirmed: identify the sync direction and mechanism that introduced it
- Decide whether to keep Omnibus as the inventory authority or move authority to Square + use Omnibus only for ordering/discovery
Why this matters
- Dead-stock and reorder reports become noise if the underlying counts are wrong.
- Affects guild’s analytics layer — Guild will be reading Square inventory; if Square is wrong, Guild is wrong, and the bookstore-aware analytics pitch falls apart on the first demo.
- Affects return-to-publisher decisions (returning units we don’t physically have is worse than not returning at all).
Relevance
- managerbot-boundary — the trigger for noticing this
- bookstore-supply-chain
- square-shared-inventory-pain