Sale Dashboard
Use your Meesho Google account to open the dashboard. Google sign-in controls dashboard access; Admin fetches still use the separate Admin session cookie.
Checking sign-in…
Sale Dashboard
Config validation and scale-up operations
Schema: bundled
Proxy: detecting…
![]()
Validator
Paste config JSON or open from Scale-ups/Admin, then review sale-readiness checks.
Prebuzz window
Not set
Sale window
Not set
Sync schema
Re-sync the schema
Pulls the latest ConfigResponse.kt from supply_android and applies it live — no reload needed. Requires start.command (or serve.js) to be running.
Auto-syncs every 10 minutes in the background. Manual re-sync needed only for a different ref or immediate update.
First time? Start the launcher
In Finder, double-click start.command. It preflights node & gh, starts the server, and opens this page automatically. Closing the Terminal window stops everything.
Requires gh auth status ✓ and read access to Meesho/supply_android. Optional args: ./start.command [port] [ref].
Advanced / fallbacks
One-shot CLI — rewrite index.html without running a server:
node sync-schema.js # default ref develop node sync-schema.js <ref> # any branch / commit SHA
Drop a file — session-only schema swap (when offline or sync isn't available):
Drop ConfigResponse.kt here or click to pick
Reset — revert this session to the schema baked at page-load time:
What gets checked
Click Validate with a config fragment on the left. Each rule produces one or more report entries; filter by severity using the buttons above the report.
✓ PASS
checked, value is fine
! WARN
probable issue, manual look
✕ FAIL
almost certainly wrong
i INFO
advisory / couldn't check
Structure & schema
1
Structure
PASS
FAIL
INFO
Root must be a non-empty JSON object. Each top-level key is resolved against the parsed
ConfigResponse.kt schema (e.g. sale_marker_config → SaleMarkerConfig).
Unknown top-level keys fail with a typo suggestion.
2
Schema keys (Kotlin model match)
PASS
FAIL
Recursively walks every nested object / list / map and compares each key against the allowed fields of its data class. Anything not in the Kotlin model fails, with a "Did you mean …?" suggestion from Levenshtein distance.
"slanted_sale_discount__enabled": false ✕ Unknown key in SaleMarkerConfig
Did you mean "slanted_sale_discount_tag_enabled"?
3
Enum values
FAIL
When a field's Kotlin type is an enum class declared in ConfigResponse.kt,
the value must match one of the enum's allowed wire values exactly. Wire value is the
@Json(name = "…") when present, otherwise the Kotlin identifier. Typo-distance
suggestion included on failure.
"type": "lottie" ✓ pass (AssetType: image / gif / lottie)
"type": "LOTTIE" ✕ Invalid value for enum AssetType. Did you mean "lottie"?
"type": "webm" ✕ Allowed: image, gif, lottie
4
Schema types (primitive type check)
FAIL
Every field's value is checked against the Kotlin primitive type declared on the data class.
Boolean requires true / false; Int / Long
/ Short / Byte require a finite integer; Float /
Double require a finite number; String requires a string.
Recurses into List<T> and Map<String, T>. Types we don't
recognize (e.g. enums or classes from other Kotlin modules) are skipped to avoid false positives.
"slanted_sale_discount_tag_enabled": false ✓ pass (Boolean)
"slanted_sale_discount_tag_enabled": "k" ✕ Expected Boolean (true / false), got string ("k")
"banner_height": 64 ✓ pass (Int)
"banner_height": "64" ✕ Expected Int (integer), got string ("64")
"slanted_sale_bg_color": "#9F2089" ✓ pass (String)
Assets — URLs, sizes, language
5
URL validity & HTTPS
PASS
FAIL
Every discovered asset URL must be absolute and use https://. Cleartext
http:// fails — Android rejects mixed-content traffic.
6
Extension sanity
WARN
Lottie URLs should end in .json or .lottie. Image URLs should end in
.png / .jpg / .jpeg / .webp /
.gif / .svg. Mismatches warn rather than fail (CDNs can serve through query-string routes).
7
Asset size limits
PASS
WARN
FAIL
INFO
Defaults: image < 60 KB, lottie < 120 KB (configurable in the settings strip). Each asset is fetched through the local CORS proxy and its byte count checked. At or over the limit → fail. ≥ 85% of the limit → warn. Otherwise pass. Fetch errors (CDN down, proxy not running) surface as info.
image 61808 B (60.4 KB) ✕ over 60 KB limit
image 53000 B (51.8 KB) ! within 85% of 60 KB
image 12000 B (11.7 KB) ✓ pass
8
Per-asset language
PASS
WARN
FAIL
INFO
When the JSON has a language map — an object keyed by ISO-639 codes
(en / HI / TE / MR / TA /
BN / KN / ML / OR / GU /
PA / AS) — every URL inside inherits that key as its expected language.
- Lotties are downloaded, text layers extracted, and the dominant Unicode block compared to the expected script (Devanagari, Tamil, Telugu, etc.).
- Under
EN, Latin must dominate; significant Indic content fails. .lottiefiles are ZIPs — unwrapped in-browser viaDecompressionStream.- Images are opaque to JS, so we fall back to filename heuristics (
_en/_hindihints).
"HI": {"type":"lottie","url":"...english_text.lottie"}
✕ Lottie under HI is English (no Devanagari)
"HI": {"type":"image","url":".../1779946133578.jpg"}
✓ size 38 KB (filename has no language hint)
9
Cross-language duplicates
WARN
Within one language map, if multiple language slots point to the same URL, warns. Usually a copy-paste bug — one image can't simultaneously be Hindi and Tamil and Bengali.
! Same asset used for 9 languages: EN, HI, TE, MR, TA, BN, KN, ML, OR
Code quality & sanity
10
Hex color format
WARN
Field names ending in _color / _bg_color / _text_color
(or just color) must match #RRGGBB or #RRGGBBAA.
"timer_bg_color": "#1a1a1a" ✓ pass
"some_color": "#ff00gg" ! invalid hex
"text_color": "#FFFFFFCC" ✓ with alpha
11
Required-when-enabled
FAIL
When an object has enabled: true or is_enabled: true, every sibling
field whose name looks like an asset reference (*_url / icon /
logo / banner / lottie / animation) must be
non-empty. Empty asset on an enabled feature fails.
12
Numeric ranges
WARN
FAIL
Sanity caps on numeric fields:
min_version/version_code/app_versionnegative → fail*percent/*percentageoutside 0–100 → warn*_seconds/*_ms/*_millis/*_countnegative → warn
Sale readiness
13
Price-drop animation counts
PASS
WARN
FAIL
price_drop_sale_day.feed_animation_count should stay between 1-30;
pdp_animation_count should stay between 1-6. Values below 1 fail,
values above the usual sale range warn for manual confirmation.
14
Dynamic app icon alias
PASS
FAIL
When dynamic_app_icon.enabled is true, alias must match the aliases
declared in IconAlias.kt.
15
Lottie framerate
PASS
WARN
FAIL
INFO
Fetched .json and .lottie animations are parsed for fr.
≤ 30 fps passes, 31-60 fps warns, and > 60 fps fails.
16
Splash media dimensions
PASS
FAIL
INFO
splash_config.splash_asset.url and fallback_asset.url are checked for
width/height when fetchable. Splash media must be exactly 360×720.
17
Sale timing
PASS
WARN
FAIL
INFO
Epoch start_time/end_time fields are compared against the Admin experiment
window when available. Config start/end must be within ±1 day of experiment
start/end, and within ±7 days of the saved IST Sale or Prebuzz window in the top bar.
Previews
·
Asset previews
INFO
Below the report, every discovered asset shows up as a thumbnail card with its path,
kind, size, and language (if known). Images render natively (no CORS needed for
<img>). Lotties render via lottie-web — both raw .json and
.lottie ZIPs are supported. Auto-collapsed when more than 20 assets.
How asset URLs are discovered
Three signals, checked in priority order:
- Sibling
typefield — the{type, url}pattern.type:"lottie"wins regardless of URL. - Field-name regex —
*_image_url/*_icon_url/*_lottie_url/*_animation_url, or bareicon/lottie/ etc. - File extension — fallback when name is ambiguous (e.g. just
url)..json&.lottie⇒ lottie..png/.jpg/ etc. ⇒ image.
New asset fields added to ConfigResponse.kt are picked up automatically — no catalog update needed.
Edit scale-up
Cache Scale-up configs
Fetch admin configs for the Scale-ups archive and save only the JSON configs in this browser's local DB. A pasted cookie is used for this run only and cleared from the form before the fetch starts.
Config JSON
Paste JSON, drop a file, or receive configs from Admin/Scale-ups.
Empty
Drop a
.json file · ⌘+↵ to validate
Validation report
Failures and warnings stay easy to scan first.
Start a validation
Pick any of these to get going.
Or paste any config JSON on the left. ⌘+↵ validates · the
Checks button in the sidebar explains every rule.
Admin fetch workflow
Session setup, URL/cURL fetch, extracted configs, and validation handoff.
⚙ Setup edit
Session cookie
DevTools → Application → Cookies → admin.meeshosupply.com → select all → Copy → paste any format
requested-by email
added as a header — required by ab-experiment APIs
Paste any abacus URL — the planner translates it to the right API call.
Try:
Fetch history recent admin responses 0
Response
Raw response
Scale-up catalog
A reusable ops list for the current sale scale-ups.