Skip to main content
How Stokis works

A procurement agent, not another ERP module.

Stokis is for B2B e-commerce operators who have outgrown spreadsheet. A 24/7 agent watches stock, sales and supplier mail, learns demand patterns, drafts purchase orders with explainable logic, talks to suppliers on your behalf, and can send the orders automatically under your rules.

No card needed 10-min PrestaShop setup Cancel anytime
Section 01 · The full workflow

From sign-up to a closed PO, step by step.

You sign up, connect PrestaShop with a read-only API key, the agent reads your products, stock and last 90 days of orders, and within minutes you have a real reorder dashboard. From there, the loop runs itself: draft → approve → send → supplier reply → reconciled stock. Five flows below cover every step the agent owns and the one it hands back to you.

01
Flow 01 · A 24/7 procurement agent

An agent that watches stock, sales and supplier mail — and acts the moment it needs to.

The agent doesn’t wait for a 02:00 batch. It re-reads stock and sales in short loops, parses every supplier email the moment it lands, re-forecasts demand whenever a SKU drifts off trend, and drafts a purchase order the second a line crosses its reorder point. By the time you check the inbox, the work is already done — and you can see exactly which signal moved it.

  • Watches the deltas continuously. A sudden sales spike or a stock dip on a single SKU triggers a draft within minutes — not on a nightly cron.
  • Re-forecasts when reality changes. A returns wave, a supplier ETA slip, a seasonal pattern shifting earlier — the forecast updates the same hour, not next week.
  • Reads supplier mail as it arrives. Confirmations, ETAs, price changes and MOQ updates are parsed and queued the same hour they land in the inbox.
  • Auto-sends inside your cap, holds outside it. Under the per-PO cap, the agent sends. Over it, the PO waits with its reasoning and the signals it relied on attached.
02
Flow 02 · Approve a held order

When the agent isn’t sure, you decide. In ninety seconds.

Held POs land in the inbox with the agent’s reasoning, signals it relied on, the lines it drafted, and the supplier it chose. You can read it like an email, edit a quantity inline, or kick it back. No spreadsheet, no toggling between five tabs.

  • The reasoning is on tap. Why this supplier, why this quantity, what the alternative would cost.
  • Edits are local. Change a line and the totals, ETA, and supplier note recompute before you approve.
  • Approval is auditable. Every send carries the approver’s name, timestamp, and the version of the policy that allowed it.
03
Flow 03 · Receive & reconcile

When stock lands, the books close themselves.

You enter the received quantities per line. Stokis applies the deltas to your storefront, flags any short-shipment, and closes the PO with the supplier’s invoice attached. Stock in PrestaShop reflects reality within the hour — no double entry, no end-of-week reconciliation.

  • Discrepancies surface immediately. Short by 12? The agent flags it, opens a reply draft, and adjusts the supplier’s reliability score for next time.
  • Stock writes are the only push by default. Everything else is read-only until you turn it on.
  • FX is honest. A GBP invoice stays GBP in the audit trail; rollups convert at the day’s ECB rate, with the rate stamped on the page.
04
Flow 04 · Supplier replies

When the supplier emails back, the inbox is already on it.

Inbound mail is parsed into structured fields — confirmed lines, ETAs, price changes, MOQ updates. You see a clean summary, not a wall of forwarded text, and you accept, counter, or reject in a click. The reply goes out under your name; the audit row goes into the run log.

  • Price-change replies are gated. The agent never accepts a price increase on its own — that’s an explicit human decision.
  • ETAs feed the next forecast. If a supplier slips by two weeks, the next run knows.
  • The original email is preserved. Every parsed task links back to the raw message, headers and all.
05
Flow 05 · First run

Eight minutes from sign-up to your first agent draft.

You connect a store, import a supplier (manual or CSV), set the per-PO cap you’re comfortable with, and trigger the first agent run. By minute eight, you have a real draft to look at — built from the last 90 days of your sales, not a demo dataset.

  • No fields to fill in for ninety minutes. The agent gets what it needs from the storefront and the supplier list, and asks for the rest only when it has to.
  • Auto-send stays off until you flip it. The first runs are draft-only. You watch the agent work for a week before handing it the keys.
  • Onboarding is reversible. Disconnect the store, the agent stops drafting. No vendor lock, no exit fee.
