How it works
How Stocktimal works
[CONTENT SLOT: P0 hero — one plain sentence of positioning plus the boundary, 60-90 words. No jargon (D5). Rests on C1/C2.]
Not an ERP. Not S&OP.
You already know roughly what you'll sell. The open question is what to order this week, in what quantity, from which supplier — and that question usually gets answered in a spreadsheet, under time pressure, by whoever is around. Stocktimal answers it explicitly: it takes your forecast, your lead times, your current stock and your outstanding orders, and comes back with a proposed order per SKU. It is not an ERP and not an S&OP suite. Your ERP keeps holding the stock and the orders and the bookkeeping; Stocktimal reads what you export from it and hands back a plan you can argue with.
[CONTENT SLOT: P1 — expand the boundary statement to 80-120 words. Ceiling: C2 only.]
Part one — the forecast
[CONTENT SLOT: P2 — the plain version in plan §7.3: most tools forecast a number, we also work out how wrong that number is likely to be. Safety stock sized to how uncertain demand actually is, not to a rule of thumb. 300-450 words. No sentence concedes that ordering algorithms converge (D3). No accuracy numbers (N1).]
How the forecast is built
[CONTENT SLOT: P2b — the model portfolio and error-distribution fitting, one level down, for the reader who asks (D5). 150-250 words. Permitted claims are the five bullets in plan §7.3 verbatim in substance. No accuracy number, no claim that the portfolio is exhaustive, no claim that a specific model is used for the reader's data.]
Part two — the order
[CONTENT SLOT: P3 — per-SKU quantity and timing, fill-rate target, lead-time distribution, MOQ, case-pack rounding, minimum order value. 250-350 words. Stocktimal INGESTS AND REPORTS ON holding cost and order cost — never "decides using" (N15). Rests on C1/C3/C7.]
Why the two halves are one argument
[CONTENT SLOT: P4 — a tighter error distribution produces smaller orders at the same service level. 120-180 words. NO NUMBERS (N1). Diagram D1 belongs here and is built separately under WI-10.]
Review, edit, export
[CONTENT SLOT: P5 — the operator stays in control: propose, review, adjust inline per SKU, approve or reject, export CSV. 150-200 words. Rests on C6. Human review is by design (C15) — never claim automated ordering (N10).]
Does this work with my ERP?
Yes — because nothing has to be connected. You export current stock, outstanding orders and your forecast; Stocktimal returns proposed orders that you bring back into your ERP when you're satisfied with them. There is no integration project standing between you and the first useful output, and nothing reaches your system of record without a person deciding it should.
[CONTENT SLOT: P5b — the body above is the plan's permitted formulation and is a CEILING. Shorten or restyle; never strengthen. Must not name any ERP, claim a connector, API or webhook, or promise a future one (N11).]
Ask why
[CONTENT SLOT: P6 — the chat assistant answering investigation questions from the tenant's own data, framed as grounded investigation, not "we have AI chat" (D10). 150-220 words. ALL THREE qualifiers must appear together inside the pitch, not as a footnote (D11/C8): read-only by construction, paid-tier, per-environment opt-in. No screenshot at launch.]
Defensible by design
[CONTENT SLOT: P7 — every run pins the mapping version, parameter set and override set, and is DESIGNED TO BE replayable from a frozen snapshot; the explanation names a constraint only when it moved the quantity. 150-200 words. Hedged register is mandatory (C4/C5). Never "proven", "validated" or "audit-ready" (N2).]
Where does my data live, and what is your security posture?
Your data sits on Microsoft Azure in the EU (West Europe). Each customer gets its own tenant, and every record is stamped with the tenant it belongs to, so one customer's catalogue cannot be read from another's account — that separation is enforced in the database itself, not just hidden in the interface. We sign a Data Processing Agreement.
We do not hold a security certification today, and we will not imply one. Plenty of vendors our size lean on a logo here and hope you don't check the scope; we would rather you hear it from us first. What we can tell you is how the system is actually built: secrets live in a managed key store rather than in configuration, access is scoped per role, and the tenant separation described above is enforced on every record. If that is not enough for your procurement process yet, we would rather know that now than after you've signed.
[CONTENT SLOT: P7b — the two paragraphs above are the plan's permitted formulations and are a CEILING. Must not claim data never leaves the EU, state backup locations, retention periods or encryption specifics, imply the DPA is legally reviewed, or name any certification, uptime SLA or the word "compliant" (N12). The "we will answer a security questionnaire in writing" clause is CUT pending O-13.]
Who this is and isn't for
[CONTENT SLOT: P8 — short recap, 60-100 words, LINKING to the fit/anti-fit section on the landing page rather than duplicating it.]
Stocktimal is onboarding partner customers.
[CONTENT SLOT: P9 — 40 words leading into the single primary CTA.]