Sales Records

Sales records track what you've sold—from external systems like Odoo or imported from CSV files. Use this data to plan production based on actual demand.


Overview

Sales records capture:

  • What sold — Item name, quantity, price
  • When it sold — Sale date, delivery date
  • Who bought it — Customer name, order number
  • Menu item link — Maps to your PrepStation menu items
Sales Records → Menu Items → Recipes → Production Requirements

Accessing Sales Records

Navigate to SalesSales Records

Or go directly to /sales_records


How Sales Records Are Created

From External Sync

When you sync from Odoo or other systems:

  1. Sales orders are fetched
  2. Line items become sales records
  3. Auto-mapping attempts to link to menu items
  4. Unmapped items need manual mapping

See External Sync for setup.

From CSV Import

Import sales data from your POS:

  1. Go to ImportsSales
  2. Upload your CSV file
  3. Map columns to fields
  4. Match items to menu items
  5. Import creates sales records

See Importing Sales Data for details.


Sales Record Fields

Core Information

Field Description
Item Name Product name from your POS/ERP
Quantity Sold Number of units sold
Unit Price Price per unit
Line Total Total for this line item
Sale Date When the sale occurred

Order Information

Field Description
Order Number Sales order reference
Customer Name Who placed the order
Salesperson Who made the sale
Sales Team Team attribution

Delivery Information

Field Description
Delivery Date When it should be delivered
Delivery Status Pending, delivered, cancelled

Mapping Sales to Menu Items

For sales records to flow into production planning, they must be linked to your menu items.

Mapping Status

Status Meaning
Auto-mapped System matched automatically
Manual-mapped You linked it manually
Unmapped Needs your attention
Ignored Intentionally skipped

Auto-Mapping

PrepStation tries to match sales items to menu items by:

  1. Exact name match
  2. Similar name match
  3. SKU/code match (if available)

High-confidence matches are auto-mapped. Low-confidence matches need review.

Manual Mapping

For unmapped items:

  1. Find the sales record
  2. Click Map or Link to Menu Item
  3. Search for the correct menu item
  4. Select it
  5. Future sales of this item will auto-map

Ignoring Items

Some sales don't need to be tracked (non-food items, services):

  1. Find the sales record
  2. Click Ignore
  3. It won't appear in production planning

Using Sales for Production

How It Works

  1. Sales records with mapped menu items are included
  2. Menu items link to recipes
  3. Recipes list required ingredients
  4. Production requirements calculate total needs

Date Range Analysis

Calculate production requirements from sales:

  1. Go to ProductionRequirements
  2. Select Date Range analysis
  3. Choose your date range
  4. See what needs to be produced based on historical sales

Forecasting

Use sales history to predict future needs:

Approach Description
Same period last year Compare to previous year
Rolling average Average recent sales
Growth adjusted Apply growth percentage

Managing Sales Records

Viewing Records

The sales records page shows:

  • Item name and quantity
  • Sale date and customer
  • Mapping status
  • Processing status

Filtering

Filter by:

Filter Options
Mapping Status Unmapped, Mapped, Ignored
Date Range Sale date range
Import Source External sync, CSV import
Customer Specific customer

Bulk Actions

Action Description
Bulk Map Map multiple items to the same menu item
Bulk Ignore Ignore multiple non-relevant items
Export Download as CSV

Handling Changes

Updated Sales

When a sale is modified in your external system:

  • Next sync updates the record
  • Quantity changes flow to production
  • Cancellations are marked

Cancelled Sales

Cancelled orders:

  • Are marked as cancelled
  • Are excluded from production calculations
  • Remain visible for history

Common Workflows

Daily Production Planning

  1. Sync latest sales from Odoo
  2. Review any unmapped items
  3. Go to Production Requirements
  4. Calculate needs for tomorrow
  5. Generate production plan

Weekly Forecasting

  1. Review sales from past weeks
  2. Calculate requirements for date range
  3. Identify trends or anomalies
  4. Adjust production plans accordingly

New Product Launch

  1. Add menu item to PrepStation
  2. Sales come in via sync
  3. Map sales to the new menu item
  4. Production requirements include new item

Common Questions

Q: Why are some items unmapped?
A: The item name in your POS doesn't match any menu item in PrepStation. Map it manually once, and future sales will auto-map.

Q: Do I need to map everything?
A: Only items you want in production planning. Ignore non-food items, drinks, or things you don't prep.

Q: How far back can I analyze sales?
A: As far back as you have data. Import historical data or sync from your external system.

Q: What if a menu item changes?
A: Update the mapping. Future sales will use the new link.

Q: Can I edit sales records?
A: You can change the mapping and ignore status, but quantities come from the source system.

Q: How do cancelled orders affect production?
A: Cancelled orders are excluded from production requirement calculations.


Next Steps

Last updated: March 23, 2026