StoreFulfil handles sensitive PII. Basic security hygiene must be maintained.
Best Practices
- Use strong, unique passwords for all accounts.
- Ensure browsers are kept up to date.
- Log out of shared terminals when not actively supervising them.
Account Security Guidelines
General security hygiene for all StoreFulfil users.
How-to
Updated Aug 2026
Owner: Technical Support
Area: Security
Before you begin
Give every signed-in user a short, practical routine for protecting access and customer shipping information.
Prerequisites
- The user can access their own sign-in account.
- Shared terminals and browsers are identified.
- The user knows the approved route for reporting suspected access.
Stop and check
Never share passwords, session details, credentials, full addresses, or private label links.
Expected Outcome
User accounts remain secure.
Runbook evidence
Use these signals to decide whether the work is ready to continue, complete, or needs an owner.
State checkpoints
Normal session
The signed-in person is working within the intended role and client scope.
Next: Use only the data needed for the current task and sign out of shared terminals.
Suspicious access
A password, session, role, or client scope may have been exposed or changed unexpectedly.
Next: Stop sharing access, report the visible facts to an Admin, and follow the account response.
Session finished
The user no longer needs the terminal or account open.
Next: Sign out and remove any temporary working notes or downloaded data.
Completion evidence
- The user is signed out when finished and any suspected access issue has an owner.
Escalation evidence
- Record the account or role, time, visible symptom, and affected scope; never include secrets.
Work safely
Who may take this action
Each signed-in Warehouse Operator, Warehouse Admin, or Brand User
What you should see
The signed-in person is working within the intended role and client scope.
Safe next step
Use only the data needed for the current task and sign out of shared terminals.
What not to do
Never share passwords, session details, credentials, full addresses, or private label links.
How to tell it is complete
The user is signed out when finished and any suspected access issue has an owner.