> For the complete documentation index, see [llms.txt](https://resources.atriptech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.atriptech.com/api-document/product-guides/booking/optional-ancillaries/baggage-and-seat-productcode-freshness.md).

# Baggage and seat productCode freshness

{% hint style="info" %}
💬 **Need help?** If you're stuck, ask Eva in the Help Center for instant diagnostics.

<a href="https://www.atriptech.com/" class="button primary" data-icon="comments">Ask Eva</a>
{% endhint %}

Use this page when seat or baggage selection fails because the ancillary mapping may be stale.

### Short answer

Treat baggage and seat `productCode` values as booking-context data, not as reusable catalog IDs.

If the verify context, offer context, itinerary, passenger mix, or booking timing changed, refresh ancillaries before `order.do`.

### FAQ

#### Can I reuse an old baggage `productCode`?

Not safely.

Use the `productCode` returned by the current ancillary response for the current booking context.

#### Can I reuse an old seat selection?

Not safely.

Seat availability can change before booking or ticketing.

#### When should I refresh ancillaries?

Refresh them when the booking context changed or when booking was delayed.

### What freshness means here

A `productCode` is only meaningful inside the current booking context.

That context includes:

* current itinerary
* current passenger mix
* current verify or offer state
* current ancillary response

Do not treat ancillary codes as long-lived static values.

### What makes ancillary selection stale

Refresh baggage or seat selection when any of these changed:

* `sessionId`
* `OfferId`
* target flight
* segment structure
* passenger count or passenger type
* fare or inventory state
* booking delay long enough to make the old context unreliable

### Baggage freshness rules

#### Use the latest baggage response

Use the baggage `productCode` from the current `getLuggage.do` response.

#### Keep segment mapping exact

Make sure each baggage selection still matches the correct segment.

#### Keep connected-direction selection consistent

For connecting flights, baggage may need to stay consistent across connected segments in the same direction.

### Seat freshness rules

#### Use the latest seat response

Use seat data from the current `seatAvailability.do` response.

#### Do not assume the seat still exists later

Seat inventory can change before booking and again at ticketing.

#### Keep fulfillment behavior explicit

Set the seat handling mode in `order.do`.

This controls what happens if the selected seat is gone at fulfillment time.

### Common failure signals

Typical stale-ancillary failures include:

* `309` — ancillary `productCode` is invalid or stale
* `409` — baggage `productCode` does not match the segment
* seat or baggage mismatch after the session or offer changed

### Quick decision rule

Use this rule in production:

* new `sessionId` or new `OfferId` — refresh ancillaries
* changed itinerary or passenger mix — refresh ancillaries
* delayed booking — refresh ancillaries before `order.do`

### Common mistakes

#### Reusing baggage `productCode` across a new verify session

Do not do this.

A new `sessionId` means the old ancillary context may be stale.

#### Reusing seat selections after itinerary changes

Do not do this.

Even small flight changes can break seat mapping.

#### Treating `productCode` like a permanent SKU

Do not do this.

It is context-bound booking data.

### Best practice

Keep ancillary selection close to order creation.

If booking is delayed, rerun ancillary lookup before `order.do`.

### Related pages

* [Seats](/api-document/product-guides/booking/optional-ancillaries/seats-and-baggage.md)
* [Baggage](/api-document/product-guides/booking/optional-ancillaries/baggage.md)
* [Verify](/api-document/product-guides/booking/booking-step-guides/verify.md)
* [Get Offer](/api-document/product-guides/booking/booking-step-guides/get-offer.md)
* [Create Order](/api-document/product-guides/booking/booking-step-guides/create-order.md)
* [Error Codes](/api-document/support-and-reference/troubleshooting-and-support/errors-handing.md)