About
Built by people who got tired of the spreadsheet.
CartKit came out of running small commerce brands and discovering that the hard part was never the storefront.
Setting up a store is a solved problem. You can have a checkout, a theme and a payment processor running before lunch. What nobody solved is the part after: the weekly ritual of exporting orders, pasting supplier invoices next to them, working out which variants are actually earning anything, and discovering that one of them stopped paying for itself a month ago.
That work is repetitive, it's numerical, and it has clear rules. Hold this margin. Reorder at this cover. Use this facility for European orders. It is, in other words, exactly the kind of work that shouldn't need a person at eleven at night — but every tool available either ignored it or sold it back as four separate apps with four separate subscriptions.
What we're building
A commerce platform where the operating layer is the point. The storefront, catalog and checkout are table stakes and we intend them to be unremarkable. The part we care about is the layer that watches the numbers continuously, acts inside limits you set, and writes down what it did.
We are deliberately not building a general-purpose automation canvas. Those tools are powerful and almost nobody finishes configuring them. You should be able to describe how you want your store run in five sentences.
Placeholder narrative — replace with the real founding story.
Principles
What we hold to.
These are constraints on the product, not values on a wall. Each one costs us something.
The log is the product
An agent you can't audit is a liability. Every automated action carries its reason, its input and an undo. We would rather ship fewer behaviours than behaviours you can't explain to your accountant.
Cost is a first-class field
Platforms treat cost as an optional attribute for a margin widget. We treat it as part of the order record, snapshotted at sale, because everything useful downstream depends on it being right.
Ask before spending
Anything that moves customer money or raises a budget stops for a human by default. Autonomy is opt-in, per behaviour, with a ceiling.
No percentage of your sales
Taking a cut aligns us with your gross revenue. A flat fee aligns us with whether you keep using the product. We prefer the second.
Your data leaves cleanly
Full export of products, orders, customers and cost history, any time, no support ticket. Lock-in should come from the product being good.
Private beta
We're looking for operators, not testers.
If you run a store and you've built the margin spreadsheet yourself, you're exactly who we want in the beta — you already know where it hurts.