AlphaAlpha Docs

Production Shifts

Managing production by work shift

Production Shifts

Organize production activities by work shift.

Shift Configuration

Defining Shifts

Set up production shifts:

ShiftStartEndDays
Day06:0014:00Mon-Fri
Evening14:0022:00Mon-Fri
Night22:0006:00Mon-Fri

Shift Assignments

Assign workers to shifts:

  1. Go to Production > Shifts
  2. Select shift
  3. Assign team members

Shift Operations

Starting a Shift

  1. Worker logs in
  2. Selects production shift
  3. Views assigned orders

During Shift

Activities tracked:

  • Production orders worked
  • Units produced
  • Waste recorded
  • Machine time

Ending Shift

  1. Complete entries
  2. Record handover notes
  3. End shift

Shift Reporting

Shift Summary

Per-shift metrics:

MetricDescription
Units ProducedOutput quantity
Orders CompletedFinished orders
Waste RateScrap percentage
EfficiencyActual vs target

Shift Comparison

Compare shifts:

Day Shift: 500 units, 2% waste
Evening: 480 units, 2.5% waste
Night: 400 units, 3% waste

Importing an Oracle Sales Mix

If your point-of-sale runs on Oracle Simphony, you can import a shift's actual sold goods straight from a Sales Mix (Top Menu Items Summary) export. The imported sales become a sales order linked to the shift, which drives the sold-versus-inventory variance shown in the waste analysis.

Steps

  1. In Simphony, run and export the Sales Mix report for the business date as .xlsx.
  2. Open the shift in Production > Shifts and click Import Oracle Sales Mix.
  3. Drop the .xlsx file and click Import.

Alpha parses the report's menu-item hierarchy and imports only the sold menu items. The Modifiers / Condiments block is intentionally skipped — Alpha already derives ingredient consumption from each product's bill of materials, so importing those rows would double-count.

How items are matched

Each sold line is matched to a product, in order:

  1. Product reference — the product's reference field equals the Oracle item name (case-insensitive). This is the recommended, stable mapping.
  2. Product name — falls back to a case-insensitive name match.

After import you'll see a summary of matched and unmatched items. Unmatched lines (for example combos that have no equivalent product yet) are listed so you can fix the catalogue:

  • Set the product's reference to the exact Oracle item name, or rename the product to match, then re-import.

Combos (e.g. Whopper Cmb) are sold as a single Oracle item. Create a matching combo product in Alpha — with a bill of materials of sandwich + fries + drink — so the import maps it and inventory consumption stays accurate.

Handover

Shift Handover Notes

Communicate between shifts:

  • In-progress orders
  • Machine issues
  • Quality concerns
  • Special instructions

On this page