Shift desk / Bandista
The work before service
Uploaded PMIX / pre-service board
A calmer board for
real service data.
Recipes, prep, batch planning, and PMIX demand now sit together in one source-aware desk. The unknowns stay marked until a manager or a measurement closes them.
Uploaded source sheets stay preserved. Manager review and measured-yield gates remain visible before release.
Today's control list
Open loops
Source ledger
Source summary
Batch quantities come from the uploaded recipe and measured prep yields. Pickup additions remain separate so the team knows what belongs in the batch and what is added per drink.
Library / active & review
Recipes with a paper trail.
Batch, service-build, and PMIX demand coverage are visible on every record. Manager decisions can be recorded here.
Service / uploaded pickup chart
Cocktail cards for the floor.
Each card uses the pickup-chart wording inside the app: the source build, service method, presentation details, and the operational batch split. The original scan stays available when someone needs to verify the source.
Production / syrups and infusions
Syrups and infusions for service.
Each record includes its ingredients, yield, and method so the team can make the amount the batch needs.
Source records
Syrups and infusions
Yield check
Measure the finished product.
Record the finished weight or volume. The app uses it to scale future batches.
Production / batch planner
Build the prep packet before service.
Choose a recipe. The app loads the batch base and service build. Enter any batch already on hand so it calculates what remains.
New production record
Batch inputs
Before release
Record the yield and check the linked recipes.
Enter the amount you made. Add a note if it differs from the plan.
Confirm the direct ingredients and linked prep amounts.
Save the measured result with the batch packet.
Production packet / local pilot
Batch packet
Add each recipe needed for the prep run, then open the packet as one print-ready document.
Forecast / source intake
Turn a PMIX into prep decisions.
Upload a PMIX screenshot or report for the manager to review. The source image stays attached to the import, and only confirmed rows should drive weekly batch planning.
Source report / current pilot data
Uploaded PMIX demand rows
Average weekly usage is calculated from the uploaded PMIX source period. Use “Plan weekly batch” to carry the rounded starting target into production.
Planner rules
Demand first. Yield second.
Keep the source file attached to every import.
Use quantity sold as demand, not as a batch volume.
Confirm screenshot rows before they affect planning.
Push linked prep requirements through every nested recipe.
Use the weekly average as the starting portion count, then adjust for events and reservations.
Control room / feedback
Review build and yield reports.
Staff can report a build or yield mismatch. You can record the fix and close the report.
Local issue log
Open review queue
Gate / readiness
Ready for shared use.
Confirm the source files, recipe decisions, cloud setup, and staff access before opening the app to the team.
Rebuild readiness
Source-connected pilotThe real data layer is present locally. Cloud ownership, manager decisions, and live validation remain open.
Activation gate
Required inputs
Department model
One app, multiple outlet assignments.
A team member can be assigned to more than one outlet. Supabase Row Level Security still limits each person to the departments assigned to them.
Source intake / manager review
Upload the sheets the app should work from.
The local pilot stages the filename and review status. The live Supabase version preserves the original file and extracts reviewable rows before anything changes in production.
Team access
Invite staff without opening Supabase.
Add an email, title / access level, and one or more outlets. The invitation email will send the new team member to the password setup screen.