Backdating allows you to change the recorded date of certain activities to reflect when they actually occurred. This FAQ covers what you can backdate, how the process works, and what to watch out for.
In this article:
- What Is Backdating?
- Which Activities Can Be Backdated?
- How to Backdate an Activity
- Frequently Asked Questions
🎯 What Is Backdating?
Backdating is the process of changing an activity's timestamp to an earlier date. This is useful when an action was performed but not recorded in GrowerIQ on the same day — for example, if you harvested a batch on Friday but didn't log it until Monday.
Backdating maintains a complete audit trail: the system records both the new date and the reason for the change.
✅ Which Activities Can Be Backdated?
The following activities support backdating:
| Activity | Description |
|---|---|
| Receive Inventory | Receipt of materials into the facility |
| Germinate Seeds | Seed germination events |
| Record Harvest Weight | Harvest weight recording |
| Record Dry Weight | Dry weight recording |
| Record Cured Weight | Cured weight recording |
| Record Crude Oil Weight | Crude oil weight recording |
| Record Distilled Oil Weight | Distilled oil weight recording |
| Batch Visual Inspection | Visual inspection activities |
| Create Sample | Sample creation events |
| Record Final Yield | Final yield recording |
| Create Lot | Lot creation events |
| Sample Lab Result Received | Lab result receipt |
| Batch QA Review | QA review activities |
Activities that cannot be backdated:
- Variety name changes
- Inventory variety updates
Non-Backdatable Activities
Activities not listed above (including variety changes) cannot be backdated.
📝 How to Backdate an Activity
Step 1: Navigate to the Activity Log
Go to the detail page of the batch, lot, or inventory item and open the Activity Log tab.
Step 2: Select Activities
Select one or more activities you want to backdate. You can select multiple activities to backdate them all to the same date.
Step 3: Click Backdate
Click the Backdate button. A dialog will open showing:
- A list of the activities that will be backdated
- A date/time picker for the new date
- A text field for the reason
Step 4: Choose the New Date
Select the new date and time. The date picker has restrictions:
- Maximum date: The activity's current date (you cannot move activities forward in time)
- Minimum date: The earliest related activity date (you cannot backdate before dependent activities)
Forward Dating Not Allowed
Backdating cannot move activities forward in time. The new date must be earlier than or equal to the activity's current timestamp.
Step 5: Enter Reason for Modification
Provide a clear explanation of why the activity is being backdated. This is required and becomes part of the permanent audit trail.
Step 6: Confirm
Click Confirm to apply the backdate.
❓ Frequently Asked Questions
Can I backdate an activity to a future date?
No. Backdating only moves activities to an earlier date. The maximum date allowed is the activity's current timestamp.
Can I backdate multiple activities at once?
Yes. You can select multiple activities from the Activity Log and backdate them all to the same date and time in a single operation.
Are there dependency rules when backdating?
Yes. Some activities have dependencies that prevent them from being backdated before related activities. For example:
- A Batch QA Review cannot be backdated before:
- Sample Lab Result Received
- Create Sample
- Sample Sent to Lab
- Batch Visual Inspection
If you try to backdate an activity before one of its dependencies, you'll see a validation error explaining which rule was violated.
What happens to inventory adjustments when I backdate?
When an activity is backdated, the system recalculates inventory adjustments to reflect the new timeline. This ensures that inventory quantities are accurate for the adjusted period.
Related entities are also updated:
- Inventory timestamps
- Order timestamps (if applicable)
- Invoice timestamps (if applicable)
- Shipment timestamps (if applicable)
Will backdating affect my regulatory reports?
Cross-Month Backdating
If your backdate crosses a month boundary, contact GrowerIQ Support before proceeding. Changes to past months can affect Health Canada Reports, CRA Cannabis Duty Returns, and other compliance reports for that period.
Yes, potentially. If you backdate an activity to a previous month, this changes the recorded data for that reporting period. This can affect:
- Health Canada Reports — Inventory movement totals for the affected month
- CRA Cannabis Duty Returns — Packaged quantities for the affected period
- Any compliance reports that reference activity dates
Is backdating tracked in the audit trail?
Yes. Every backdate operation records:
- The original date of the activity
- The new date it was changed to
- Who performed the backdate
- The reason for modification
This information is visible in the Activity Log and cannot be deleted.
Why can't I backdate a variety name change?
Variety name changes and inventory variety updates are excluded from backdating to maintain data integrity. These changes affect how inventory is classified and cannot be safely moved to a different date.
I accidentally backdated to the wrong date. Can I fix it?
Yes. You can backdate the same activity again to a different date. The same rules apply — the new date must be earlier than or equal to the activity's current timestamp, and you'll need to provide a new reason for modification.
Where do I find the Backdate button?
The Backdate button appears in the Activity Log view on batch, lot, and inventory detail pages. Select one or more activities using the checkboxes, and the Backdate option becomes available.
🔗 Related Articles
- Recording Weight Adjustments on Batches - Correcting batch weights
- Batches - Understanding batch management
- Working With Lots - Lot inventory management