Peter Zou Translation — Trilingual ZH-EN-AR · English-Pivot Translation & Compliance Docs

Positioning

For the Saudi & Gulf market, translation as evidence

为沙特及海湾市场的企业提供中、英、阿三语专业翻译与合规文档服务。以英文为枢纽语言，任何译文都可追溯、可复核、可审计——不是"翻译完成"，而是"交付证据"。

We provide professional trilingual (Chinese-English-Arabic) translation and compliance document services for the Saudi & Gulf market. English serves as the pivot language: every deliverable is traceable, verifiable and auditable — we deliver evidence, not just translations.

نقدّم خدمات ترجمة احترافية ثلاثية اللغات (صينية-إنجليزية-عربية) ووثائق الامتثال لسوق السعودية والخليج، مع اللغة الإنجليزية كمحور أساسي، حيث يكون كل تسليم قابلًا للتتبع والتحقق والتدقيق — لا نسلّم "ترجمة" فحسب، بل "أدلة".

Service Catalog

What we translate

Eight scenarios, each with its register and deliverable. The EN middle state is included in every CN↔AR job.

Scenario	Register	Direction	Deliverable
Business email & quotation	Formal business	CN↔AR, EN→AR	4-part translation + check report
Contracts & legal documents	Legal formal	CN↔AR, EN→AR	Obligation register + human verdict table
Product catalogs & e-commerce listings	Commerce marketing	CN→AR, CN→EN	Terminology hit report + register notes
Marketing copy & menus	MSA marketing	CN→AR	Terminology hit report + register notes
Daily comms (WhatsApp / email)	Daily	CN↔AR, EN↔AR	Concise translation + NOTE
Technical articles & web content	Formal written	CN→EN→AR	Terminology consistency + hit report
SFDA registration compliance	Formal	CN→AR, EN→AR	Registration pack + SABER / halal / label

Try the Engine

Live trilingual preview

Paste product copy, an email or a clause. Chinese↔Arabic jobs show the English middle state — the same auditable path every delivered job follows.

→

Preview only — not a certified deliverable.

Language Roadmap

Starts trilingual, scales to any language

The English-pivot architecture is language-agnostic: adding a language means adding a target column, not reworking the pipeline.

Today

ZH · EN · AR

Chinese, English, Arabic (MSA) with English as the pivot and a script-enforced glossary.

Next wave

Turkish · Persian · more

Turkic and Middle-Eastern languages follow the same EN-anchored glossary pipeline.

Long-term

Any target market

Each new language inherits the auditable two-gate quality model.

Why Us

Five reasons the deliverable can be checked

A translation you can verify beats a translation you must trust.

01

English pivot, fully auditable

CN↔AR is never a blind jump. The EN middle state means any error can be located by eye or by a third party.

02

Terminology enforced by script

A machine-checked glossary keeps one EN anchor mapped to one AR rendering across the whole document.

03

Dual quality gates

Machine check (FAIL never ships) plus a signed human verdict with every open item explicitly declared.

04

Honest boundaries

We promise terminology consistency against the current glossary — not zero errors. Native-speaker review is offered as a paid option.

05

Compliance-sensitive by design

Hard rules for religious wording, obligation register (shall / shall not), and Western numerals + Gregorian dates in RTL text.

Deliverable Format

What you receive, in order

Every job ships as a 4-part deliverable with two check tables attached.

1. Source — 2. EN middle state (mandatory for CN↔AR) — 3. Target translation (glossary-bound) — 4. NOTE list: ambiguity, new terms, calendar assumptions, religious wording.

Attached: terminology hit report (coverage + compliance from script), machine check table, and a signed human verdict table (gender, register, religious wording, native review).

四段式交付：源文 → EN 中间态（中阿必含）→ 译文（术语表强制）→ NOTE（歧义/新词/历法/宗教用语逐条列出）。附术语命中报告、机器校验表、人工判定表（署名）。

G1

Machine gate

Terminology / proper nouns / numeral system / Latin residue / hygiene. FAIL does not ship.

G2

Human gate

Signed verdict with "undecided" declared explicitly where a reviewer did not rule.

Workflow

Eight steps, two gates

Confirm brief

Direction, register, scenario, risk

Route

Pivot / glossary injection / draft

First draft

EN pivot first

Polish

Register & flow

Machine check

FAIL does not ship

Human verdict

Signed, declared

Deliver

4 parts + two tables

Revise

One round free

Pricing

Three tiers

Standard for daily work, Formal for contracts and compliance, SFDA special for registration materials.

Standard

Email · daily · marketing

Per item / 1,000 chars

One free revision round
4-part deliverable
24–48h SLA

50% upfront, 50% on delivery

Formal

Contracts · technical · compliance

Per page / 1,000 chars

Obligation register retained
Terminology hit report
2–5 business days SLA

Most chosen for SFDA-adjacent work

SFDA Special

Registration · labelling

Per project

Checklist-based scope
SABER / halal / label line items
Milestone payments

Native-speaker review available, priced separately

SOW Essentials

Terms that protect both sides

S1

SLA

Standard 24–48h; formal 2–5 business days; SFDA per project.

S2

Revisions

One free round included; extra rounds billed by tier.

S3

Liability cap

Anchored to the service fee itself (industry standard).

S4

Glossary ownership

Project-specific terms become client-reusable after confirmation; the general glossary stays a service asset.

S5

Governing text

In case of divergence, the English version prevails.

S6

Confidentiality

Client documents are never used for model training; data-residency (local deployment) is on the roadmap and disclosed when unavailable.

SFDA Vertical

SFDA registration & compliance, translated

Document translation and compliance support for Saudi food, pharma and device registration — from application forms to agent correspondence.

Application forms & support docsنماذج التسجيل والمستندات الداعمة

SABER certification filesوثائق شهادة سابر

Halal certification materialsمواد شهادة الحلال

Food label complianceمطابقة ملصقات الغذاء

Cold-chain storage licencesتراخيص التخزين البارد

Agent / counsel correspondenceمراسلات المفوّضين والمستشارين

FAQ

Questions we are asked

No provider can promise zero errors. We promise terminology consistency plus auditable delivery; for critical texts we recommend adding native-speaker review.

We currently commit to Modern Standard Arabic (MSA) only. Colloquial assets are under construction and will be announced when open.

Western numerals and the Gregorian calendar by default in commercial letters and contracts; Hijri annotations added on official filings when required.

Yes — with the obligation register hard rule. The Arabic version is not a standalone legal basis; the English version prevails.

CN↔AR jobs pass through a mandatory EN middle state that is delivered to you, so both ends can be checked against one anchor.

The pipeline is glossary-bound and machine-checked; final Arabic is reviewed by a native speaker as an optional, separately priced gate.

Turkish and Persian are next in the roadmap; the EN-pivot architecture makes each new language an additive column, not a rework.

No. Client documents are never used for model training. On-premise deployment is on the roadmap and disclosed when it becomes available.

Contact

Start with the source document

Send the source file plus a one-line scenario note; you get a requirement confirmation and a quote within 24 hours.

How to orderSource document + scenario → confirmation & quote in 24h
DeliverablesPDF core format, ZH-EN-AR aligned, EN anchored
LanguagesToday ZH · EN · AR — Turkish, Persian and more on the roadmap
Served byPeter Zou · service head

Requests are stored and answered within 24 hours.

Evidence, not just translations.English-pivot. Auditable.