Integrations
Live: AxisRooms for the OTAs, Tally and CSV for the accountant, signed webhooks and mail. Built and switched on with the first hotel that holds the account: Razorpay and PhonePe, Zoho Books and QuickBooks, and IRP e-invoicing. Aggregators can already post orders in.
The product integrates where a hotel already has a relationship it will not change — its payment provider, its channel partner, its accountant's software, the tax portal — and nowhere else.
Live
- Channel — AxisRooms, two-way, with the sync log. Inventory and rates go out on every change; a booking pushed by the channel is on the chart in the same request.
- Accounting — Tally vouchers with party and GST, and the same day as a CSV journal that QuickBooks and most packages read.
- Tax — GSTR-2B read in and matched for input credit.
- Webhooks — a signed delivery of every posted day and of the room's story, retried until the receiver answers.
- Mail — a sending service on a verified domain.
Built, switched on with the first hotel that has the account
Each is written to the partner's published API and is waiting for a live credential. The first real run is the test; if the partner answers differently from its documents, the error lands on the row for us to read, not on a guest.
- Payments — Razorpay and PhonePe, on the hotel's own account, with the payout matched in the books.
- Accounting by API — Zoho Books and QuickBooks Online, pushed directly instead of by file.
- E-invoicing — the Invoice Registration Portal, directly or through ClearTax as the GSP.
Partly
- Orders — a receiving door for aggregators that can post JSON, with idempotency and item mapping. Sending the menu, order status and the partners' own signatures need a partner agreement, and that comes with scale.
The shape
Channels and payments are each a module against a registry; Zoho Books and QuickBooks share one connector interface. The credentials live in the vault. A partner's endpoint is never called from a browser.
Not yet
A door-lock interface, WhatsApp as a channel, and metasearch. Each will be a module when a hotel needs it, not a checkbox on a feature list before.