FLYR’s integration with Shiji PMS is designed to provide accurate and timely synchronization of reservations, blocks, and revenue data. However, due to certain limitations in Shiji’s API, some data points may not be fully supported or may appear differently in FLYR.
If any of these discrepancies were identified during your onboarding process, our team would have proactively flagged them and discussed potential impacts and workarounds with you.
Below is a list of known unsupported scenarios, along with detailed explanations and suggested workarounds.
1. No Revenue Breakdown for Future Group Blocks
Description
For future group blocks, Shiji does not provide a detailed revenue breakdown by revenue category or item type (e.g., accommodation, food & beverage, meeting space).
As a result, all revenue associated with future group blocks that have not yet been picked up will appear in FLYR as overnight accommodation revenue.
This is a data limitation within Shiji’s API — revenue line item details are not available until individual reservations are created under the group block.
Suggested Workaround
There is no workaround required or recommended.
This limitation will automatically resolve as bookings under the group block are picked up, since detailed revenue breakdowns become available at that stage.
Summary
While FLYR’s integration with Shiji PMS delivers robust data synchronization for reservations and revenue, certain limitations in the Shiji API. For more information on temporary discrepancies, check out this article.
These discrepancies typically self-resolve as reservations are picked up and actualized.
If you have questions or notice discrepancies not listed here, please contact the our support team for further assistance.