Options
Stockly → Settings → Options holds four tabs that do not belong to any single subject: Route planner, Order Creation, Barcode Scanner and Scheduled tasks.
Barcode Scanner
Section titled “Barcode Scanner”One configuration for the hardware scanner used outside packing. The scanner inside the packing workflow is a separate configuration and is set up under Order Packing; this tab does not affect it.
The scanner needs no driver and no setup on the screen itself: a hardware scanner types the code and presses Enter, and the module recognises that pattern.
Pages with an active scanner
Section titled “Pages with an active scanner”The multi-select decides where the scanner listens. An empty selection turns it off everywhere.
| Selected page | What a scan does there |
|---|---|
| Order creation | adds the product to the order being created |
| Purchase order creation | adds the product to the purchase order being created |
| Warehouse transfer creation | adds the product to the transfer being created |
| Stock movement creation | adds the product to the movement being booked |
| Stocktake count | records the counted product |
| Return receipt | jumps to the scanned article’s card and puts the cursor in its quantity field |
| Bin details | pins the scanned product to the top of the location’s list |
| Product list | puts the code into the list’s search |
Return receipt is the one page not selected out of the box. Everything else on the list is switched on when the module is installed.
On the four creation screens the scanner remains inactive until the counterparty is known: a purchase order requires its supplier, a transfer its source warehouse, an order its customer. This is deliberate, because without them there is nothing to add the item to.
Product fields for barcode matching
Section titled “Product fields for barcode matching”Which field the scanned code is compared against: EAN, Manufacturer number, Product number. Several may be selected at once.
Two screens ignore this selection, and the help text under the field says so: Stocktake count resolves scans on the server and always matches EAN and manufacturer number, and Product list feeds the code to the ordinary search.
The confirmation window
Section titled “The confirmation window”Show product modal after scanning decides whether a scan adds the item straight away or first shows a window with quantity and prices. It applies only to order, purchase order and transfer creation, because stock movement creation, the counting screen and the location window have nothing to confirm.
Auto-confirm modal after (seconds) closes that window by itself after 3, 5, 10, 15 or 30 seconds; Disabled waits for the operator. Moving the mouse or clicking inside the window cancels the countdown, so an operator who hesitates is not overruled.
Sounds
Section titled “Sounds”Play sound on successful scan and Play sound on rejected scan are separate, so a quiet warehouse can keep only the error tone. Sound delay after scan (seconds), set to No delay or up to 5 seconds, is used where the scanner fires faster than the screen reacts.
Order Creation
Section titled “Order Creation”Two switches for Shopware’s own order screens:
- Use product picker modal in order creation — replaces the inline product line with a window that has a proper search, variant selection, an image and editable quantity, price and tax.
- Use product picker modal in order detail — the same window in the Items section of an existing order.
Route planner
Section titled “Route planner”A sandbox for the walking route the picking screens draw. It is not a setting an operator encounters during work; it is where the route is tuned and tested.
The upper section picks what to draw the route on: a Warehouse and its Floor, or one of the prepared Layout shapes with a Scenario to route through.
The parameters below decide what the route avoids and how precisely it is computed:
- Route scale (initial) — how fine the routing grid is. A higher value lets the path run closer to obstacles, at a cost in computation.
- Auto-rescale on parallel overlap with Route scale (max) and Rescale threshold — when too many parallel paths claim the same spot, the route is recomputed on a denser grid.
- Wall proximity cost — pushes the path away from walls and shelves into the aisle.
- Adjacent path cost — spreads parallel routes so they do not stack on top of one another.
- Label avoid cost — bends the path around shelf labels so the drawing stays readable.
Save stores the values, Reset to defaults restores them.
The second card, Voice route (audio guidance), is the same sandbox with the spoken guidance switched on: Start begins the walk, ticking locations off moves it along, Speak (browser voice) reads the instructions aloud and the Narration log shows what was said. → Voice picking
Scheduled tasks
Section titled “Scheduled tasks”Every task the module performs on its own has a switch here. The tab does not change when a task runs: the schedule is fixed, and Shopware’s scheduled task processing has to be running for any of it to happen. A switch decides whether the module performs that work at all.
Six groups, matching what the work is for.
| Group | Switch | What stops when it is off |
|---|---|---|
| Stock | Stock integrity scan (daily) | nothing is scanned on its own; a run can still be started by hand on the integrity screen |
| Rebalance planning run (daily) | the list of transfer proposals stops being refreshed — releasing one was always a human action | |
| Backorder re-sourcing (hourly) | backordered lines keep pointing at the warehouse they were first assigned to until somebody re-allocates them | |
| External stock write digest (daily) | the daily summary of foreign stock writes is not sent | |
| Downtime catch-up (daily) | after a period with the module inactive the books stay behind | |
| Warehouse planning | Threshold plans (hourly) | due plans are not dispatched, and a plan blocked by a run that died stays blocked |
| Rebalance schedule dispatch (every 5 minutes) | every scheduled transfer in the shop stops firing, not just one | |
| Transfer demand sync (hourly) | demand figures drift from coverage and cross-docked goods nobody collected stay where they are | |
| Zone reclassification (weekly) | the A/B/C zones freeze at their last classification, which is the intended state while a layout is being reworked by hand | |
| Pack capacities (daily) | the cartonizer falls back to fitting by volume, which is an estimate | |
| Product affinity (daily) | slotting stops learning which products are ordered together; purely advisory either way | |
| Reports and snapshots | Product snapshots (daily) | a day without a snapshot is a permanent gap — period-over-period figures cannot be reconstructed later |
| Report cache warming (every 2 hours) | reports are computed when somebody opens them instead of in advance | |
| Back in stock | Availability check (every 6 hours) | no new notifications are ever queued, whatever the sending switch is set to |
| Notification sending (every 5 minutes) | queued mails wait rather than being dropped — they go out when it is switched back on | |
| Printing | Print queue watchdog (every 5 minutes) | a job a device claimed but never finished stays stuck until somebody releases it by hand |
| Print queue cleanup (daily) | finished jobs are kept past their retention; nothing waiting to print is ever affected | |
| Maintenance | Job watchdog (every 5 minutes) | an abandoned background job shows as running forever and its progress bar never resolves |
| API log cleanup (daily) | the API log table grows without bound | |
| Threshold run cleanup (weekly) | old runs and their proposals are kept; the thresholds they produced live elsewhere and are not affected | |
| Pick wave cleanup (hourly) | a wave that was planned but never started keeps its orders claimed, and nobody can pick them until somebody releases the wave by hand | |
| Sourcing decision cleanup (daily) | the recorded reasoning behind past sourcing decisions is kept forever, which is what makes that list unreadable |
Some switches depend on settings elsewhere. External stock write digest only does anything when the digest itself is on under Stock → General, and both cleanup tasks delete by the retention periods set on their own screens — under Print queue and API logs. Pick wave cleanup waits out the time set in Release an unstarted wave after this many minutes under Packing settings before it releases anything. → The work queue
→ Scheduled tasks — what each task does, and how often