The new Strator Neo login identifier, which now combines the Logista client code and the employee profile name, generates errors whenever one of these two elements is incorrectly entered. Before looking for a network bug or server issue, the first check should focus on this identifier/password pair and how the browser handles it.
Strator Neo Identifier Format: Exact Structure and Common Input Errors
The expected identifier on the page gestion.strator.eu follows a specific format: Logista client code followed by a slash and the employee profile name. The client code is found on the header of the Logista invoice, on the delivery schedule, in the “About” menu of the sales application, or on the Strator+ application.
Further reading : Practical tips for knowing where to place the jack on a Peugeot 307
Each employee profile created in management has its own identifier. A point of sale with three operators thus has three distinct identifier/password pairs. We regularly observe login failures related to confusion between the POS code (old format) and the Logista client code (new format).
When a tobacconist tries to log in with their old POS code, the page returns a generic error without specifying that the format has changed. Systematically checking the correspondence between the code displayed on the invoice and the one entered in the “CodeClient/user” field avoids most blocks. To better understand logging into the Strator management Neo register, this starting point remains the most reliable.
Recommended read : The best smartwatches for swimming: how to choose?
Browser and Cache: Why Chrome or Edge Block the Strator Login Page
Connection incidents have increased since recent updates to Windows 10/11 and browsers like Chrome and Edge. The most common symptoms: blank page on loading or infinite refresh loop on the login screen.
The problem often stems from a corrupted cache or outdated cookies related to the old Strator domain. When the browser retains an expired authentication cookie, the page attempts to validate an expired session and loops without displaying the form.
Targeted Cleaning Procedure
Clearing the entire browser cache works, but we recommend a more surgical approach to avoid losing active sessions on other sites:
- Open the developer tools (F12), Application tab, then delete only the cookies associated with the domains strator.eu and tpos.logista.com
- Temporarily disable ad-blocking or enhanced security extensions, which sometimes intercept Strator authentication requests
- Test the connection in a private browsing window: if it succeeds, the problem is confirmed on the cache or extension side
- As a last resort, switch to Firefox or another non-Chromium browser to isolate a potential conflict with a recent Chrome/Edge update
These insights come from support groups of tobacconists and support technicians who documented these incidents between 2023 and 2025. Changing browsers remains the quickest solution when the login page simply does not display.
Password Policy and Strator Neo Account Lockout
Account lockouts have increased with the tightening of password rules imposed by certain partners (insurers, franchisors, tobacconist networks). An expired password or one that does not meet the new complexity requirements triggers a lockout without an explicit error message.
The “Forgot Password” link on the login page gestion.prod4.strator.eu allows for self-resetting. We recommend synchronizing the internal renewal frequency of the point of sale with that required by Strator. When a network imposes a change every 90 days while Strator requires it at a different frequency, the discrepancy causes surprise expirations.
Best Practices for Multi-Profile Access Management
Each employee profile having its own password, a point of sale with rotating staff accumulates identifiers. Storing these accesses in a dedicated password manager (not in a text file on the desktop) limits input errors and cascading lockouts.
Another common pitfall: the “Save Password” checkbox on the login page. If an employee saves their credentials and then a colleague tries to log in without unchecking the box, the browser pre-fills the field with the wrong profile. On a shared workstation, disabling the automatic password saving in the browser settings eliminates this risk.
Strator Support Disparities: Which Channel to Use for Persistent Blocking
Not all Strator support channels are equal in terms of response time. The premium number displayed on the Bleez documentation (charged by the minute) is suitable for quick unlocking. In contrast, tickets opened via the Bleez Atlassian portal offer more structured follow-up for recurring issues.
We recommend documenting each incident (screenshot of the error message, browser used, Windows version, time of attempt) before contacting support. A well-documented ticket divides the resolution time compared to a call without technical context.
- For a blank page or a login loop: specify the browser, its version, and if the problem persists in private browsing
- For an account lockout: indicate the client code, the affected employee profile, and the date of the last password change
- For an intermittent problem: note the exact times of connection failures and successes to identify a potential server maintenance window
Facebook groups of tobacconists also constitute a useful source of information to check if an incident is isolated or widespread on the Strator infrastructure. When several points of sale report the same symptom at the same time, the problem is on the server side, and the call to support mainly serves to confirm that an intervention is underway.
Most connection failures to Strator Neo are resolved in less than ten minutes with a methodical check: identifier format, browser cache status, password validity. Keeping an alternative browser installed on the cash register and an up-to-date password manager covers the two most frequent causes of blockage.