How to use vtexSnitch

The VTEX OrderForm is the source of truth for every checkout session — items, totals, shipping, promotions, payment methods, marketing UTMs — but the raw JSON is dense and hard to eyeball. The OrderForm X-Ray reformats the live orderForm response into readable sections so you can spot a missing attachment or a wrong seller without a text editor.

Everything updates in real time as the page fires mutations: add an item in another tab, apply a coupon, change a shipping address, and the panel reflects the new state the moment the storefront does. Click into any field to inspect the raw payload and the request that produced it.

Use it when a promotion isn't applying, when checkout totals don't match the cart, or when marketing UTMs aren't landing on the order.

Chrome's built-in Network panel only captures traffic *after* you open DevTools. That means the very first wave of requests a VTEX storefront fires — orderForm, segment, tracker bootstraps — is usually invisible by the time you start debugging. vtexSnitch injects a MAIN-world content script at document_start and monkey-patches fetch and XMLHttpRequest before the page has a chance to run.

Every request the storefront makes shows up in the panel, filterable by method, status, host, or VTEX-specific endpoint group (checkout, catalog, intelligent search, trackers). Click any row to see the full request, response, headers, and timing.

Reach for this tab when something fires once on page load and you need to see it, or when you want to confirm a request never happened.

Every VTEX store is one of four architectures — Legacy CMS, VTEX IO (Store Framework), Headless, or FastStore — and the debugging surface is different in each. Store Info sniffs the runtime, the DOM, and the network signatures to detect which one you're looking at, along with the account name, workspace, binding, locale, code version, and current sales channel.

Instead of opening the console and hunting through __RUNTIME__, __STATE__, dataLayer, and meta tags one by one, you get the full storefront context in one card.

One click copies a plain-text block you can paste into a bug report, a Slack message, or a ticket — no more asking "what account is this, again?"

VTEX availability, pricing, and seller lineup all change based on the customer's region — and the region is driven by a cookie that's painful to edit by hand. Region Simulator takes a postal code or ISO country, resolves the matching regionId, and shows every seller that can fulfill to that address in one call.

It hits the public /api/checkout/pub/regions endpoint, so no admin token is required. Copy any seller ID with a single click, or hot-swap the active region to see how the storefront behaves without touching cookies or reloading the session.

Use it to reproduce a customer's "this item shows as unavailable" complaint, or to audit which sellers serve a market before a go-live.

MarTech pixels are the quiet part of a VTEX store: they fire, they send data to ad networks, and they rarely fail loudly. MarTech Inspector matches every outgoing request against a signature library of known trackers — GA4, GTM, Meta Pixel, TikTok, Pinterest, Bing, Criteo, Hotjar, Clarity, and more — and lights up the matching row each time one fires.

For every tracker you get a live hit count, the last payload, and which event triggered it. UTM and click-id attribution for the current session is broken down in a separate panel so you can confirm the campaign parameters you paid for actually landed.

Reach for this tab when a paid-media agency swears the pixel is firing (and it isn't), or when you suspect a ghost tracker is leaking data you never approved.

On single-page VTEX IO and FastStore stores, the meta tags that matter for SEO are injected client-side — which makes manual auditing a chore. SEO Meta watches the DOM and reports the current title, description, canonical, robots, OG tags, Twitter cards, domain verification tags (Google, Bing, Meta, Pinterest, Yandex), and duplicate warnings for every route the user navigates to.

Every tag is validated against the current URL, so a stale canonical or a missing og:image jumps out instead of hiding. Duplicates (two google-site-verification metas, for example) are flagged explicitly — a common footgun on stores with multiple GTM snippets.

Use it to catch SEO regressions before they hit production, or to verify a migration didn't drop critical meta tags on a specific template.

Products Watch streams every catalog response the storefront receives — /api/catalog_system/pub/products/search and its Intelligent Search equivalents — and surfaces the raw product document as readable cards. You see what the API actually returned, not what the PDP chose to render.

Drill into any SKU for price, list price, availability, dimensions, sellers, and images. A specs and category breakdown sits one click away, so you can confirm why a facet did (or didn't) match.

Useful when a product looks wrong on the PDP and you need to know whether it's a catalog issue, a template issue, or a cache issue.

Checkout Simulation lets you POST to /api/checkout/pub/orderForms/simulation with any combination of SKU ID, quantity, and seller — without creating a real cart or touching the logged-in session. For each item you get availability, pricing, and the full seller chain back, with the requested seller highlighted.

Build the cart from real SKUs, run the simulation, and inspect each transition in the checkout pipeline. Diff payloads between two runs to isolate a regression, or swap sales channel to see how a different trade policy changes the outcome.

Perfect for reproducing an order that a customer says failed, or for confirming an SKU is actually deliverable to a given address before anyone places a real order.