Skip to main content

Plant Destruction in Plant Detail

Streamlined process for recording plant destruction events and managing cultivation inventory.

I
Written by Ivan Jelinic
Updated over 3 months ago

Purpose

The Plant Destruction feature, accessible from the Plant Detail page, allows users to destroy plants and generate corresponding Destruction Events for accurate record-keeping.

What can you do with it?

With Plant Destruction, you can:

  • Remove specific plants from your inventory

  • Record detailed information about each destruction event

  • Maintain compliance by documenting reasons for plant removal

  • Track destroyed plant weights and associated destruction lots

How is it done?

Follow these steps to destroy plants:

  1. Select plants for destruction

    • Batch: Automatically set to the current batch

    • Plant Count: Displays the number of selected plants

    • Plant ID(s): Choose specific plants to destroy

  2. Enter destruction details

    • Destruction Lot: Select the appropriate lot

    • Weight: Enter the weight of destroyed plants (in grams or kilograms)

    • Reason: Choose a reason for destruction from the dropdown

    • Description: Add any additional comments or notes

  3. Set destruction date

    • Collected on: Select the date of destruction (defaults to current date if left empty)

  4. Review and confirm

    • Double-check all entered information

    • Submit the destruction request

Important Considerations

  • You can only destroy plants from the batch where the Destroy Plants workflow request originated.

  • The Plant ID(s) field defaults to the plants listed on the Plant Page.

  • Destruction Events are automatically generated to record each destruction action.

Best Practices

  • Always provide a clear and specific reason for plant destruction.

  • Double-check the weight and plant IDs before confirming destruction.

  • Use the description field to add any relevant context or details about the destruction event.

  • Regularly review your destruction records to ensure accuracy and compliance.

Did this answer your question?