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 its OpenETR control graph is created, queried, and evaluated through shared services.
Read-only mode: query receipt control status without logging in. Log in to create control records as a warehouse operator or issuer profile.
Query Control Record
Upload a warehouse receipt document and inspect the OpenETR control record associated with its digest.
Create Control Record
Publish the initial OpenETR control record for an already-issued warehouse receipt document.
Domain Actions
These receipt actions are domain names for general OpenETR control events. Query or create a control record 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
UNCITRAL notes that some items, such as letters of credit, may be treated differently across jurisdictions, which affects scope questions.