Central 2 won’t win design awards. But it might finally let HR professionals sleep through the night.
If you manage shebao for a company in Shenzhen, migrate your batch jobs to query the new API endpoints by Q3 2026. The legacy Central 1 read replicas are scheduled for read-only sunset by December. Have you encountered SZVY Central 2’s quirks or wins? Reply or ping me—I’m collecting real-world edge cases for a follow-up post. szvy central 2
If you’ve ever tried to reconcile social insurance records across multiple cities in Guangdong province, you know the feeling: fragmented portals, legacy UI, and that one dreaded verification code that never arrives. Central 2 won’t win design awards
Not a flashy rebrand. Not a mobile feature dump. But arguably the most significant backend shift in how Shenzhen—and by extension, the Pearl River Delta—handles social insurance (shebao) data aggregation. For the uninitiated, SZVY (深圳社保局 online system) has historically operated as a decentralized federation of municipal databases. Each district, each employer type, each insurance pillar (pension, medical, unemployment, work injury, maternity) often lived in slightly incompatible schemas. The legacy Central 1 read replicas are scheduled
April 14, 2026 Read time: 6 minutes
When you can trust that your 15 years of contributions won’t vanish during a job change, or that your employer isn’t silently underpaying, you stop fearing the system. You just use it.
Enter .