@v-office/website-sdk 2.10.0 → 2.12.0

package/dist/instructions/versions/2.12.0/MIGRATION.md

@@ -0,0 +1,194 @@
+# Migration: 2.11.0 to 2.12.0
+
+2.12.0 adds optional discount information to priced legacy v9 search results,
+normalizes empty quote booking-card lines across v9 and v10, and completes v10
+card-level pre-modifier totals across all modifier presentation paths. It also
+rejects unsupported v9 flexible-period searches before transport and restores
+empty-query inventory browsing on v9. Existing supported calls remain valid
+without changes.
+
+## 1. Reuse the Shared Discount Output
+
+Legacy v9 now uses the same optional shape introduced for v10 in 2.11.0:
+
+```ts
+type SearchDiscount = {
+  readonly formattedOriginalTotal: string;
+  readonly applied: readonly {
+    readonly label: string;
+    readonly formattedAmount: string;
+  }[];
+};
+```
+
+For exact-period results, read `discount` from the item:
+
+```ts
+result.items[0]?.discount;
+```
+
+For nearby suggestions, read it from the individual alternative period:
+
+```ts
+result.alternatives?.[0]?.alternativePeriods[0]?.discount;
+```
+
+## 2. Understand the Legacy v9 Mapping
+
+For priced v9 results:
+
+- `calc.total` remains the final `formattedTotal`.
+- `discount` is present only when `calc.oTotal` is greater than `calc.total`.
+- `discount.formattedOriginalTotal` is formatted from `calc.oTotal`.
+- A non-empty `calc.discountName` becomes the label of the single applied entry.
+- The applied amount is the formatted negative difference
+  `calc.total - calc.oTotal`.
+- If the backend supplies no usable discount name, `applied` is empty while the
+  formatted original total remains available.
+
+The SDK omits `discount` when there is no final total or when the original total is
+not greater than the final total.
+
+## 3. Account for Backend Detail Differences
+
+v9 exposes one aggregated discount name and therefore returns at most one
+`discount.applied` entry. v10 search can expose multiple `discount.applied`
+entries. Consumers should render the array without assuming a fixed length.
+
+Both backends return presentation-ready localized strings. Backend numeric amounts
+and internal modifier keys are not part of the public output.
+
+## 4. Account for Booking-Card Cleanup
+
+Quote booking cards on both backends now omit numeric zero-value lines without
+subitems from the `other` section, matching the existing handling of included and
+tax sections.
+
+- A zero-only `other` section is omitted.
+- A mixed `other` section retains its non-zero lines unchanged.
+- Lines with subitems remain available because they still carry descriptive
+  content.
+
+No required booking-card property was added and the public schema remains
+source-compatible. Runtime output can contain fewer empty rows. Sites that used a
+zero-value row to represent a declined service should use explicit selection or
+service state instead of inferring that state from the price breakdown.
+
+## 5. Render v10 Quote Modifiers
+
+On v10, an item at `bookingCardInformation.sections[].lines[].item` can include:
+
+```ts
+{
+  modifiers?: readonly {
+    label: string;
+    amount: string;
+  }[];
+  totalBeforeModifiers?: string;
+}
+```
+
+The card can also include `bookingCardInformation.totalBeforeModifiers`.
+`appliedCharge` and `total` are the final amounts after modifiers. The
+corresponding `totalBeforeModifiers` is the formatted amount before modifiers and
+is omitted when there is no non-zero net modifier effect. `modifiers` is omitted
+when the item has none; entries with the same localized label are grouped and
+their amounts are summed before formatting.
+
+Included, tax, and other lines attach their adjustments to `item.modifiers`.
+Negative modifiers from backend lines that do not map to those sections may
+instead appear as dedicated booking-card lines. In 2.12.0, card-level
+`totalBeforeModifiers` accounts for both forms. v9 quote cards omit these fields.
+
+Example for `de-DE`:
+
+```json
+{
+  "bookingCardInformation": {
+    "sections": [
+      {
+        "lines": [
+          {
+            "item": {
+              "position": "Inklusivpreis",
+              "appliedCharge": "1.554,00 €",
+              "modifiers": [
+                {
+                  "label": "Frühbucher/Last-Minute",
+                  "amount": "-140,00 €"
+                }
+              ],
+              "totalBeforeModifiers": "1.694,00 €"
+            }
+          }
+        ]
+      }
+    ],
+    "total": "1.596,70 €",
+    "totalBeforeModifiers": "1.736,70 €"
+  }
+}
+```
+
+Do not assume a voucher appears as its own section line. Use
+`quote.voucher.status` for voucher application status and the booking-card fields
+for price presentation. To keep price arithmetic visible, render the pre-modifier
+amount, modifier rows, and final amount separately. Whether to display or strike
+through a reference price remains the consuming site's product and legal
+decision.
+
+## 6. Keep Flexible Search Disabled on v9
+
+No configuration or supported request migration is required. Legacy v9 now rejects
+the unsupported flexible-period keys `month`, `dates`, `nights`, and `weekend`
+before transport instead of silently returning an unpriced item list. Keep
+flexible search unavailable on v9 sites and use fixed `start`/`end` period
+queries. v10 flexible search is unchanged.
+
+The rejection is a `CoreSDKError` with operation `v9.search` and occurs before a
+GraphQL request is sent. The public `SearchSearchInput` type remains unchanged
+because its `query` field is an opaque query string.
+
+This release enriches v9 search output when its existing response contains
+sufficient discount data, removes empty quote breakdown rows from both backends,
+and can return the existing optional card-level `totalBeforeModifiers` in
+additional v10 cases.
+
+## 7. Remove Dummy Occupancy from Empty v9 Searches
+
+Legacy v9 now sends an empty backend-filter set as GraphQL `data: null` instead of
+`data: []`. An empty query can therefore browse the first page of searchable
+inventory under the configured rental scope:
+
+```ts
+await sdk.live.search.search({
+  locale: "de-DE",
+  query: "",
+});
+```
+
+Remove workarounds that inject `adults=1` only to make an empty query return
+results. Real occupancy, period, and non-empty backend filters keep their existing
+mapping. Pagination and `limit` still apply, and an undated result does not assert
+availability for a particular stay.
+
+## Recommended Verification
+
+1. Run a priced v9 exact-period search where the original total exceeds the final
+   total and verify the formatted values and label.
+2. Verify discounted v9 alternative periods independently.
+3. Run a v9 search without a discount and confirm existing rendering is unchanged.
+4. Verify a missing v9 discount name produces an empty `applied` array.
+5. Verify v9 rejects `month`, `dates`, `nights`, and `weekend` before transport.
+6. Run an empty v9 query and confirm it returns searchable inventory without a
+   dummy occupancy value.
+7. Recheck a discounted v10 search and confirm its existing multi-entry behavior
+   remains unchanged.
+8. Quote a v9 and v10 rental with a zero-value `other` service and confirm the
+   empty section is absent.
+9. Confirm a mixed `other` section retains only its non-zero lines.
+10. Quote a discounted v10 rental and render `item.modifiers`, item-level
+    `totalBeforeModifiers`, and card-level `totalBeforeModifiers`.
+11. Confirm a v9 quote continues to omit the modifier fields.
+12. Verify a v10 modifier rendered as a dedicated line still contributes to the
+    card-level `totalBeforeModifiers`.

