CruiseAPI
Home › Technical Guides › Operations
Operations

Post-Booking Modifications, Cancellations & Fare Rules (/v2/operations)

Manage self-service cancellations, tiered penalty calculations, cabin upgrades, and manifest corrections after ticket issuance.

Parsing Cruise Line Cancellation Penalty Schedules

Cruise cancellation policies are time-stepped schedules tied to days before sailing (DBS) and fare type. A standard refundable booking might incur zero penalty 90 days prior to departure, forfeit the deposit at 75 days, and escalate to 50%, 75%, or 100% penalty tiers inside 30 days—whereas promotional non-refundable fares carry immediate deposit forfeiture.

Exposing a machine-readable penalty_schedule array via /v2/operations lets travel portals display exact refund eligibility before a customer confirms a cancellation, reducing support tickets and chargeback disputes.

  • Include exact UTC and ship-port cutoff timestamps for each penalty tier.
  • Provide a dry-run preview mode (simulate=true) before executing cancellations.
  • Break down refundable taxes and port fees separately from non-refundable fares.

Cabin Upgrades, Repricing, and Name Corrections

Travelers frequently request category upgrades, dining time swaps, or minor spelling fixes after booking. Not every change is permitted under every fare code: changing the lead passenger name can trigger a full cancel-and-rebook at current prevailing rates on certain lines, whereas swapping a second guest may incur only a flat administrative fee.

The /v2/operations endpoint standardizes allowed_actions flags per booking so agency dashboards and self-service portals enable only valid modifications for the active fare class.

Balance Reminders and Final Payment Settlement

Many cruise bookings are secured months in advance with an initial deposit, leaving a remaining balance due 60 to 120 days before embarkation. Querying payment_schedule milestones through /v2/operations lets SaaS portals automate reminder emails and submit secondary payment settlements before the cruise line auto-cancels an unpaid PNR.

Common Post-Booking Operations & Constraints

OperationTypical Endpoint ActionRepricing RiskDry-Run Recommended
Cancel SimulationPOST /v2/operations/cancel?dry_run=trueNone (read-only)Yes (mandatory)
Commit CancellationPOST /v2/operations/cancelPenalty tier appliedFollows simulation
Cabin Category UpgradePATCH /v2/operations/cabinPrevailing fare deltaYes
Guest Name CorrectionPATCH /v2/operations/guestsFee or rebook if lead paxCheck allowed_actions
Balance PaymentPOST /v2/operations/paymentNone if paid by due dateVerify balance_due

Always check the booking's allowed_actions capability map before presenting edit controls to end users.

Worked Illustration: Dry-Run Cancellation Penalty Preview

This worked illustration evaluates a cancellation request 42 days before sailing on a $2,400 booking:

  1. Agency calls POST /v2/operations/cancel with booking_id and dry_run=true.
  2. Gateway evaluates the booking's stored penalty tier: 45–30 days prior = 50% of cruise fare ($1,000 penalty on $2,000 fare).
  3. Government taxes and port fees ($400) remain 100% refundable under supplier rules.
  4. API returns refundable_amount: $1,400 and penalty_amount: $1,000, requiring explicit confirmation to commit.

Worked Illustration Summary: Two-step dry-run previews eliminate accidental high-penalty cancellations and display exact refund math.

Post-Booking Operations Checklist

  • Expose machine-readable penalty_schedule milestones at booking time.
  • Implement dry_run=true previews for every cancellation and upgrade flow.
  • Respect lead-passenger immutability rules surfaced in allowed_actions.
  • Track final_payment_due dates to prevent automated supplier cancellations.
  • Log every post-booking mutation with operator ID and timestamp.
  • Sync refund receipts and credit memos back via asynchronous webhooks.

Frequently Asked Questions

Are government port taxes refunded if a traveler cancels inside the 100% penalty window?

In most jurisdictions, unincurred government taxes and port authority fees are refundable even when the cruise fare itself is 100% penalized, and /v2/operations itemizes both separately.

What happens if an agency misses the final payment due date?

Cruise lines typically release the stateroom back to inventory and apply applicable cancellation penalties. Automated balance alerts via /v2/operations prevent missed deadlines.

Can a traveler upgrade from an Interior to a Balcony cabin via API?

Yes. When allowed_actions includes CABIN_UPGRADE, the API quotes the fare difference against current inventory and updates the PNR atomically.

Why does changing the primary guest sometimes trigger repricing?

Supplier rules often treat replacing all original passengers or the primary traveler as a new reservation, forfeiting locked promotional pricing.

Primary Standards & Industry References

  • OpenTravel Alliance Cruise Modification & Cancellation Messages
  • ISO 8601 — UTC Timestamp & Duration Standards
  • CLIA Passenger Bill of Rights & Booking Transparency Guidelines

Related Technical Guides