Section 02 · Feature deep-dives

What you'll lean on, when you're in the work.

The workflow above is the loop. These five are the muscles inside it — the parts you'll come back to once Stokis is running. Each one is an explicit design choice we'd defend.

Confidence labels

Strong · Moderate · Low data — labelled on every line.

A SKU with twelve months of sales doesn't deserve the same trust as one with twelve days. Every draft line carries a confidence chip so you know which numbers to wave through and which to eyeball before approving.

  • Strong: 90+ days of clean sales, low variance, stable lead time.
  • Moderate: enough signal to draft, but the quantity has wider error bars.
  • Low data: the agent drafts a placeholder and asks you to confirm.
Per-line reasoning

Plain language. Every line. No black box.

Each draft line shows the math: days of cover, lead time, sales velocity, the signal that moved it. You can read the agent's logic in one sentence — and if you disagree, edit inline and the totals recompute before send.

SKU-7733 · Filter pads · 144 units
Stock covers 6 days. Lead time 14. Sales steady at ~24/day for 30 days, +18% week-over-week. Drafted 144 to buffer the spike — confidence Strong.
Auto-send caps

A €-value boundary, not a slider.

You set a per-PO cap (we suggest €1,000 in week one). Under the cap, the agent can send autonomously. Over it, the PO drafts and waits in your inbox with full reasoning. The cap is the only thing that lets a PO leave the building without you — and it never raises itself.

  • Suggested defaults shown during onboarding — conservative on purpose.
  • New supplier emails are always gated, regardless of cap.
  • Price-increase replies are always gated, regardless of cap.
Supplier reply parsing

Inbound mail → structured fields, the same hour.

When a supplier confirms, slips an ETA, or bumps a price, the inbox parses the email into clean fields — confirmed lines, new ETA, price deltas, MOQ changes. You see the summary, accept/counter/reject in a click, and the original message stays linked for the audit trail.

Helsinki Supply OY · Re: PO-2026-0182
14 of 14 lines confirmed · ETA -7d · price +4.2% on SKU-7733 (gated for your approval).
Shadow mode (the default)

Draft-only until you've watched it work for a week.

Auto-send stays off on every fresh workspace. The first runs build the trust paper trail: the agent drafts, you review, you send. Once you've watched a few cycles close cleanly, you flip auto-send on for the suppliers and €-bands you trust — supplier by supplier, not all-or-nothing.

  • First-week default: 100% drafts, 0% auto-sends. Reversible any time.
  • Auto-send turns on per workspace, gated by your cap.
  • Every send carries the approver name, timestamp, and the policy version active at the time.
Where the agent stops

The autonomy boundary, in plain text.

The agent’s authority isn’t a slider — it’s a fixed boundary, by design. You pick the autonomy mode for the workspace; the table below is exactly what the agent will and won’t do at each one. Nothing is hidden behind a setting.

ActionSuggest modeAuto-send modeAuto-send + replies
Pull stock, sales and supplier historyYesYesYes
Forecast demand per SKUYesYesYes
Draft a purchase orderYesYesYes
Send a PO under your auto-send capOff by defaultYesYes
Send a PO over your auto-send capNeverAsks firstAsks first
Send to a brand-new supplier emailNeverNeverNever
Accept a supplier price increaseNeverAsks firstAsks first
Block or unblock a supplierNeverNeverNever
Change your auto-send cap or policyNeverNeverNever
Cancel a sent PONeverNeverNever
Trust principle

Every action is reversible, or the irreversible threshold is visible before it happens. Every decision shows its reasoning and the signals it relied on. We don’t ship features that hide what the agent did.

What changes

What this swaps out, in concrete terms.

Operators come to Stokis from spreadsheets and ERP exports. These are the differences we hear about most often in the first month — pulled from design-partner feedback, not marketing surveys.

