ONE CLEAR COMMERCIAL VERSION
Know which commercial version the team actually issued
Prepare priced quotation lines, issue a numbered revision and keep later changes connected to the exact earlier version.
Replace uncertain attachments with a clear version
A customer request can lead to several commercial discussions. Tsumira distinguishes the original request from its issued quotation revisions. Each issued revision captures the priced result at that point. A later revision is a deliberate new action based on a known version, rather than a silent replacement of historical totals. This gives the team a concrete answer when it needs to establish which scope and price it had issued.
Prepare lines from their actual source
Supported lines can reference current provider offerings or use explicitly authored ad-hoc content. Quantity, unit amount and tax class must satisfy the relevant rules. When a request selection or earlier provider-linked line needs independent pricing, supported detach operations make that choice explicit. Copying and reconnecting existing lines are distinct operations. These differences matter because a historical offer and a current catalog item do not necessarily represent the same price decision.
- Provider-linked and ad-hoc lines
- Explicit copy, detach and reconnect
- Validated quantities and tax classes
Issue a priced snapshot deliberately
Issuance calculates and records the actual revision totals, line snapshots and calculator context. An optional validity date and supported localized note can clarify the commercial conditions. The existing calculation path is JPY with the implemented Japanese gross-price and consumption-tax model. It must not be presented as universal multi-country financial compliance. Issuing the revision changes the request to quoted; it does not establish that the customer accepted or paid it.
- Numbered issued revision
- Recorded line and total snapshots
- Optional note and validity date
Revise against a known base
A reissue identifies the earlier revision by its ID and number and checks the request’s expected current state. This reduces ambiguous editing when colleagues work on the same request. Review which lines are carried forward and which need updated source resolution or explicit manual pricing. The history should show the commercial sequence instead of pretending that an older customer discussion happened against today’s catalog. A closed request is not an editable quotation playground.
- Known base revision
- Current request checked
- Historical commercial context retained
A concrete workflow
Review the request
Understand the submitted scope and any clarification before pricing.
Prepare the revision
Choose source-linked or deliberate ad-hoc lines and verify quantities and tax treatment.
Issue the result
Review totals, note and optional validity date, then issue the numbered version.
Revise explicitly
Use the identified earlier version as the base for a reviewed subsequent issue.
An illustrative working example
Example: a customer changes the requested scope
The first revision covers two units from the supported catalog. The customer later requests an additional service and a manually priced adjustment. The operator reviews the earlier revision, copies the unchanged content and deliberately prepares the new line. The second issue has its own number and pricing snapshot. The first remains understandable as the offer that supported the earlier conversation, rather than being rewritten to look like the updated request.
Questions about this topic
Can issued totals change when the catalog changes?
An issued revision records its priced snapshots. A new commercial change should be represented by a deliberate later revision.
Does issuing mean customer acceptance?
No. Issuance records the company’s quotation action. Customer acceptance, financial processing and payment are distinct events.
Can a revision contain manually defined lines?
The supported ad-hoc and explicit detach operations allow authored pricing within the validated schema and permissions.
Is this already a global tax calculation promise?
No. This current quotation path uses JPY and the implemented Japanese gross-price model. Country localization is a separate capability.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Google Sheets
Workflow concept: Check quantities and commercial assumptions before issuing a numbered priced revision.
DocuSign
Workflow concept: Plan a separate acceptance step that refers to the exact issued version rather than a mutable draft.
Pipedrive
Workflow concept: Relate a commercial discussion to the exact quotation revision without interpreting issuance as acceptance.