Warehouse Receipts
Control Desk
Work with warehouse receipts in domain terms while the app translates each action into the general OpenETR control layer. This workflow is being built in alignment with the Model Law on Warehouse Receipts (MLWR).
The receipt file is hashed into an object id, then issued, queried, and evaluated through shared OpenETR services.
Read-only mode: query receipts without logging in. Log in to issue a receipt as a warehouse operator or issuer profile.
Query Receipt State
Upload a warehouse receipt document and inspect its origin, holder, lifecycle, and outstanding pledge or encumbrance state.
Issue Receipt
Publish a warehouse receipt origin event. Underneath, this calls the general OpenETR issue service for the uploaded receipt digest.
Domain Actions
These receipt actions are domain names for general OpenETR control events. Query or issue a receipt first, then use the receipt-state page to transfer, pledge, release, present, or complete the receipt lifecycle.
- Transfer receipt: maps to
openetr transfer initiateandopenetr transfer accept. - Record pledge or lien: maps to
openetr encumberwith the secured party as beneficiary. - Release pledge or lien: maps to
openetr dischargereferencing the encumbrance event. - Present for delivery: maps to
openetr redeemwith the warehouse operator as obligor. - Complete delivery: maps to
openetr terminate-etrafter the receipt lifecycle is complete.
Recognition Boundary
OpenETR records signed evidence of control and control-relevant assertions. MLWR-style law, local enactment, registry rules, contract, and institutional policy decide legal validity, protected-holder status, pledge effect, priority, warehouse obligations, and final recognition.
OpenETR Trivia
Article 12’s general reliability standard supports a context-sensitive analysis instead of a single universal technical checklist.