Running Snipcart?

Snipcart totals or webhooks acting up? We sort it out.

Snipcart is the checkout dropped into an otherwise static site, and most of the problems we see come from exactly that seam: a product crawled with the wrong price, a webhook endpoint that returns 200 before it has actually recorded anything, or a shipping provider whose rates never make it back to the cart. We walk the order lifecycle from the data-item attributes through to the order confirmation and close the gap.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

snipcart-orders.log

still broken

What it is

Snipcart at a glance

Snipcart is a hosted shopping cart designed to bolt onto any website, built by a team in Québec City and launched in 2013. You add a few data attributes to buy buttons, drop a script tag in, and the checkout, taxes, shipping and order management live on their side.

It is a fit for static sites built with Jekyll, Hugo, Eleventy, Gatsby, Astro and Next.js, and for existing CMS sites that do not want to turn into a full ecommerce platform. The pricing is transaction based rather than per seat, and it leans on Stripe, Square, or PayPal underneath to actually move the money.

Type
Hosted checkout widget for existing websites
First released
2013
License
Proprietary, transaction fee pricing
Maintained by
Snipcart Inc., Québec City
Typically used for
Adding checkout to static sites, Jamstack stores, CMS driven catalogs, digital downloads

The honest version

Snipcart pros and cons

No technology is all upside. This is where Snipcart earns its place and where it tends to cause trouble.

Where Snipcart is strong

  • Drops into any websiteA script tag and a handful of data attributes turn plain HTML into a working checkout, which is the whole reason people choose it over a heavier platform.
  • Works beautifully with static generatorsProducts can live in markdown, YAML or a headless CMS, and the crawler reads the live page to validate prices rather than relying on a separate product database.
  • Webhooks for every lifecycle eventOrder paid, subscription renewed, inventory updated, customer created: each one fires a webhook you can act on without writing ecommerce from scratch.
  • Built-in subscriptionsRecurring orders, trial periods, and pauses are first class rather than something you have to glue together from raw charges.
  • Reasonable developer documentationThe JS SDK, server events and REST API are documented clearly enough that a competent engineer can be productive in an afternoon.
  • Transaction pricing suits small storesNo monthly minimum once you clear the free tier threshold means tiny catalogs do not pay platform rent they have not earned yet.

Where Snipcart bites

  • The crawler is the whole trust modelSnipcart revalidates every item by fetching the public product URL. If that page is paywalled, rate limited, or renders prices client side, the checkout will refuse the order with messages that are not always clear.
  • Thin on reportingThe dashboard covers orders and customers; anything resembling cohort analysis, LTV, or marketing attribution needs to be exported and analysed somewhere else.
  • Tax and shipping webhooks add latencyDelegating rates to your own endpoint means the cart is only as fast as your slowest integration, and an upstream carrier timeout freezes the checkout for everyone.
  • Less third-party plugin ecosystem than ShopifyFewer apps for loyalty, reviews, upsells and marketplace connectors. Most of those capabilities need to be built or integrated manually.
  • Hosted checkout limits visual controlThe checkout modal is themeable but not fully custom; teams who want a bespoke multi-step flow will push the boundaries fast.
  • Vendor lock-in on the order modelOrders, subscriptions and customer records live in Snipcart, and moving to a different platform later means an export, a mapping exercise and a payment processor migration.

Sound familiar?

Common Snipcart problems we fix

The Snipcart problems that bring people to us, and what you have once each one is fixed.

Crawler error: product not found

Snipcart cannot validate a product

The buy button references a URL that is behind auth, returns a 404 in production, or only renders the price after JavaScript runs. The crawler sees no price and refuses the line item.

Products crawlable and priced

Price mismatch detected

The cart total disagrees with the product page

A product that was edited in the CMS but not redeployed, a stale CDN cache, or a currency conversion applied in the wrong place. The customer sees one price and the receipt shows another.

Totals line up on both sides

Taxes.calculate webhook HTTP 500

Taxes or shipping rates fail at checkout

