To localize product specifications on an export website, classify each change as language, conversion of the same physical quantity, or an actual market specification. Keep the approved source value, unit, applicable revision and evidence for each model. Maintain display values and market applicability separately, then verify that listings, details, manuals and enquiries identify the same product.
This guide is for B2B equipment, machinery and component enquiry websites. For language setup, see the multilingual maintenance guide; for categories and filters, see the product centre guide. The focus here is deciding and checking how specifications appear across markets.
1. Identify whether the change concerns wording, units or the product
- Language: translate a label such as “Net weight” while preserving its value and physical meaning. Have a language reviewer confirm terminology, capitalization and decimal separators.
- Unit conversion: express the same length in millimetres and inches. Retain the original value and unit, document the formula, display precision and affected locations, and obtain technical review.
- Actual specification: when voltage, frequency, plug, connection, material or applicable certification changes, confirm the model, variant and approved evidence before choosing a shared page or separate records.
Record market and language separately. An English page may serve several countries, and one market may use several languages. Voltage, frequency and supply eligibility are product and business facts; page language determines their wording. State the applicable model and conditions so sales can check suitability.
Akeneo’s measurement documentation explicitly manages numeric values and units and discusses conversion for channels and locales. It provides relevant industry vocabulary for this task. Each product’s conversion features and configuration require separate confirmation.
2. Keep evidence in a specification register
Start with one real model and an approved technical document. Split its parameters into reviewable entries. The following is a project design suggestion: the implementation team configures actual fields in the current model and connects them to the theme.
| Record | Purpose | Reviewer |
|---|---|---|
| Stable product ID, variant and document revision | Identify the product and applicable hardware | Product owner |
| Parameter, source value, unit and measurement conditions | Preserve traceable technical evidence | Technical owner |
| Market, language, display unit and precision | Define presentation for each page | Business and language reviewers |
| Formula, source and review date | Recalculate and track rule changes | Technical owner |
| Pages, files, enquiry options and owner | Find every affected location | Content owner |
Rated, limiting and typical values and permitted tolerances have distinct meanings. Preserve their operating conditions. Mark parameters with missing evidence or uncertain applicability for technical confirmation. Keep an explicit zero according to the field’s meaning; document an empty value as pending or an agreed empty state.
Shared fields can hold common technical source values; translatable fields can hold reviewed labels and explanations. Design market applicability in the project model. When an existing PIM or ERP supplies approved records, agree which system owns each value. See multi-site product data ownership for cross-site responsibilities.
3. Agree display precision and retain values for recalculation
Calculate from the approved source value and apply agreed rounding at the final display stage. Review the value, unit, decimal places and qualifiers such as “approximately” together. Use the original value for subsequent calculations. Agree a base unit and tolerance for filters and boundary comparisons too.
Length, temperature and pressure require their respective rules. Confirm physical meaning and calculation conditions for temperature offsets, gauge versus absolute pressure, and net versus shipping weight. Preserve connection designations and pipe-thread specifications from technical evidence and add explanations where needed. Have technical staff review compatibility.
Before bulk conversion, select an ordinary value, a decimal value, a boundary value and a missing value. Have a second person independently calculate expected results. Record permitted error, display precision and empty-value presentation. AI can organize differences, draft translations and assist calculations; a designated owner approves final technical claims. Follow the AI content review workflow.
4. Fictional example: two power-supply variants in one series
All model names, specifications, page arrangements and precision choices below are fictional. A company has separately approved variants MX-240-A and MX-240-B. Assume A uses 220 V / 50 Hz and B uses 110 V / 60 Hz. Both have a source width of 254 mm. This exercise demonstrates data management; product and business owners confirm real supply specifications and eligible markets.
The team approves “254 mm (10.00 in)” as the dual-unit width display. The calculation is 254 ÷ 25.4 = 10, using 1 in = 25.4 mm. Two decimal places are an assumed display convention for this exercise; measurement precision and tolerances retain their approved meaning. Chinese and English labels refer to the same reviewed source value.
- Record a stable identifier, supply specification, manual revision and approved supply scope for A and B. Identify the variants clearly in listings.
- Show approved variants and supply conditions on English pages according to customer needs; maintain Chinese pages for their confirmed business scope. Check language and specification applicability separately.
- Identify A or B in the detail page, download and enquiry option. If a buyer selects A on an English page and leaves the project location pending, sales checks the intended environment against A’s evidence.
- Deliberately attach B’s manual to A in the test exercise. Expect a correction-required result. Repair the link and verify the model, supply specification and revision inside the file before acceptance.
The sample checks conversion, distinct variant identities, file mapping and sufficient enquiry information for selection review. Record and remove test-environment submissions according to the agreed procedure; handle real enquiries through the business process.
5. Publish a change in six steps
- Approve scope: list product IDs, variants, markets, languages, document revisions and writable fields. Preserve affected original values and files.
- Find references: inspect listing summaries, detail tables, text in images, SEO descriptions, filters, PDFs and enquiry options for repeated specifications.
- Test a sample: check formulas, rounding, missing values, zero, boundaries and different market specifications against the actual model and theme behavior.
- Review responsibilities: technical staff confirm values and conditions; language reviewers confirm terminology; business owners confirm supply scope and contact paths.
- Save and read back: save approved fields for the intended site, record and language. Compare submitted and retained values. Preserve actual URLs and publication dates when updating existing records.
- Check public output: open each language page and actual file, verify the final cached presentation and contact path, and record results and owners.
Copyable acceptance row: product ID | variant | market | language | source value and unit | display value and unit | formula and precision | document revision | public URL | PDF contents check | enquiry option | reviewer | time | result. Use the download revision checklist for replaced files.
6. Check content and search signals after publication
- Content and relationships: enter through the listing, inspect the model, values, units and applicability, then open the manual and contact link.
- Mobile reading: check long English labels, signs, tolerances and units at about 390 pixels. Ensure tables remain readable and links usable.
- Public output: inspect HTTP status, one H1, title, description, canonical, language links and applicable structured data. Review specifications repeated in summaries.
- Change record: retain readback, public URLs, document revisions and repair results. Track indexing, rankings, organic visits, enquiries and AI citations using actual measurements.
When one page presents several market specifications, put applicability beside the values. Decide on separate variant pages using real product differences and buyer tasks. Confirm URLs and language configuration in the project and use the SEO output checklist.
7. Divide CatchCMS configuration and project development
CatchCMS supports content models, dynamic fields, site languages, body translations and values for fields enabled for translation. A project can organize product IDs, parameters, explanations and file references, with the theme handling presentation. Current schema definitions determine field types and validation. See content models and fields.
Conversion engines, market and variant rules, automatic specification selection, system synchronization, technical approval workflows and automatic enquiry prefilling require project design and development. Smaller teams can start with a controlled register and manual review, complete one real product workflow, then assess automation against repeated work. See the form guide for fields, validation and notifications.
Frequently asked questions
Should every English page use imperial units?
Choose units using confirmed customer practice, technical evidence and project requirements. Approved metric or dual-unit displays can serve the page, with clear applicability across the markets using English.
How should a series with different voltages be presented?
Establish stable variant IDs and approved specifications. Then use buyer comparison, download and enquiry tasks to choose a clearly labeled shared page or separate detail pages. Verify file mapping and submitted information in either arrangement.
How can a team start an acceptance trial?
Prepare product and variant evidence approved for public use, markets, languages, original parameter sheets, manuals and enquiry requirements. Use CatchCMS project consultation to agree fields, theme work and development scope. Complete sample entry, bilingual review and public acceptance before expanding the batch.