Integration · Shiji

Shiji already sees the arrival wave. Your roster should too.

Yes, HotelCadence connects to Shiji Enterprise Platform via its API in under two weeks, read-only. Reservations, pickup, arrivals and occupancy flow into hourly demand forecasts and draft rosters; nothing writes back. Shiji Group technology runs in 91,000+ hotels with its deepest footprint in Greater China, exactly where falling RevPAR makes labor the cost that has to flex.

Book a demo with your own Shiji dataHotel labor savings calculator →

Shiji logoShiji Group · vendor website: shijigroup.com ↗

When rate cannot carry the year, the roster has to

China closed 2025 with RevPAR down about 3% (STR/CoStar), and luxury operators across the region are being asked for the same service at lower cost. Labor runs 32.4% of revenue (CBRE, US benchmark), and most of it is still scheduled flat while occupancy moves daily.

HotelCadence turns the Shiji reservation stream into demand-matched rosters via AI hotel staff scheduling: labor cost down 6-12%, guest service and review scores held. The forecast blends your Shiji history and real-time bookings with external signals, weather, day of week, and the holiday calendars that move this market: Golden Week, Chinese New Year.

91,000+hotels run Shiji Group technologyShiji, marketing figures
API-firstShiji Enterprise Platform, built for read-only integrations
−3%China RevPAR in 2025: costs must flex with demandSTR/CoStar
Exact scope

What data does HotelCadence read from Shiji?

Five data points, all read-only, all counts and dates, no guest-identifying data is required. This is the complete list; there is nothing else in the scope.

Data pointViaSync frequency
Reservations & pickupShiji Enterprise Platform API, reservationsEvery 15 minutes
Arrivals & departuresShiji Enterprise Platform API, reservation statesHourly
Occupancy & house countShiji Enterprise Platform API, availability & occupancyHourly
Rate & segmentShiji Enterprise Platform API, rates & market segmentsDaily
F&B covers (where available)Infrasys POS (Shiji) or your POS exportDaily

Read-only scope, approved and revocable by your Shiji administrator.

Setup

Live in under two weeks, in three steps

  1. Step 1

    Approve read-only API access

    Your Shiji administrator approves a read-only API connection scoped to the pilot properties, a short configuration task guided by our onboarding team, revocable at any time. Nothing writes back to Shiji.

  2. Step 2

    Backfill and calibrate

    HotelCadence pulls up to two years of Shiji reservation history and calibrates hourly demand forecasts per department against your own actuals, blended with external signals such as weather, day of week and public holidays like Golden Week and Chinese New Year.

  3. Step 3

    Go live and measure

    Forecasts refresh as pickup changes and draft rosters flag shifts that no longer match demand. Managers approve everything. Typically live in under two weeks, measured monthly against your agreed baseline.

Worked example

Shanghai, 320 rooms: the desk staffed to the curve Shiji already knew

Corporate arrivals cluster after 17:00; the flat roster paid seven agents from 08:00 and still queued the evening peak. Staffed to the hourly arrival forecast, the same total headcount moved to where guests actually arrive.

Demand-matched rosterStaff required (from Shiji arrivals)Old flat roster
05101508, Demand-matched roster: 410, Demand-matched roster: 312, Demand-matched roster: 514, Demand-matched roster: 516, Demand-matched roster: 717, Demand-matched roster: 1018, Demand-matched roster: 1119, Demand-matched roster: 1020, Demand-matched roster: 822, Demand-matched roster: 508101214161718192022 08, Demand-matched roster: 4 · Staff required (from Shiji arrivals): 4 · Old flat roster: 7 10, Demand-matched roster: 3 · Staff required (from Shiji arrivals): 3 · Old flat roster: 7 12, Demand-matched roster: 5 · Staff required (from Shiji arrivals): 5 · Old flat roster: 7 14, Demand-matched roster: 5 · Staff required (from Shiji arrivals): 5 · Old flat roster: 7 16, Demand-matched roster: 7 · Staff required (from Shiji arrivals): 7 · Old flat roster: 7 17, Demand-matched roster: 10 · Staff required (from Shiji arrivals): 10 · Old flat roster: 7 18, Demand-matched roster: 11 · Staff required (from Shiji arrivals): 11 · Old flat roster: 7 19, Demand-matched roster: 10 · Staff required (from Shiji arrivals): 10 · Old flat roster: 7 20, Demand-matched roster: 8 · Staff required (from Shiji arrivals): 8 · Old flat roster: 7 22, Demand-matched roster: 5 · Staff required (from Shiji arrivals): 5 · Old flat roster: 7
Typical weekday, front desk: the demand-matched roster (bars) follows staff required from Shiji arrivals (amber); the old flat seven (dashed) idled mornings and drowned at 18:00.

The data behind this chart

HourStaff requiredOld flat rosterDemand-matched roster
08:00474
10:00373
12:00575
14:00575
16:00777
17:0010710
18:0011711
19:0010710
20:00878
22:00575

Worked example, figures indicative, 320-room city property.

Shiji integration questions, answered

How long does a Shiji integration take?

Under two weeks in most cases. Your Shiji administrator approves read-only API access; the remaining time is backfilling reservation history and calibrating the forecast against your actuals. Integration is included in the 90-day pilot (from US$7,500).

Which Shiji systems does HotelCadence connect to?

Shiji Enterprise Platform, the API-first cloud PMS, is the standard connection. F&B covers can flow from Infrasys, Shiji’s cloud POS, where it is deployed. Properties on legacy Shiji installations are scoped individually in the integration audit before any commitment.

Can data stay in mainland China?

Yes. For portfolios with mainland China properties, regional hosting keeps operational data in-region, consistent with PIPL obligations. The connection is read-only either way, and no guest-identifying data is required for forecasting or scheduling.

Is HotelCadence a certified Shiji partner?

Certification listing is in progress. HotelCadence connects today through the documented Shiji Enterprise Platform APIs, the same mechanism Shiji’s own integration ecosystem uses, so nothing about the connection waits on the listing.

We run Shiji in China and OPERA Cloud elsewhere, does that work?

Yes, and it is the typical setup for chains in the region. Shiji properties connect via the Enterprise Platform API, OPERA Cloud properties via OHIP, Mews and Cloudbeds via their own APIs, and everything rolls up into one portfolio view with the same per-department, per-hour forecasts.

Why does scheduling matter more in a market where RevPAR is falling?

China closed 2025 with RevPAR down around 3%, so profit has to come from cost discipline rather than rate. Labor is the largest controllable cost, and demand-matched rosters make it flex with occupancy instead of staying fixed while revenue falls.

Book a demo with your own Shiji data

30 minutes · read-only access · no obligation. Different PMS at other properties? See all integrations.