Can I order 40 pieces? Handling bulk requests on WhatsApp without overpromising
Turn a Salla shopper's bulk or gift request into a clear brief for your team, without inventing stock, a discount, customization or a delivery promise.
Posted by
Related reading
“Will it arrive before the occasion?” Answering delivery-date questions on WhatsApp
Check the product, destination and deadline before answering a time-sensitive delivery question. Includes example replies and a practical staff handoff.
Abandoned cart WhatsApp reminders: a practical guide for online stores
How ecommerce stores can use WhatsApp reminders for abandoned carts with consent, opt-out controls, retries, and useful copy.
AI order tracking for ecommerce: how to verify customers safely
How to answer order-status questions with light verification, privacy limits, and handoff rules.

How should you answer “Can you supply 40 of these?”
Ask for the exact product and option, the quantity, the destination city and the date the customer needs it. Then have your team confirm availability and commercial terms. A product marked available does not prove that 40 matching pieces are ready, and its retail price does not establish a bulk discount.
For a Salla merchant selling office supplies, coffee gifts or event favors, the useful next step is a complete request, not an instant promise. The customer should know which details are confirmed, which are still being checked and who will answer next.
Start with four essential details
- Exact item: the product link and chosen color, size or pack. Clarify whether “40” means individual pieces or packs.
- Quantity: the count for each option. Ask whether all pieces must match, rather than silently substituting another color.
- Destination: the city is enough for an initial feasibility check. Do not request a full address or a list of recipients yet.
- Required date: distinguish arrival from dispatch. If the shopper has a fixed event, record the arrival requirement without promising it.
Ask about wrapping, a printed logo or individual name cards only when the customer requests them or the store actually offers them. Customization is a separate requirement to confirm, not something an assistant should add to make the offer sound better.
| Question | Useful first reply | Staff check |
|---|---|---|
| Are 40 available? | Confirm the exact option and requested count. | Available quantity for that option and whether it can be committed to this order. |
| What is the wholesale price? | Explain the store's documented bulk-order process, if one exists. | Approved price, any discount conditions, delivery charges and quote validity. |
| Can you add our logo? | Record the request without accepting the job. | Whether the service exists, its requirements, cost and lead time. |
Fictional example: 40 coffee gift boxes for an office
This is an invented teaching example, not a customer conversation or recorded TajirTalk output.
Shopper: “I need 40 of the coffee boxes in Riyadh before our office event. Can you give me a better price?”
Useful first reply: “Please send the product link and the date you need the boxes to arrive. Do all 40 need to be the same option? Our team will check the quantity and any bulk pricing before confirming.”
Brief for staff: 40 units of the selected coffee gift box; all the same option; Riyadh; arrival required by the customer's stated date; bulk price requested. Quantity, price and arrival date remain unconfirmed.
Not a useful reply: “Yes, all available, with a special discount and guaranteed delivery.” None of those promises follows from the shopper's message or a normal product listing.
Set up TajirTalk to explain the process, not invent a quote
TajirTalk uses connected product information and merchant-written FAQs for replies. Its agent settings include custom instructions and handoff keywords. These tools can support a clear bulk-request process, but they are not proof of reserved stock or an approved quotation.
- Add a FAQ explaining whether you accept bulk inquiries and what details staff need. If there is no published bulk discount, do not add a percentage.
- Use agent instructions to require staff confirmation for requested quantities, negotiated prices and custom work.
- Consider specific handoff phrases such as “wholesale price,” “corporate gifts,” «سعر جملة» or «هدايا شركات». Test them: a broad word can hand off an ordinary question too early.
- Agree who on the team reviews these conversations. A handoff message does not establish that someone has read it or accepted the request.
Test the exceptions before using this with shoppers
Try one ordinary request and three variations in Arabic and English: a quantity not confirmed in the source, an unsupported discount request, and a deadline your team has not accepted. Check that the answer does not turn a question into a confirmed order.
Also test “I only want one, not a wholesale order.” If a keyword sends that to staff, adjust the rule or keep the handoff and answer it manually. Review the actual conversation rather than assuming a saved setting works as intended.
Count complete inquiries, staff-reviewed quotes and verified orders separately. A handoff is not a sale. Check the confirmed order before counting the request as won.
View TajirTalk on Salla Review current plans and setup requirements before installing.
Related: plan human handoff and answer arrival-date questions.