01
Hotel / restaurant POS
Designed when enabled
Hotel / restaurant POS
LimeTray
LimeTray is listed as designed when enabled — status chips stay honest.
03
Book a demo
External connector
Designed when enabled
Hotel / restaurant POS
PMS · Finance
limetray.com
03 phases
Overview
How LimeTray fits NISKA
Evaluate when F&B / outlet POS should post into the property folio model.
03Pillars
Three operator outcomes — not a logo wall.
Overview
LimeTray is listed on the NISKA integrations catalog with status “designed”. LimeTray hotel/restaurant POS surface designed for F&B and outlet posting into the property folio model when enabled.
- Outlet charges can post into the guest folio model
- Fewer end-of-day surprises between restaurant POS and front desk
- Stay truth stays on PMS even when outlets use specialist POS
Why this connector matters
Three operator outcomes — not a logo wall.
Post
Outlet tickets are designed to post into the property folio when POS packaging is enabled.
Settle
Folio settlement stays on PMS / Finance — not a second guest ledger.
Ops split
Outlet teams keep POS workflows; the desk keeps stay truth.
Data paths
What is designed to sync
Flows stay on the shared property model — not a bolted relay layer.
03Paths
Post
Outlet tickets are designed to post into the property folio when POS packaging is enabled.
Settle
Folio settlement stays on PMS / Finance — not a second guest ledger.
Ops
Outlet teams keep POS workflows; the desk keeps stay truth.
Surfaces
What this connector covers
Capability language stays tied to Channel Manager / owning modules — not invented APIs.
03Surfaces
- LimeTray surface in the pos category
- Enablement is property- and certification-dependent — status chips stay honest
- Actions stay on the NISKA property model with confirm gates where agents write
Enablement
What “when enabled” means
A marketing logo is not a green UAT checklist. Rollout certifies what your property gets.
03Steps
Start here
Vendor
POS vendor and outlet mapping are confirmed.
Step 02
Prove
Posting rules and tax treatment are UAT-tested.
Step 03
Audit
Night-audit impact is reviewed with Finance.
Day-2 ops
How teams should run it
After go-live, keep the property model as the writer and treat alerts as book-risk.
Spot-check outlet posts before night audit for the first weeks
Keep tax treatment ownership with Finance
Next step
Map LimeTray to your property
Book a demo to verify enablement, or return to the catalog for the full grouped list.
Field notes
Sign up to our mailing list for regular updates on the travel & hospitality industry.
Operator-ready briefs on Agentic AI HMS, revenue, Concierge, and India compliance — not vendor fluff.
- Agents & ops
- Revenue
- Compliance