Skip to main content
GullySystem
Hospitality

Loyalty and Offers for Resorts

Apply customer reward and promotional rules to eligible purchases.

Retail and POS

Does this function belong in your operation?

Use when repeat purchases support a defined loyalty or promotional programme.

A customer earns or redeems a configured reward.

Returning guests earn points on cottage nights and meals. An off-season offer, such as a free dinner on a third night, is set against the stay. The reservations manager sees which offer was used.

Bring the records the workflow depends on.

  • Customer identifiers and permissions
  • Earning and redemption rules
  • Offer dates and exclusions

Outputs to check

  • Customer reward ledger
  • Offer application and redemption record
  • Expiry and reversal statement

Follow the loyalty and offers workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Define the programme

    Approve earning, eligibility, redemption and expiry rules.

  2. 2. Identify the customer

    Use the permitted account or contact reference.

  3. 3. Record eligible purchase

    Calculate the reward from the accepted transaction.

  4. 4. Redeem under the rules

    Check the available balance and apply the authorised offer.

  5. 5. Reconcile changes

    Adjust returns, expiry and approved corrections with their source references.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Counter staff

Types the number, and the offer is already on the bill.

Whoever sends the messages

Picks a list, such as customers who have not come since the last festival, and sends one message that suits them.

Owner

Reads two things: the regulars who have drifted away, and what the last scheme actually cost.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Return after redemption

Apply the agreed reversal policy and show any resulting adjustment.

Duplicate customer identity

Review balances and permissions before merging accounts.

Offer withdrawn early

Record the effective decision and treatment of already accepted transactions.

Can this work independently?

Loyalty depends on eligible customer transactions and a permitted customer identifier. It can accept reviewed imports, but POS or invoicing links provide current earnings and redemptions. Messaging and refunds are separate processes; a reward balance is not automatically cash payable to the customer.

Systems and records it connects with

  • Point of sale billing: Counter sales, tender records and authorised returns.
  • Product management: Item identifiers, units and controlled variant definitions.
  • WhatsApp and SMS: Permitted message content and channel delivery responses.
  • Multi-outlet stock: Outlet quantities and acknowledged transfer movements.

Configure, test and introduce the workflow.

  • Rules matter here. Tell us how customers earn and spend points and which offers you run, and a written note comes back for approval.
  • Send phone numbers and names from wherever you keep them. A trial import arrives with duplicates marked. Counter staff bill a few sample sales. Points and offers apply, and corrections go into the setup.
  • You write or approve the wording. Templates for WhatsApp or SMS come back for the person who sends them.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Rewards follow eligibility rules.
  • Redemption cannot exceed the permitted balance.
  • Returns apply the agreed reward reversal.
Resorts

How the business operates.

A resort has more to sell than rooms. Guests buy a cottage for the weekend, a day pass for the family, a hall for a wedding, and an activity slot on arrival.

Cottages, rooms and rate plans

Set up cottage and room types with season, weekend and agent rates, and room-only, breakfast and full-board plans, so a booking quotes the right rate for the dates asked.

Reservations and the room chart

See every cottage against every date, take advances, move a guest and refuse a second booking on nights already held. Online travel site bookings arrive only through a channel manager that you run.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Cottages, villas and rate plans. Enter each cottage, villa and room with its type, capacity and features. Weekday, weekend, season and package rates apply to the dates a guest chooses.
  • Reservations and availability calendar. See every unit by date on one chart. Holds, changes and cancellations update the chart at once, so a unit cannot be sold twice.
  • Enquiries and quotations. Record where each enquiry came from. Send a quotation with rooms, meals and activities, and chase it until it is confirmed or closed.
  • Front desk, ID proof and check-in. Arrivals and departures are listed for the day. Guest details and ID proof are recorded at check-in and kept with the guest’s history.

Operational bottlenecks to check

Day outing guests are counted by hand

Passes are sold at the gate against a notebook, and lunch covers, pool entries and the day’s collection rarely match. The count differs each evening.

Package prices do not reach the bill

A weekend package bundles the cottage, meals and one activity, and the folio shows each item at its list rate. The guest waits at the desk.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Enquiry

    A guest, agent or planner asks by phone, web form or message. Dates, party size, rooms, meals and any event needs are recorded against one contact.

  2. 2. Quotation and advance

    Rooms or passes are held at the rate plan for those dates, with meals and activities added as a package. The advance and cancellation terms are stored with the booking.

  3. 3. Arrival

    Reception opens the day’s list, takes the ID proof, assigns the cottage and tells housekeeping and the restaurant who is arriving and what was asked for.

  4. 4. Stay and visit

    Meals, spa, activities and extra services post to one folio. Each day guest enters on a pass. Group counts update as people come in.

  5. 5. Checkout

    One bill is settled across rooms, dining and activities, the advance is applied and the cottage is released to housekeeping.

  6. 6. Follow-up

    Guests receive a thank-you message and a note about the next season. Corporate and wedding clients are logged for a repeat booking.

Industry reports to connect with

  • Occupancy by cottage type and night
  • Arrivals, departures and cottages ready for the day
  • Day outing headcount and meals by date and group
  • Takings by department: rooms, dining, activities and events

Questions before implementation.

When should resorts consider loyalty and offers?

Use when repeat purchases support a defined loyalty or promotional programme. A customer earns or redeems a configured reward.

What should we bring to the requirements discussion?

Bring anonymised examples of Customer identifiers and permissions; Earning and redemption rules; Offer dates and exclusions. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Apply customer reward and promotional rules to eligible purchases. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Customer consent, promotion terms and financial treatment require approved business rules.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Rewards follow eligibility rules. Use this check when reviewing the first working version.

Talk to us

Discuss loyalty and offers for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements