How can we help?

Use this procedure for a dedicated Windows till running desktop Google Chrome, either in a normal browser window or as an already installed ShopTill-e POS web app (PWA). Start with a working receipt printer. Installing the web app or making the till full screen does not itself enable silent printing.

Before changing the till

1. Arrange a quiet maintenance window with the person responsible for the device. Finish or safely preserve any unfinished basket, check pending local orders and any unresolved payment, and record the working browser profile and shortcut. Do not close an active checkout or interrupt synchronisation.
2. Keep the original working shortcut unchanged. Make a copy for the intended till user and name it clearly, for example ShopTill-e till — silent printing. Record the original Target privately so the launch change can be undone.
3. Confirm that the receipt printer works through its manufacturer's driver and matches the installed paper roll. For Windows 11, open Start → Settings → Bluetooth & devices → Printers & scanners, turn Let Windows manage my default printer off, select the receipt printer, then choose Set as default. Check that its status is Default. Follow Microsoft's instructions for other Windows versions. Do not change another user's printer setup.
4. Using the existing browser profile and ordinary receipt-printing route, check an agreed reprint of an existing saved receipt. In preview, select the actual receipt printer, not an office printer or Save as PDF. Check paper size, scale, margins and browser headers/footers, then check one physical copy. See browser receipt printing.
5. Record the browser's actual selected destination as well as the Windows default. Chrome can remember a previous destination, and managed policies can change its initial selection. A Windows default alone is not proof that Chrome will use it.

Use silent printing only for a trusted till. The browser skips the normal confirmation step; other printable pages opened in that browser process may also print without asking. Keep unrelated browsing out of the till session. This shortcut is not a security lock or a substitute for device access controls.

Option A: desktop Chrome in a normal browser window

1. Copy the exact HTTPS till address from the working shop's till page. Use your own normal shop address, not an old beta address, another shop's address or a support example.
2. Right-click the copied Chrome shortcut and choose Properties → Shortcut.
3. In Target, preserve the existing quoted executable path and any existing profile selection. After the closing executable-path quote, add a space and --kiosk-printing. Keep the intended till URL as a separate quoted argument. If the shortcut already has that URL, do not add it twice.
4. The added switch is exactly --kiosk-printing. Do not put it inside the executable-path quotes. Do not paste a guessed Chrome installation path or change the browser profile.
5. Save the copied shortcut. Once local work and synchronisation are safe, exit all Chrome windows, including installed Chrome web-app windows, normally. If Chrome remains running in the background, have the device administrator close it safely through its normal controls; do not force-end a till with pending work.
6. Open the till using the copied shortcut as the normal till user. Startup options need a fresh browser process; opening the shortcut while the old process is still running may not apply the change.
7. Complete the acceptance checks below before using silent printing for trading.

Option B: the existing installed Chrome till PWA

An installed PWA still uses its browser's printing route. Preserve the shortcut Chrome generated for that particular installed app and profile; there is no universal ShopTill-e Chrome App ID.

1. Locate the existing working desktop shortcut that opens this shop's installed till app. Copy that shortcut and leave the original untouched. Check the copy opens the intended shop before changing its launch configuration.
2. Open the copy's Properties → Shortcut. Preserve its executable path, whether Chrome or Chrome's app launcher, all existing arguments, the existing --profile-directory value and the complete --app-id value where present.
3. Append a space and --kiosk-printing to the end of the existing Target, outside quoted values. Do not replace the Target with a generic browser command. Do not append a till URL to an app-ID shortcut or replace its app ID with the web manifest's ID.
4. Save the copy. At the agreed safe maintenance point, exit all Chrome and Chrome PWA windows normally, then start the app with this copied shortcut. Check the intended shop and till identity.
5. Complete the acceptance checks below. Until checked, the original Start-menu or taskbar launch is not proof of the same launch configuration; staff must use the checked shortcut.

If the existing shortcut has no editable Target, its launcher is managed, or its app/profile identity is unclear, stop at that specific point and have the device administrator adapt the existing launcher. Do not uninstall or reinstall the PWA, invent an App ID, create a new browser profile or clear site data to obtain a shortcut. Local orders and device identity must be preserved.

Check one physical receipt before trading

1. Open the intended saved sale and verify its reference. Arrange one deliberate receipt reprint; do not take another payment or create another sale to test printing.
2. Use the receipt's print action once. Check that output reaches the intended physical printer without a printer-choice prompt. A preview may appear briefly; its disappearance or an on-screen success message does not establish that paper emerged.
3. Inspect the actual receipt: correct order, complete content, readable text, expected paper width and no clipping. Check cutter and drawer behaviour separately where required and safe.
4. After a safe browser restart, launch with the checked shortcut and repeat the agreed receipt check. Recheck after browser, driver, printer or default-destination changes. An online receipt check does not establish offline readiness.

These are merchant/device acceptance checks, not a claim that support has physically tested your hardware. Compatibility depends on the exact operating system, browser build, printer, driver and local configuration.

If the prompt remains, output is missing or the wrong printer is used

• Keep the order reference. Check whether a copy already printed or a job is waiting before retrying.
• Check that staff used the edited shortcut and the expected profile, and that Chrome was restarted safely rather than reusing an earlier process.
• To restore ordinary print preview, first make local work safe, then exit Chrome normally and launch using the untouched original shortcut. A managed silent-print policy can still apply; the device administrator must review it rather than trying to override management.
• Review the actual printer destination and layout in ordinary preview. If the change is unsuitable, retain the working original shortcut and remove only the added switch from the copy. Do not reset the browser, remove its profile, clear storage or reinstall the app.
• For unresolved problems, provide the browser version, Windows version, printer model/interface, selected destination, exact error and whether paper emerged. Keep shortcut details containing account or local user information private. See receipt and drawer troubleshooting.

Full screen, managed devices and other browsers

Full screen: --kiosk-printing does not require --kiosk. Keep the ordinary window or installed app unless you separately need an administrator-managed restricted kiosk. Do not add kiosk, private-session or automatic-reset settings to a working till without checking sign-in, local-order retention and recovery. Full screen is not silent printing.

Managed Chrome: Chromium's current policy definition lists SilentPrintingEnabled for desktop Chrome from version 144, as well as ChromeOS. An administrator can use the supported policy on an eligible installed build instead of a shortcut switch. It is not a per-profile policy. Confirm the effective policy and actual destination before trading; do not treat a shared browser as a till-only silent-print session. See Google's policy reference.

Microsoft Edge: Microsoft documents SilentPrintingEnabled for desktop Edge version 144 or later on Windows and macOS (not Android or iOS). This is a managed-browser route, not a promise that copying Chrome's shortcut flags produces an equivalent supported Edge till. The policy prints with the default destination/settings; Save as PDF can save to Downloads instead of producing paper. Have the device administrator confirm policy availability and effective configuration, then perform the same receipt acceptance checks. See Microsoft's silent-printing policy. Edge's separately documented kiosk experiences use InPrivate sessions and can reset sessions; do not substitute that route for a persistent offline till without a checked recovery plan.

Firefox, Opera and other legacy recipes: ordinary browser printing remains the starting point. This guide does not establish a current supported unattended-print setup for those browsers. Do not copy historical Firefox hidden preferences, old Opera launch recipes, Chrome 57 timer-throttling switches, obsolete print-preview flags or invented app-ID lookup addresses. Keep a working existing setup intact while its exact version and device-management requirements are reviewed. Desktop instructions do not apply to Android/iOS native apps or Star WebPRNT; use the printing-route guide for those routes.