Still-open items by the day they were created — clears to zero once resolved (not a static backlog). Cash-on-delivery & high courier charges usually read zero; kept for quick detection.
Daily control — open per task, by created day
Ops tasks — open nowhow many open per task · click to action
Internal backlog
0
created, not yet shipped
Total open
0
not yet delivered
In transit
0
shipped, awaiting delivery
On hold
0
flagged is_on_hold
To be confirmed
0
stage 01
Awaiting QC
0
confirmed, not QC'd
QC'd, not shipped
0
to book shipping
Aged backlog (>30d)
0
old open items — see Order Tables
① Internal backlog evolution — by stage at 09:00 UAEreconstructed from status dates
② Total open by country — internal + in transit
③ Backlog aging — open orders by age (older = more urgent)live
④ Backlog carry-over — how much of today's open was already open earlierof today's open orders, how many were already open on each past day
Created today
0
Loading...
Shipped today
0
Loading...
Delivered today
0
Loading...
Net flow today
0
created − shipped (+ = backlog grows)
Created per day
0
Daily Avg
0
Avg GMV/day
Shipped per day
0
Daily Avg
0
Yesterday
Delivered per day
0
Daily Avg
0
Yesterday
Cancelled per day
0
Daily Avg
0
Yesterday
Net flow (created − shipped)
0
Daily Avg
—
Backlog trend
Confirmed & QC'd per day
0
Confirmed Avg
0
QC Avg
④ In-flight orders by stage — volume and aging0 items ✓
⑦ Fulfillment worklist — items to action from the ops sheet · "Shijesh to action"
Case tables over all open orders — replaces checking views one by one in the app. Sorted oldest first.
Late orders0 items
Broken out into one table per order stage — oldest first, high-age rows flagged.
Open orders by stageeach stage as its own table
Aged backlog — items stuck in open statuses (data cleanup candidates)counts only
These are order line items still marked as open/shipped but older than 30 days. Review with ops whether they are real backlog or need status cleanup — this is how old cases get forgotten.
Stage
Country
31–90 days
91–365 days
> 1 year
Loading...
Daily backlog trend per task — raised, closed and time to resolve
Bars are cases closed per day; the line is the average days those
cases took. Raised counts the day an item entered the queue — for late orders that is the
day it crossed 15 days, not the day the order was placed.
COD (flow inactive upstream), High courier charges (the decision is
stored but not when it changed — no close date exists) and Disputes (Google sheet,
not this database) cannot be measured this way and are left out rather than shown as zero.
hover for each task's exact rule
Saudi national-address automation — resolved per day
Bars are the orders the automation processed that day, split by outcome:
resolved automatically (it found the national short code and wrote it on
the order) and sent to an agent (flagged Need address for a
human). The two are exhaustive, so the stack height is the day's total. The solid line is
that day's % resolved; the dashed line is the volume-weighted 7-day rate.
Nothing before 21 Aug 2026 — the automation did not exist, so those
days are absent rather than plotted as zero. On a day under 10 orders the daily point is
withheld: 22 Aug resolved 4 of 4, and a 100% dot above every real day
would read as the best day of the series. The table always shows the true rate.
This measures the automation's outcome at the time. An order it escalated
that an agent later fixed by hand still counts as sent-to-agent for that day — the
series is automation coverage, not order health.
Fulfillment — live from the appreading the ops sheet…
Requests a supplier raises against an order in the Resolution Manager — revibe_resolutions (status: Not Replied / Replied / Cancelled; type: Need address / Other…). Fed live.
Revibe Resolution — summary
Resolution lifecycleall-time · order entity
Open resolutions — by created day × statusstill open only · clears when resolved
By request type
By country
Total received per dayrequests created each day · open + closed