EOD and Carryover tickets added
This commit is contained in:
@@ -65,6 +65,31 @@ existing tickets rather than duplicating them.
|
||||
Dashboard's Carryover count is just these tickets filtered to "created
|
||||
before today."
|
||||
|
||||
## The Done pile
|
||||
|
||||
Once a ticket reaches either fulfilled status, it moves off the
|
||||
**Active Orders** tab and onto the **Done** tab automatically - the
|
||||
active view stays focused on what's still being worked. This is a
|
||||
filter, not a physical move: everything's still the same `orders`
|
||||
table, split by current status each time the view refreshes, so if a
|
||||
status ever changed back there'd be nothing to reconcile. Cancelled
|
||||
tickets stay on Active Orders (still need eyes on them) - only the two
|
||||
fulfilled statuses trigger the move. The Dashboard's "Active Orders"
|
||||
count and company breakdown only reflect what's still active;
|
||||
"Fulfilled Today" and "Arrived Past Cutoff Today" look at all of
|
||||
today's activity regardless of which tab something ended up on.
|
||||
|
||||
## Intake cutoff tracking
|
||||
|
||||
`INTAKE_CUTOFF_TIME` (default `15:30`, i.e. 3:30 PM) flags any ticket
|
||||
created after that time on its arrival day with a **Past Cutoff** "Yes"
|
||||
in the table, and the Dashboard shows how many of today's tickets
|
||||
arrived past cutoff. Since a cutoff ticket is known to spill into
|
||||
tomorrow the moment it arrives, it also counts toward **Carryover**
|
||||
immediately - not just once the date actually rolls over - unless it
|
||||
still gets fulfilled the same day despite arriving late, in which case
|
||||
it correctly drops out of both.
|
||||
|
||||
## How tracking numbers get pulled and matched
|
||||
|
||||
Confirmed against a real ShipStation payload from your queue (not
|
||||
|
||||
Reference in New Issue
Block a user