Stop Sale Workflow
How stop sale data flows from hotel to tour operator — creation, propagation, and integration patterns.
What Is a Stop Sale?
A stop sale signals that a property (or specific room type) is not available for sale on specific dates. It is distinct from an actual booking — Ananas GDS is not a booking system. Stop sales are informational constraints distributed to tour operators so they can suppress those dates in their own sales channels.
Availability Status Codes
| Code | Label | Meaning |
|---|---|---|
0 |
Available | No restrictions. Full allotment available. |
1 |
Stop Sale | Property not available for this date. |
2 |
On Request | Availability subject to hotel confirmation. |
3 |
Limited | Limited availability — allotment running low. |
4 |
Closed | Property closed (seasonal or maintenance). |
Hotel Creates a Stop Sale
The hotel goes to Stop Sale Calendar , clicks on a date or range, selects the status code, optionally enters an allotment count and room type, and saves. The event is stored immediately and is available to all connected tour operators via the API.
Tour Operator Reads Stop Sale
The TO's integration polls
/api/v1/stop-sale/{token}/
and updates their inventory system accordingly. For real-time updates, the TO can subscribe to
stopsale.created
,
stopsale.updated
, and
stopsale.cancelled
webhooks instead.
Allotments
An allotment is the number of rooms available under a specific contract — either a series allotment (S) or a group allotment (G). Allotments are attached to stop sale events and are visible to TOs with an
active contract that includes allotment access. The
ss_deadline
field on a contract specifies how many days before the travel date allotment rights expire.