All your commerce in one place. Point your own AI at it.
FACK brings every channel, system and warehouse you already run together into one clear picture. Then you bring the AI you already use — and let it work on real data instead of guesswork. You decide faster, and you know exactly why.
Everything you run
Webshops Marketplaces ERP & PIM Warehouses & 3PL Carriers & financeYour AI, your choice
One model · one API · every event
What you get back
One picture of the operation Answers, with the reason The manual work, automated Decisions you can defendConnect what you already run — twenty today, and a framework for the twenty-first
How it works
From scattered systems to decisions you can defend.
Five steps. No migration, no rip-out, and nothing you have to replace.
Connect what you already run.
Your webshop, your marketplaces, your ERP, your warehouse, your carriers. FACK plugs into them and leaves every one of them exactly where it is. Nothing gets migrated, nothing gets switched off.
Shopify · Amazon · SAP
Dynamics · Mirakl · and more
Everything becomes one shape.
An order from Amazon and an order from your own shop stop being two different things. Same for stock, suppliers, shipments and returns. One model over all of it — so a number finally means the same thing in every conversation.
order · order line · stock
shipment · return · supplier
Every change becomes an event.
The moment something moves — or gets stuck — FACK knows. Not in a report tomorrow morning, but the second it happens. That is the difference between looking back and being able to act.
order.allocated
exception.opened
Your own AI reads it.
Point the assistant you already use at one clean, current model instead of six systems that disagree with each other. Ask in plain language what is costing you time or money, and get an answer that comes from your real data — with the reasoning attached.
And then it acts.
Rules handle the obvious. AI handles the judgement calls. Your people only see what genuinely needs a person. You decide how far it is allowed to go, per process — and you can always move that line back.
observe → recommend
→ approve → execute
What makes it different
Three things, and nobody does all three at once.
It understands, it doesn’t just move.
Integration platforms shuttle data between systems and understand none of it. FACK carries fifteen years of commerce modelling — orders, allocation, warehouses, suppliers, VAT, returns. It knows what an order is, which is why it can tell you when one is wrong.
It replaces nothing.
Your ERP stays. Your warehouse system stays. Your shop stays. FACK sits over them, not instead of them. No migration, no eighteen-month programme, no steering committee. If it does not pay for itself in year one, we have not done our job.
The AI is yours, not ours.
Most platforms bolt on their own assistant and lock you into it. FACK gives you an open model and an open event stream instead. Bring ChatGPT, Claude, Copilot or something you built yourself — and swap it whenever you want.
Your AI, your choice
An AI cannot run an operation it cannot see.
Your operation lives in six systems that disagree with each other. That is why most AI pilots in commerce quietly stop — the model was never the problem, the data was. FACK’s job is to give whatever assistant you already use one clean, current picture to work on, plus a defined set of actions it is allowed to take.
01
ObserveIt watches, nothing more02
RecommendIt suggests, you read03
ApproveIt proposes, you sign off04
ExecuteIt acts within limits05
AutonomousWhen you trust itYou set the line per process. And you can always move it back.
What it means in practice
The part of your operation nobody has ever counted.
Somewhere between your webshop and your warehouse, people are doing what software should. Orders that get stuck. Addresses that get retyped. Shipments that never get invoiced. It never appears in a report, because no system owns it — and what nobody counts, nobody fixes.
FACK makes it visible as a number first. Then it takes the work away.
[SAMPLE FIGURES — replace with a real anonymised operation before launch]
Want that number for your own operation? We measure it in four weeks, for a fixed fee, and you keep the result either way.
For developers
One model. One API. Every event.
FACK is API-first, not API-also. The same object model the interface runs on is the one you build on — no hidden endpoints, no nightly export, no CSV in between. Six primitives cover the operation; everything else is composed out of them.
orders.capture()An order from any channel, in one shapeinventory.available()Real availability across every locationinventory.allocate()Reserve and assign — or say why it can’tshipments.create()Any carrier, one call, label includedreturns.authorize()A return, with its stock and money consequencesexceptions.list()Everything stuck right now, and what it costs# capture an order and allocate it POST /v1/orders { "channel": "amazon-de", "rows": [{ "sku": "AX-2201", "qty": 3 }] } 201 order_8f21c POST /v1/orders/order_8f21c/allocate 200 allocated 3/3 · warehouse_nl_venlo
// npm i @fack/sdk import { Fack } from "@fack/sdk"; const fack = new Fack(process.env.FACK_KEY); const order = await fack.orders.capture({ channel: "amazon-de", rows: [{ sku: "AX-2201", qty: 3 }] }); await fack.inventory.allocate(order.id);
# pip install fack from fack import Fack fack = Fack(os.environ["FACK_KEY"]) order = fack.orders.capture( channel="amazon-de", rows=[{"sku": "AX-2201", "qty": 3}], ) fack.inventory.allocate(order.id)
# the event that comes back when it sticks { "event": "exception.opened", "type": "paid_no_stock", "order": "order_8f21c", "cause": "supplier_backorder", "cost": { "amount": 14.60, "cur": "EUR" } }
The name
Why FACK?
Everything behind your storefront — orders, stock, shipments, returns, invoices — is what the industry calls the back office. It is where the actual work happens. It is also the part nobody ever bothered to make good.
So we took the back office and gave it an F. That is the whole story, and we are keeping it.
Same operation. Completely different day.
It doubles as Forward Acknowledgment — the networking term for confirming what actually got through instead of assuming it did. Which is exactly what we do. But the F came first.
One letter of difference. Everything else, different too.
Ready to see your operation in one piece?
Join the waitlist and you will be among the first to get a sandbox, the docs and an invitation to the first scans.