How to use Terra /

Before you begin

Begin with the brand experience, then follow its primary action into the interactive studio or private workspace.

Create an account in Terra and work in its own private workspace. Accounts and records from another Lumia product are separate. Independent stay operators and small travel teams that curate their own inventory and want an enquiry-led itinerary workflow. Terra is suited to offerings where a person reviews dates and details before confirming availability through the operation's actual booking process.

Follow the workflow below to understand the application. Contact Lumia for a guided walkthrough; account access is private. An exported file reflects the record at the time of export.

Create the field guide inventory

Add a stay with its description, timezone, supported currency, nightly price and illustrative map position. Upload an owned image and its credit when using photography or artwork. Add activities with a duration and per-guest price in the stay's currency. The evaluated inventory mode is operator confirmed, so listing a stay does not establish live availability.

Choose the stay, dates and guests

Select the stay using the field-guide controls, then enter arrival, departure and guest count. The terrain can be rotated and reset as an exploratory visual. Its markers are illustrative positions; the tested selection flow uses the field-guide buttons rather than clicking pins on the scene.

Build a valid activity schedule

Place activities at explicit times within the stay's local dates. Inspect duration and avoid overlapping entries; adjacent activities are permitted. Review the lodging and activity amounts before saving. The estimate uses the entered nightly price, number of nights and per-guest activities, without silently adding transport or other applicable charges.

Request and record an operator response

Save the itinerary, export its PDF if useful and request the current version with contact details. The operator reviews the frozen request and records a response with a note. Reload the saved journey to inspect that response. A local confirmed state does not charge the traveller or create a reservation in another system.

Operating the product

Keep the stay timezone and pricing units accurate before publishing real inventory. A per-guest activity price differs from a group price, and a nightly price must be reviewed alongside the selected number of nights and any exclusions.

Use image credits that explain the actual source and rights context. Generated fictional scenery should remain identified as such rather than imply that it depicts the listed real property or an experience a traveller will encounter.

When a schedule is rejected, inspect the activity's local time and full duration, including the end instant. A start that falls on a permitted date is insufficient if the activity ends beyond the stay or overlaps another entry.

When the working itinerary changes after a request, compare it with the request snapshot before responding. The original request deliberately retains its earlier dates and estimate; submit the revised version when that is the decision the operator should review.

Write operator notes that state what was actually checked and what remains outstanding. Arrange any real booking, payment or traveller communication through a verified process, and do not use the application's local status as evidence that those external actions occurred.