VSVaultStageOperator handbook
HandbookIncident guide
Incident guide

Something looks wrong

Find the owner of the fact before changing anything. Most expensive mistakes come from making a second system imitate the first.

How it works

  • Physical unit, location, receiving, shipment or inspection → WMS Admin
  • DTC order, customer, payment, refund, reservation or ATS → Medusa Admin
  • Storefront content or publication → DTC Manager
  • Cross-system event, queue, replay or disagreement → DTC Manager → Operations
  • Wholesale customer or order → Sales Portal
  • Customer-visible rendering only → Storefront

  1. 1Record the order, transfer, event, shipment or product identifier.
  2. 2Note the last confirmed state in each relevant app.
  3. 3Check the audit or movement history before retrying.
  4. 4Use the narrow recovery action for that exact item.
  5. 5Verify the destination changed and the queue cleared.

  • Create a duplicate product, order or shipment to replace a missing projection
  • Edit inventory in Medusa to imitate a WMS movement
  • Refund a normal return before WMS inspection
  • Retry a conflicting event without understanding why it conflicts
  • Call a green page or HTTP 200 proof that the business action completed
VaultStage operator handbookWhen systems disagree, use the app that owns the fact.

Search the VaultStage handbook

Search app guides and workflows