Before you start
Configure the fee before offering a paid extra. Managing the catalog, deciding requests and collecting payment require their respective permissions.
-
Open the Extras catalog and enable only services the team can deliver, setting each fee, eligible units and approval requirement. This gives the team a consistent offer to review instead of promising an extra without checking its scope.
Prepare the service catalog Garden studioMake the stay your own
Late check-outStay until 14:00COP 80,000Airport pickupArrival transferCOP 120,000Available to request- Service catalog
- Fee and eligible units
-
Open the guest request and read its stay, service, price and relevant travel details before approving or declining it. The decision should reflect what the team can provide for this guest and the price attached to the request.
Decide on the guest request
Mon 26 OctAlex’s request
Late check-outRequested until 14:00COP 80,000Awaiting decisionDeparture windowAvailability determines approvalFor review- Decision
- Approve or decline
-
Use the supported payment action where needed, then follow the linked task. Keeping delivery separate prevents a payment result from being mistaken for a completed service.
Follow payment and delivery Airport pickupFrom yes to delivered
Request approvedFri 23 Oct · 14:05ApprovedPickup taskTeam follow-up attachedOpenApproved request- Collection
- Separate payment result
Check the result
The request has a recorded decision, with any linked charge and fulfillment task showing their own states.
Limits and prerequisites
Suggestions such as airport pickup are not automatically enabled. Approval and payment do not themselves complete the service.
