IT, MARKETING & AI
How to Build a Bilingual Quotation Form for a Malaysian Small Business
Build a quote request in English and BM that produces the same usable answers. Includes sample labels, a branch test and a five-record acceptance sheet.
Little things.
Local knowledge.
plazaclass.

Someone asks your print shop, “Berapa untuk 100 keping?” Your colleague asks for the quantity again because the English version put “100” under budget. The customer already gave the answer. The form lost its meaning between the counter and the person preparing the quote. The fix starts before you translate a single label: decide exactly what a usable request looks like at the receiving end.
Use this worksheet to build a quote request for a fictional neighbourhood printer. The two language versions should give a teammate the same facts about the same job. The form does not promise a price, confirm stock, reserve a production slot or subscribe anyone to promotions. If you are still choosing the software, see our comparison of online form builders for Malaysian businesses. This guide starts where that decision ends.
Begin with the reply you want to write
Write a draft reply to an imaginary order: “Thanks for asking about 100 A5 flyers, printed on both sides, for collection in Bangi. We will check the artwork and confirm whether your requested collection date is possible.” Underline each detail you could not have supplied without asking the customer. Those details become candidate fields. The sentence also reveals what not to promise: a requested date has not been accepted merely because it appears in the reply.
Now give the sentence to someone who estimates jobs. They may need the number of distinct designs, not just the number of sheets. A quote for 100 copies of one design is different from a quote for ten copies of each of ten designs. They may not need a complete delivery address to estimate a collection order. Test each proposed field against a decision somebody will make. If the answer will not change the next reply, leave the field out for now.
Use one dictionary for both languages
| Internal field | English label | Bahasa Malaysia label |
|---|---|---|
| item | What would you like printed? | Apa yang anda ingin cetak? |
| copies | How many copies in total? | Berapa jumlah naskhah yang diperlukan? |
| designs | How many different designs? | Ada berapa rekaan berbeza? |
| sides | One side or both sides? | Cetakan sebelah atau dua belah? |
| need_by | When do you need to receive it? | Bila anda perlu menerima hasil cetakan? |
| fulfilment | Collect or request delivery? | Ambil sendiri atau minta penghantaran? |
| reply_language | Preferred language for our reply | Bahasa pilihan untuk balasan kami |
Give each field a short internal name that does not need translating. On paper, “collect” and “ambil sendiri” mean the same fulfilment choice. They must either arrive as the same value or be explicitly mapped to it before the quote writer filters the queue. If your tool stores the visible label as the value, keep a simple reference list. Do not assume two similar-looking dropdown entries will combine automatically in a spreadsheet.
Set the unit in the question. “Quantity” invites an answer such as “five” without telling you whether that means five boxes, designs, pages or finished copies. Ask for a whole number where appropriate, but decide what to do when someone doesn’t yet know it. A choice such as “I need help estimating” creates an honest follow-up task. A person forced to enter a number may type one to get past the screen, giving you a precise but false quotation request.

