Define the billable unit before multiplying the price
Agree which source words, files and embedded text a translation quote covers, then give your Japanese buyer a count record and reproducible subtotal.
What happened
You are a translator outside Japan. A Japanese company asks for a price to translate a fifty-page English report into Japanese, and you propose a rate per English source word. The page count identifies the document’s size, but it does not establish the quantity that your rate will multiply.
In this fictional example, the agreed counting record would contain 12,000 English words in editable text and another 600 in images. At an invented USD 0.12 per source word, those quantities produce different totals depending on whether image text is selected. No actual customer document was counted for this example; the quantities are supplied assumptions, not software test results or market rates.
Your output is a count record attached to the quote: which file, which content, which unit, how it was counted and what happens if the file changes. This is narrower than defining the deliverables: the question here is whether another person can reproduce the quantity behind your price.
What’s going on on the Japanese side
Name the unit that the rate actually buys
A buyer may need a quantity and unit for its order, not only a project total. Takeda’s published instructions ask suppliers to report discrepancies in purchase-order price, quantity, delivery time or unit of measure, and to align the later invoice with the order details. This is one company’s procedure, not a Japanese translation-pricing rule. Source
Write “USD 0.12 per English source word” rather than “0.12 per word.” In this fictional proposal, that rate covers translation into Japanese followed by one provider check against the English source for omissions and terminology consistency. Layout reconstruction, image-text extraction and client-requested review rounds need explicit scope decisions. A unit price does not describe all those services by itself.
| Possible unit | Meaning to settle before pricing | Do not substitute silently |
|---|---|---|
| English source word | Counted English content in the named input and agreed scope | Words in the Japanese output |
| Source character | Character definition and included content under an agreed method | An assumed conversion from English words |
| Page | Source or finished page, dimensions and included content | An unspecified quantity of words |
| Video minute | Selected time range, rounding and included work | Hours spent doing the work |
| Interview | Duration, preparation, output and review allowance | Each participant or each recording file |
These are editorial questions, not prescribed industry definitions. The worked example starts with English source text; it does not impose a word-based measure on Japanese source material or propose a word-to-character conversion. If the buyer expects a different unit, resolve that before comparing rates.
Separate the counted text from unresolved embedded content
A count is useful only with its scope. In the fictional report, the 12,000-word body includes the selected editable headings, captions and table text, but excludes image labels. The separate 600-word image transcript must contain only those excluded labels, so adding it does not count captions twice.
Treat recurring headers, footnotes, tracked changes, duplicated passages and comments as explicit inclusion decisions. Do not assume that a displayed count includes the content the buyer intends to purchase. Nor should repeated text automatically earn a discount: identify any proposed treatment and obtain agreement before using it in the subtotal.
What to do next
Freeze the source version and record how the quantity was obtained
-
Identify the baseline. Keep the supplied file in the agreed private location and record its filename, revision and received date. If the source is still being edited, mark the count provisional rather than implying that the final quantity is known.
-
Write the counting method before trusting the result. Record the application and version actually used, the selected text or sections, relevant settings and the saved count evidence. This article does not prescribe a software button sequence or claim that different applications produce identical counts.
For the hypothetical quote, the record might read as follows. The figures are inputs to the example, not counts independently extracted from a real fifty-page document.
| Record field | Fictional quote baseline |
|---|---|
| Source | Report_EN_v3.docx, fifty source pages, received 2 November 2026 |
| Translation direction | English source into Japanese |
| Main scope | Editable report text, including headings, captions and table text; excluding image labels, recurring headers and comments |
| Main quantity | 12,000 English source words, assumed for this example |
| Embedded scope | Image labels copied into a separate transcript; captions already in main text excluded |
| Embedded quantity | 600 English source words, assumed for this example; not yet selected for translation |
| Counting evidence needed in an actual quote | Application/version, selected scope, relevant settings and retained count output; checked image transcript |
| Rate | Proposed USD 0.12 per included English source word |
| Finalization condition | Buyer confirms scope and baseline; changed files are recounted and any resulting price change is confirmed before that additional work |
- Resolve a disagreement by comparing scope. If your count and the buyer’s differ, first check whether both used v3 and the same selected sections. Then compare inclusion of captions, tables, headers, comments and image text. A PDF export and an editable file may represent different selected content; do not describe the discrepancy as harmless rounding without investigating it.
If the difference remains, retain both count records and agree which reproducible method will price the work. Do not force your number into the buyer’s template while leaving its competing number unresolved.
Check image text for omissions and duplicate counting; price extraction separately
- Build a separate embedded-content list. Record the page or image identifier, the text to be translated and whether that text is already included in the main count. Check a transcript against the images before using its total, especially if text was extracted automatically. An unverified extraction should remain an estimate or unresolved item.
For confidential source material, use the client’s permitted tools and storage. Do not upload the report to a public counting or AI service merely to settle a price. Request an approved export or obtain agreement on a permitted method if the material cannot be examined safely.
Show the selected subtotal without billing an undecided option
- Multiply each agreed quantity by its matching rate. Keep the image option visible but unselected until the buyer answers. The following figures exclude tax, expenses, payment charges, image extraction and layout work; their treatment needs separate confirmation in the actual quote.
| Scope decision | Calculation | Translation subtotal |
|---|---|---|
| Main text only | 12,000 source words × USD 0.12 | USD 1,440 |
| Additional image text, if selected | 600 source words × USD 0.12 | USD 72 additional |
| Main plus image text, if both selected | 12,600 source words × USD 0.12 | USD 1,512 |
The USD 72 is translation of the image text, not a price for extracting it or rebuilding the images. If extraction is needed, define who supplies the checked transcript and how that work will be priced before treating the combined offer as complete. Do not publish USD 1,512 as an all-inclusive project total while those items remain unresolved.
Recount changed files and confirm the resulting price change
- Define the final-file branch. If v3 is confirmed unchanged, use its agreed count record. If a new revision arrives before acceptance, identify changed content, recount under the same method and send a revised quantity and price for confirmation. Keep the earlier quote identifiable rather than overwriting its evidence.
For a second fictional calculation, suppose the main text increases to 12,500 words while the selected image transcript remains 600 words. The revised quantity would be 13,100 words and the translation subtotal USD 1,572; the increase over USD 1,512 is USD 60. This arithmetic is a proposal calculation, not permission to charge for a change without agreement.
If the project has already been accepted, use the agreed-project change record. If an incoming purchase order uses another quantity or unit, use the quote-to-PO discrepancy process instead of silently changing the counting rule.
Attach the count record and ask for the missing scope choice
Before sending, check that the quote and attachment identify the same source revision, unit, included sections, quantity, rate, selected subtotal and unresolved work. Retain the buyer’s answer with the version incorporating it. A reply confirming the translation direction alone does not resolve the image option or extraction responsibility.
Template
Replace the fictional filename, quantities and price. Both versions ask for the same scope decision; neither presents the optional amount as already authorized.
Subject: Confirming the counted scope for Report_EN_v3
We propose pricing English-to-Japanese translation of Report_EN_v3
at USD 0.12 per English source word, using the attached count record.
The main-text quantity is 12,000 words: USD 1,440.
Should the quote also cover the 600 words in the image transcript?
If selected, their translation adds USD 72, giving USD 1,512.
These are translation subtotals, not an all-inclusive project total.
Image-text extraction, layout, tax and payment charges are not included
in this calculation and need separate confirmation.
Please confirm the scope, who supplies the checked image transcript,
and whether v3 is the final source. Changed files would be recounted
and any revised scope and price sent for confirmation.
件名:Report_EN_v3の計数対象の確認
添付の計数記録に基づき、Report_EN_v3の英日翻訳を
英語原文1語あたり0.12米ドルでお見積もりする案です。
本文の対象は12,000語、小計は1,440米ドルです。
画像文字の転記に含まれる600語も翻訳対象に含めますか。
選択された場合、翻訳分72米ドルが加わり、小計は1,512米ドルです。
これは翻訳の小計であり、案件全体の総額ではありません。
画像文字の抽出、レイアウト、税金、支払手数料はこの計算に
含めておらず、別途確認が必要です。
対象範囲、確認済みの画像文字転記の提供者、v3が確定原稿かを
お知らせください。原稿変更時は再計数し、範囲と価格の変更案を
確認用にお送りします。
When to bring in a professional
A translator or relevant subject specialist can help determine what must be translated and check a difficult image transcript. Ask an appropriate adviser when a dispute concerns what an accepted price legally covers, rights to process the supplied material, or applicable tax treatment. A count record organizes the facts; it does not settle those questions.
For an ordinary pre-quote quantity discrepancy, start with the two source versions, counting records and the buyer’s requested scope. Do not turn a missing inclusion choice into a legal conclusion.
Kit
Keep the count record in an existing document or spreadsheet; no kit, purchase or registration is required. Use the quotation checklist and selling-to-Japanese-companies workflow for the surrounding process. Your next action is to resolve one unselected content category before placing a total on the final quote.
This guide goes stale when
- Takeda changes its published purchase-order review instructions.
- The source file, counting method, included content or pricing unit changes.
- The buyer changes the quantity or unit required on its order.
Sources
| Publisher | Document | Checked |
|---|---|---|
| other | Takeda Third-Party Tools and Resources — Purchase Order Review | November 2, 2026 |
Was this useful?
More on Selling B2B
-
Japanese Client Requests Extra Work After Accepting Your Quote: Agree on the Change
Preserve accepted scope, price a requested addition, and ask your Japanese client to approve the work, delivery conditions and purchasing record.
-
Give a budget estimate without presenting it as a final quote
Build a defensible budget range from named uncertainties, show assumptions and exclusions, and identify what is needed for a final proposal.
-
Three buyer contacts give different instructions: map who owns each approval
Record conflicting project, procurement and onboarding instructions, ask the buyer to name a coordinating owner, and preserve one traceable answer.
Get the next guide by email
Two emails a month: new guides, and what changed on the Japanese side. Unsubscribe in one click.