AdrasisAdrasis

Contracts & setup

Setup flow

Setup prepares the information and operating terms for a new property, supplier or organization. For example, complete a new hotel's rooms, contract and channel connections before sales begin.

Three starting points

Record Information to prepare Result
Property Catalog content, rooms, contract and channel connections A property record with reviewed information and sales terms
Supplier Connection, source-code mappings and contract A supply source with agreed products and terms
Organization Users, branding, language, currency and default rules The team's workspace

Each flow defines the relationship, collects information, obtains required signatures and checks the conditions for use.

Add a property

Property setup: relationship, configuration, signature and opening for sale
Prepare property content and commercial terms before sales begin.

Check room types, capacities, images and descriptions. Then prepare the contract and channel connections. Adrasis AI Operator can prepare available actions; changes apply after your approval. See Property.

Add a supplier

Supplier setup: connection, contract, mapping and activation
Match the supplier's codes to their catalog records.

Suppliers may use different codes for the same room or meal plan. Review suggested mappings, complete missing matches and check the contract terms. The AI Operator can suggest matches; you decide which record to use.

See Receive supplier data for transfers and Mapping and review for source codes.

Add an organization

Organization setup: application, activation, defaults and opening for use
Prepare the new workspace's users and settings.

Check branding, language and region, currency and default rules. Each organization keeps its users, catalog, contracts and payment settings separate.

After the application is approved, the organization administrator names an authorized signer. Three initial agreements are signed through one private link. The signer does not need an account. Signature status is tracked separately from organization creation, and the administrator retrieves completed documents from the Console. See Sign initial agreements.

Track progress

The flow shows completed steps and missing information. Review the preview before applying changes. You can pause and resume the process.

Common items requiring review:

  • Missing mappings: Match new room, feature or category codes to the catalog.
  • Missing content: Complete required images and descriptions.
  • Contract exceptions: Check property-specific terms.
  • Connection approval: Follow the channel's required tests and approvals.

Example AI Operator requests

  • "Extract the property's name, address and room count from this email and prepare its setup."
  • "Suggest catalog room-type matches for the new supplier's room codes."
  • "Is anything missing from the new organization's branding, language, currency or default rules?"
  • "Prepare a preview to activate properties for the supplier whose first data transfer succeeded."

Requests to view information do not change records. Actions that change records require approval before they apply.

Where to next