Start
Start free. Switch one place at a time.
Start with your exports and 14 days of Observe. Take over one place when the numbers say so.
Send your exports. The mapping is drafted for you; you confirm each field. Nothing is written back.
Five steps
From your exports to one place, each step with its test.
-
Open your account.
Done when your sign-in reaches your work email.
-
Exports in.
Done when you have confirmed every field.
-
Observe, 14 days free.
Done when your Observe report is in, with nothing written back.
Exports in · fields proposed with their confidence · confirmed · a finding · nothing written back
Example week
-
Take over one place.
Done when you have 30 days of kept dates against your baseline.
Hand back whenever you choose.
Store A · Warehouse A · Warehouse B: watched with nothing written back, then one place on KarmanFlow, approved for that place only
Example week
-
Expand.
Done when each place has moved on its own numbers.
What happens at each step, and who is it for?
Who it fits. A brand selling through its own online store, marketplaces and wholesale, shipping from one third-party warehouse and its own warehouse or stores, on a spreadsheet or an outgrown tool. KarmanFlow connects to any system, including legacy.
- Open your account. Send the form at the foot of this page. The team opens it within one working day and emails your sign-in.
- Exports in. Upload your exports, or connect your store read-only. KarmanFlow proposes each field, with its confidence. Rules map the columns first; when you ask, a small model suggests the rest. You confirm every field. KarmanFlow reuses the mapping for matching files and asks you to review changes.
- Observe, 14 days free. Your current system stays the record and keeps authority over its stock. KarmanFlow reads what it already knows and writes nothing back. It checks orders at risk, stranded stock, ageing holds and stuck returns, each with evidence and one suggested action.
- Take over one place. Pick a store or a warehouse. Before the takeover, every open hold is reconciled. A named person approves the takeover, and the approval covers that place only. KarmanFlow holds a separate allocation for that place's new orders, each with a held date and a receipt, and runs its orders, stock, fulfilment and returns under your rules. Your current system keeps authority over every other place. Done when: 30 days of kept dates against your baseline, each unit sold at most once from KarmanFlow's count, a receipt for each yes, and a named person who answers when a Friday breaks. Hand back whenever you choose. Open holds reconcile before control returns, and every step leaves a receipt. Nothing is lost on the way back.
- Expand. The next place takes the same steps, when its own numbers say so. The same mapping and tables, the same rules and the same receipts carry across.
Observe
Your Observe report.
One page on your own data: what your current system does not surface, the evidence behind each finding, and what to do about it.
What the check finds in the first week
Example weekWritten back: 0
Linen Overshirt · Sage · M: 4 short at Warehouse A.
Warehouse A has 0 available; Warehouse B has 8 available and open demand of 0.
Suggested: move 4.
- 14 days freeWatching. Nothing written back.
- 30 daysof kept dates on the one place you take over.
Every week after
Try a new promise on Tuesday. Live by Thursday.
Dan asks
A new promise, in plain words.
Agent K drafts
The rule, one question at a time.
Replay
On past weeks, before anything is live.
A person approves
Never the one who asked.
Live on one place first
One place runs the new rule.
On the record
Each step keeps a receipt.
Connections
What KarmanFlow connects to.
Any system, including legacy.
- Your store platform
- Marketplaces
- Wholesale
- Your warehouses and a third-party warehouse
- Your payment provider
- Carriers
- Suppliers
Connect, test, run, repair.
What comes in and goes out, and how is each connection proven?
| Connection | What comes in | What goes out |
|---|---|---|
| Your store platform | orders, products, customers | stock counts, fulfilment |
| Marketplaces | orders | stock counts |
| Wholesale | orders and allocations | held dates |
| Your warehouses and a third-party warehouse | stock counts, shipments | fulfilment requests |
| Your payment provider | captures, refunds | refund and cancel requests |
| Carriers | quotes, tracking | bookings |
| Suppliers | dates and quantities | purchase orders |
Connect.
Each connection is declared once: what it reads, what it may write, and who approves.
Test.
It is proven on the connector bench before go-live: a signed test event, a refused call, and a mapping you accept.
Run.
It runs with rate limits, retries and an audit trail. You see each connection keeping up.
Repair.
When a provider changes a field or a delivery fails, KarmanFlow shows it and replays it once it is fixed.
A connection KarmanFlow does not have yet is built on the same bench with the connector kit.
Licence
Observe is free for 14 days, and the team can extend it.
Then one licence that grows with orders, places and connections. Never per question, never a seat, never a cut of sales.
Start free
Request your Observe account.
Free for 14 days, on your own exports. Nothing written back.
What does an invitation open?
The working demo
The console, with an example week of orders, stock and decisions.
Time with the team
Bring the date your team struggles to hit.
Architecture notes
How the engine, the rules and the receipts fit together.
Developer docs and the API explorer
Commands, events, webhooks and the schema, with an explorer.
Protocols and integration guides
How agents and systems connect.
Security and trust
How access, approvals and data are handled.
Tutorials
Six of the films, each with the steps to do it yourself in KarmanFlow.
What is next
Where the product goes next, in order.
Or email the team at info@karmanflow.com.