/ SOURCES
Every File Sales Runs On
ERP order exports, price lists and invoices, uploaded as files or synced from the database behind them on a schedule you set. norami only ever reads them.
/ solutions / Sales & Commercial
Every customer's orders, price list and invoices, joined. See price per kilo and margin by account — and the order that shipped short — before the next call.


Put customer margin, pricing, deliveries and credit notes on one model of your orders — so sales, finance and logistics quote from the same price per kilo.
Join invoices to cost sheets and ask which customers and products earn their margin, then check the rows behind each figure.
[ IN THEIR WORDS ]
“At Seajoy we compare, pond by pond, what an extra week of growth is worth against what it costs to wait. By hand that’s half a day of work for a single pond, which is why it never got done. Now it runs every week.”
[ YOUR FIRST ANSWER ]
Pick one — the customer whose margin keeps slipping, the price that never matched the list, or the order that shipped short. We'll show how norami connects your orders, price lists and invoices and traces the answer back to its source.
Bring one decision your sales team is working through, from a customer's margin to a price nobody can explain.
We identify the ERP exports, price lists, invoices, or databases that hold the relevant records.
See the answer alongside its source and the exact query, so your team can verify the numbers.
[ THE PLATFORM ]
Three layers, one workspace: your files and databases in, one model in the middle, answers the whole team can check.
/ SOURCES
ERP order exports, price lists and invoices, uploaded as files or synced from the database behind them on a schedule you set. norami only ever reads them.
/ WORKSPACE
Customers, orders, price per kilo and margin mapped once, and a sales assistant that can only query the datasets linked to it.
/ ANSWERS
When next month's export lands, saved questions keep working on the new numbers — each answer with its source rows and the exact query.
[ SECURITY ]
What protects your orders, prices and customers today — each control described on our security page, in plain terms.
Each customer's data is scoped to its own workspace, with Row-Level Security switched on for every table.
norami never writes to your ERP or database. Sessions are read-only, and queries are single SELECT statements with row caps and timeouts.
Each team reaches its own assistant, and an assistant can only query the datasets linked to it — checked on the server for every query.
Sign-ins, access changes, uploads, connections and exports go to an append-only, hash-chained log.
No. norami reads the order exports, price lists and invoices you already have and answers across them. Your ERP stays the system of record, and norami never writes to it.
Yes, when both are in your workspace. Upload them as files or connect the database behind them, then ask across them. Every answer shows the rows it used from each.
Drop it in, or let the connected database sync on its schedule. Saved questions keep working on the new numbers, and a refresh that looks wrong — rows vanishing, columns changing shape — is held for review before it reaches anyone.
Everyone you invite, with a role that matches their job. Assistants are grouped by department, so the sales team reaches the sales assistant and the datasets linked to it.
No. Ask in plain language, typed or by voice. The exact query is there for anyone who wants to check it.
[ Get started ]
Tell us about your data and we'll get in touch to arrange a walkthrough. Prefer to explore on your own? Create your workspace and bring your data in minutes.