package/dist/instructions/versions/2.5.0/MIGRATION.md

@@ -121,6 +121,12 @@ The public output type is unchanged, but v10 search cards now reflect the REST p
 - `property` is the minimal `{ id, nameOrLabel }` shape. Hydrate `property.location`, `property.images`, or `property.address` from `sdk.static.rentals.getRentals(...)` when a search card needs them.
 - Exact-period matches are returned in `items` with `formattedTotal`; nearby suggestions are returned in root-level `alternatives`, unchanged.
 
+Starting with 2.11.0, priced v10 items and alternative periods may also include
+optional localized `discount` details. See `../../search.md`.
+
+Starting with 2.12.0, legacy v9 maps the same optional shape from its aggregated
+original total and discount name when the original total exceeds the final total.
+
 ## Backend Behavior
 
 - Fixed-period and flexible searches are priced by the REST backend; occupancy is required for priced searches.

package/dist/{quote-Cs6jGoRS.mjs → quote-Qy_affum.mjs}

@@ -241,12 +241,12 @@ const toSections = ({ input, guestQuoteResult, locale, translations }) => Effect
 		locale,
 		translations
 	});
-	const sectionsOther = yield* toSectionsOther({
+	const sectionsOtherWithContent = (yield* toSectionsOther({
 		input,
 		guestQuoteResult,
 		locale,
 		translations
-	});
+	})).filter(hasSectionLineContent);
 	if (hasSectionLineContent(sectionsIncluded)) sections.push({
 		lines: [sectionsIncluded],
 		displayOrder: GuestQuoteBookingCardDisplayOrder.inclusive
@@ -255,8 +255,8 @@ const toSections = ({ input, guestQuoteResult, locale, translations }) => Effect
 		lines: [sectionsTax],
 		displayOrder: GuestQuoteBookingCardDisplayOrder.tax
 	});
