From store setup to daily operations
Explore the responsibilities and actions at each step.
Create a store environment
Choose Chrome / Chromium or Firefox, name the profile for the store and task, and place it in the right folder.
Set its network and locale
Bind and check a proxy. Use automatic language, timezone and location settings when the intended setup follows the proxy exit.
Prepare the operator
Invite teammates, assign roles and keep store account permissions aligned with their tasks. Add a note for the next operator.
Run and review the task
Open the store profile, complete the work and close it normally. Use audit logs and your task records to review changes.
Reuse configuration across a growing operation
Save recurring settings as templates and use quick create when adding environments. Folders separate stores or projects; tags distinguish regions and work categories. Edit proxies, labels and notes directly from the list.
Each profile has its own browser storage. Import Cookies when preparing a session and use cloud Cookie archiving when closing the environment. Keep store-specific identity and content associated with the corresponding profile.
Connect recurring tasks to your tools
Use Local API to prepare and open environments from your own scripts. Connect MCP when an AI tool needs to inspect a page, navigate or capture a screenshot in a selected store environment. Window synchronization supports repeated browser interaction.
These capabilities help operate the browser. Catalogue publishing, order decisions and content approval remain in your store systems and team process.
A practical store workspace
| Folder | Profile | Configuration focus |
|---|---|---|
| Store A | Catalogue work | Store session and operator context |
| Store B | Customer support | Support session and handoff note |
| QA | Regional storefront checks | Expected locale, network and browser engine |