Medusa's Next.js Starter storefront puts the shopper's country in the URL, so a United States visitor lands on /us and a Danish one on /dk. When there's no country cookie yet, the starter's middleware reads the x-vercel-ip-country header, then falls back to a default region. That one detail decides the region, the cart currency and the payment methods a buyer sees, and it is exactly the part of a checkout that breaks quietly when someone adds a region on the Friday before Cyber Monday (30 November 2026).
I test that path by hand before every big sale, but not one window at a time. I open 20 isolated profiles in BitBrowser, point each at a different country path of my own store, and let the Synchronizer mirror my clicks from one master window into the other 19. One pass through cart, shipping, payment and confirmation takes about four minutes instead of an afternoon.
This post shows the whole setup: the rules that frame it, a profile map, the MCP config that lets an AI assistant open and arrange the windows (and nothing else), the mirrored checkout routine, and what to do when a profile misbehaves.
Contents
- Rules that come first
- Why test the checkout from 20 profiles
- The profile map
- Connect BitBrowser MCP (read-only first)
- Routine 1: open and arrange the 20 profiles
- Routine 2: the mirrored checkout pass
- Device layer: none needed for this test
- Offboarding and incidents
- Quick answers
- One next step
Rules that come first
Everything here runs against a store you own or are paid to test. The Synchronizer copies mouse and keyboard input from one window into others, and BitBrowser markets it for bulk work, but I only point it at my own storefront and my own test accounts. Repeating the same action from many accounts on someone else's platform is a different thing, and most marketplaces forbid it.
Three more rules shape the routine:
- Payments run in test mode. Medusa's payment providers (Stripe, for example) have sandbox keys. The store under test uses those keys, so no card is charged and no real order reaches fulfilment.
- Locations are honest. The country path, not a proxy, tells Medusa which region to load. If your deployment geolocates by IP (the
x-vercel-ip-countryfallback), a profile with a local IP is fine for viewing your own storefront the way a local buyer would. It is a test of your app, not a login somewhere else. - The AI assistant only organises. Through MCP it can list, open, arrange and close profiles. It never clicks inside the store, never fills a form, never places an order and never touches settings or money. I do the clicking in the master window.
The Synchronizer is a Windows feature. On macOS you can still use the profiles and MCP; you'll click through each window yourself or script it with Playwright.
Why test the checkout from 20 profiles
A checkout is a chain of small decisions keyed to the region: currency, tax lines, shipping options, the list of payment providers, address fields. In a Medusa project those live in regions and sales channels in the admin, and the storefront asks for them per country code. A typo in one region's shipping option shows up only for buyers in that region.
Testing from one browser and switching countries in the selector works, but cookies carry over. The _medusa_country_code cookie sticks, a cart created in one region gets moved to another when you switch, and you end up testing the region-switch code path instead of a clean first visit. Separate profiles fix that. Each one has its own cookie jar, local storage and cache, so every window is a fresh shopper who has never seen your store.
Twenty is not magic. I run one profile per active region plus a few edge cases:
- a country with no shipping option configured (the checkout should say so, not crash),
- a country whose currency has no minor unit,
- a returning shopper with an abandoned cart from last week.
If you have five regions, run eight profiles. The routine is the same.
Timing matters too. Most teams I work with freeze deploys a few days before Black Friday (27 November 2026) and keep the freeze through Cyber Monday. The last full checkout pass should happen just before that freeze, against the exact build that will serve the sale, and a short repeat pass should follow any hotfix during the freeze. With the profiles already built, the repeat pass costs ten minutes, which is why it actually gets done.
The profile map
Name profiles so the window title tells you what you're looking at. I use QA-<region>-<case>. Group them in a BitBrowser group called checkout-qa and tag them medusa. That lets the assistant open "every profile in checkout-qa" without guessing.
| Profile | Store path | Region in Medusa | Test case |
|---|---|---|---|
| QA-US-new | /us | North America (USD) | first visit, guest checkout |
| QA-US-return | /us | North America (USD) | returning shopper, saved cart |
| QA-CA-new | /ca | North America (USD) | address form with province |
| QA-GB-new | /gb | United Kingdom (GBP) | VAT line on the summary |
| QA-DE-new | /de | Europe (EUR) | German address format |
| QA-FR-new | /fr | Europe (EUR) | free-shipping threshold |
| QA-DK-new | /dk | Europe (EUR) | default region fallback |
| QA-JP-new | /jp | Japan (JPY) | currency with no decimals |
| QA-AU-new | /au | Australia (AUD) | GST line |
| QA-NZ-noship | /nz | Oceania | no shipping option set |
| ... | ... | ... | one row per remaining case |
Keep the table in your repo next to the seed script. When a region changes in the admin, the table changes in the same pull request.
Fingerprint settings stay at BitBrowser's defaults for each profile. You're not trying to look like anything; you only need clean storage per window. Give the master profile a coloured window frame or a distinct name so you never type into the wrong one.
Connect BitBrowser MCP (read-only first)
MCP support is built into the BitBrowser client from version 7.1.5. Open Settings > Browser Settings > Local API, turn on authentication control, and copy the API token. The local MCP endpoint is http://127.0.0.1:54345/mcp, and the token travels in an x-api-key header. BitBrowser's own guide gives this general config for MCP clients such as Claude Code or Cursor:
{ "mcpServers": { "bitbrowser": { "url": "http://127.0.0.1:54345/mcp", "headers": { "x-api-key": "<YOUR_API_TOKEN>" } } } } If you changed the Local API port, use the address your client shows. Reset the token and the config needs the new one.
The first prompt I send to a new setup changes nothing. It only reads:
List every BitBrowser profile in the group "checkout-qa" with its name, tags and proxy setting. Do not open, create, edit or delete anything. You only organise profiles and windows. Never click inside a website, never fill forms, never buy, post or change any setting or payment. If the list matches the table above, the connection works and the names are right. If a profile is missing, fix it in the client by hand before you let the assistant open anything.
Routine 1: open and arrange the 20 profiles
This is the prompt I paste on test day. It opens the windows in order, waits between them, and tiles them so the master sits top left.
Open the profiles in the group "checkout-qa" one at a time, in this order: QA-US-new first (this is the master), then the rest alphabetically. Never open two profiles at the same moment: wait until one window is fully open before starting the next. If you close a profile for any reason, wait 5 seconds before opening another one. When all are open, arrange the windows in a 5 x 4 grid, master top left. Then stop and tell me which profiles opened and which failed. You only organise windows. Do not click inside any page, do not type into the store, do not place orders and do not change settings. Two habits keep it calm. The "one at a time" rule stops twenty Chromium instances from fighting for CPU during launch, and the 5-second pause after a close gives the client time to release the profile before the next one starts. I've had profiles hang when I skipped that pause; with it, none have.
When the grid is up, I load the start URL myself in the master window and press the Synchronizer's start button. The other 19 follow.
Routine 2: the mirrored checkout pass
With sync on, every click and keystroke in the master repeats in the controlled windows. Medusa's starter shows the same layout in every region, so a click on "Add to cart" lands on the same button in all 20 windows. Here is the pass I run, with what I watch for at each step:
- Product page. Pick a product that exists in every region. Watch the price line in each window: currency symbol, decimals, and whether the price exists at all.
- Add to cart, open cart. The cart total should match the product price plus nothing. A tax line here usually means a region has tax-inclusive pricing set differently.
- Checkout, address step. Type the address in the master. The Synchronizer can enter the same text in every window, or different text per window; I use different text so each country gets a valid postcode. Then check that each address form shows the fields its country needs.
- Shipping step. Every region should list its options. The
QA-NZ-noshipwindow should show a clear message, not a spinner. - Payment step. In test mode, choose the provider and use the provider's published test card. Look for regions where the provider list is empty.
- Review and place order. Orders go to the test database only. Then open the Medusa admin and check that 19 orders arrived with the right region and currency (the no-shipping case should have none).
The Synchronizer lets you add a random delay to mirrored mouse events. I leave a small one on, because some cart updates race when 20 windows press the same button in the same millisecond against one dev server.
Turn sync off before you investigate a failure. Click into the broken window alone, reproduce the bug, and copy the network response from DevTools. With sync still on, your debugging clicks would travel to all 19 other windows too.
Device layer: none needed for this test
This row runs on browser profiles alone, no cloud phone or cloud PC. Medusa's starter is responsive, so desktop windows cover the logic. If your buyers are mostly on phones, a second pass on real mobile browsers is worth it: BitCloudPhone gives you Android devices whose language, time zone and location follow their IP, which helps when you want to see your own store as a local phone buyer sees it. Keep that pass small, one phone per region that matters.
That covers all four things BitBrowser puts on its banner in one small test: many accounts kept apart, one-click sync, more than one kind of device, and isolation between profiles.
What does need a check after the pass is the database. I run a quick SQL count of orders created in the last ten minutes grouped by region and currency, and compare it to the table. Nineteen rows, nineteen regions, one missing on purpose.
Offboarding and incidents
When the test is over, ask the assistant to close every profile in the group, one at a time with the 5-second pause, and to report which ones closed. Then clear the test orders from your staging database with your normal reset script. I keep the profiles; next week's run reuses them.
When a teammate leaves, remove their BitBrowser seat and rotate the Local API token, because the token sits in their MCP config file. Share profiles through Employee Management with basic permission rather than sending the token around. Your brief may mention 7, 15 or 30-day share codes for outside testers; check the current options in the client before relying on them.
When the sync drifts, usually one window scrolled differently or a cookie banner appeared in only some regions, stop the Synchronizer, fix the odd window by hand, and restart sync from a known screen (the cart page is a good one).
When a profile won't open, don't retry in a loop. Close it, wait 5 seconds, and open it once more. If it fails again, take it out of the run and note it in the log; a 19-window pass is still a good pass.
When you find a real bug, write down the profile name, the country path, the step, and the response body. That's usually enough to find the region setting in the Medusa admin that caused it.
Quick answers
Do I need proxies for this? Not for the country-path test. Medusa picks the region from the URL. Only if your deployment geolocates by IP do you need profiles with local IPs, and then only to view your own store.
Can the AI assistant run the clicks too? No, by design. In this setup it opens, arranges and closes profiles. The checkout clicks come from you in the master window, mirrored by the Synchronizer.
Will 20 windows slow my laptop down? A little. Twenty Chromium profiles on 16 GB of RAM is fine for a checkout. If you're on 8 GB, run two passes of ten.
Does this work with a headless backend on another host? Yes. Point every profile at your staging storefront URL; the backend location doesn't matter to the profiles.
What about stores that sell in one country only? Then the region matrix is small, and the profiles earn their keep on the other cases: guest versus logged-in buyer, an expired discount, a cart left open for a week. Each case gets its own clean profile.
Is the Synchronizer free? BitBrowser lists it as a free feature, and the free plan includes 10 browser profiles, enough for a first run with ten regions.
On plans: if you need more than ten profiles for one sprint, BitBrowser's Year-End Mega Sale runs from November 11 to December 12, 2026, with 3 months at 20% off (6 months 30%, 12 months 40%, 24 months 50%), and 3 months covers one Cyber Monday QA sprint plus the Christmas fixes after it. The BitBrowser link above is the place to check it. Cloud Phone and Cloud PC plans are up to 40% off in the same window.
One next step
Write the profile table for your own regions tonight, create the checkout-qa group, and run the read-only MCP prompt. If the list comes back right, you're one Synchronizer click away from a 20-window checkout pass before Cyber Monday.




