Dutchie POS API for dispensaries: reads, writes, limits

RECONCILIATION

What a reconciliation run needs from Dutchie POS

A daily reconciliation compares each completed sale in the POS with the sales receipt in the state system. It matches on package tag, quantity and total, and it shows a match rate per store. To do that, the POS has to hand over completed tickets with their line items, plus voids and returns. Everything else in a Dutchie POS account is context.

Dutchie POS's API reads products and inventory with lab results, register transactions with package IDs, customers, discounts, employees, deliveries and purchase orders. Dutchie POS has no webhooks and is read by incremental polling ("No — incremental polling, about 120 requests/min per key"). The adapter's sync is described as: polling within the per-key budget; nightly full reconcile.

For online orders, the fact sheet records Dutchie POS as "No create-order API — staff handoff plus receipt match-back". That decides where a ticket can go missing between the order, the register and the state receipt, and so where the daily list is most likely to show an unmatched ticket for a store using Dutchie POS.

Whatever the POS, a difference is classified as documentation, timing, process or loss before anyone adjusts a record, and an adjustment in the state system always carries a reason code and a person's name. The full procedure is in the Metrc reconciliation guide linked below.