Question 1

Is the current hotel inventory bookable?

Accepted Answer

The Partner Preview flow can create a clearly marked $0 simulation for demonstration. It does not reserve a real room, contact a supplier or create a financial charge. Live booking will open only after an approved hotel supplier and payment flow are connected and verified.

Question 2

Where does Nomadly destination data come from?

Accepted Answer

Destination names and coordinates in this showcase are based on Wikidata structured data under CC0. Editorial descriptions and visual assets were created specifically for Nomadly.

Question 3

Are the displayed prices real?

Accepted Answer

No. Any price shown for a Partner Preview stay is an indicative UX example, not an offer, quote or live rate. Contracted supplier rates will replace preview values.

Question 4

Can partners provide their own content?

Accepted Answer

Yes. The partner workflow is designed to accept approved property facts, room details, policies, imagery and editorial context with clear ownership and review status.

Question 5

How will availability be updated?

Accepted Answer

Live availability will come from the contracted provider integration. The production integration workers remain disabled until credentials, mapping and operational checks are complete.

Question 6

Does Nomadly copy reviews from other travel sites?

Accepted Answer

No. This showcase does not scrape or republish third-party reviews, ratings or proprietary hotel descriptions.

Question 7

Which currencies will be supported?

Accepted Answer

The platform already models multiple currencies. Final currency availability and rate refresh rules will be confirmed before commercial launch.

Question 8

Will guests receive instant confirmation?

Accepted Answer

That is the target experience, subject to provider confirmation semantics. The final booking flow will clearly distinguish pending, confirmed and failed states.

Question 9

How are cancellations handled?

Accepted Answer

Live cancellation terms will be shown before payment and stored with the order. Partner Preview simulations carry no real cancellation terms because they do not create supplier bookings.

Question 10

Can Nomadly support boutique and independent hotels?

Accepted Answer

Yes. Rich editorial merchandising is particularly useful for distinctive independent properties that need more context than a rate-and-photo grid.

Question 11

Is the partner portal ready?

Accepted Answer

A secured backoffice is deployed for demonstration. Partner-specific roles, onboarding and reporting remain part of the commercial integration phase.

Question 12

How is personal data protected?

Accepted Answer

Production secrets are held in 1Password, databases are not publicly exposed, transport uses TLS and server access is key-only. Privacy and retention controls will be reviewed before onboarding guests.

Question 13

Are payments active?

Accepted Answer

No real payments are active. The partner demo uses an isolated $0 simulator, never renders card fields and never sends PAN or CVC data. Payment credentials and webhooks remain disabled.

Question 14

Can we launch in one destination first?

Accepted Answer

Yes. A destination-by-destination rollout is preferable because supplier mapping, content quality, support and booking verification can be validated in a controlled scope.

Question 15

How does Nomadly select featured destinations?

Accepted Answer

The showcase uses a curated global mix. In production, merchandising can combine partner priorities, seasonal relevance, content quality and verified inventory health.

Question 16

Are the showcase images photographs of real hotels?

Accepted Answer

No. They are original generated editorial visuals depicting fictional properties and are not intended to represent a particular hotel.

Question 17

What happens when live inventory arrives?

Accepted Answer

Preview records can be removed or isolated, provider properties are imported with stable identifiers, and the same build, migration, smoke and backup gates are repeated.

Question 18

How can a partner begin?

Accepted Answer

Agree the pilot destination and commercial model, provide a test credential set and sample property mapping, then complete a joint content and booking certification checklist.

Question 19

Who owns and approves property content?

Accepted Answer

The supplying partner remains the source for operational facts and media rights. Nomadly can edit structure and voice, but publication should retain an owner, approval state and review date for every partner record.

Question 20

How are content changes reviewed?

Accepted Answer

Material changes should move through draft, partner review and publish states. Safety, policy, fee, accessibility and room-configuration changes receive priority because they can directly affect a booking decision.

Question 21

Can content be localized?

Accepted Answer

Yes. Destination and property narratives can be localized while stable identifiers, coordinates, amenities and policy fields remain shared. Machine-assisted drafts should still receive human review for meaning, tone and local accuracy.

Question 22

What property data is needed for a pilot?

Accepted Answer

At minimum: stable property and room identifiers, coordinates, address, room names and occupancy, amenities, policies, fees, tax treatment, availability and rate semantics, image rights, support contacts and cancellation rules.

Question 23

How does inventory mapping avoid duplicate hotels?

Accepted Answer

Provider identifiers are mapped to a canonical property record and checked against location and normalized property facts. Ambiguous matches are held for manual review rather than automatically merged.

Question 24

What reporting can partners expect?

Accepted Answer

The planned partner view can cover content completeness, search visibility, booking funnel, confirmation outcomes, cancellations and operational exceptions. Commercial definitions and retention periods will be agreed before launch.

Question 25

How are incidents handled?

Accepted Answer

A production pilot needs named escalation owners, monitored health checks, provider and payment stop conditions, log and booking evidence, plus a documented rollback path. The current showcase already uses health, backup and fail-closed deployment gates.

Question 26

Is accessibility information supported?

Accepted Answer

Yes. Accessible rooms, step-free paths, lift dimensions, bathroom configuration and assistance policies should be captured as specific facts rather than a single generic accessibility label.

Question 27

Can room types have their own content?

Accepted Answer

Yes. Room-level merchandising can include a distinct name, dimensions, view and orientation, bed and occupancy, bathroom details, accessibility, imagery, inclusions and policy notes linked to the provider room identifier.

Question 28

How often should property content be refreshed?

Accepted Answer

Operational facts should be updated whenever they change and formally reviewed on an agreed schedule. Seasonal services, renovations, construction notices and temporary closures need shorter review windows.

Question 29

What is required before enabling real payments?

Accepted Answer

An approved payment provider, signed commercial and data-processing terms, webhook and idempotency testing, reconciliation and refund procedures, fraud controls, card-data scope review and a successful end-to-end production certification.

Question 30

What defines pilot launch readiness?

Accepted Answer

A pilot is ready when inventory mapping, content ownership, pricing and cancellation semantics, payment and confirmation paths, monitoring, support escalation, backup and rollback have all passed the jointly reviewed checklist.