RFQ and technical guide
Measurement Sheets Across Locales: Protect Decimal and Unit Meaning
Declare the unit and numeric convention before sending a measurement table. Ask the receiver to read back representative values from the imported file, because a correctly written source sheet does not prove another application interpreted its numbers as intended.
For technical teams exchanging measurement tables across software locales.
Keep values and units identifiable
Use a clear unit declaration for the relevant table and avoid mixing unexplained units within one column. Record the source application and export format when useful to the exchange. Keep a human-readable reference beside the editable file. Do not change garment dimensions merely to make an import appear tidy. The task is to preserve agreed values, not to decide measurement tolerances, rounding policy or the actual point-of-measure method.
Declare separators instead of assuming them
Tell the receiver how the submitted numeric values use a decimal mark and whether any grouping separator appears. If a delimited file is supplied, identify the field delimiter separately. Avoid presenting a separator rule as universal across all applications. Ask the receiver to flag text values or unexpected column splits. A visually aligned preview may conceal a numeric field imported as text, so appearance alone should not be the acceptance check.
Use a controlled read-back example
Choose representative entries that expose the conventions in this actual file, including any fractional value present. Identify the row, column, source value and unit. Ask the receiving team to report what its application shows without silently correcting the file first. Keep this demonstration labeled as an exchange check, not a new garment specification. If an import differs, preserve the evidence and resolve export or import handling before downstream calculations or pattern work proceed.
Lock the accepted received version
Retain the confirmed file identity and the accepted read-back with the handoff. Recheck after an export route or software setting changes. Keep the source and received copies distinguishable, especially when a PDF reference and editable spreadsheet are supplied together. Do not claim one successful example validates every formula or every row. Ask for the wider checks appropriate to the project and record unresolved fields rather than converting ambiguous strings by guesswork.
Decision and evidence checklist
| Decision | Include in the brief | Review evidence |
|---|---|---|
| Meaning | Unit and source numeric convention | Human-readable reference |
| Exchange | Format, decimal and field separators | Received-file inspection |
| Confirmation | Representative row/column read-back | Accepted revision identity |
What this brief does and does not establish
File-exchange recommendations, not software certification or a complete spreadsheet audit. No garment dimension, rounding precision or tolerance is prescribed.
Attach the measurement table and its numeric convention to the technical handoff inquiry. Open the MyOwnWear RFQ form.
Buyer questions
Is this a rounding guide?
No. It preserves existing values during file exchange; rounding and tolerance are separate decisions.
Does a PDF replace the editable table?
Not automatically. Use it as a reference and confirm the required deliverable formats.
Can ambiguous values be guessed?
Request clarification and preserve the original entry instead of silently converting it.