How to Screenshot B2B Catalog Prices Behind a Customer Login
Capture a B2B catalog price in its customer context, preserve the details that explain it, and avoid exposing unrelated account information.
To screenshot a B2B catalog price, sign in with an authorized customer account, select the correct company location if asked, open the relevant product or catalog, and capture the displayed price with its product and quantity context. Record the capture date and relevant account or company-location context separately when useful. Before sharing the image, check the merchant’s terms and your organization’s confidentiality rules, and redact unrelated personal or account information.
A screenshot records what appeared for a particular customer context at a particular time. It does not establish that the price is generally available, that another buyer sees the same price, or that the price remains current.
1. Confirm the account and pricing context
Use an account you are authorized to access. Sign in through the merchant’s normal customer flow. Some B2B storefronts require sign-in before showing B2B products and prices. On Shopify, a customer can sign in with a six-digit code, and a buyer associated with multiple company locations may need to choose which location to purchase for. The catalog assigned to that location can determine the prices and products shown. Shopify’s B2B sign-in documentation describes this flow.
- Sign in through the portal’s normal login page. Complete any one-time code or other verification prompt yourself.
- If the portal asks, choose the company and location relevant to the price you need to document.
- Navigate to the product or catalog page. Confirm the product name, SKU or variant, and any selected options.
- Check whether the displayed price depends on quantity, a volume break, currency, or another visible condition.
- Capture the page once the relevant price and context are visible.
Do not assume an anonymous catalog or another buyer’s view is equivalent. Customer-specific price sheets and product restrictions can result in authenticated users seeing different prices from anonymous visitors or other customers. Propeller Commerce’s customer-specific pricing documentation describes this distinction.
2. Capture enough context to interpret the price
A useful record makes it possible to tell what the number applies to later. Include the visible product name and identifier, selected variant, price and currency, and the quantity or price break that applies. If the account or company location determines pricing, note that context separately when appropriate.
Shopify catalogs can specify product prices and overall adjustments. B2B catalogs can also use quantity rules and volume pricing, so a displayed unit price may depend on the quantity purchased. Shopify’s catalog and pricing overview explains these options. Capture the relevant condition when the portal shows it; do not infer a quantity break that is not visible.
| Record | Why it matters |
|---|---|
| Product name, SKU, variant | Identifies which item the price belongs to. |
| Price and currency | Prevents ambiguity about the amount displayed. |
| Quantity or volume break | Shows whether the price applies only at a specified quantity. |
| Capture date | Places the observation in time; prices can change. |
| Relevant company or location context | Explains which customer pricing context was active, without needing to expose unrelated account details. |
For a one-off record, use the screenshot function provided by the browser or operating system on the device where the authorized session is already open. Shortcut keys vary by device and operating system, so consult the instructions for your specific device if needed. Make sure the captured area includes the price and enough surrounding product details to identify it.
3. Share the screenshot carefully
- Check merchant terms and workplace confidentiality rules before copying or sharing negotiated or customer-specific prices.
- Redact unrelated names, email addresses, delivery addresses, account identifiers, cart contents, and order information before sharing.
- Keep the original only where your organization’s rules allow it; create a redacted copy for broader distribution.
- Include the capture date and relevant pricing context in an accompanying note when the image alone does not explain them.
- Describe the image as a record of what appeared in that account context, not as proof of a public or current price.
The available sources establish that B2B prices can be login-gated and customer-specific. They do not determine whether a particular merchant allows copying or public redistribution of negotiated prices. Resolve that question with the applicable terms and your organization’s rules.
4. Automate only when the workflow and credentials allow it
For recurring captures, an automated screenshot service may be able to load a page using session cookies or an Authorization header. For example, Screenshot Scout documents passing cookies or an Authorization header. That is a technical capability, not evidence that a particular merchant permits automation or that transferring session credentials to a third party is acceptable. Confirm authorization and assess how credentials and captured data are handled before using an external service.
Never paste a live session cookie or bearer token into a public URL, source control, shared log, or support ticket. Treat session credentials like passwords: use only a permitted, restricted workflow, keep them out of application logs, and revoke or rotate them if exposed. If the portal uses an interactive verification step, do not try to bypass it; use the authorized manual process or ask the merchant about an approved export or integration.
For a browser-based one-off capture, there is no need to transfer credentials to a screenshot service. If recurring capture is necessary, first establish that automation is allowed, that the account has access to the intended company location, and that the chosen process is acceptable for the data involved.
5. Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. For an authorized page that is accessible to the capture request, its basic one-call request looks like this. For a login-protected portal, consult the ScreenshotNeo documentation for supported cookies or headers, and use them only when the merchant and your organization permit the credential handling involved.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before the shot. Bot checks, blank pages, and failed loads are never billed, and the response identifies page verdict and billing status in headers. Its MCP server lets AI agents use take_screenshot, get_page_info, and capture_pdf. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. These capabilities do not grant permission to automate a customer portal or transfer its credentials.
Create a free ScreenshotNeo account for 1,000 screenshots a month with no card.
6. Troubleshooting
| What you see | Likely cause | What to do |
|---|---|---|
| Login page instead of the catalog | The capture was taken before sign-in, or an automated request did not have an authorized session. | For a manual capture, sign in and navigate to the product first. For automation, confirm the approved authentication method and session context; do not assume a browser’s logged-in state is automatically available to another service. |
| Unexpected or missing price | The wrong company location may be selected, the catalog may differ, or the customer account may have different pricing visibility. | Verify the selected account and location, then reload the product page. Record the context that actually appeared. |
| Price seems inconsistent with the order quantity | A quantity rule or volume price break may apply. | Check the visible quantity conditions and capture the relevant break. Do not treat a conditional unit price as an unconditional price. |
| Verification prompt or access denied | The portal requires an additional user action or the account lacks permission. | Complete the prompt through the normal flow or ask the merchant or account administrator for access. Do not bypass the control. |
| Screenshot omits identifying details | The selected screen area was too small or the page was scrolled away from product context. | Capture a view that includes the product identity and price together, or take a second contextual capture and label both clearly. |
| Image contains unrelated personal or order data | The capture included more of the account page than needed. | Make a redacted sharing copy and check it before distribution. Keep only data allowed by your organization’s rules. |
| Automated capture returns a blank or unexpected page | The portal may require interactive sign-in, location selection, or other session state that was not established in the capture. | Use the authorized manual method or an approved integration. Review the service’s documentation and credential handling before attempting another automated workflow. |
7. Reliability, performance, and cost considerations
A manual screenshot is usually the simplest choice for an occasional capture because the authorized session and customer context are already visible in the browser. It also avoids transferring session credentials to another service. For repeat work, automation can reduce repeated navigation, but it adds dependencies: permission to automate, valid session handling, correct company-location selection, and safe credential and image handling.
Prices and account context can change. Keep the capture date with the record and verify the page again before relying on an old screenshot for a current decision. A screenshot is a visual record, not a substitute for the merchant’s live catalog, quote, or order confirmation.
Do not estimate a provider’s cost or security from the mere fact that it supports cookies or headers. The available research does not establish comparative provider pricing, retention, or security controls. Evaluate those details from the service’s own current documentation and your organization’s requirements before adopting a recurring workflow.
Frequently asked questions
Does a screenshot prove that every customer can buy at this price?
No. It shows what appeared for the active customer context at the capture time. Other customers or anonymous visitors may see different prices or products.
Should I include the customer name in the image?
Only if it is necessary and permitted. Prefer noting the relevant company or location context separately, and remove unrelated personal or account details from any copy you share.
Can I publish a negotiated B2B price publicly?
The research does not establish a general permission. Check the merchant’s terms and your organization’s confidentiality rules before publishing or distributing it.
Can ScreenshotNeo access a portal just because I can access it in my browser?
No. Your browser’s session does not automatically transfer to an API request. Any use of cookies or headers must be configured through supported options and must be authorized for that portal and account.
