Saltar al contenido principal

Send New Orders to Your POS

Step-by-step recipe for sending every new order to Indica, Blaze, Dutchie, or your own system the instant it comes in, using a saved webhook.

What this recipe does

This walks through sending every new DabDash order straight to your point-of-sale or CRM — Indica, Blaze, Dutchie, a Zapier/Make automation, or your own custom endpoint — the instant a customer checks out. No re-typing orders by hand, and you keep running your own register.

This uses the Saved Webhooks feature under the hood — this recipe just walks through it with your POS in mind. See the related articles below for the full technical reference.

What you'll need first

A URL on your POS/CRM side that can receive an HTTPS request and read JSON. Most POS systems and automation tools (Zapier, Make, n8n) call this a "webhook URL," "inbound webhook," or "custom trigger" — check your POS's own integrations or developer settings for it. If your POS doesn't offer one directly, a Zapier or Make "Catch Hook" step works as a middle step between DabDash and your register.

Step by step

  1. Go to Settings › Webhooks and click Add webhook.
  2. Paste the URL your POS/CRM gave you into the endpoint field. It must start with https:// and be reachable from the public internet — a local-only address won't work.
  3. Save. DabDash generates a signing secret automatically — you don't need it unless your POS asks you to verify the sender.
  4. Click Test webhook to send a sample order to your POS right away, before any real customer order arrives. Confirm it shows up on the other side.
  5. Turn the webhook on. From now on, every new order fires automatically.

What gets sent

DabDash sends the order the moment it's placed — the customer's name, phone, items ordered, quantities, and total, plus your store's name so you can tell orders apart if you run more than one DabDash shop. Full technical field-by-field detail is in the related Saved Webhooks article below.

If it's not showing up

  • Click Test webhook again — if it fails immediately, double-check the URL is correct and starts with https://.
  • Confirm the webhook toggle is switched on — a saved-but-off webhook never sends.
  • Check with your POS/CRM's own support on how their inbound webhook endpoint expects data — some require a specific header or authentication token, which you can add under Advanced on the webhook's edit page.