Setup

This guide assumes you've established a Craft site and you're setting up a new store for the first time.

Create a Snipcart Account

Start by creating an account (opens new window) via Snipcart. Copy your API keys from Account → API Keys in Snipcart to Settings → Snipcart on your Craft site.

Orders

Everything here is off by default, but you can configure a number of options that don't require any extra code unless you'd prefer your own markup, field types, and integrations.

Order Comments and gift notes are explained more in their own section, and while email notifications are ready to go you can learn more about using your own templates for them in Custom Email Notifications.

Webhooks

There's nothing to set here, but this part is important: use this URL to link Snipcart and Craft with webhooks.

Logging

Caching is enabled and somewhat conservative to balance timeliness and speed, but here you can adjust that and optionally turn on webhook logging that could help with troubleshooting.

Shipping

If you've set up a ShipStation account and want the Snipcart plugin to get live rates or forward orders, this is where you'll need to add your credentials along with a Ship From address.

See the Shipments page for more about how ShipStation integration works.

Complete a Test Order

Enable Test Mode and configure the matching test keys. Create a recognisable product, such as a Studio Notebook, with its price and identifier. Follow Templating to include the cart assets and render its buy button on the product page.

Open that page as a visitor, add the product and inspect the cart. Check its name, quantity, price and product URL before completing a test checkout. Snipcart needs to be able to reach and validate the product data, so test on a reachable environment when a local URL is unavailable to the service.

After checkout, inspect the order in Snipcart and confirm the corresponding webhook reaches Craft. Check the resulting order and any configured notification or shipping integration. A successful browser checkout does not prove that the webhook was delivered; use Testing Webhooks to diagnose that part separately.