working-day

Calculate restaurant business day ranges from 4:00 AM to 4:00 AM.

Updated Jul 18, 2022

Search Tags:#analytics #reporting #date-range #working-day #business-day #range-calculation #date-normalization

Ready to run

npx skills add https://github.com/milosptr/pos-system --skill working-day

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: working-day
Source: https://github.com/milosptr/pos-system/tree/main/.claude/skills/working-day
Command: npx skills add https://github.com/milosptr/pos-system --skill working-day

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restaurants and retail operations often operate past midnight, causing revenue and activity to be counted on the wrong calendar day. This Skill defines a 4:00 AM to 4:00 AM working day so reports, filters, and analytics align with actual business days.

Core Features & Use Cases

Establishes a deterministic working-day window (4:00 AM to 4:00 AM next day) for all date-based calculations.
Supports accurate date filtering, invoicing, dashboards, and warehouse data by aligning late-night transactions with the prior business day.
Provides helper utilities to obtain the current working day range and range for a given date.

Quick Start

Use the WorkingDay service to get today's working day range

Frequently Asked Questions about working-day

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I assign late-night restaurant transactions to the previous business day for sales reporting?▼

To assign late-night restaurant transactions to the previous business day for reporting, you define a working day window from 4:00 AM to 4:00 AM. This shifts post-midnight sales data into the prior business day for accurate analytics.

What is a 4am to 4am working day in retail analytics?▼

A 4am to 4am working day in retail analytics is a deterministic date normalization window that groups late-night transactions with the previous calendar day. It ensures revenue and activity align with actual operational hours.

How do I normalize date ranges for invoices that cross midnight?▼

You normalize date ranges for invoices crossing midnight by applying a 4:00 AM cutoff boundary. This deterministic window reassigns early morning transactions to the previous business day to maintain accurate invoice filtering.

Can I use a custom business day range for dashboard date filtering?▼

Yes, you can use a custom business day range for dashboard date filtering by implementing a 4am to 4am window. Helper utilities retrieve the current working day range to support accurate range queries.

Does this 4am working day calculation apply to warehouse data aggregation?▼

Yes, the 4am working day calculation applies to warehouse data aggregation. It aligns late-night activity with the prior business day, ensuring warehouse data and sales analytics accurately reflect operational days.

Why are my late-night sales counted on the wrong calendar day in analytics?▼

Late-night sales are counted on the wrong calendar day because standard date filtering uses midnight cutoffs. Shifting to a 4:00 AM to 4:00 AM working day window correctly groups these transactions with the previous business day.