2. Admin Dashboard
[← Getting Started]/01-getting-started/ · [Index]/00-index/
2. Admin Dashboard
Verified against: Medusa admin dashboard (@medusajs/dashboard 2.18.0), running locally at
http://localhost:9000/app; source inspected directly (node_modules/@medusajs/dashboard/src)
since this is Medusa’s own default admin, not custom-built for Sindhu Naturals.
Dashboard overview
The admin dashboard is Medusa’s own built-in UI — nothing here was custom-built for Sindhu Naturals except the GST invoice/credit-note download buttons described below.
- Local:
http://localhost:9000/app - Live testing server:
https://app.sindhunaturals.com/app(note the/apppath is required even on theapp.subdomain — the subdomain just proxies to the same Medusa process)
IMPORTANT: There is one admin login per environment (local vs. the live testing server), and they are different accounts. Credentials are not stored in this wiki and are not committed to git.
TO BE CONFIRMED: the process for issuing a new staff member their own admin login. Today only one account exists per environment, so a new staff member would currently share credentials with whoever already has access — see [Section 26]/26-user-roles-and-permissions/ for the proposed fix.
Sidebar structure
The left sidebar has six top-level sections:
| Section | Sub-items |
|---|---|
| Orders | — |
| Products | Collections, Categories, Product Options |
| Inventory | Reservations |
| Customers | Customer Groups |
| Promotions | Campaigns |
| Price Lists | — |
INFO: Medusa calls discount codes “Promotions,” not “Coupons.” If a colleague asks “where are the coupons,” the answer is the Promotions section.
A gear icon opens Settings, covering: Store, Users, Regions, Tax Regions, Return Reasons, Refund Reasons, Sales Channels, Product Types, Product Tags, Locations (stock locations/shipping), Publishable API Keys, Secret API Keys, Workflow Executions, and your own Profile.
INFO: There is no separate “Reports” or “Payments” or “Shipping” item in the sidebar — this is a default-Medusa dashboard, and those aren’t top-level sections in it:
- Reports — Planned / Not yet implemented. No sales/inventory/financial reporting screen exists. The closest available today is filtering/sorting the Orders and Products list tables themselves.
- Payments — not a sidebar section; payment status/actions live inside each individual order’s detail page.
- Shipping — configured under Settings → Locations, not a dedicated sidebar item.
For every section below: what it is, when to use it, what it contains, common actions, and what to verify before changing data.
Orders
What it is: The list of all orders placed through the storefront. Opens to an order’s full detail (line items, customer, addresses, payment, fulfillment status) when clicked.
When to use it: Checking new orders, fulfilling/shipping an order, checking payment status, issuing a refund, or cancelling an order.
What it contains: Order number, customer, date, payment status, fulfillment status, total.
Common actions: View order detail, mark as fulfilled/shipped, cancel order, view/download the GST invoice (custom addition — see below).
INFO: A “Download Invoice”-equivalent exists via the API route
GET /admin/orders/:id/gst-invoice/pdf(this project’s own addition, not stock Medusa). If a customer needs their invoice re-sent, this is where it comes from. Cancelling an order from here automatically triggers a GST credit note (see.ai/features/gst.mdin the codebase, and the upcoming Refunds & Returns / Invoicing sections of this wiki).
Verify before changing data: Confirm you’re looking at the right order (not a similarly named/priced one). Order status changes (cancel, fulfill) are consequential — see the upcoming Order Management section for the full lifecycle.
WARNING: No order has ever been completed end-to-end on the live payment flow at the time this wiki was written (per
.ai/features/orders.md) — treat any order you find as something to verify carefully, not assume is routine, until real order volume exists.
Products
What it is: The product catalog — currently 2 products (Groundnut Oil, Coconut Oil), each with 3 size variants.
When to use it: Creating a new product, editing descriptions/images/pricing, checking HSN/GST metadata, publishing/unpublishing.
What it contains: Product list (title, status, sales channel), and per-product detail (general info, organization, variants, media, attributes).
Common actions: See the full [Product Management]/03-product-management/ workflow.
Verify before changing data: See the “Safe vs. sensitive changes” guidance in [Section 19 — Product Editing]/19-product-editing/ — as a rule, price/SKU/status changes are more consequential than description/image changes.
Inventory
What it is: Stock quantity tracking per variant, per stock location.
When to use it: Checking current stock, adjusting stock counts.
What it contains: Every variant’s SKU and its stocked quantity at each location. Today
there’s a single location, “India Warehouse,” and every one of the 6 variants was seeded with a
flat 1000 units (an arbitrary starting number, not a real count) — see
.ai/features/inventory.md in the codebase.
Common actions: Manually adjust a stock quantity; view reservations (stock held against in-progress orders, under the “Reservations” sub-item).
WARNING: There is no documented real stock-counting process yet. Any quantity you see reflects whatever was last manually entered, not a verified physical count. Treat the “1000” baseline as a placeholder, not a real inventory figure, until a real stock-take happens. See the upcoming Inventory Management and Stock Audit sections.
Verify before changing data: Confirm the SKU/variant you’re adjusting matches the physical
product in hand — SKUs like SINDHU-GRN-500 (Groundnut, 500ml) and SINDHU-COC-500 (Coconut,
500ml) are easy to mix up at a glance.
Customers
What it is: Everyone who has registered an account or placed a guest order.
When to use it: Looking up a customer’s order history, checking contact details.
What it contains: Name, email, registration date, order history, address book — all from
Medusa’s default customer module (see .ai/features/customers.md).
Common actions: View a customer’s profile and order history. “Customer Groups” (sub-item) exists in the UI but nothing has been configured — no groups exist today.
Verify before changing data: This is personal data — only look up what’s needed for the task at hand. No custom access-restriction exists yet (see admin roles note above), so this is a process/discipline matter, not a system-enforced one today.
Promotions (Coupons & Discounts)
What it is: Medusa’s discount-code system — referred to as “Coupons” in the original wiki brief, called “Promotions” in this admin.
Status: Planned / Not yet implemented for this business. The screen exists (it’s part of default Medusa), but no promotion/campaign has ever been created for Sindhu Naturals.
When to use it: Once the business decides to run a discount — do not invent discount values or codes; see the upcoming Coupons & Discounts section, which will need real business input before it can be written.
Price Lists
What it is: Medusa’s mechanism for overriding prices for specific customer groups or sales channels (e.g. wholesale pricing).
Status: Not used — the store has one flat retail price per variant, set directly on the product (see [Product Management]/03-product-management/). No price list has been created.
Payments
What it is: Not a separate sidebar section — payment status and actions (capture, refund) live inside each order’s detail page.
Status: Razorpay is integrated in test mode only (rzp_test_... credentials) — real
money never moves today. See .ai/features/payments.md. Server-side authorization independently
re-verifies every payment with Razorpay’s API; the storefront’s payment button is never trusted
on its own.
TO BE CONFIRMED: Live (production) Razorpay keys are not configured. Do not treat any current transaction as a real payment.
Shipping
What it is: Configured under Settings → Locations, not a dedicated top-level section.
Status: One nationwide flat-rate option, “Standard Delivery,” ₹49 — explicitly a
placeholder, not a confirmed real shipping cost (.ai/features/shipping.md). No carrier
integration is fully live yet; a Shiprocket integration exists in the codebase for
label/AWB generation but is blocked on a real Shiprocket account for end-to-end testing.
Reports
Status: Planned / Not yet implemented. There is no reports/analytics screen in this admin. For now, sales/order/inventory totals must be read off the Orders/Products/Inventory list screens directly, or queried from the database by a developer — there is no self-service report builder for staff today.
Settings
What it is: Store-wide configuration — not day-to-day operational work. Includes Store details, Users, Regions, Tax Regions, Return/Refund Reasons, Sales Channels, Product Types, Product Tags, Locations (stock + shipping), and API key management.
WARNING: Settings changes are store-wide, not per-order or per-product. Changing a Region or Tax Region here can affect GST calculation for every future order. Only make Settings changes if you understand the consequence, or check with the developer first.
Common actions relevant to daily staff work: Usually none — Settings is a one-time/rare setup area, not part of the daily order/product workflow.
[← Getting Started]/01-getting-started/ · [Index]/00-index/ · [Next: Product Management →]/03-product-management/