Laydyne

Saturday checkout

See where Saturday shoppers wait: the staffed lanes or the self-checkout pod.

No sign-in needed: open it in Studio, inspect the saved results and edit in 2D and 3D. Sign in to connect your own AI; project files remain free. Check Account for execution access. Opening asks before replacing your current space.

Does steering shoppers to self-checkout, or faster scanning, shorten the Saturday queue, or only move it?

Who uses it
Supermarket managers and front-end (checkout) supervisors
How it can create value
Compare self-checkout shares and scanning times before changing the cashier schedule or buying kiosks, and see where the queue goes. Weigh each wait reduction against staff hours and kiosk cost; shorter queues alone do not establish extra sales.
Bring your site data
Arrivals by time of day, measured scanning, payment and bagging times, the share of shoppers who use self-checkout and the lanes staffed by hour. How shoppers really choose lanes, balk or switch needs observation before trusting queue lengths.
Turn a comparison into a business decision →
Actual Laydyne 3D model: Saturday checkout
Saturday checkout1 level · 917 parts · synthetic layout

A model you can inspect.

Shoppers arrive at parked cars (poisson, 300 per hour for 36 minutes), walk in, visit 1–2 fresh departments and 2–4 aisles, then either take a free one of eight staffed lanes (counting shoppers already walking to one; in turn when several are free, else the lane with the fewest ahead, judged from the front aisle) or join the single line of the six-kiosk self-checkout pod, and walk back to the car they came in with their bags; a stock clerk brings three pallets to the aisles. Lane 8's cashier takes a 15-minute break from 15:00, in the peak (no one is sent to the closed lane; those already in its line are served when it reopens). Shoppers keep out of the back of house. Walking, service times and FIFO queues only: no crowd physics, balking, lane switching or sales.

Park → enter → fresh and aisles → choose a lane or the pod → scan and pay → bag → drive off

Change one thing

With the same shoppers, move the shares from 70/30 to 60/40 and 50/50, cut the mean scanning time from 90 to 60 s, or move lane 8's break out of the peak (breakStart 900 → 2400 s).

Read the consequence

The queue at each lane and at the pod, mean wait and visit time: watch whether the queue shrinks or only moves to the pod. Purchases, balking, lane switching and physical crowding are not modelled.

View the starting inputs
Shoppers per hour
300
Share choosing staffed lanes (%; the rest self-checkout)
70
Mean scanning time at a staffed lane (s)
90
Lane 8 cashier's 15-minute break starts (s)
900

Agent counts, routes and resource definitions are also saved in the project JSON.

A reproducible starting result.

One run, seed 11. Observation window 60 minutes.

ScenarioCompletedMean waitMean cycleBlocked
Original scenario1931m 34s14m 28s0

Waiting averages cover arrived jobs, including unfinished waits; cycle averages cover completed jobs only. These are synthetic calculations, not measured site performance, revenue or a safety assessment.

Engine, status and output notes

process-des-2.7.0. Status: Original scenario: completed. “Completed” is the engine run status, not success for every job. Check blocked jobs and warnings.

  • No engine warnings.

Engine inputs and saved comparisons stay with the saved project. Any limited trace affects playback details, not aggregate metrics.

Articles on this example

Plan in 2D. Inspect in 3D. Keep the whole project.

  1. Open and adjust. Switch between 2D and 3D; edit a part, a floor or an input. Both views describe the same model.
  2. Connect your agent for free. Sign in, choose Connect AI and connect ChatGPT, Claude, Codex or Claude Code. Ask it to inspect the example, edit the layout and check a route.
  3. Save a checkpoint. Project → Project file, or ask the agent to export the complete project. Import it later to restore floors, scenarios, saved comparisons and the selected view.
  4. Compare options. Run new operational comparisons under the same demand. Check Account for execution access, built-in AI and manual cloud-saving limits.