The data is already correct in a system you have. It is just not in this one.
The rules and your dashboard are always included. Automation is the part that loads the data for you and tells you when something changes. Products and volumes come across; volumes only ever as aggregate quantities by market and month. Customers, payment details and order contents are never read.
One allowance covers the AI work. AI generations pay for both AI-mapped imports and design generations, and AI packs top it up.
Every market · every regime · cited absences
What it actually does
Mechanism, in the order it happens.
- Connect a storefront with read-only OAuth
Shopify and Squarespace connect with OAuth you approve from inside Oblifee, and sync every night by shipping country. Each sync covers roughly the last year of shipped orders and uses replace semantics, so a re-run lands in the same place rather than doubling up.
- Push from any ERP over the REST API
A REST ingestion API lets an ERP or any custom system push products, packaging and volumes straight in, on its own schedule, authenticated with a scoped bearer token you generate per workspace and label per platform. Revoking is instant and audit-logged, and a replace rotates the token without losing the label.
- Take a spreadsheet in the shape it is already in
Upload a CSV in your own layout and Oblifee proposes a mapping from your columns to its fields, after the file has passed scanning so its contents are never read early. You review the mapping and confirm it before a single row loads. A file that cannot be proven clean is blocked, not imported.
- Let your own assistant read the workspace
Obli Connect gives Claude, ChatGPT or a Copilot Studio agent read-only access over the Model Context Protocol: seven read tools, no tool that adds, edits or deletes, one workspace per token, and every call recording the tool, a fingerprint of its arguments, the response size and the outcome.
- Tell you when a rule moves
Set the markets and programmes your workspace is told about, and the same alerts arrive in Slack, Microsoft Teams or a shared mailbox alongside the bell and email. Every alert names the market, the programme, the date and, where the brain holds one, the source it cites, and any figure carries its status.
Before you run one. AI-mapped imports and Obli Connect are the Oblifee AI add-on. Shopify, Squarespace and the REST API are the Connectors add-on. Drop Connectors and the access tokens are revoked so syncing stops; your data stays.
What you see
A nightly sync you can forget about
Shopify and Squarespace, by shipping country, about a year of orders at a time, with replace semantics so a re-run never doubles up.
A mapping you confirmed
Shown before the load, not after it, and only the compliance fields are read: anything else in your sheet, names and emails included, is dropped at the boundary and never stored.
A token you can watch and revoke
Each shows its state, its expiry and its calls this month, and Revoke stops it at once.
Channels that cannot drift
The bell, email and every channel receive the same events in the same daily sweep, so a channel can never say something the feed does not. A webhook URL is stored encrypted, shown to nobody after you paste it, and only its host appears on the page and in the audit log.
Reading the brain from your own systems is a different product: the Brain API serves duties, rates, labelling, claim rules and the change log, read only, every row with its status and citations, and it never touches your workspace data. It is on the price list.
What it costs
From +£25 a month for Oblifee AI; Connectors +£49 a month. Prices are in GBP and exclude VAT, and annual billing is charged as ten months for twelve.
During the public beta every module is switched on for every workspace, whatever add-ons you hold. This is the price that applies once the beta ends.
The regulatory brain is reference data shared by every workspace: what you see in it is what every other customer sees, with the same citations and the same confidence labels. A module decides which regimes the platform answers for, never how sure it is allowed to be.
What it does not do
It does not send your customers anywhere. Only the whitelisted compliance fields are read; names, emails and order references are dropped at the boundary and never stored.
It does not let an assistant write. There is no tool that adds, edits or deletes anything. What a tool returns does go to the assistant you connected, and so to its provider, so read their data terms before you connect.
It does not silently overwrite an upload. Where a new import overlaps an old one, Oblifee flags the overlap and offers a cleanup, confirmed in two clicks and audit-logged.