-	if (sectionsOther.length > 0) sections.push({
-		lines: sectionsOther,
+	if (sectionsOtherWithContent.length > 0) sections.push({
+		lines: sectionsOtherWithContent,
 		displayOrder: GuestQuoteBookingCardDisplayOrder.other
 	});
 	return sections;

package/dist/{rentals-CFod9H4m.mjs → rentals-BG1diZoo.mjs}

@@ -1,4 +1,4 @@
-import { c as VofficeUnitDataFieldSchemas, d as VofficeUnitDataPropertyMetadata, f as parseVofficeFacilityData, i as toLocalizedString, l as VofficeUnitDataPropertyCategoryLabelKeys, m as parseVofficeUnitData, n as toImages, o as rentalsAllFeedbacksQuery, p as parseVofficeFeedbackData, r as toAddress, s as rentalsAllWithoutFeedbacksQuery, t as toRentalHighlights, u as VofficeUnitDataPropertyCategoryValues } from "./to-rental-highlights-B6a_fi0j.mjs";
+import { c as VofficeUnitDataFieldSchemas, d as VofficeUnitDataPropertyMetadata, f as parseVofficeFacilityData, i as toLocalizedString, l as VofficeUnitDataPropertyCategoryLabelKeys, m as parseVofficeUnitData, n as toImages, o as rentalsAllFeedbacksQuery, p as parseVofficeFeedbackData, r as toAddress, s as rentalsAllWithoutFeedbacksQuery, t as toRentalHighlights, u as VofficeUnitDataPropertyCategoryValues } from "./to-rental-highlights-BVikT4Iz.mjs";
 import { makeTranslate, renderLabeledAttributeValue, renderResolvedCustomAttribute, toCustomAttributeList, toResolvedCustomAttributeCategoryTranslationKey } from "@v-office/sdk-core";
 import { Effect } from "effect";
 //#region src/legacy-v9/parser/rentals/to-description.ts
@@ -91,9 +91,10 @@ const toRentalAttributes = ({ locale, translations, attributes, customAttributes
 	for (const { key, metadata } of PROPERTY_METADATA_ENTRIES) {
 		const value = knownAttributes[key];
 		if (!canRenderLabeledAttributeValue$1(value)) continue;
+		const label = yield* translate(metadata.labelKey, key);
 		const attribute = renderLabeledAttributeValue({
 			key,
-			label: yield* translate(metadata.labelKey, key),
+			label,
 			locale,
 			value
 		});
@@ -154,9 +155,10 @@ const toRentalVicinity = ({ locale, translations, attributes }) => Effect.gen(fu
 	for (const { key, metadata } of LOCATION_METADATA_ENTRIES) {
 		const value = knownAttributes[key];
 		if (!canRenderLabeledAttributeValue(value)) continue;
+		const label = yield* translate(metadata.labelKey, key);
 		const item = renderLabeledAttributeValue({
 			key,
-			label: yield* translate(metadata.labelKey, key),
+			label,
 			locale,
 			value
 		});
@@ -200,7 +202,8 @@ const toReviews = ({ locale, translations, rental }) => Effect.gen(function* ()
 		}];
 	}) ?? [];
 	if (parsedItems.length === 0) return void 0;
-	const summaryRating = roundRatingUp(parsedItems.reduce((ratingSum, item) => ratingSum + item.rating, 0) / parsedItems.length);
+	const averageRating = parsedItems.reduce((ratingSum, item) => ratingSum + item.rating, 0) / parsedItems.length;
+	const summaryRating = roundRatingUp(averageRating);
 	const summaryRatingTemplate = yield* translations.translate(locale, "reviews.summary.rating");
 	const summaryCountTemplate = yield* translations.translate(locale, "reviews.summary.count");
 	const classification = toClassification(summaryRating);

package/dist/{search-QlZrI7ue.mjs → search-BlL8vSPY.mjs}

@@ -1,5 +1,5 @@
-import { a as parseQueryParameters, i as collectQueryParameters, n as makeV9CustomAttributeFilterCapabilities, o as toQueryString, r as toBasicQueryInputs, s as applyVofficeFilterDerivedBasicQueryInputs } from "./client-DYAHnU5F.mjs";
-import { a as searchQuery, c as VofficeUnitDataFieldSchemas, m as parseVofficeUnitData, n as toImages, r as toAddress, t as toRentalHighlights } from "./to-rental-highlights-B6a_fi0j.mjs";
+import { a as parseQueryParameters, i as collectQueryParameters, n as makeV9CustomAttributeFilterCapabilities, o as toQueryString, r as toBasicQueryInputs, s as applyVofficeFilterDerivedBasicQueryInputs } from "./client-Bmxh2SAu.mjs";
+import { a as searchQuery, c as VofficeUnitDataFieldSchemas, m as parseVofficeUnitData, n as toImages, r as toAddress, t as toRentalHighlights } from "./to-rental-highlights-BVikT4Iz.mjs";
 import { CoreSDKError, STABLE_SEARCH_INPUTS, daysBetweenLocalDates, expandCustomAttributeFilterCompositions, parseChildrenAges, parseOccupancyCount, resolveExpandedCompositions, toFormattedSearchPrice, toIsoDateFromPeriodQueryDate, toStableSearchInputBackendQueryKeys, toStableSearchInputParameterValues, toStableSearchInputQueryKeys, toUnusedFilterKeys } from "@v-office/sdk-core";
 import { Effect } from "effect";
 //#region src/legacy-v9/parser/search/input/search-input-error.ts
@@ -79,9 +79,11 @@ const PERIOD_QUERY_KEYS = toStableSearchInputBackendQueryKeys({
 	backend: "v9",
 	group: STABLE_SEARCH_INPUTS.period
 });
+const UNSUPPORTED_FLEXIBLE_PERIOD_QUERY_KEYS = new Set(STABLE_SEARCH_INPUTS.period.keys.filter((key) => !PERIOD_QUERY_KEYS.has(key)));
 //#endregion
 //#region src/legacy-v9/parser/search/input/period/collect-period-query-parameters.ts
 const hasPeriodInput = (query) => parseQueryParameters(query).some(([key]) => PERIOD_QUERY_KEYS.has(key));
+const hasUnsupportedFlexiblePeriodInput = (query) => parseQueryParameters(query).some(([key]) => UNSUPPORTED_FLEXIBLE_PERIOD_QUERY_KEYS.has(key));
 const collectPeriodQueryParameters = ({ query }) => {
 	const { matchingParameters, remainingParameters } = collectQueryParameters({
 		query,
@@ -178,6 +180,7 @@ const toVofficeSorting = (sort) => {
 //#endregion
 //#region src/legacy-v9/parser/search/input/to-query-input.ts
 const toQueryInput = ({ query, sort, customAttributeFilterDefinitions, locale, translations }) => Effect.gen(function* () {
+	if (hasUnsupportedFlexiblePeriodInput(query)) return yield* failInvalidV9SearchInput("Legacy v9 search does not support flexible period query parameters \"month\", \"dates\", \"nights\", or \"weekend\". Use \"start\" and \"end\" for a fixed period.");
 	const compositionResult = expandCustomAttributeFilterCompositions({
 		capabilities: makeV9CustomAttributeFilterCapabilities(customAttributeFilterDefinitions),
 		customAttributeFilterDefinitions,
@@ -221,21 +224,41 @@ const toQueryInput = ({ query, sort, customAttributeFilterDefinitions, locale, t
 				alternatives: true,
 				sorting: toVofficeSorting(sort)
 			},
-			basicQueryInputs
+			basicQueryInputs: basicQueryInputs.length > 0 ? basicQueryInputs : null
 		},
 		unusedFilterKeys: compositionFilters.unusedFilterKeys
 	};
 });
 //#endregion
-//#region src/legacy-v9/parser/search/output/to-formatted-price.ts
-const DEFAULT_V9_SEARCH_CURRENCY$1 = "EUR";
-const toFormattedPrice = ({ locale, calc }) => {
-	if (calc?.total == null) return Effect.succeed(null);
-	return Effect.succeed(toFormattedSearchPrice({
+//#region src/legacy-v9/parser/search/output/to-search-price-fields.ts
+const DEFAULT_V9_SEARCH_CURRENCY = "EUR";
+const toSearchPriceFields = ({ locale, calc }) => {
+	if (calc?.total == null) return {};
+	const formattedTotal = toFormattedSearchPrice({
 		amount: calc.total,
-		currency: DEFAULT_V9_SEARCH_CURRENCY$1,
+		currency: DEFAULT_V9_SEARCH_CURRENCY,
 		locale
-	}));
+	});
+	if (calc.oTotal == null || calc.oTotal <= calc.total) return { formattedTotal };
+	const label = calc.discountName?.trim();
+	return {
+		formattedTotal,
+		discount: {
+			formattedOriginalTotal: toFormattedSearchPrice({
+				amount: calc.oTotal,
+				currency: DEFAULT_V9_SEARCH_CURRENCY,
+				locale
+			}),
+			applied: label == null || label.length === 0 ? [] : [{
+				label,
+				formattedAmount: toFormattedSearchPrice({
+					amount: calc.total - calc.oTotal,
+					currency: DEFAULT_V9_SEARCH_CURRENCY,
+					locale
+				})
+			}]
+		}
+	};
 };
 //#endregion
 //#region src/legacy-v9/parser/search/to-search-output-item.ts
@@ -258,26 +281,23 @@ const toSearchOutputItem = ({ locale, imageProxyBaseUrl, rentalHighlightPrioriti
 		attributes: data
 	});
 	if (highlights != null) item.highlights = highlights;
-	const formattedPrice = yield* toFormattedPrice({
+	if (includeFormattedTotal) Object.assign(item, toSearchPriceFields({
 		locale,
 		calc: rental.additional_voffice_data?.calc
-	});
-	if (includeFormattedTotal && formattedPrice != null) item.formattedTotal = formattedPrice;
+	}));
 	return item;
 });
 //#endregion
 //#region src/legacy-v9/parser/search/output/to-alternative-periods.ts
-const DEFAULT_V9_SEARCH_CURRENCY = "EUR";
 const toAlternativePeriods = ({ locale, alternatives }) => Effect.succeed((alternatives ?? []).flatMap((alternative) => {
 	if (alternative.fromdate == null || alternative.tilldate == null) return [];
 	return [{
 		start: alternative.fromdate,
 		end: alternative.tilldate,
-		...alternative.calc?.total == null ? {} : { formattedTotal: toFormattedSearchPrice({
-			amount: alternative.calc.total,
-			currency: DEFAULT_V9_SEARCH_CURRENCY,
-			locale
-		}) }
+		...toSearchPriceFields({
+			locale,
+			calc: alternative.calc
+		})
 	}];
 }));
 //#endregion

package/dist/{to-rental-highlights-B6a_fi0j.mjs → to-rental-highlights-BVikT4Iz.mjs}

@@ -5900,10 +5900,11 @@ const toRentalHighlights = ({ locale, translations, highlightPrioritization, cus
 			const attribute = customAttributes.byKey[highlightKey];
 			if (attribute === void 0) continue;
 			const binding = attribute.v9;
+			const value = binding === void 0 ? void 0 : knownAttributes[binding] ?? attributes.unknown[binding];
 			const highlight = renderResolvedCustomAttribute({
 				attribute,
 				locale,
-				value: binding === void 0 ? void 0 : knownAttributes[binding] ?? attributes.unknown[binding]
+				value
 			});
 			if (highlight != null) {
 				highlights.push(highlight);
@@ -5914,9 +5915,10 @@ const toRentalHighlights = ({ locale, translations, highlightPrioritization, cus
 		if (seenKeys.has(v9Key)) continue;
 		seenKeys.add(v9Key);
 		const metadata = VofficeUnitDataPropertyMetadata[v9Key];
+		const label = yield* translate(metadata.labelKey, v9Key);
 		const highlight = renderLabeledAttributeValue({
 			key: v9Key,
-			label: yield* translate(metadata.labelKey, v9Key),
+			label,
 			locale,
 			value: knownAttributes[v9Key]
 		});

package/instructions/CHANGELOG.md

@@ -4,6 +4,8 @@ This file is the versioned changelog index for the website SDK instructions.
 
 ## Versions
 
+- `versions/2.12.0/CHANGELOG.md`: `@v-office/website-sdk` 2.12.0 release notes.
+- `versions/2.11.0/CHANGELOG.md`: `@v-office/website-sdk` 2.11.0 release notes.
 - `versions/2.10.0/CHANGELOG.md`: `@v-office/website-sdk` 2.10.0 release notes.
 - `versions/2.9.0/CHANGELOG.md`: `@v-office/website-sdk` 2.9.0 release notes.
 - `versions/2.8.0/CHANGELOG.md`: `@v-office/website-sdk` 2.8.0 release notes.

package/instructions/MIGRATION.md

@@ -4,6 +4,8 @@ This file is the versioned migration index for the website SDK instructions.
 
 ## Available Guides
 
+- `versions/2.12.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.11.0 to 2.12.0.
+- `versions/2.11.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.10.0 to 2.11.0.
 - `versions/2.10.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.9.0 to 2.10.0.
 - `versions/2.9.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.8.0 to 2.9.0.
 - `versions/2.8.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.7.0 to 2.8.0.

package/instructions/README.md

@@ -1,7 +1,7 @@
 # Website SDK Instructions
 
 These instructions describe the current source targeted for
-`@v-office/website-sdk` 2.10.0. Package versions remain unchanged until the release
+`@v-office/website-sdk` 2.12.0. Package versions remain unchanged until the release
 workflow performs the coordinated core and website bumps.
 
 Use this directory as the consumer-facing reference for the package:
@@ -12,12 +12,17 @@ Use this directory as the consumer-facing reference for the package:
 - `custom-attributes.md`: custom attribute catalog, configuration, per-backend behaviour, and the v9-to-v10 move.
 - `search.md`: `sdk.live.search.search`.
 - `availability.md`: date-picker availability flows.
-- `quote.md`: quote, additional services, cancellation policy, and insurance flows.
+- `quote.md`: quote booking-card modifiers, additional services, cancellation policy, and insurance flows.
 - `booking.md`: booking and payment option submission.
 - `contact.md`: contact submission.
 - `document-structured-json.md`: `sdk.static.documents.getTermsAndPrivacyPolicy` and structured document JSON rendering rules.
 - `CHANGELOG.md`: versioned changelog index.
 - `MIGRATION.md`: versioned migration index.
+- `versions/2.12.0/`: 2.12.0 legacy-v9 search discounts, empty-query browsing,
+  and flexible-period rejection; quote booking-card cleanup; and v10 modifier
+  guidance, plus the 2.11.0-to-2.12.0 migration guide.
+- `versions/2.11.0/`: 2.11.0 search-discount release notes and
+  2.10.0-to-2.11.0 migration guide.
 - `versions/2.10.0/`: 2.10.0 option-booking release notes and 2.9.0-to-2.10.0 migration guide.
 - `versions/2.9.0/`: 2.9.0 highlight-selection release notes and 2.8.0-to-2.9.0 migration guide.
 - `versions/2.8.0/`: 2.8.0 custom-attribute release notes and 2.7.0-to-2.8.0 migration guide.
@@ -76,4 +81,6 @@ website-sdk --backend v10 search --locale de-DE --query "adults=2"
 website-sdk --backend v10 search --locale de-DE --query "adults=2" --sort '{"by":"field","orderBy":{"label":"ASC"}}'
 ```
 
-Config file examples in these docs use the flat `WebsiteSDKConfig` shape introduced in 2.0.0 and kept in 2.10.0. v10 config additionally requires `searchEndpoint` as of 2.5.0.
+Config file examples in these docs use the flat `WebsiteSDKConfig` shape introduced
+in 2.0.0 and kept in 2.12.0. v10 config additionally requires `searchEndpoint` as
+of 2.5.0.

package/instructions/quote.md

@@ -62,13 +62,13 @@ Sample:
 ```
 
 Dates are local dates formatted as `YYYY-MM-DD`. For `v9`, `rentalId` must be a numeric vOffice unit id.
-Both backends accept `voucher` on quote and booking flows. `v10` can expose voucher discounts as booking-card modifiers when the backend returns voucher modifiers; `v9` reflects voucher effects in the quoted totals but does not expose a separate voucher modifier line.
+Both backends accept `voucher` on quote and booking flows. On `v10`, applied voucher and non-voucher modifiers can be exposed through the booking-card fields described below. `v9` reflects voucher effects in quoted totals but does not expose booking-card modifier details.
 
 ## Output
 
 Returns `Promise<GuestQuoteResult>`.
 
-Available sample:
+Available sample without modifiers:
 
 ```json
 {
@@ -139,6 +139,94 @@ Unavailable sample:
 
 Selection methods return `{ ok: true, quote }` or `{ ok: false, error }`. Possible selection errors include unknown additional service, additional service limit exceeded, unknown cancellation policy, unavailable cancellation policy quote, and unavailable quote combination.
 
+## Booking-Card Breakdown
+
+Booking-card sections are returned in display order. On both v9 and v10, the SDK
+omits numeric zero-value lines without subitems from the included, tax, and other
+breakdown sections. If no lines remain in a section, the section is omitted.
+Non-zero lines are unchanged, including when they share an `other` section with a
+filtered zero-value line.
+
+A zero-total line with subitems can remain because those subitems carry
+descriptive content. Do not use the absence or presence of a zero-value price row
+as service-selection state; use the quote's explicit service or selection data.
+
+### Modifiers and Pre-Modifier Totals
+
+On `v10`, a booking-card item at
+`bookingCardInformation.sections[].lines[].item` can include these optional
+fields:
+
+```ts
+{
+  modifiers?: readonly {
+    label: string;
+    amount: string;
+  }[];
+  totalBeforeModifiers?: string;
+}
+```
+
+`modifiers` contains localized, formatted adjustments applied to that item. A
+negative amount represents a deduction and a positive amount represents a
+surcharge. The SDK groups backend modifiers with the same label and formats their
+summed amount as one entry. The field is omitted when the item has no modifiers.
+
+`item.totalBeforeModifiers` is the formatted item amount before its modifiers. It
+is present when the item has a non-zero net modifier effect and the amount can be
+derived; otherwise it is omitted. `item.appliedCharge` remains the final amount
+after modifiers.
+
+The booking card itself can also include
+`bookingCardInformation.totalBeforeModifiers`. It is the formatted whole-card
+total before all backend modifiers and is present when those modifiers have a
+non-zero net effect. It is omitted when there are no modifiers or their amounts
+net to zero. The SDK derives quote pre-modifier totals from the final amounts and
+modifier values.
+
+Items in the included, tax, and other sections carry their adjustments in
+`item.modifiers`; do not expect those adjustments to be separate section lines.
+Negative modifiers on backend lines that cannot be mapped to those sections may
+instead appear as dedicated booking-card lines. `v9` quote cards omit
+`modifiers` and both `totalBeforeModifiers` fields.
+
+Discounted `v10` example for locale `de-DE`:
+
+```json
+{
+  "bookingCardInformation": {
+    "sections": [
+      {
+        "lines": [
+          {
+            "item": {
+              "position": "Inklusivpreis",
+              "appliedCharge": "1.554,00 €",
+              "modifiers": [
+                {
+                  "label": "Frühbucher/Last-Minute",
+                  "amount": "-140,00 €"
+                }
+              ],
+              "totalBeforeModifiers": "1.694,00 €"
+            }
+          }
+        ]
+      }
+    ],
+    "total": "1.596,70 €",
+    "totalBeforeModifiers": "1.736,70 €"
+  }
+}
+```
+
+For a price breakdown that keeps its arithmetic visible, render
+`totalBeforeModifiers` as the pre-modifier amount, show each modifier as an
+adjustment row, and use `appliedCharge` or `total` as the resulting final amount.
+The SDK supplies formatted values but does not decide whether a reference price
+should be displayed or struck through; that presentation and its legal
+requirements remain the consuming site's responsibility.
+
 ## Vouchers
 
 When `voucher` is provided in the quote input, an available quote may include `quote.voucher`:
@@ -153,7 +241,11 @@ When `voucher` is provided in the quote input, an available quote may include `q
 
 `status` is `"applied"`, `"not_applied"`, or `"unknown"`. `v10` reports `"applied"` when the backend returns a non-zero voucher modifier and `"not_applied"` when no voucher modifier is returned for the requested voucher. `v9` returns `"unknown"` for available voucher quotes because the legacy response does not provide a reliable voucher modifier signal.
 
-Voucher modifiers can appear in `bookingCardInformation.sections`. Sections are returned in display order.
+Do not assume an applied voucher appears as its own section line. On `v10`, a
+voucher adjustment on an included, tax, or other line appears in that line's
+`item.modifiers`; an unmapped negative modifier can appear as a dedicated line.
+Use `quote.voucher.status` for voucher application status and the booking-card
+fields for price presentation.
 
 ## Additional Services