Your rate endpoint errors, times out, or returns a payload Snipcart does not accept. The checkout stalls, the customer retries, and some of them give up.

Rates returning within the timeout

WebhookValidationException: Token validation failed

Webhooks are being rejected

A signing token that rotated after a redeploy, a load balancer stripping headers, or a handler returning before it has finished the work. Snipcart retries and eventually gives up.

Orders recorded every time

order.completed with no inventory decrement

Stock counts drift away from reality

Orders complete but the inventory sync hook never runs or runs after a timeout, so two customers can buy the last unit within a minute of each other.

Inventory accurate after each order

subscription.paused: payment declined

Subscriptions fail silently on renewal

A card that expired or a bank that rejects off session renewals without SCA setup. Snipcart marks the subscription paused and nobody notices until a refund is requested.

Renewals recover or alert

Invalid data-item-url

Products added from a dynamic page refuse to check out

SPAs and gated catalogs produce URLs the crawler cannot reach. Snipcart treats the item as unverified and blocks the order.

Public URL per product, cart happy

Discount code expired

Promo codes behave inconsistently

Overlapping campaigns, timezone boundaries on expiry, or a usage limit that was lower than the newsletter list. The result is customers quoting codes support staff cannot honour.

Discounts predictable and documented

What we do

Snipcart help, from one failed order to the whole cart

Pick one broken checkout, or let us look after the full storefront.

Rescue
Orders failing, webhooks silent, or totals mismatching on live traffic. We stop the bleeding first and dig through logs afterwards.
Catalog and crawler fixes
Product URLs made crawlable, prices rendered server side, and the Jamstack build pipeline wired so Snipcart always sees the latest data.
Taxes and shipping
Rate webhooks built or repaired, carrier APIs integrated properly, and timeouts handled so the checkout never stalls.
Subscriptions
Recurring plans, trials and pauses configured against your real contracts, with dunning that wakes a human instead of a dashboard.
Migrations
Moving in from Gumroad, Shopify Lite, or a bespoke cart, with order history preserved and customers retained.
Managed Tech
An engineer on retainer to watch order webhooks, audit discount leakage, and answer when Snipcart changes something in the dashboard overnight.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Snipcart alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Snipcart questions

Something else? Call+1 737 727 7327

Why does Snipcart say it cannot find my product?

The crawler fetches the public URL you set on the buy button and compares the price it finds there against what the cart is sending. If the URL is behind auth, returns a 404, or renders the price only after JavaScript runs, the crawler will refuse the line item. The fix is to make sure each product URL is publicly reachable with the price present in the initial HTML.

Can Snipcart work on a static site generator like Astro or Hugo?

Yes, that is its intended use case. Products live in the content layer, the generator renders a page per product with the price in the markup, and Snipcart's crawler reads that page on checkout. The main thing to get right is making sure the build pipeline redeploys when prices change, otherwise the cart and the page disagree.

Why is the checkout slow to load tax or shipping rates?

Snipcart calls your taxes.calculate and shipping.fetch webhooks during checkout, so the cart is only as quick as those endpoints. A slow carrier API or a cold serverless function can turn a two second checkout into fifteen. Cache rates aggressively, keep the handlers warm, and have a sensible fallback when the upstream is unresponsive.

How do I migrate from Gumroad or Shopify Lite to Snipcart?

The catalog usually needs to be exported and re-published through whichever generator or CMS you are using, since Snipcart does not store products the way those platforms do. Customers and orders can be imported for reference but saved payment methods do not transfer directly. Plan a short overlap where both checkouts run and new orders go to Snipcart.

Does Snipcart handle subscriptions?

It does, with recurring plans, trials and pauses as first class objects. The common pitfall is forgetting that renewals are off session charges, so the payment method must be captured with SCA in mind from the start. If it is not, European and UK cards start declining on renewal.

How much does Snipcart help cost?

Estimates are on the house. Send us the symptom, a link to the store, and a snippet of the order log, and a price lands in your inbox before any work begins.

Free estimate

Snipcart giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.