Void an unsigned Delivery Note
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Withdraw an open note through the permission-protected status action.
Where to goTechnical authorised action → `/admin/delivery_note/void/{noteId}`
What this guide helps you do
Withdraw an open note through the permission-protected status action. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.
Follow these steps
- Go to and verify the note is unsigned.
- Obtain approval to withdraw it.
- Invoke the supported void controller action from an authorised interface or controlled request.
- Verify the success message and return to the register.
- Check status Void and the `void` event.
- Create a replacement from the invoice only when required.
Fields and options
- Note ID
- Delete capability
- Existing status must not be signed
Rules and limits
- The controller uses Delete permission for voiding.
- The model returns false for a signed note.
- Void updates status and updated_at; it does not delete the row.
- The supplied admin detail template does not render a visible Void button.
Check it worked
- The note remains auditable but no longer acts as the invoice’s active public delivery note.
Safety checks and troubleshooting
- Do not add an undocumented hard-delete action or tell users to look for a button the supplied view does not contain.
Stay within the supported flowDo not force database values, expose secure tokens, bypass permission checks, replace a stored signature or invent a status or interface that the supplied code does not implement.
Related guides
Was this guide useful?Your response is stored only in this browser.