OMO is not simply "online courses plus offline courses" — that is just dual-track operation. The "merge" lives in data and process: one student profile holds both online learning records and offline attendance; one schedule drives both classroom booking and live-session planning; class-hour consumption is settled in real time wherever it happens.

A typical OMO evolution has four stages: (1) online supplements (offline-first, online for after-class service) → (2) online enrollment (trials and content-driven acquisition) → (3) dual-mode teaching (classes mixing offline and online students) → (4) unified data (all-scenario data driving scheduling, churn alerts and decisions). Most institutions stall at stage 2 — usually not for lack of will, but because the online-offline data wall remains.

Three tests for genuine OMO: can a cross-campus class auto-convert timezone and room; are online trial students and enrolled offline students managed in the same CRM pool; does the class-hour balance parents see in the app match the admin console in real time?