SleekView Charts for Instamojo for WooCommerce
Instamojo for WooCommerce stores payment id and payment request id against each order's meta. SleekView Charts reads those rows alongside the order totals and renders a configurable dashboard of revenue, status mix, and refunds inside WP Admin.
♾️ Lifetime License available
Read Instamojo-paid orders as charts, not per-order clicks
WooCommerce writes every Instamojo-paid order to wc_orders on HPOS stores (or posts on legacy ones) with total_amount, status, currency, and date_created_gmt on each row. The Instamojo plugin attaches its own payment id and payment request id to wc_orders_meta (or postmeta) so the gateway-side identifiers live alongside the order. The default Orders screen shows a list, not a shape.
SleekView Charts reads the same tables and the same meta keys and turns them into chart cards on a single dashboard. A Number KPI summing total_amount for Instamojo-paid orders this month, a Donut splitting orders by status, a Bar of refund volume by day, and an Area of daily revenue across the selected range. Each card is a saved query against the live tables.
The Instamojo dashboard remains the source of truth for settlements and chargebacks. SleekView Charts adds the WooCommerce-side reading layer that pairs against it: finance reconciles totals, ops watches the status donut, support sorts the refund queue, all on one screen rather than three.
Workflow
From wc_orders and Instamojo meta to a chart dashboard
Point SleekView at WooCommerce + Instamojo meta
Scope to Instamojo orders
Switch the view to Charts
Save per role
Sample dashboard
Charts you can build from Instamojo for WooCommerce data
Instamojo revenue this month
Sum(total_amount)
Orders by status
Count
group by status
Refunds by day
Sum(total_amount)
group by date_created_gmt
Daily Instamojo revenue
Sum(total_amount)
group by date_created_gmt
Comparison
Default Instamojo for WooCommerce reporting vs SleekView Charts
Default WooCommerce admin
- WooCommerce admin lists orders, but does not chart Instamojo-paid revenue separately
- No combined dashboard for status mix, refund volume, and daily revenue scoped to Instamojo
- The Instamojo dashboard lives outside WordPress and cannot mix with WooCommerce columns
- No saved dashboards per role for finance, ops, or support
- Refund-rate trends require manual CSV exports and a spreadsheet
SleekView Charts
- Chart cards built from wc_orders and Instamojo payment meta
- Filter every card to payment_method = instamojo for clean gateway views
- Mix Number, Pie, Bar, and Area cards on one dashboard
- Save dashboards per role for finance, support, and ops
- Queries hit existing HPOS indexes on id, status, and date_created_gmt
Features
What SleekView Charts gives you for Instamojo for WooCommerce
Gateway revenue at a glance
Number cards on Instamojo-paid totals, donuts on order status, and area charts on daily revenue. The reconciliation shape finance has been building in spreadsheets becomes a saved dashboard.
Scoped to one payment method
Every card on the dashboard inherits the payment_method = instamojo filter. Stack date range and status filters to focus on the day's reconciliation queue.
Role-scoped dashboards
Finance keeps the revenue and refund cards, support keeps the status donut, ops watches the daily trend. Each view gated by WordPress capability so the right team sees the right slice.
Audience
Who builds Instamojo for WooCommerce charts dashboards with SleekView
Indian-market finance teams
Reconcile against the Instamojo dashboard with totals, status mix, and refund volume on one WP Admin screen. The settlement summary on Instamojo gets matched in seconds, not minutes.
Refund auditors
Watch the refunds-by-day bar and the refunded slice of the status donut. Patterns in refund volume surface before the monthly report makes them official.
Support leads
Open the daily revenue area chart and the status donut to brief the team each morning. The Instamojo slice of the day is visible without a second login.
The bigger picture
Why Instamojo stores need a charts dashboard inside WordPress
Indian-market WooCommerce stores running Instamojo end up bouncing between two surfaces: the WP Admin where orders live and the Instamojo dashboard where settlements and chargebacks live. Both are accurate. Neither lays out the questions finance actually asks (today's Instamojo revenue, this week's refund rate, this month's status mix) on a single screen.
SleekView Charts reads the WooCommerce-side data and renders it as a configurable dashboard scoped to Instamojo-paid orders. Finance gets the totals and the refund volume, ops gets the status mix, support gets the daily trend, all on one view that the Instamojo dashboard then pairs against for the authoritative settlement match. The Instamojo dashboard stays the source of truth.
WP Admin becomes the reading surface that matches the rhythm of the rest of the operation.
Questions
Common questions about SleekView Charts for Instamojo for WooCommerce
No. The Instamojo dashboard remains the source of truth for settlements, chargebacks, and payouts. SleekView Charts reads what the Instamojo plugin already stored against each WooCommerce order (payment id, payment request id, totals, status, dates) and renders it as a dashboard scoped to gateway-paid orders. The two surfaces pair: dashboard for authoritative settlement data, SleekView Charts for the WooCommerce-side reading layer.
Yes. On HPOS the order data lives in wc_orders and wc_orders_meta; on legacy stores it lives in posts and postmeta. SleekView detects the schema and builds the chart queries against whichever the store uses. The chart cards themselves stay identical between schemas.
Yes. The base saved view filters on payment_method = instamojo (matching the gateway slug the plugin uses on the install), and every chart card inherits that filter. Stack additional filters for date range, status, or country at the card level if a specific dashboard needs them.
Live. SleekView Charts queries the WooCommerce tables directly, so a card refresh reflects the orders, status changes, and refunds that have happened up to the moment of the request. There is no separate sync that can fall behind.
Only where the plugin records them as pending orders. The default Instamojo flow promotes successful attempts to orders, so failed attempts often do not exist as WooCommerce rows. Where they are recorded, the failed status is filterable and chartable like any other order status.
Yes. SleekView views, including chart dashboards, can be embedded on a frontend page with role-based access. Useful for sharing the daily revenue and refund trend with finance stakeholders who do not have WordPress admin access.
No. Chart queries hit the same HPOS indexes WooCommerce already maintains on id, status, and date_created_gmt. Aggregations are bounded by the date range or filter on the card, and pagination is keyset where the schema allows it.
Yes. Each gateway stores its own meta against the order. You can build a single mixed-gateway dashboard, or scope per-gateway dashboards by setting the base view's filter to one payment_method value. Most teams prefer the per-gateway split because reconciliation lives per gateway.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout