Built for Hotel Chains & Groups

Central procurement. Local autonomy.

For hotel groups, regional chains and central-purchasing operators. Push group standards (recipes, suppliers, brand pricing) down to the property; roll cost + margin + compliance back up. Multi-site reporting built into the core.

Multi-site
native, not bolted on
SSO
SAML / OIDC + SCIM
BI
warehouse export ready
EU
data residency
The problem

One brand, twelve tech stacks.

01

Procurement leverage left on the table

Central buying agreements exist, but properties order off-script. Volume discounts unclaimed.

02

Recipes diverge across properties

The brand burger has 8 variations. Cost differs by 18%. Margin is property-by-property roulette.

03

Group P&L lands 6 weeks late

Twelve properties send 12 spreadsheets to finance. The picture is always backward-looking.

How Inntally fits

Built for groups, not retrofitted.

Most used

Central procurement

Group agreements baked into Marketplace. Properties see brand-approved prices first. Off-contract orders flagged.

Marketplace →

Central recipes

Brand-standard recipes published to all properties. Cost variance per property visible in one report.

Recipes →

Rolled-up analytics

F&B GP per property, per outlet, per service period. Drill in or roll up. BI warehouse export.

Analytics →

Connect (ERP / PMS)

SAP, Oracle, NetSuite, Sage Intacct, Mews, Opera. Adapters in Connect; custom-built where needed.

Connect →
Three before/after stories

What changes for the group.

Illustrative scenarios based on industry benchmarks for hotel groups operating in Ireland and the EU.

01

Procurement leverage applied automatically

Central buying agreements published to every property’s Marketplace view. Off-contract orders flagged, approved or denied at group level.

Before Group rate negotiated, ignored property-by-property.
After Brand-approved prices first; volume discounts captured.
3–6% group-level price improvement (illustrative)
Central procurement
02

Brand-standard recipes; visible cost variance

Group publishes the burger recipe. Each property runs it. Variance report shows who’s 18% over food cost — and why.

Before 8 versions of the brand burger, all priced differently.
After One recipe, variance flagged, intervention possible.
Margin parity across properties
Central recipes
03

Group P&L the day it’s relevant

F&B GP per property, per outlet, weekly. Drill into the underperformer; roll up to the board pack. No spreadsheet relay.

Before 6-week lag on group F&B P&L.
After Weekly dashboard, drillable to dish-level.
Weekly rolled-up viewBI warehouse export for Power BI / Tableau
Group analytics
The math

What groups tend to recover.

3–6%
group procurement leverage

Off-contract orders flagged; central rates applied.

Margin
parity across properties

Central recipes + variance reporting.

Weekly
group P&L (was 6-wk lag)

Rolled-up F&B GP per property.

SSO
+ SCIM for IT teams

Standard SAML / OIDC; provisioning automated.

Illustrative scenarios based on industry benchmarks for hotel groups in Ireland and the EU. Named case studies available under NDA on request.

Foundation

Group-ready security & integrations.

SSO + SCIM

SAML 2.0, OIDC, SCIM provisioning. Standard with Custom Rollout.

ISO 27001 + 27701

ISMS live. Cert target Q1–Q2 2027. Customer evidence binder on request.

ERP / PMS integration

SAP, Oracle, NetSuite, Sage Intacct, Mews, Opera, Cloudbeds.

BI warehouse export

Scheduled CSV / Parquet to your S3 / Azure / Snowflake.

From a pilot

“Group P&L is now a Monday meeting, not a quarterly fight.”

Illustrative voice from our group pilot programme — full case study published as pilots formally permit.

FAQ

Group ops directors ask these first.

Multi-tenant rollup — how does it work?
Each property is a tenant; rollup tenant aggregates. Permissions per tenant; group-level read access for finance + ops directors.
Do you do SAP / Oracle integration?
Yes — via the platform’s integration layer (REST + webhooks + pre-built adapters). Inbound: supplier catalogues, contracts. Outbound: invoice + journal posting. Custom builds for unusual setups.
SSO requirements?
SAML 2.0 or OIDC. SCIM provisioning. Azure AD, Okta, Google Workspace, OneLogin all supported.
Data residency for properties outside Ireland?
All data in AWS eu-west-1 (Dublin). EU/EEA properties served from there. Non-EU properties — talk to us about regional strategy.
How long is rollout for a 10-property group?
Typical: 8–14 weeks. Pilot property first (4 weeks); template the configuration; roll to remaining properties in waves.
Group rollout starts with a pilot property

Pilot one property. Roll out the group.

Free workspace, your own data, 14 days. We audit; we shape the multi-site rollout plan.