1 day → 10 min
A full working day on one supplier order becomes ten minutes of reviewing what the agent drafted.
5 suppliers
Typical Stokis customer. The pain is proportional to count — five becomes ten, ten becomes twenty without a new spreadsheet.
90 days
Sales history imported at sign-up so the first draft isn’t built on a demo dataset. Rolling thereafter.
5× ROI
On Growth before the AI insights kick in. Anchored on €20/hr operator time across five repeat suppliers.
Section 03 · Edge cases

The trust questions, answered up front.

These are the four objections operators raise in the first call. Quick answers here; longer answers in the FAQ below.

My store has bad or incomplete data.

The agent flags low-confidence lines instead of guessing. SKUs with thin sales history get a 'Low data' chip and a placeholder quantity — you confirm rather than rubber-stamp. Stockouts in history are detected and excluded from velocity math so they don't depress the forecast.

What if the agent makes a mistake?

Every line is reviewable before send. Auto-send only fires under your cap, on suppliers you've used before, with the reasoning preserved on every PO. After send, you handle it the way you do today — a quick email back inside the supplier's amendment window. The full audit log retains every approval, every signal, every policy version.

Multi-currency stores?

Native — not a paid upgrade. A GBP supplier stays GBP all the way through the PO, the email, the invoice, and the audit row. Workspace KPIs convert at the latest ECB rate with the rate stamped on the page. We never destructively convert.

Where does my data live?

EU. PostgreSQL in Frankfurt. The agent's reasoning runs at Anthropic in their EU region. PrestaShop access is read-only by default — opt-in writes (stock pushes, PO sends) are explicit. DPA available on request before you sign anything.

Common questions

The objections we hear, about the agent.

Three things: a connected PrestaShop store, a list of suppliers with email, lead time and currency, and a per-PO auto-send cap. Everything else — days of stock, reorder quantities, plain-language reasoning per line — the agent computes from your last ninety days of sales. You can override any of it.
The agent flags rather than guesses. SKUs with thin history get a 'Low data' confidence chip and a placeholder quantity for you to confirm. Stockouts in your sales history are detected and excluded from velocity math so they don't depress the forecast. Bad supplier records (missing lead time, missing email) block sends on that supplier with an explicit error — never a silent default.
Drafts are reversible. If you spot an over-order at 09:00, you cancel it before the supplier ships — most invoices have a 24-hour amendment window. Even after send, you handle it the same way you would today: a quick email back. Every recommendation labels its confidence (strong / moderate / low data) before you approve, so the wrong quantities flag themselves.
No. New supplier emails are gated — the agent will draft, but never send to an address it hasn’t seen before. You confirm the destination once on first send, and after that it’s automatic inside your cap.
It’s the maximum euro value of any single PO the agent can send without your approval. Default is conservative (we suggest €1,000 in week one). Above the cap, the agent drafts and waits in your inbox. You raise the cap when you trust the drafts. We never raise it on our own.
Yes — that’s the default, not an upgrade. A GBP supplier stays GBP all the way through. Workspace KPIs convert at the latest ECB rate, with a 'rates as of …' stamp on the page so nothing’s silently massaged. We never destructively convert.
EU. PostgreSQL in Frankfurt. Anthropic Claude runs the agent’s reasoning in their EU region. Your supplier list and order history never leave the EU. DPA available on request before you sign anything.
Self-serve export of every table you’ve used: products, suppliers, POs, audit log. CSV or JSON. The agent stops drafting the moment you disconnect the store. No exit fee, no manual offboarding queue.
Stokis vs. the spreadsheet

The same work, without the workday.

Every row on the left is something most B2B operators still do by hand every week. Stokis isn’t a new place to do the work — it’s the work, already done, waiting for your review.

The spreadsheet wayWith Stokis
Pull stock data manually every weekAgent scans every 60 minutes
Calculate reorder quantities by handComputed from 90-day sales velocity
Write PO emails one by oneDrafted and sent automatically
Chase suppliers for confirmationReply parsing + auto-confirmation log
Forget about lead timesLead time per supplier, baked into every draft
4–6 hours per order cycle10-minute review
Try the agent

Watch the agent work for a full reorder cycle.

No card. Full Growth features for 30 days. Auto-send stays off until you turn it on — the first runs are draft-only so you can read the agent’s reasoning before trusting it with a send.