Skip to content
Function in detail

CONNECTED BUSINESS OPERATIONS

Show a fixed price, a starting price or a request

Choose the price mode that describes the real offer instead of forcing every service into one amount.

Illustrative function excerpt

Four modes describe four different offers

Choose hidden, request, fixed or starting price to match the actual service.

Hidden—
RequestAsk for scope
Fixed30,000
From30,000

Diagnostic workshop

A starting price is not a fixed quote for unspecified additional work.Prepared example; no real customer or live state is shown.

A clear responsibility in your daily work

A shared business record serves colleagues preparing an offer and people reading the published explanation. Keep those audiences distinct. Check what information is being changed, where the result appears and who should review it. One representative example is more useful than assuming an internal edit has already produced the intended public or commercial result.

Keep the source information clear

The service schema distinguishes hidden, request, fixed and from price modes. These convey different information to the customer. Choose based on the actual commercial arrangement: a fixed package differs from work that requires a scoped quotation, and a starting price should not imply that every possible project costs the displayed amount. The service record combines names, descriptions, category, optional duration and a deliberate price-display mode. Fixed and starting prices use whole Japanese yen. A request-based or hidden price has a different commercial meaning, so choose the mode before writing the surrounding customer-facing explanation.

  • Classify the service as fixed, starting-price, request-based or intentionally without public price.

Review the relevant presentation

Fixed and from modes require a whole-JPY price; hidden and request modes do not carry an incompatible amount. Review mode and number together when changing an offer. A stale number beside a request-based service can create a misleading impression even if the service description explains the need for a conversation. Services have draft, review and published states. Public website content is assembled from an allowed published projection, with Japanese and optional English fields. Review both the source record and its presentation; publishing content does not make it a confirmed booking or a signed customer agreement.

  • Set or remove the whole-JPY amount consistently with the mode, then review the service scope.
Illustrative function excerpt

Review mode and amount together

Fixed and from need a JPY amount; hidden and request must not retain an incompatible price.

Selected modeFixed
Whole-JPY amount30,000Whole JPY

A defined initial session

A starting price is not a fixed quote for unspecified additional work.Prepared example; no real customer or live state is shown.

Check the actual use

Inspect the public rendering and any connected commercial selection after the change. Make the starting-price qualifier or inquiry path clear in the actual destination. This catalog presentation is not a customer-specific tax opinion, a binding contract for unspecified work or multicurrency billing. Agree the detailed scope before final commercial commitment. An enabled quotation catalog can reuse service offerings. Explain what the service includes, what needs an individual discussion and who reviews changes. Duration and public pricing describe the offering; availability, appointment rules and final quoted terms need their own connected workflow and checks.

  • Inspect the actual presentation and inquiry route using a representative customer question.
A concrete workflow
  1. Prepare the context

    Classify the service as fixed, starting-price, request-based or intentionally without public price.

  2. Review the decision

    Set or remove the whole-JPY amount consistently with the mode, then review the service scope.

  3. Check the result

    Inspect the actual presentation and inquiry route using a representative customer question.

An illustrative working example

Illustrative working example

A diagnostic session has a defined package price, while implementation work needs a scoped request. The owner selects fixed for the first and request for the second. A colleague checks that the public wording does not promise a complete implementation for the diagnostic price.

Questions about this topic

Which price modes exist?

Hidden, request, fixed and from. Their meaning differs, so choose the mode that matches the actual offer.

Can every mode have a numeric amount?

No. Fixed and from require a whole-JPY amount; hidden and request do not retain an incompatible price.

Does this publish every edit automatically?

Do not assume so. Review draft, review and published state and inspect the actual enabled website destination.

Can AI changes bypass review?

No. Treat proposed wording or updates as reviewable work and respect the user’s actual editing and publication permissions.

Explore connections around this workflow.

Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.

Explore all integrations

Bring your business's work together.

Start with a specific workflow and your team.

Start for free