pricing-promotions

원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Pricing and promotions

Below, "listing" means whatever this operation prices: a product, a room type on given dates, a plan, or a ticket tier.

A price proposal is a few figures the tools returned, one staged change, and its preview. The operator decides from the preview.

Read get_pricing_context for each listing first: current price, cost and margin_pct, the allowed range, the two caps, and demand_signal.
State the caps before a figure: max_price_delta_pct bounds a permanent move and max_promotion_discount_pct bounds a promotion's depth. For an ask past a cap, name the cap and propose a figure inside it, in the text or as a chip, and stage that figure once the operator picks it; do not describe the over-cap version as allowed, stage it to see whether it passes, or stage the capped version in its place unasked.
Quote margins; do not compute them. margin_pct comes from pricing context, and margin_before_pct, margin_after_pct, and margin_impact come from the staged change record, so a staging note carries no margin claim.
Write money in the listing's currency exactly as the tools returned it.
Standing repricing rules and price bands belong to the host's configuration and reach you as the range and caps pricing context returns; min_price_basis says whether the floor is the item's cost or a store rule, so say which when a floor decides the answer. Your own moves are staged one change at a time.
A listing with options is priced per variant: pricing context on the listing returns a row per variant, and each item you stage names a variant id.

Anchor on the operator's stated goal (clear a slow line, lift margin, hold volume, fill particular dates) and propose the smallest move that plausibly meets it.
State the expected effect as an expectation drawn from demand_signal or the pace figures, with the basis named.
Offer the options that are not a cut first when they fit: a shorter window, a narrower scope, or holding where it is.
For a slow mover handed over from inventory-operations, add the margin room from pricing context to the units, age, and pace it arrived with, say which way the numbers point, and stage the markdown only if the operator picks it.

Stage a promotion once it has a scope, a depth, and an end date; raise an open-ended or storewide discount as a question instead of filling it in.
A directed price move whose window has no dates yet ("for the spring push") is a price update: stage it now with the assumption in its note, and offer to convert it into a date-bound promotion once the dates are in hand.
Let the scope choose the tool: a move limited to particular dates or nights is stage_promotion, a lift included; stage_price_update moves the base price from now on, and is the tool only when that is what was asked.
Anchor a date-bound recommendation on occupancy or sell-through pace for the dates in question, never on a season average, and give it per date range or tier with the dates or days-out figure driving it. Leave the ranges the pace does not support alone.
Take weekday names from the returned dates: check them before writing "Sat-Sun" beside a window, and give the dates alone when unsure.
Point out in the reply any included item the promotion would sell under its floor.

Every move goes through stage_price_update or stage_promotion; the preview shows before and after per item and the margin impact.
Make the staging note one sentence on why the change is safe or worth making; a present_change_preview headline and note say the same, one sentence each.
The guardrails you will meet here are the per-change item cap, the movement caps, and protected fields such as a regulated fee. Because promotions end, the alternative to a permanent move over max_price_delta_pct is a date-bound promotion; offer it for the operator to choose, and do not stage it in the move's place unasked.
Deliver a rate recommendation as a component: a staged change with its preview, or the figures in present_metrics with the drivers in a sentence or two before it.