Appearance
What can be configured
Page summary: Answer “can EMS do this?” without guessing.
Use this when: Use this for sales, client conversations, setup, and product discovery.
- Supported means safe to promise; caveated and unknown do not.
- Some things that look configurable are fixed in code or environment settings.
- Scope matters: vendor, partnership, channel, or everyone.
For answering "can EMS do this for our client?" without asking an engineer.
Supported is the honest answer to give a client. "Partly" and "unknown" mean exactly that — do not round them up to yes.
Whether a vendor must approve each booking — Per vendor · Supported
Options: Confirms straight away, or waits for the vendor
Default: No approval needed
Depends on: Set per availability slot, not per experience. Vendor-made and partner bookings ignore it entirely.
Rule: approval is decided per slot
Checked: Confirmed in code, 5 Aug 2026
Proposing a change moves the booking to "pending customer confirmation" — Everyone · Not a setting
Options: On or off
Default: On
Depends on: On in dev, staging and production. Not something a client can change.
Rule: propose-changes always moves the booking to pending
Checked: Confirmed in code, 5 Aug 2026
Whether the status control appears on a booking — Per sales channel · Not a setting
Options: Shown or hidden
Default: Shown
Depends on: Hidden for Get Your Guide bookings. Fixed in the dashboard code.
Rule: the dashboard keeps its own copy of the transition rules
Checked: Confirmed in code, 5 Aug 2026
Tax rate — Per vendor · Supported
Options: A percentage
Default: None found
Depends on: Tax always comes out of the price, never added on top. Where it is set has not been traced.
Rule: tax is inside the price
Checked: Confirmed in dev at 13%, 5 Aug 2026
Platform fee — Everyone · Supported
Options: A percentage
Default: 3.6%
Rule: the order of operations is fixed
Checked: Confirmed in code, 5 Aug 2026
Commission rate — Per partnership · Supported
Options: A percentage
Default: 0%
Depends on: Which partner model the deal uses
Checked: Confirmed in code, 5 Aug 2026
Commission basis — Per partnership · Supported with caveat
Options: From gross, or from net
Default: From gross
Depends on: "From net" means different things in the two partner models — after the platform fee in one, after tax in the other. Confirm which before quoting a number.
Rule: "net" means two different things
Checked: Confirmed in code, 5 Aug 2026
Partner model — Per partnership · Supported
Options: White label, or authorised agent
Default: None
Depends on: Changes which formula applies entirely. White label: the partner prices above a floor and keeps the difference. Authorised agent: the partner takes a percentage.
Rule: Prices and fees
Checked: Confirmed in code, 5 Aug 2026
Floor price for a white label partner — Per partnership · Supported
Options: A percentage below the vendor's rate
Default: None
Depends on: The partner cannot sell below it. A lower sell price is rejected.
Rule: a partner cannot sell below the floor
Checked: Confirmed in code, 5 Aug 2026
Commission treated as a discount instead — Per partnership · Supported with caveat
Options: On or off
Default: Off
Depends on: Does not fully work. The part that forces the calculation to "from gross" has no effect.
Rule: commission as a discount does not work
Checked: Confirmed in code, 5 Aug 2026
Order of discount, fee, commission and tax — Everyone · Not a setting
Options: Not changeable
Default: Discount, then platform fee, then commission, then tax
Depends on: Changing the order changes every number. This question is already answered.
Rule: the order of operations is fixed
Checked: Confirmed in code, 5 Aug 2026
Currency — Per vendor · Supported
Options: Over thirty currencies
Default: None
Depends on: Yen and won have no decimal places; most others have two.
Checked: Confirmed in code, 5 Aug 2026
How capacity is limited — Per vendor · Supported
Options: No limit · limit by bookings · limit by people · every booking needs approval
Default: None
Depends on: Changes how a booking is counted and whether it needs approval. Limit-by-bookings counts one per booking however large the party; limit-by-people counts one per person.
Rule: there are four kinds of capacity
Checked: Confirmed in code, 5 Aug 2026
How many places a slot has — Per vendor · Supported with caveat
Options: A whole number
Default: None
Depends on: Only applies to the two limited kinds. The limit is not enforced when a booking is created — see the rule.
Rule: bookings can exceed capacity
Checked: Confirmed in code, 5 Aug 2026
Minimum party size — Per vendor · Supported
Options: A whole number
Default: None
Depends on: Seat-limited slots only. The slot disappears from the booking page once fewer places remain than the minimum.
Rule: a seat-limited slot hides itself
Checked: Confirmed in code, 5 Aug 2026
Cut-off time, how far ahead people can book, blackout dates — Per vendor · Not established
Options: Unknown
Default: Unknown
Depends on: Not located in the code yet. Do not commit to this for a client.
Checked: Not established
Branding and appearance of the booking page — Per vendor · Supported
Options: Not yet detailed
Default: None
Checked: Confirmed in dev — a settings page exists for it, 5 Aug 2026
Which guest details are collected — Per vendor · Supported
Options: A configurable form
Default: None
Depends on: Hotel partners can require extra fields of their own.
Checked: Confirmed in dev, 5 Aug 2026
Language — Per vendor · Supported
Options: English and Japanese seen
Default: English
Checked: Confirmed in dev, 5 Aug 2026
Which experiences a partner may sell — Per partnership · Supported
Options: Visible or not visible, per experience
Default: Not visible
Depends on: Requires an active partnership. Publishing to the vendor's own page does not offer anything to a partner.
Rule: the vendor chooses what a partner may sell
Checked: Confirmed in code, 5 Aug 2026
Commercial terms for a partner — Per partnership · Supported
Options: A sales model, optionally overridden per experience
Default: The vendor's default sales model
Depends on: One partner can have different terms on different experiences.
Rule: the vendor chooses what a partner may sell
Checked: Confirmed in code, 5 Aug 2026
Partnership state — Per partnership · Supported
Options: Invited · active · inactive · rejected · cancelled
Default: Invited
Depends on: Only active partnerships can sell.
Rule: only an active partnership can sell
Checked: Confirmed in code, 5 Aug 2026
What happens to live bookings when a partnership stops — Per partnership · Not established
Options: Unknown
Default: Unknown
Depends on: Real money and real guests. Do not commit to this for a client.
Checked: Not established
Before promising anything: several entries above look like settings and are not — the order money is worked out in, the propose-changes behaviour, and whether the status control appears are all fixed in code or set per environment. Two are marked unknown. Two are marked partly and the caveat matters.