DK keeps your books. Stokk runs your shelves.
We don’t replace DK, we’re built on it: DK was Stokk’s first connector. Stokk reads stock, sales, items and suppliers from DK every night, runs the buying and the floor, and writes counts, transfers, invoices and prices back. Your accountant never logs into anything new.
What DK does, and what Stokk adds on top.
| What you need | DK alone | Stokk |
|---|---|---|
| Financials, invoicing and the item master | DK | Stay in DK |
| Demand forecast per product per store | No | AI-driven, scored every night |
| Orders drafted per supplier, with reasons | Purchasing module, built by hand | The Morning Brief |
| An AI check on every order line | No | |
| Store top-ups | Built by hand | A draft every morning, per store |
| Counting | Counting module | On phones, several people per count, posted to DK |
| Picking, labels and carrier shipping | No | |
| Loyalty cards in Apple and Google Wallet | No |
The books, done properly. Stokk leaves them there.
DK keeps your financials, invoicing, stock master and receipts straight, and your accountant knows it inside out. What it doesn’t do is decide: forecast each store, draft the morning’s orders, or tell a buyer which supplier to call first. That’s the layer Stokk adds.
DK underneath, Stokk on top.
- DK
Keeps the books
Accounting, invoicing, the item master and receipts stay in DK.
- Every night
Stokk reads
Sales, stock, items and suppliers come across through the DK API.
- Every morning
Stokk runs the floor
The Morning Brief, store top-ups, counting, picking and loyalty.
- As you work
Written back
Counts, transfers, invoices and prices go back to DK. Orders live in Stokk and DK records the receipt.
Questions people ask before the call.
Is the DK connection live?
Do purchase orders go into DK?
Keep DK. Run the shop on Stokk.
Half an hour on a working sample, then we map it to your DK setup. Your accountant won’t notice a thing.