.png)
Role based home screens, color flagged list screens, management charts and BI pivots on orders, invoices, work in progress and stock, with standing dashboards in Power BI, Live Excel and the AI assistants on the same live data.
Dashboards in AIMS360 are not one screen, they are layers. A home screen built for your job. Color flags that make overdue orders impossible to miss. Pivot reports on orders, invoices, work in progress and stock. And the same live data behind a standing Power BI or Excel dashboard, or an AI assistant you just ask. All of it reads one set of numbers, at style, color and size.
Five layers, each for a different question. Home screen dashboards put the modules a role uses one click away. Color flags turn any list into a status board. Management dashboards show company data as charts. The built in BI modules build pivot reports on orders, invoices, work in progress and stock. And for the standing executive view, the same data feeds Microsoft Power BI, Live Excel and the AI assistants.
The reason it is layered rather than one big screen: a customer service rep, a production manager and an owner do not want the same dashboard, and the owner does not want to open the ERP to see it. So the ERP gives each user their own working view, and hands the standing chart to whichever tool the reader already lives in.
AIMS360 ships with preset home screens. Each user picks a favorite, and can reorder or hide the left side navigation so the modules they use every day come first.
Where new and important features land first. It is the fullest view, and for that reason the busiest, which is why the others exist.
For anyone doing a small set of things all day: order entry, picking, invoicing. The modules for that, and not much else.
Adds materials and the work in progress modules for cut tickets, production purchase orders and garment dye to the basics.
For whoever handles EDI every day: the inbound and outbound tools you touch most, up front, so the morning's documents are one click away.
On the main list screens, rows change color by rules you set, so the orders that need attention are the ones lit up, whatever the sort order. It takes five minutes to set up and it is the thing customer service teams say they would miss most.
| Detail | How it works |
|---|---|
| Where | The primary module list screens: customer orders, invoices, pick tickets and the other main lists. |
| Set up | Setup, system settings, grid color settings. Each area of the system has its own rules, so orders and invoices can flag differently. |
| The rules | Date bands. A common setup on orders: due to ship inside seven days red, eight to twenty one days yellow, beyond that green. Invoices flag on days past due the same way. |
| Checking a row | A flag details button at the bottom of any flagged list shows the date ranges in force, so nobody has to guess why a row is yellow. |
| No colorBy design | All, canceled and completed orders show no flags. They are not outstanding, so there is nothing to prioritize. |
Flags sit on top of everything the grids already do: filter builders, saved views by role, style, color and size switching, pivots and exports. That is all on grids and the report editor.
Four modules under reports: Order BI, Invoice BI, WIP BI and Stock BI. The three operational ones carry allocation columns.
By customer, class, season, style, rep or division. Includes allocated stock, allocated WIP and allocated totals, so open orders show what is already covered.
Work in progress with allocated quantity and available to allocate, so production can see what is promised before it is finished.
Stock with allocated stock and available to stock quantities. The dashboard number is what is left to sell, not what is on the shelf.
Each BI module is a pivot builder. Pick the level, run the query, drag fields into rows, columns and values, collapse to a summary or expand one row, filter on any field, switch a value to percent of grand total, and save the layout as a view, for yourself or for everyone. The example every brand builds first is booked and shipped by customer class: how much of the business is boutiques, how much is department stores, and is the mix moving.
The BI export is formatted data for a chart in Excel, not a live link; the live routes are below. More on the modules on the built in BI tool page.
For a chart that refreshes on its own and lives on a wall screen or in the Monday deck, AIMS360 hands the data to the tool rather than trying to be the tool. Three doors, one set of numbers.
Power BI's SQL Server connector against the read only database login, or its web connector against the AIMS360 API. Built once, refreshes on its own. No native connector or template pack; the first build is yours or a partner's.
A workbook connected to your AIMS360 data, so the management sheet refreshes instead of being rebuilt. The people who read it already live in Excel.
Claude, ChatGPT or Grok connected to AIMS360, answering in plain English over live data and handing back a table, a chart or an export. Read only, provisioned by AIMS360.
Any list view can refresh a CSV or JSON file at a link on a daily, weekly or monthly cycle, which is how a dashboard tool that is not Power BI gets fed.
Each door has its own page: Microsoft Power BI, Live Excel and the AI assistants. Pick by who reads the dashboard, not by which is most powerful.
| KPI | Where it comes from |
|---|---|
| Booked versus shipped | Order BI, by customer, class, season, style or rep, with a percent of grand total option so you can see what share of the business each class or account is. This is where a fill rate comes from: shipped against booked, for the window you filter. |
| Overdue and about to ship | Color flags on the orders list. Orders inside the ship window you set turn one color, orders past it another, whatever the sort order. |
| Open to sell | The open to sell views and reports, by style, color and size, by delivery date, with or without work in progress. |
| Work in progress by stage | WIP BI, with allocated quantity and available to allocate, plus the cut ticket, production PO and garment dye lists the production home screen puts one click away. |
| Stock and what is already spoken for | Stock BI with allocated stock and available to stock quantities, so the number on the dashboard is what can still be sold, not what is on the shelf. |
| Receivables and credit exposure | The accounts receivable views and the credit limit view on each customer record, which shows open invoices plus approved orders against the limit. |
| Sell-through and margin by style | Style analysis and sales reports, or the same data in Power BI or Live Excel when you want it as a standing chart. |
Every one of those is the same number whether you read it on a list, in BI, in Power BI or from an AI assistant, because there is one database underneath. The open to sell and style reporting behind several of them is covered on the reporting hub.
Each user sets their favorite. Reorder the left navigation so the daily modules come first and hide the sections they never touch.
Setup, system settings, grid color settings. Decide what red means on orders and on invoices, save, and the lists light up from the next refresh.
Build booked versus shipped by class in the order BI, save it as a public view, and do the same for the stock and WIP questions you get asked weekly.
Connect Power BI or Live Excel to the data, build the page once, and let it refresh. Feed anything else from a scheduled view export.
For the questions nobody thought to chart, connect Claude, ChatGPT or Grok and ask. The answer comes from the same live data as everything above.
The scheduler refreshes a CSV or JSON file at a URL. Nothing is emailed by the system; you share the link. And the link runs under the permissions of whoever scheduled it, so a financial view shared with the wrong person shows financial data. A one off email of a grid export from the desktop export dialog is a separate thing and does work.
Power BI connects through its standard SQL Server or web connector, not through an AIMS360 app in the marketplace, and there is no template pack. The first dashboard is a build, then it maintains itself.
Exporting from a BI module gives you formatted data to chart in Excel. It is not a live connection that refreshes; Live Excel and Power BI are.
New features land on the default screen, and icons move between releases as the product develops. If a team wants a screen that does not shift under them, put them on the role based screens instead.
Several layers, and they do different jobs. Home screen dashboards put the modules a role uses one click away, and there are versions for general use, customer service, production and EDI. Color flags turn any list screen into a status board, so overdue orders or unpaid invoices stand out in red. Management dashboards show company data as charts and graphs. The built in BI modules build pivot style reports on orders, invoices, work in progress and stock. And for a standing executive dashboard, the same data feeds Microsoft Power BI, Live Excel and the AI assistants.
Yes, with a caveat worth knowing. Inside AIMS360 the lists, color flags and BI pivots read live data every time you open them, so an open orders list flagged by ship date is a real time dashboard by any practical definition. A standing chart that refreshes on a wall screen is a Power BI or Live Excel job, both of which connect to your AIMS360 data directly. Neither needs a separate analytics product, but the Power BI route does need Power BI.
The order BI holds booked and shipped amounts and quantities by any dimension you drag in: customer, class, season, style, rep, division. Fill rate is shipped against booked for the window you filter, and order value is the booked column. Brands that want it as a standing chart build that view once in Power BI or Live Excel from the same data.
Preset home screens, one per way of working. The default carries the newest and most used features, and gets busy. Basic flow suits customer service and anyone who mostly enters orders, picks or invoices. Production flow adds materials and the work in progress modules for cuts, production purchase orders and garment dye. The EDI screen puts the EDI tools you touch every day up front. Every user picks their own.
Yes. A user sets a favorite home screen for themselves at any time, and can reorder or hide the sections in the left side navigation so the modules they use every day come first. A customer service rep and a production manager on the same system open to different screens.
Colors on the rows of the main list screens, set by date rules you define per module under system settings. The usual setup on customer orders is something like: due to ship inside a week turns red, one to three weeks yellow, beyond that green. Then whatever the sort order, the orders that need attention are the ones that are lit up. Invoices past due, pick tickets waiting and other lists work the same way.
Because they are not outstanding. If you are viewing all orders, or canceled or completed ones, the flags stay blank since there is nothing to prioritize. On any flagged list there is a flag details button that shows the date ranges currently in force, so you can check why a row is the color it is.
The BI modules, under reports, are pivot style report builders on orders, invoices, work in progress and stock. You choose the level, run the query, drag fields into rows, columns and values, collapse to a summary or expand a single row, filter, switch a value to percent of grand total, and save the layout as a view for yourself or for everyone. It is the fastest way to answer a question like how much of our business is boutiques versus department stores. A dashboard is what you build when you want that answer on screen every morning without asking.
Yes, through the standard routes: Power BI's SQL Server connector against the read only database login, or its web connector against the AIMS360 API. There is no native AIMS360 connector in the Power BI marketplace and no template pack, so the first dashboard is built by you or a partner, then it refreshes on its own. Details are on the Power BI page.
Live Excel connects a workbook to your AIMS360 data, so a finance file or a sell-through sheet refreshes instead of being rebuilt. Many brands keep their management dashboard in Excel for exactly that reason: the people who read it already live there.
Yes. The AIMS360 connectors for Claude, ChatGPT and Grok answer questions over live data in plain English and hand back a table, a chart or an Excel export. They are read only and provisioned by AIMS360. It is the right tool for the question you just thought of; a dashboard is for the question you ask every day.
Not as an email. The scheduler on list views refreshes a file at a link on a daily, weekly or monthly cycle, and you share the link. Two things to know: the file is not emailed by the system, and the link runs under the permissions of whoever scheduled it, so do not share a financial view with someone who should not see financial data. A one off email of a grid export from the desktop export dialog is separate and does work.
Yes. Every grid can be switched between style, color and size views, the BI modules break down to the level you choose, and the open to sell views run by size and delivery date. That is the difference between an apparel ERP dashboard and a webstore report: the number is at the level a buyer or a warehouse actually acts on.
In views, exports and BI, yes; a field you named on styles or customers can be a column or a pivot dimension. They are not on the standard printed reports. So a dashboard that groups by your own category, buying group or program name is built in BI, Power BI or Live Excel, not from a stock report.
The same permissions as the rest of the system. A user only sees the modules and data their role allows, so a rep's home screen does not expose margin, and a BI view saved as public is still filtered by what each viewer may see. The one exception to watch is the scheduled export link, which carries the scheduler's permissions to whoever holds it.
AIMS360 runs in a browser, so the lists, flags and BI open on a tablet. The rep app is for writing orders, not for management reporting. For a phone friendly executive view, Power BI's own mobile app is the usual route once the dashboard is built there.
Orders from your online store, marketplaces and EDI retailers arrive in AIMS360 through the integrations, and warehouse activity from an integrated 3PL comes back the same way, so a dashboard built on AIMS360 data already covers those channels without a second connection.
The home screen and the color flags are minutes: pick a screen, set the date bands, save. A BI view is an afternoon of dragging fields until it says what you want. A Power BI or Live Excel dashboard is a small project, usually a few days with someone who knows the tool, and then it maintains itself.
The one you answer by hand every week. We will show you where it already lives in AIMS360, which layer answers it fastest, and what it looks like as a chart that refreshes itself.
