Built Word Documents (.docx):
Spensara Overview (.docx)
Capability Assessment (.docx)
Brink POS Ingestion Analysis (.docx)
The Borg Ingestion Architecture (.docx)
Categories
Monitor Specs (29)
Operational monitoring, alerting, anomaly detection, and health specifications.
- backend/Kds.Ai.Data/MonitorSpecs/customer-churn-risk.md
- backend/Kds.Ai.Data/MonitorSpecs/customer-profiles.md
- backend/Kds.Ai.Data/MonitorSpecs/daily-forecast.md
- backend/Kds.Ai.Data/MonitorSpecs/demand-drivers.md
- backend/Kds.Ai.Data/MonitorSpecs/forecast-demand.md
- backend/Kds.Ai.Data/MonitorSpecs/forgotten-items.md
- backend/Kds.Ai.Data/MonitorSpecs/identify-high-value-customers.md
- backend/Kds.Ai.Data/MonitorSpecs/identify-plowhorse-items.md
- backend/Kds.Ai.Data/MonitorSpecs/identify-star-items.md
- backend/Kds.Ai.Data/MonitorSpecs/incorporate-seasonality.md
- backend/Kds.Ai.Data/MonitorSpecs/inventory-levels.md
- backend/Kds.Ai.Data/MonitorSpecs/item-recall-storm.md
- backend/Kds.Ai.Data/MonitorSpecs/kitchen-performance.md
- backend/Kds.Ai.Data/MonitorSpecs/large-order-wave.md
- backend/Kds.Ai.Data/MonitorSpecs/menu-item-profitability.md
- backend/Kds.Ai.Data/MonitorSpecs/monthly-forecast.md
- backend/Kds.Ai.Data/MonitorSpecs/optimal-pricing-adjustments.md
- backend/Kds.Ai.Data/MonitorSpecs/optimize-order-quantities.md
- backend/Kds.Ai.Data/MonitorSpecs/order-surge.md
- backend/Kds.Ai.Data/MonitorSpecs/prep-time.md
- backend/Kds.Ai.Data/MonitorSpecs/pricing-recommendations.md
- backend/Kds.Ai.Data/MonitorSpecs/priority-flood.md
- backend/Kds.Ai.Data/MonitorSpecs/seasonality-trends.md
- backend/Kds.Ai.Data/MonitorSpecs/segment-customers.md
- backend/Kds.Ai.Data/MonitorSpecs/segment-descriptions.md
- backend/Kds.Ai.Data/MonitorSpecs/slow-kitchen.md
- backend/Kds.Ai.Data/MonitorSpecs/station-bottleneck.md
- backend/Kds.Ai.Data/MonitorSpecs/waste-reduction.md
- backend/Kds.Ai.Data/MonitorSpecs/weekly-forecast.md
id: c2a4f6d1-9b7e-4c2b-8d3f-1e6a7b9d5c21 name: Recommend optimal pricing adjustments
Detect pricing optimization opportunities by analyzing demand patterns, price sensitivity, and external factors to maximize revenue and margin.
Known Tables & Columns
curated.pos_transaction_items
ITEM(varchar) - menu item identifierITEM_NAME(varchar) - menu item nameQTY(int) - quantity soldPRICE(decimal) - selling priceNET_SALES(decimal) - total revenue from itemBUSINESS_DATE(date) - transaction dateHOUR(int) - hour of saleREVN_CENTER(varchar) - revenue center (Dining Room, Bar, Delivery)
curated.pos_hourly_sales
ITEM(varchar) - menu item identifierDATE(date) - transaction dateHOUR(int) - hour of saleQTY_SOLD(int) - quantity soldSALES_AMOUNT(decimal) - total salesREVN_CENTER(varchar) - revenue center
curated.pos_transactions
DATE(date) - transaction dateREVN_CENTER(varchar) - revenue centerTOTAL_REVENUE(decimal) - total revenueTOTAL_ORDERS(int) - number of orders
Analysis Approach
- Analyze item-level sales for the last 90 days to determine demand levels and revenue contribution for each menu item.
- Identify demand drivers:
- high-demand and low-demand items based on sales volume
- demand patterns by hour of day
- demand patterns by day of week
- differences between weekdays and weekends
- demand shifts across revenue centers.
- Establish a baseline demand for each item using normal (non-holiday, typical weather) periods.
- Detect deviations from baseline caused by:
- holidays and special periods (e.g., Christmas, Easter, New Year, long weekends)
- weather conditions (rain, temperature, wind impact on dine-in vs delivery).
- Estimate price sensitivity (elasticity proxy):
- compare changes in price vs changes in quantity sold over time
- identify items with low sensitivity (stable demand despite price variation)
- identify items with high sensitivity (demand strongly affected by price).
- Identify pricing opportunities:
- peak-hour pricing for high-demand, low-sensitivity items
- off-peak discounts for low-demand periods
- weather-based pricing adjustments (e.g., delivery during rain. Use get_weather_forecast tool to check weather for Orlando. Get current weather conditions and forecast.)
- holiday/event-based pricing strategies
- revenue center-specific pricing differences.
- Validate that each item has sufficient data (minimum 30 units sold) to ensure reliable recommendations.
- Avoid overly aggressive pricing changes unless supported by strong and consistent demand patterns.
- Balance price increase vs expected volume drop, prioritizing overall revenue and margin improvement.
- Generate concise pricing recommendations including:
- item name
- context (time, day, weather, event, revenue center)
- demand insight
- recommended price adjustment (percentage, discount, bundle, dynamic pricing)
- expected impact (revenue, volume, margin)
- short reasoning.
- Minimize database usage:
- prefer aggregated summaries
- do not request more than 3 queries unless necessary
- reuse previously retrieved data when possible.
Severity Guidance
- Low: Small pricing optimization opportunity with limited impact.
- Medium: Clear pricing inefficiency across specific time periods or segments.
- High: Strong, consistent demand imbalance or pricing inefficiency with significant revenue upside.