Daily shop action records
CounterCart Open the shop day with a short, useful action list.
Gather the day’s open shop work, group it by urgency, and prepare clear handoffs without forcing the owner through a large back-office menu.
Sign-in opens the CounterCart conversation. No order, refund, inventory, or customer action happens from this page.
THE MORNING CHECKThree fixed thresholds decide which supplied rows need attention.
01 / BRING THE DAY
Open with the records you already have.
Inputs cover unfulfilled hours, stock, reorder point, refund age, named action types, and approval identifiers.
- 01
Record IDs with unfulfilled hours, stock, reorder point, and refund-pending hours
- 02
Action items using payment dispute, overdue fulfilment, stale refund, or low stock types
- 03
Action, order, amount, currency, and approval identifiers for a queued record
02 / SORT WITHOUT GUESSING
The queue uses a closed weight table.
The engine scores only four named action types. It rejects an unknown type rather than inventing a priority.
The engine applies fixed thresholds to daily records and fixed weights to named action types.
03 / WORK THE OPENING
One pass from rows to a reviewable record.
- 1
CounterCart flags fulfilment over 24 hours, stock at or below reorder point, and refunds pending over 48 hours.
- 2
It adds the closed weight table for each item's named action types and sorts the highest score first.
- 3
It builds an approval-bound queued record whose idempotency key combines approval ID and action.
WHAT LANDS ON THE COUNTER
A short worklist with the reasons left in.
Exception rows with every matched daily rule
Action IDs ordered by the fixed type weights and then by ID
A queued action record with amount, currency, approval ID, and idempotency key
THE OWNER KEEPS THE KEYS
CounterCart prepares the record. You still run the shop.
Gather the day’s open shop work, group it by urgency, and prepare clear handoffs without forcing the owner through a large back-office menu.
It does not
- Placing an order, changing inventory, issuing a refund, or contacting a customer
- Accepting an action type outside the four named types
- Treating a queued record as proof that an external commerce action completed
Before acting
- Connected shop data determines which daily tasks can be surfaced.
- Messages, refunds, and inventory changes require owner confirmation.
STARTER / MONTHLY
Keep the daily list close to the counter.
Bring the shop records, review the ordered work, and approve any next action in the signed-in workspace.
BEFORE THE DOOR OPENS
Questions from the shop floor.
Which daily records become exceptions?
A record is returned when fulfilment exceeds 24 hours, stock is at or below its reorder point, or a refund has been pending for more than 48 hours.
How are actions prioritized?
Payment disputes, overdue fulfilment, stale refunds, and low stock have fixed weights. Scores are added and ties are sorted by action ID.
What does an approved action record contain?
It contains the action and order IDs, amount, currency, approval ID, a derived idempotency key, and queued status.
Does queued mean the action happened?
No. Queued is the engine's record status and is not evidence that an order, refund, inventory change, or customer contact occurred.