AI
Most questions are not reports.
They are one number.
Where is my order. How many do I have in Union. Did that Walmart PO ship. Nobody wants a dashboard for those, they want the answer and then they want to get on with the day. OMNI is built so the small questions never become tickets, and the big ones become reports you keep.
The fastest answer is the one nobody had to ask for
Right click any value in any grid. OMNI builds the comparison from the cell you clicked, so most of what people would have asked someone else becomes two clicks. This is live today, on every grid in the product.
Where is my order?
Right click the SO number, filter to it, open the line. Channel, ship by date, shipments and status are already on the row.
How many do I have in Union?
Scan the zone, or filter the inventory grid to the location. On hand and available to sell come back together, with the count source named.
Which Target lines are late?
Filter Sales Channel to Target, then Ship By to before today. Two clicks, no query, no ticket.
The live context menu. Six comparisons generated from whatever value you clicked.
When it is a real question, describe it
Some questions genuinely need a report. Describe what you want in plain language and OMNI proposes one built against your own fields, not a template someone else shipped.
What do you need to see?
Proposed report, using your fields
Filter: Sales Channel is Target, Ship By is before today, Status is not Shipped. Group by Brand. Sum Qty and Line Total.
| Brand | Late lines | Units | Line Total |
|---|---|---|---|
| Harbor Goods | 28 | 2,016 | 12,075.84 |
| Cedarline | 11 | 396 | 5,049.00 |
| Northline | 3 | 72 | 1,332.00 |
| 3 brands | 42 | 2,484 | 18,456.84 |
Every field named in that report is a real column on your order line. Brand, Sales Channel, Ship By, Status, Qty, Line Total and EDI already exist, which is why the answer can be trusted.
An answer is only as good as the catalog under it
This is the unglamorous part and it is the part that decides whether any of this works. A question about a SKU can only be answered if that SKU means the same thing in every system that touches it.
One identifier, everywhere
UPC and SKU have to agree across your WMS, your channels and your client’s records. Aggregator parses and cleans incoming feeds so the same item is one item.
Fields that are actually filled
Weights, dimensions and brand assignments are what let a report group correctly. Missing fields do not produce wrong answers so much as confident ones.
Then the questions work
Ask anything you like of a clean catalog. Ask the same question of four systems that disagree and you get four answers, none of them useful.
And when it is not enough, a person picks it up
We would rather tell you where the line is than let you find it during a busy week.
Today
Our team builds reports with you, against your configuration, during onboarding and whenever your operation changes. That is a service, and we are not going to dress it up as something else.
Where it is going
More of that work moves into the product, starting narrow, with a route back to our team whenever the answer needs a human. The escalation path stays either way.
Your data stays yours
Your order history, your client list and your rate cards are the most commercially sensitive things you own. They are yours, you can export them whenever you like, and nothing about how OMNI answers a question requires you to give that up.