Decide how language selection really works
For a short form, paired labels on one page can be easier to maintain than two separate forms. For a longer brief, two versions may be easier to read on a phone. The right choice is the one your team can maintain without creating two different products. If there are two entry links, check that both lead into the same quoting process. A new BM submission should not land in a personal inbox a colleague never opens.
The language used to fill out the form and the language requested for a reply can differ. A daughter might complete an English form on behalf of a parent who wants a BM reply. Ask about that preference rather than inferring it from a name, phone number or postcode. Offer only languages the shop can actually support. A language switch is useful only if the important instructions, choices, error prompts and confirmation message remain intelligible.
Put the fork after the shared questions
All print requests need an item and quantity. Only someone requesting delivery needs an initial delivery area. Ask the shared questions first, then separate collection from delivery. For a quote, a town or postcode may be enough to check coverage; get the full address later when it is needed for an actual order. For collection, show the real collection branch if there is a choice. Do not ask a customer to invent an address to get through the collection path.
Tally’s conditional-logic documentation describes showing or hiding questions according to earlier answers. Other builders may implement this through whole sections. It is fine to use a simple optional “Delivery area, if relevant” field if a branch function is unavailable. Treat the workflow as the requirement, not a particular animation. Always test changing from delivery back to collection: a hidden field must not block submission or silently change what the quote writer sees as the final choice.
Ask for a reply route, not a customer biography
Choose one suitable route for giving the quote, such as an email address or a business messaging number. If both are optional without a requirement to supply either, you can receive an unanswerable request. If both are compulsory, you collect more than you need. A practical design is a preferred-channel question followed by the one matching contact field, or a single required email field if that is the only channel the team monitors.
Introduce the form plainly: “Use this form to request a printing quotation. We will use the details to reply about this request. Sending it does not confirm an order.” Adapt that text to what the business actually does. Avoid requesting identity numbers, banking details, personal family information or unrelated attachments in an initial printing enquiry. If artwork is necessary later, tell the customer which file is needed and where to share it privately. Do not publish response sheets or include the customer’s personal details on a thank-you page.
Read the result as a staff member
Google’s response-storage guide explains how Forms responses can be stored in a linked Sheet. A connected sheet is a destination, not proof that the next person can interpret it. In your practice copy, submit two fictional orders with identical specifications, one in BM and one in English. Hide the language column temporarily and give the two rows to the estimator. Ask them to describe the jobs without looking at the forms.
Look for differences that matter commercially. Does one row say “both sides” while the other says “two designs”? Is the requested date understood as the day to receive the prints in both versions, or as the day to start work in one? Does a pickup request still show a delivery fee as if delivery was chosen? Correct the question or mapping at its source. Do not leave the estimator with a private list of translation errors to remember.

The five-record acceptance sheet
| Practice record | How to fill it out | What must be visible in the queue |
|---|---|---|
| A: English, pickup | One design, 100 A5 flyers, both sides | Collection branch, no delivery-area requirement |
| B: BM, pickup | Same job and requested date as A | Same quantities and meaning; BM reply if selected |
| C: English, delivery | Choose delivery, enter a fictional coverage area | Area shown as a quote request, not a confirmed delivery |
| D: changed choice | Choose delivery, then switch back to collection | Final collection choice wins; former area is ignored |
| E: incomplete | Leave the chosen contact route blank | Clear prompt near the missing field; no unusable request |
Use a form or test copy that cannot trigger messages to real customers. An address such as print-test@example.com is good as text on a worksheet; do not use it as a destination for a message you expect to receive. If testing an actual email flow is necessary, use an inbox the business owns specifically for testing. Separate any practice rows from the live work queue so the morning team does not start quoting imaginary jobs.
Release the form with an owner
Give one named role responsibility for field meanings, translation and the response destination. When the shop adds a new paper size, that person updates both language choices and tests a matching pair of submissions. Keep the previous field meaning in a short change note. Old responses should not suddenly mean something different because somebody reused “Option 3” for a new service.
Before sharing the public link, read the complete journey on a narrow phone screen, using the keyboard if available as well as touch. Check that the submit control is recognisable, the error is beside the correct question and the final message explains what happens next. Only promise a response time the actual shop can honour. A well-built form has done its job when the customer knows what they have requested and a colleague can prepare the next reply without asking them to start again.
Frequently asked questions
Do I need two spreadsheets for two languages?
No. One queue works if both versions use the same field definitions and your tool maps answers consistently. If separate sheets are unavoidable, document where both arrive and who checks each one.
Should the price appear on the confirmation screen?
Only if the business has deliberately built and validated a pricing process for that job. For variable work, confirm receipt and explain the next step instead of displaying a guessed total.
Is a quote request permission for a newsletter?
Treat it as permission to handle the request. If you also offer a newsletter, make that a separate, optional choice with its own explanation.