Produce subscriptions and redemption
https://docs.hazbase.com/en/use-cases/agriculture-token/deep-dive/

USE CASES
 ← All use cases Produce subscriptions and redemption
 Connect purchased deliveries with dispatch, receipt and unused entitlements.
 Equipment & business assets Example architecture 
 The scenario
 For Farms, producer groups and food subscription operators
 Issue four delivery vouchers for a produce subscription and consume one per dispatch. Manage addresses and delivery dates in the order system.
 What this makes visible
 Producers can track outstanding deliveries, while customers see remaining entitlements and receipt history.

 Token and business-data roles
 Represented by tokens
 Represent box-redemption quantities with PrivilegeEdition. Distinguish types and orders when products, origins or delivery periods differ.

 Managed in business systems
 Order ID, box contents, dispatch schedule, delivery address, receipt status and substitutions/cancellations.

 Map project, asset or order IDs to chainId, contract address and tokenId where applicable. Link the operation ID to the confirmed transaction so the application can trace the result.

 Contract composition
 Contract Role in this use case 
 PrivilegeEdition Issue and redeem delivery entitlements. 
 Whitelist Limit usage to eligible members when required. 

 Follow each contract for its key operations, SDK and source. Select the components your workflow needs and connect them to business approvals and records.

 User and processing flow
 1 Define the product and period
 Map contents, order deadlines and change/transfer policies to voucher types.

 2 Link order and issuance
 Verify payment and issue four vouchers linked to the order.

 3 Record dispatch and redemption
 Identify each dispatch request and consume one entitlement at the stage defined by operating policy.

 4 Reconcile delivery results
 Reconcile delivered, outstanding and cancelled shipments with voucher balances and order actions.

 Operating considerations
 Physical delivery
 Token redemption and physical receipt are separate events. Link redelivery or crop-shortfall substitutions to order records.

 Delivery information
 Keep personal addresses in access-controlled delivery systems rather than token metadata.

 Review approvals, reconciliation and recovery 
 Implement this use case
 These implementation patterns provide architectures, data models, processing steps and SDK examples. Start with the capabilities this use case requires.
 Access & membership
 Manage rights to use facilities or services and participation conditions.
 Explore the implementation Physical assets & inventory
 Connect asset identity and rights to issuance, transfers and holdings.
 Explore the implementation 
 Start with a sample Discuss an integration 

 Related use cases
 Equipment and robotics rights Community housing operations 
 ← Back to all use cases