Production Shifts
Managing production by work shift
Production Shifts
Organize production activities by work shift.
Shift Configuration
Defining Shifts
Set up production shifts:
| Shift | Start | End | Days |
|---|---|---|---|
| Day | 06:00 | 14:00 | Mon-Fri |
| Evening | 14:00 | 22:00 | Mon-Fri |
| Night | 22:00 | 06:00 | Mon-Fri |
Shift Assignments
Assign workers to shifts:
- Go to Production > Shifts
- Select shift
- Assign team members
Shift Operations
Starting a Shift
- Worker logs in
- Selects production shift
- Views assigned orders
During Shift
Activities tracked:
- Production orders worked
- Units produced
- Waste recorded
- Machine time
Ending Shift
- Complete entries
- Record handover notes
- End shift
Shift Reporting
Shift Summary
Per-shift metrics:
| Metric | Description |
|---|---|
| Units Produced | Output quantity |
| Orders Completed | Finished orders |
| Waste Rate | Scrap percentage |
| Efficiency | Actual vs target |
Shift Comparison
Compare shifts:
Day Shift: 500 units, 2% waste
Evening: 480 units, 2.5% waste
Night: 400 units, 3% wasteImporting 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
- In Simphony, run and export the Sales Mix report for the business date as
.xlsx. - Open the shift in Production > Shifts and click Import Oracle Sales Mix.
- Drop the
.xlsxfile 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:
- Product reference — the product's
referencefield equals the Oracle item name (case-insensitive). This is the recommended, stable mapping. - 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