--- title: Supplier dashboard order: 9 updated: 2026-07-12 --- # Supplier dashboard The supplier dashboard is the home screen of the [Supplier Portal](/docs/procurement/supplier-portal). It gives you — the supplier — a single-screen summary of your whole relationship with the buyer's firm: how many enquiries you have received and quoted, the value you have quoted and won as orders, how quickly you respond, what is still awaiting delivery, and which of your contacts and products are most active. Every figure is **company-wide**. The portal scopes the dashboard to your supplier company, *not* to the individual contact person who is signed in — the backend deliberately keys everything off the supplier's ID and ignores which contact you logged in as. So whether it is you or a colleague who opens the portal, the totals, charts, and tables are identical: one complete picture for the whole company. Only the greeting at the top (*Welcome, …*) changes to name whoever is signed in. See [Company-wide view, person-level responses](/docs/procurement/supplier-portal#company-wide-view-person-level-responses) for the wider rule. The dashboard is **read-only** — it shows numbers and links you through to the underlying lists, but nothing on this page changes any data. ## Open the dashboard 1. Open the Supplier Portal from the link in any RFQ email the firm sent you. The link never expires — re-clicking it always logs you back in. See [How suppliers access the portal](/docs/procurement/supplier-portal#how-suppliers-access-the-portal). 2. You land on the dashboard automatically after signing in — unless the link pointed you straight at an open enquiry to quote. 3. From anywhere in the portal, click *Dashboard* (the grid icon at the top of the left sidebar) to return here. The sidebar also has *Enquiries*, *Orders*, and a pinned *Settings* entry (your read-only [Profile](/docs/procurement/supplier-portal#profile)). The dashboard lives at `/supplier/dashboard`; any unrecognised `/supplier/…` address quietly redirects here. If your session has lapsed you are bounced to a *session expired* screen instead — re-open the portal from your original RFQ email link and it drops you straight back on the dashboard. See [Session expiry](/docs/procurement/supplier-portal#session-expiry). ### Where the numbers come from Opening the dashboard (or changing the date range) sends **one** request to the server, which recomputes everything live from your enquiries, purchase orders, stock arrivals, and drafts — there is no cached snapshot, so the figures are always current as of the moment you loaded them. While that request is in flight you see a *Loading dashboard…* spinner the first time, and shimmering placeholders on each card and table on later refreshes. The request carries only the two dates as millisecond timestamps. The server re-validates them (both must be positive whole numbers) and rejects anything malformed, so a tampered or broken range simply returns an error rather than skewing your figures — consistent with the portal verifying every request server-side. ### The sidebar is desktop-width The navigation rail is shown on medium and larger screens; it expands on hover and collapses to a slim icon strip otherwise. On a narrow phone screen the rail is hidden — the dashboard content itself still renders and scrolls normally. The portal is a web experience (there is no desktop-app-only or web-only control on this page), so it behaves the same however your supplier opens the link. ## Header and greeting The top strip shows the buyer firm's logo (only if the firm has uploaded one) and name, and a welcome line: *Welcome, {salutation} {your name} — {your company}*. The salutation and contact name reflect the contact person who is currently signed in; the company name is your supplier company. If the firm has no logo on file — or the logo image fails to load — the logo slot is simply omitted and the firm name stands alone. When the firm's name is unavailable the header falls back to the literal words *Supplier Portal*. ## Date range picker Two date fields — *From* and *To* — sit at the top right. They filter most of the figures on the page. Each field is a typed date input with a calendar popover: click the calendar icon to pick visually (the popover also has a year picker for jumping far back), or type the date directly into the segments. - **Default range** — the current Indian financial year, `1 April → 31 March`. A date in January–March belongs to the financial year that began the previous April (so on any day between January and March 2027 the default window is `1 April 2026 → 31 March 2027`). - **Auto-correcting ends** — if you set *From* to a date later than the current *To*, *To* jumps to match it; likewise, setting *To* earlier than *From* pulls *From* back. You can never end up with an inverted range. - **Whole-day boundaries** — *From* always starts at `00:00:00` of the chosen day and *To* ends at `23:59:59`, so both endpoints are fully included. - **Live refetch** — every change immediately re-requests the data and redraws the cards, pie, and tables that respect the range. - **Period footer** — a small line at the very bottom of the page echoes the active window as `dd/mm/yy → dd/mm/yy`, so you always know exactly what the numbers cover. ### What the date range does and does not affect This is the most common source of confusion, so it is worth stating plainly: - **Respects the range** — every KPI card except *Open Drafts*, the *Enquiry Breakdown* pie, the *Top Contacts by Submissions* table, and the *Top Products* table. - **Ignores the range (always fixed)**: - The *Activity Trend* chart always shows the **last 12 calendar months** (this month back through the same month last year), regardless of the dates you pick. - The *Open Drafts* card counts **all** of your saved drafts, not just drafts from the selected period. - The *Pending Deliveries* table lists **every** open/partially-delivered purchase order, not only POs dated in the range. The *Pending Delivery* value **card**, by contrast, *is* range-scoped — so the card total and the table can legitimately differ. ## How money and numbers are formatted Two different money formats appear on the page, so a figure can look shorter in a card than in a table even when it is the same amount: - **KPI money cards** use a compact form to fit the tile: thousands as `₹1.2 K`, lakhs as `₹1.23 L`, crores as `₹1.23 Cr` (lakhs and crores carry two decimals, thousands one), and an exactly-zero or empty value as `₹0`. - **Table money cells** (the *Value* columns) show the full Indian-grouped amount rounded to whole rupees, e.g. `₹1,23,456` — never abbreviated. - **Counts** use Indian digit grouping (e.g. `1,234`). - **The Activity Trend left axis** uses its own tight abbreviation with no decimals and no space (`₹25K`, `₹2L`, `₹3Cr`) so the unit never wraps onto a second line. Wherever a KPI card carries both an excluding-tax and an including-tax figure, the card shows the excluding-tax value and reveals the other on hover. ## KPI cards Twelve compact cards summarise the period. A card shows `0` (counts), `₹0` (money), or `—` (averages/rates) when there is nothing to report. ### Total Enquiries Every enquiry (vendor invitation) your company received in the selected period, dated by when the invitation was created. Invitations the firm later **cancelled** or **superseded** with a revised RFQ are excluded, so the count reflects only live invitations. Internally this equals *Won + Quoted + Not Submitted*. ### Quoted How many of those enquiries you submitted a quotation for. An enquiry counts as *Quoted* the moment a quotation is submitted against it — whether you uploaded it yourself in the portal or the firm's staff keyed it in on your behalf. (It also folds in the rare *Won* enquiries; because awards are legacy, in practice *Quoted* is simply your submitted count.) ### Quoted Value The total value of the quotations you submitted in the period, shown **excluding tax**. Hover to see the **including-tax** figure (*Incl. tax: ₹…*). The value is computed per priced line as `quantity × rate × (1 − discount%)`, summed across every line; lines you marked *No Bid* are skipped, and the including-tax figure adds each line's own tax rate on top. The quantity comes from the firm's enquiry line item, so the figure reflects what you were actually asked to price rather than any quantity you might have typed. Only enquiries that were actually **submitted** contribute. ### Not Submitted Enquiries you received in the period but never submitted a quotation for — your unanswered backlog for that window. This is the same set the pie's *Failed to Quote* slice counts. ### Avg. Submission Days The average number of days between an enquiry being sent to you and your quotation being submitted, over the enquiries you quoted in the period. Rounded to one decimal and suffixed `d` (e.g. `2.5d`). Shows `—` when you submitted nothing in the range. Only **positive** gaps count, so a quotation whose timestamp is somehow earlier than the enquiry is ignored rather than dragging the average negative. ### Portal Upload Rate The share of your submitted quotations that were **uploaded by you in the portal** versus keyed in **manually by the firm's staff**, as a whole-number percentage. Hover to see the raw split (*X portal · Y manual*). Shows `—` when nothing was submitted. A higher rate means you are self-serving through the portal rather than emailing rates for staff to enter — which is the intent of the portal. See [Fill quotation](/docs/procurement/supplier-portal#fill-quotation). ### Total Orders The number of purchase orders the firm placed with you that are **dated within the period**. Only real, live POs count: a PO must be in status `sent`, `partiallyArrived`, or `arrived`. Draft, cancelled, and deleted POs are never counted. ### Order Value The total value of those in-range purchase orders, shown **excluding tax**, with the **including-tax** figure on hover. It sums every line (`price × qty × (1 − discount%)`) plus any additional charges recorded on the PO (charges are added at their amount, and the including-tax total applies each charge's own tax rate too). ### Pending Delivery The value (**including tax**) of the quantity still owed to the firm across your in-range POs — i.e. ordered quantity minus what has already been received and approved at the firm's warehouse. Note this **card** is range-scoped even though the *Pending Deliveries* **table** below is not. Deliveries are recognised only once the firm's inventory team approves the stock arrival against your PO; see [Add a stock arrival](/docs/inventory/add-stock-arrival). ### Delivered The value (**including tax**) of the quantity that has already been received and approved against your in-range POs. Per line, the delivered quantity is capped at the ordered quantity, so an over-delivery never inflates this figure. ### Avg. Delivery Days The average number of days from a PO's date to its **last** approved delivery, over the in-range POs that are **fully** delivered (status `arrived`). A PO can have several partial deliveries; the last approved one marks completion. Partially-delivered POs are excluded because they are not finished yet. Rounded to one decimal and suffixed `d`; shows `—` when no in-range PO has been fully delivered. ### Open Drafts How many quotation drafts you currently have saved in the portal but not yet submitted. **This card ignores the date range** — it always reflects your live draft count across the whole company. A non-zero number is a reminder to go back and finish those responses; see [Draft behaviour](/docs/procurement/supplier-portal#draft-behaviour). ## Enquiry Breakdown (pie) A donut chart beside the KPI cards splits the enquiries you received in the period into up to three outcomes. A legend on the left lists each slice with its share (`%`, rounded to a whole number) and count; the centre of the donut shows the grand total. Hovering a slice — or its legend row — highlights it and shows the exact count with a one-decimal percentage in the tooltip. Slices with a count of zero are hidden entirely, and if there is nothing in the period the donut reads *No data*. The three categories: - **Won** *(green)* — the enquiry was awarded to you (an award was recorded against your quotation). Awards are a legacy concept in the current flow, so in practice this slice is almost always zero and usually absent. - **Quoted** *(blue)* — you submitted a quotation but it was not (or not yet) awarded. - **Failed to Quote** *(red)* — you received the enquiry but never submitted a quotation for it. This is the same set of enquiries the *Not Submitted* card counts. ## Activity Trend (chart) A dual-axis chart titled *Activity Trend* (subtitle *Orders, enquiries & quote value — last 12 months*) plots the **last 12 calendar months**. It **always** shows 12 months regardless of the date-range picker, so you get a stable historical view alongside the period-specific cards. Months with no activity still appear as empty slots, so the axis never has gaps. It combines stacked bars and lines: - **Stacked bars** *(right axis — counts)* — each month's bar is the enquiries you received that month, split into: - *Quoted* *(dark blue, bottom)* — enquiries you responded to (won or quoted). - *Not Quoted* *(slate grey, top)* — enquiries you did not respond to. - The full bar height is therefore the total enquiries received that month. - **Order Value** *(indigo line — left ₹ axis)* — the value of purchase orders dated that month, including tax and additional charges. - **Quoted Value** *(teal line — left ₹ axis)* — the value you quoted on enquiries received that month, excluding tax. - **Orders** *(rose line — right axis)* — the count of purchase orders that month. The left axis is money, abbreviated (`₹25K`, `₹2L`, `₹3Cr`); the right axis is plain counts. Hover any month to read every series' exact value in the tooltip. ## Top Contacts by Submissions (table) Ranks your company's contact people by how many of the enquiries they were addressed to they actually submitted quotations for, within the period. Subtitle: *Enquiries received vs submitted*. Columns: - **Contact Person** — the contact's name. - **Submitted** — submitted count over enquiries received, shown as `submitted / given` (e.g. `4 / 10`). - **Rate** — the submission rate as a whole-number percentage of received enquiries. Every contact who received at least one enquiry in the period appears — even those who submitted nothing (they show as a `0` row) — so you can spot who is not responding. Rows are ranked by submitted count, then by received count, then by name, and the table shows the top 10. Click a row — or use its right-click menu (*Enquiries for {name}*) — to open your [Enquiries list](/docs/procurement/supplier-portal#enquiries-list) filtered to that contact. Only enquiries carrying a contact-person assignment feed this table. ## Pending Deliveries (table) The individual line items still owed to the firm, **oldest PO first**, so the most overdue commitments surface at the top. Subtitle: *Items awaiting delivery — oldest PO first*. **This table is not limited to the date range** — it spans every one of your POs that is still `sent` or `partiallyArrived` (a fully `arrived` PO has nothing outstanding, so it never appears here). Columns: - **Product** — the product name (the firm's external display name for the product where one is set, otherwise its internal head or code name). - **Qty** — the quantity still outstanding on that line (ordered minus received-and-approved). - **Value** — the outstanding value of that line, **including tax**, as a full rupee amount. - **Days** — days elapsed since the PO date, as a rough ageing indicator (e.g. `42d`). Only lines with a positive outstanding quantity appear, and the table shows the top 10 oldest. Click a row to open that purchase order in the portal; the right-click menu also offers *Open order {number}* and *View all orders*, and a *View orders* link at the foot of the card jumps to your full [Orders](/docs/procurement/supplier-portal#orders) list. ## Top Products (table) Your most valuable products **by order value in the selected period**, so this table respects the date range. Subtitle: *By order value in selected period*. Columns: - **Product** — the product name (external display name where set). - **Qty** — total quantity ordered across all in-range POs. - **Value** — total order value (**including tax**) for that product, as a full rupee amount. Ranked by value, top 10. Click a row (or the *Orders for {product}* right-click action) to open your [Orders](/docs/procurement/supplier-portal#orders) list filtered to that product name. ## Common questions ### Why do my colleague and I see the same numbers? By design. The dashboard is company-wide and is scoped to your supplier company on the server, not to whoever is signed in. Everyone at your company sees the same totals, charts, and tables. Only the *Welcome, …* greeting reflects the individual who logged in. Use the *Top Contacts by Submissions* table if you need to see who did what. ### Why does the Activity Trend chart show 12 months even after I change the dates? The trend chart is intentionally fixed to the last 12 calendar months so you always have a consistent historical baseline. The KPI cards, the *Enquiry Breakdown* pie, and the *Top Contacts* / *Top Products* tables respect the date range; the chart does not. ### The Pending Delivery card and the Pending Deliveries table disagree — is that a bug? No. The *Pending Delivery* **card** only totals purchase orders dated inside the selected date range, while the *Pending Deliveries* **table** lists outstanding items across *all* your open POs regardless of date. If you have older POs still awaiting delivery, the table will show items the card's range excludes. ### What counts as "Quoted" versus "Not Submitted"? *Quoted* means a quotation was submitted for that enquiry — by you in the portal, or by the firm's staff on your behalf. *Not Submitted* (and the pie's *Failed to Quote* slice) means the enquiry was received but no quotation was ever submitted. An enquiry is one or the other; the two never overlap. ### The pie has a "Won" slice but it is always empty — why? *Won* reflects an award being recorded against your quotation, which is a legacy concept in the current procurement flow. In practice almost nothing lands there, so the slice is usually zero and hidden. Treat *Quoted* as the meaningful "you responded" bucket. ### A card shows "—", "0", or "₹0" — what does that mean? `—` appears on the average and rate cards (*Avg. Submission Days*, *Avg. Delivery Days*, *Portal Upload Rate*) when there is nothing in the period to compute an average from. A plain `0` means a **count** really is zero for the selected window, and `₹0` means a **money** total is zero. If the whole dashboard looks empty, widen the date range — the default is only the current financial year. ### Why does a value look smaller on a card than in a table? They use different formats. KPI money **cards** abbreviate to fit (`₹1.23 L`, `₹1.23 Cr`), while table *Value* cells show the full rupee amount (`₹1,23,456`). The underlying number is the same. See [How money and numbers are formatted](#how-money-and-numbers-are-formatted). ### Can I export or change anything from here? No. The dashboard is read-only. But every table row and several links jump you to where you can act: the *Top Contacts* and *Top Products* rows open your filtered [Enquiries](/docs/procurement/supplier-portal#enquiries-list) and [Orders](/docs/procurement/supplier-portal#orders) lists, the *Pending Deliveries* rows open the relevant order, and the *Open Drafts* count points you back to unfinished quotations you can [continue and submit](/docs/procurement/supplier-portal#fill-quotation). ### Do the totals include tax? It depends on the figure, and the labels tell you which: *Quoted Value* and *Order Value* headline the **excluding-tax** amount with the including-tax figure on hover, while *Pending Delivery*, *Delivered*, and both tables' *Value* columns are **including tax**. Counts and averages carry no tax at all.