01 · Dispatch a shipment dated 30 April
The normal dispatch confirmation asks for the handover time, reason and acknowledgement. Warehouse processing is enabled.
Record a late dispatch, correct one fulfilment, and follow the document and audit trail.
Temporary fictional fixtures in the isolated agent test database. Warehouse processing is enabled. A normal local BrewKeeper dispatch creates a successful fulfilment, then an admin moves its delivery note from April into May consolidated invoicing. No development or production records are created.
The saved correction preserves physical allocations and recorded/processed times. Assertions verify physical and pooled Reserved history, both delivery-note dates and actual pending-invoice grouping. The note's sent state is set locally through DocumentService to show the resend warning; no email is sent.
These are current local branch screens, not a deployed release. Report-lock failures, external Shopify installation and live Xero synchronisation are outside these captures. Forms awaiting Apply are labelled unsaved.
The normal dispatch confirmation asks for the handover time, reason and acknowledgement. Warehouse processing is enabled.
Two fictional BIGI-B301 units have been approved, reserved, packaged and allocated through the normal services.
30 April at 14:00 is ready to submit. This form is still unsaved.
The saved order shows 30 April at 14:00. Dispatch created success and both physical and sales movements without editing the fulfilment status.
The pending consolidated-invoice page groups this authorised delivery note under the 30 April cutoff.
The current billing account prefers consolidated invoices, so the admin action is offered. Other eligibility checks remain visible inside.
All checks pass for 1 May at 10:00. The unsaved preview explains stock replay, both delivery-note dates and the resend warning for the locally marked sent note.
The saved effective time is 1 May at 10:00. The shipment retains 30 April and no new fulfilment is created.
The fulfilment retains its initial dispatch and accepted correction. The local sent-state fixture now requires a resend; no email or Xero call was made.
The same authorised delivery note has a second version with issue and delivery dates set to 1 May. A resend is required.
The actual pending-invoice grouping has moved from 30 April to 31 May. The saved date change moved the whole note.
A draft consolidated invoice was created through DocumentService for the 31 May period and references this same delivery note.
The action remains visible, but the panel identifies the linked consolidated invoice and explains deleting drafts or voiding issued invoices.
The same blocked correction panel at 500 pixels, captured from the actual application.
The order still shows the saved effective time. The correction action is absent for this non-admin fixture.